What this prompt does
This prompt designs a Generative Engine Optimization and Answer Engine Optimization strategy — a plan to earn citations in AI Overviews, ChatGPT search, and Perplexity rather than just classic blue-link rankings. It casts the model as a senior GEO/AEO strategist and asks for six prioritized pieces: an llms.txt plan, AI crawler access decisions, passage-level citability structure, E-E-A-T and author signals, entity consistency and internal linking, and a brand-mention plan delivered as a 30-day roadmap.
Four variables ground the strategy. [site] is the property being optimized. [niche] determines which topics the model should help AI engines resolve to your pages. [crawler_stance] drives the GPTBot, ClaudeBot, and PerplexityBot access decisions, including the tradeoffs of allowing or blocking each. [entity] is the author or brand whose E-E-A-T signals get attached across the site. The prompt deliberately leads with passage-level structure, because self-contained, well-headed answers are what models actually quote — far more than any llms.txt tweak. By keeping the roadmap week-by-week with named owners, it also stays executable rather than collapsing into an aspirational wish list.
When to use it
- AI Overviews and Perplexity are eating clicks you used to win and you want to be cited
- You're deciding whether to allow or block AI crawlers and need the tradeoffs spelled out
- You want content restructured into passages a model can lift verbatim
- You need to attach credible author signals to
[entity]across the site - You're planning an llms.txt file and want to know what to surface in it
- You want a week-by-week roadmap with owners instead of a vague "be citable" goal
Example output
You get a 30-day roadmap as a week-by-week table with owners and success signals, built on six components: an llms.txt implementation plan, crawler-access decisions for GPTBot, ClaudeBot, and PerplexityBot with tradeoffs, a content structure for passage-level citability (self-contained answers, clear headings, defined terms), E-E-A-T signals for the named entity, an entity-consistency and internal-linking plan, and a brand-mention and citation-velocity plan.
Pro tips
- Lead with the citability structure; restructuring into self-contained, well-headed answers does more than any llms.txt change
- Be explicit in
[crawler_stance]about which surfaces you'll expose (e.g. allow AI crawlers on docs and blog) so the access decisions match your real policy - Make
[entity]a real, named person or brand so the E-E-A-T signals have something concrete to attach to - Keep
[niche]tight so the entity-consistency and internal-linking advice resolves to focused topic clusters - GEO is fast-moving and partly unmeasurable, so treat citation velocity as a directional signal, not a guaranteed metric
- Decide crawler access deliberately; blocking AI bots protects content but forfeits the citations the rest of the plan chases
