GEO Strategy: A Four-Layer Framework

A GEO strategy — a generative engine optimization strategy — is a sequence, not a checklist. Retrievability determines whether you can be quoted at all. Question ownership determines what you can be quoted about. Entity clarity determines whether the model knows who is being quoted. Third-party consensus determines whether it recommends you. Work them out of order and the later layers do nothing.

This framework is deliberately small. The tactic lists circulating in this field run to sixty items, most of which are restatements of four ideas. What follows is the four ideas and how to sequence them.

Layer 1: Retrievability

Can the systems that feed each answer engine reach, render and index your content?

This is a technical question with a technical answer, and it is where an uncomfortable share of programmes silently fail. The specific checks:

• Per-agent robots.txt rules. Googlebot, Google-Extended, GPTBot, OAI-SearchBot, ChatGPT-User, PerplexityBot, ClaudeBot and Bingbot are separate agents with separate permissions. Blocking one removes you from one surface completely.
• Rendering. Content that only exists after client-side JavaScript execution is invisible to several crawlers in this set. Server-render anything you want quoted.
• Indexation. Google's AI surfaces draw on Google's index. Pages excluded from it cannot appear in an AI Overview regardless of quality.
• Access controls. Bot mitigation, rate limiting and geo-blocking configured for security frequently exclude AI crawlers as a side effect nobody reviewed.

This layer takes days, not quarters, and there is no partial credit. The current AI crawler landscape covers who is who.

Layer 2: Question Ownership

Which questions do you intend to be the answer to, and does exactly one page own each?

The failure here is subtle. Most sites have content covering their category, and no page that owns a specific question outright. Three articles half-answering "how do you measure AI search revenue" compete with each other for retrieval before they compete with anyone else, and each is a weaker candidate than one consolidated page would be.

The process:

1. Extract the questions buyers actually ask from sales call recordings, support tickets, and the query report in Search Console. Not from a keyword tool alone — tools return phrasings, and answer engines match questions.
2. Cut to twenty to fifty that precede a purchase decision. Volume is secondary; proximity to a buying decision is primary.
3. Assign each question one owning page. Where two pages compete, consolidate and redirect.
4. Rewrite each owning page answer-first: the paragraph under each heading resolves that heading in forty to sixty self-contained words.

Step three is the one teams resist, because deleting content feels like losing. In a retrieval system, consolidation is a gain.

Layer 3: Entity Clarity

Does the model know what kind of thing you are?

Generative systems reason about entities. If your company is described as a "revenue intelligence platform" on your homepage, an "AI marketing agency" in a directory, and a "GEO tool" in a press release, you are three weakly-defined entities rather than one well-defined one. Models resolve that ambiguity by choosing a competitor whose category is obvious.

What to standardise:

• One legal and trading name, used consistently, with former names declared as alternates rather than left scattered.
• One Organization schema block with sameAs links to every profile you control.
• One category sentence — the same words on your site, your profiles, your press and your directory listings.
• Consistent founding date, location and leadership across third-party databases.
• Product nouns that stay stable. Renaming features every two quarters makes you unquotable.

This is unglamorous and it compounds. Entity SEO and knowledge graph optimization are the same work described at different altitudes.

Layer 4: Third-Party Consensus

When a model is asked to recommend, what does the rest of the web say?

This is the layer with the largest effect on evaluative and commercial answers, and the one you control least. Models are appropriately sceptical of self-description: a vendor's own claim about its category leadership is treated as a claim, while three independent sources saying the same thing is treated as established.

The practical method:

1. From your baseline measurement, extract every third-party domain cited across your prompt set.
2. Rank by frequency. Usually four to eight domains account for most citations in a category.
3. For each, determine the mechanism of inclusion — a review profile, a listicle, a directory entry, an analyst note, a community thread, a contributed article.
4. Work the list deliberately over a quarter. Claim profiles, request reviews from real customers, pitch contributed pieces, correct outdated entries.

This is the layer teams cut when budgets tighten, and it is the reason most GEO programmes plateau after the on-site work finishes.

GEO Strategy Sequencing and Timeline

Note the mismatch between effort and effect. The cheapest layer moves fastest; the most expensive moves slowest and matters most. A programme scoped as a one-quarter project will complete layers one and two, report improved impressions, and be judged against a share-of-answer target it was never sequenced to hit.

What to Measure at Each Layer

• Retrievability: pages indexed, crawl coverage per agent, render success rate.
• Question ownership: number of priority questions with a single owning page; impressions on question-shaped queries.
• Entity clarity: accuracy of model descriptions of your company on a fixed prompt set; consistency audit across profiles.
• Consensus: mention rate, citation rate, share of answer, and your presence on the top cited domains.

Report all four. A programme reporting only the last one will look like a failure for its first two quarters, and a programme reporting only the first two will look like a success indefinitely without producing pipeline.

The Three Ways This Framework Goes Wrong

Starting at Layer 2

The most common pattern. A team commissions twenty articles, publishes them, and sees no change in generated answers — because half the site is blocked to one crawler, or because the pages are rendered client-side and never retrieved. Layer one is boring and takes three days, and skipping it invalidates everything downstream.

Treating Layer 4 as PR

Consensus work gets handed to whoever owns communications, who optimises for coverage volume in publications that read well in a board deck. The models cite different sources — review platforms, comparison sites, practitioner communities, documentation-heavy technical blogs. The measurement tells you which ones. Ignoring that list in favour of familiar targets is the most expensive form of activity in this discipline.

Running It Without a Baseline

If you did not measure mention and citation rates before changing anything, you cannot attribute any subsequent change to your work, and neither can anyone auditing your budget. Two hours of manual baselining protects a year of investment. It is skipped roughly as often as it is recommended.

What This Framework Deliberately Excludes

Several popular tactics are absent above, and their absence is the point.

• llms.txt. Cheap, harmless, unadopted as a ranking input by any major engine. Ship it if you like; do not sequence a programme around it. The full argument is here.
• Publishing cadence targets. Retrieval selects passages. A monthly article quota optimises for a unit the system does not evaluate.
• Keyword density and related on-page mechanics. These were proxies for relevance in a lexical retrieval world. Semantic retrieval does not need them and does not reward them.
• Attempts to influence model training. Publishing does not change model weights on any horizon a plan can commit to. What you influence is retrieval.

Anything that promises to shortcut layer four deserves the most scepticism, because layer four is where the difficulty genuinely is. If a tactic claims to produce recommendation-level visibility without changing what independent sources say about you, the claim is either about a surface that does not do evaluative recommendation, or it is wrong.

Connecting the Framework to Revenue

The four layers produce visibility. Visibility is not the outcome, and a programme that reports only mention rate will eventually be asked what it produced. Three connections are worth instrumenting from day one, not retrofitted at review time:

1. Branded search volume. The most reliable downstream signal of uncredited AI exposure. Baseline it against the same date range as your visibility baseline.
2. Self-reported attribution. A single open field on your demo form asking how the buyer heard about you catches assistant referrals that arrive with no referrer and no campaign parameter.
3. Referrer and user-agent classification. Some assistant traffic does identify itself. Segmenting it in analytics turns an invisible channel into a countable one.

None of these is precise. Together they are enough to tell whether the visibility is producing demand, which is the question the framework is ultimately answerable to. Measuring AI search influence on pipeline covers the instrumentation in detail.

Frequently Asked Questions

What is a GEO strategy?

A GEO strategy is a sequenced programme across four layers: making content retrievable by AI systems, owning specific buying questions with single pages, defining your brand as a clear entity, and building corroboration on the third-party sources models cite.

How long does a GEO strategy take to work?

Technical retrievability fixes show within weeks. Content and question ownership show in four to eight weeks. Entity and consensus effects generally take one to four quarters, because they depend on sources outside your control.

What is the first step in generative engine optimization?

Confirm AI crawlers can reach and render your content, then baseline your mention and citation rates on a fixed prompt set before changing anything. Without a baseline, later results are uninterpretable.

How many prompts should a GEO programme track?

Twenty to fifty questions that genuinely precede a purchase decision, sampled multiple times per period. Larger sets dilute attention; smaller sets are too noisy to trend.

Can a GEO strategy work without off-site work?

Partially. On-site work improves whether your passages can be quoted. Whether a model recommends you in an evaluative answer depends heavily on what independent sources say, which on-site work does not address.

Is GEO strategy different for B2B?

The layers are the same, but the weighting shifts. B2B buying questions are lower volume and higher value, the consensus layer leans on review platforms and analyst coverage rather than consumer signals, and shortlist inclusion matters more than click-through.

References

1. https://arxiv.org/abs/2311.09735
2. https://developers.google.com/search/docs/crawling-indexing/google-common-crawlers
3. https://platform.openai.com/docs/bots
4. https://schema.org/Organization