How to Get Cited by ChatGPT, Google AI Overviews & Perplexity in 2026

Most of what circulates as "GEO strategy" is guesswork that hardened into folklore. Someone published a theory in 2024, it got repeated in a hundred LinkedIn carousels, and it is now sold as a service.

The useful thing about 2026 is that we no longer have to guess about all of it. Google has published direct guidance on optimising for its generative AI features, and OpenAI documents exactly which of its crawlers controls what. Some widely sold tactics are explicitly contradicted by those documents.

This guide separates the two. Everything in the "myths" section is sourced to primary documentation, not opinion.

1. How AI search actually retrieves content

Before optimising for something, it helps to know what it does. The three systems people lump together as "AI search" work differently enough that the distinction changes your priorities.

Google AI Overviews and AI Mode

This is the one with the clearest documentation, and the answer is less exotic than the industry assumes. Google describes its generative features as rooted in its core Search ranking and quality systems. Two mechanics do the work:

• Retrieval-augmented generation (RAG) — the model does not answer from memory. It retrieves current pages using Google's existing ranking systems and generates an answer grounded in them.
• Query fan-out — a single question is expanded into several related queries run concurrently, so the answer draws on a wider set of results than the original phrasing would return.

Query fan-out has a practical consequence that most keyword-led strategies miss: you are not competing for one phrase. You are competing to be a good answer to a cluster of related sub-questions the system generates on its own. That rewards depth across a topic far more than exact-match optimisation of a single page.

ChatGPT search

OpenAI operates a separate crawler for search surfacing, and its documentation is unusually blunt about the consequence of blocking it. More on that in section 3, because it is the single most common own-goal I find in audits.

Perplexity

Perplexity leans heavily on live retrieval and cites sources inline by design — its interface is built around attribution in a way the others are not. In practice this makes it the most sensitive of the three to clean, extractable page structure, because it is pulling specific passages to attribute rather than synthesising a general answer.

2. SEO vs GEO vs AIO vs AEO

Four acronyms, and most of the time three of them describe the same work. Briefly, so we can stop tripping over vocabulary:

My honest position: GEO, AEO and AIO are not separate disciplines with separate playbooks. They are a shift in what the search result looks like. The work that makes you citable is mostly the work that made you rankable, plus a sharper focus on extractability, entity clarity and having something to say that is not already on twenty other pages.

Be suspicious of anyone selling GEO as a wholly new service with wholly new tactics. Ask what specifically differs from good SEO. If the answer is "we add special AI markup", read the next section.

3. Crawler access: the part most sites get wrong

This is the least glamorous section and the highest-impact one. You can write the best page on the internet; if the retrieval crawler cannot fetch it, none of it counts.

The critical distinction — and the one I most often find misconfigured — is between OpenAI's crawlers, because they do different jobs and blocking the wrong one silently removes you from ChatGPT search.

A robots.txt that opts into visibility

If your goal is to be found in AI answers, this is the shape you want. Note the deliberate asymmetry — training and search surfacing are separate decisions:

User-agent: *
Allow: /

# Search surfacing in ChatGPT — required to appear in answers
User-agent: OAI-SearchBot
Allow: /

# Gemini / AI Overviews grounding
User-agent: Google-Extended
Allow: /

User-agent: PerplexityBot
Allow: /

User-agent: ClaudeBot
Allow: /

# Model training — allow or disallow, it is a business decision
# and it does NOT affect search surfacing above
User-agent: GPTBot
Allow: /

Sitemap: https://example.com/sitemap.xml

Two operational notes. OpenAI says robots.txt changes can take roughly 24 hours to register, so do not judge a fix in an afternoon. And ChatGPT-User requests are user-initiated, so they do not always follow standard robots rules — do not use its traffic as evidence your configuration is right.

The other access blocker: JavaScript

Google renders JavaScript. Most AI crawlers largely do not. If your content only exists after a client-side framework boots, a non-rendering crawler receives an effectively empty page.

This is the quiet reason many well-built React, Vue and Angular sites are invisible to AI assistants while ranking perfectly well in Google. Check it directly:

curl -s https://yoursite.com/ | wc -w

If that returns a few dozen words when your page shows two thousand, your content is JavaScript-dependent. Server-side rendering or static generation is the real fix; a meaningful pre-rendered fallback in the HTML is the pragmatic one.

4. Four myths Google has explicitly debunked

Each of these is contradicted by Google's own published guidance on generative AI features. Not inference — direct statements.

Myth 1: "Add an llms.txt file so AI can read your site"

Google states you do not need to create machine-readable files, AI text files, markup or Markdown to appear in Google Search — and that such files will neither harm nor help visibility or rankings, because Google Search ignores them.

Google Search Central, guidance on optimising for generative AI features

That is about as unambiguous as Google gets. llms.txt is a proposed convention, not a standard any major search engine has committed to consuming.

Is it therefore worthless? Not quite, and I want to be precise rather than dismissive: it costs almost nothing, and some non-Google tools do read it. But it should be filed under "cheap experiment", never sold as a ranking factor or presented as the reason a site will appear in AI answers. If an agency's AI-search proposal leads with llms.txt, that tells you how current their information is.

Myth 2: "There is special schema for AI"

Google is direct: structured data is not required for generative AI search, and there is no special schema.org markup you need to add for it.

Keep your structured data. It earns rich results, it clarifies entities, it is good practice. Just stop paying for "AI schema" as a distinct product — it does not exist.

Myth 3: "Chunk your content so AI can parse it"

Google says there is no requirement to break content into tiny pieces for AI to understand it, and that its systems can understand multiple topics on a page and surface the relevant portion.

Note what this does not say. Clear structure still helps — headings, sections, scannable answers. That is good writing, and it helps humans first. What is unnecessary is the artificial fragmentation some tools recommend: shredding a coherent page into disconnected micro-sections for a parser that did not need it.

Myth 4: "Publish variations of pages to catch more AI queries"

Producing near-duplicate pages to target query variants runs into Google's scaled content abuse policy. Query fan-out already expands one question into many — you do not need a page per phrasing, and manufacturing them is a risk rather than a tactic.

5. What actually earns citations

With the myths cleared, here is what the evidence and the guidance actually support.

Information gain — having something that is not already online

Google's guidance repeatedly emphasises unique, non-commodity content with a distinctive perspective — a first-hand review rather than a summary of other reviews.

This is the single hardest and most valuable lever, and it is the reason a generated article summarising ten existing articles rarely gets cited: a system that synthesises sources has no reason to cite a page that is itself a synthesis. Give it something only you have — original data, a documented test, a real client outcome, a photograph of the actual thing, a number nobody else published.

Extractable, quotable passages

Generated answers lift specific passages. Content that is easy to lift gets lifted. In practice:

• Answer the question in the first two sentences under the heading, then elaborate.
• Make headings match real questions rather than keyword fragments.
• Use tables for comparisons — they survive extraction far better than prose describing a comparison.
• Keep each claim self-contained, so a quoted sentence still makes sense without the paragraph around it.

Entity clarity and consistency

AI systems resolve entities before they answer. If your brand, person and business details are inconsistent across your site, your profiles and your listings, you are a fuzzy entity — and fuzzy entities get skipped in favour of unambiguous ones.

• One canonical spelling of the brand and person name, used everywhere.
• Person and Organization schema with sameAs pointing at your real profiles.
• Identical name, address and phone across the site, Google Business Profile and every citation.
• alternateName for the variants people actually type.

Topic authority over single keywords

Because of query fan-out, being the best answer to one phrase is much weaker than being consistently good across a topic. Ranking for a single term does not mean you own the subject — and the fan-out mechanism means the system will ask itself several adjacent questions before answering. Depth across a cluster beats a single optimised page.

Third-party mentions

Retrieval draws on the whole web, not only your domain. Being discussed on sites the system already trusts — industry publications, forums, communities, reputable directories — raises the odds of appearing in an answer that never touches your homepage. Unglamorous, slow, and it works.

Freshness, where freshness matters

RAG exists partly to improve the recency of answers. For anything time-sensitive, visible and accurate dates matter: publication and modified dates in the markup, dates in the copy, and genuine updates rather than a changed timestamp.

Original media

Google's guidance explicitly mentions including high-quality images and video. Original media is also, conveniently, one of the hardest things for a competitor to replicate — a screenshot of your actual dashboard is evidence, a stock photo is decoration.

6. How to measure AI visibility

Measurement has historically been the weakest part of AI-search work — a lot of assertion, very little data. This has improved.

Search Console

Google now points to a Generative AI performance report in Search Console for monitoring how you appear in these features. Whatever else you do, start here — it is first-party data from the source, rather than a third-party tool's estimate.

GA4: treat AI assistants as a channel

Referral traffic from AI assistants arrives with identifiable referrers. Segment it deliberately rather than letting it disappear into Direct or Referral:

• Build an exploration filtered to referrers containing chatgpt.com, perplexity.ai, gemini.google.com, copilot.microsoft.com, claude.ai.
• Watch behaviour, not just volume. Assistant referrals are typically low-volume and high-intent — the visitor has already been pre-qualified by the answer.
• Two caveats worth knowing: Google's own AI Overview clicks are not a separate referrer, and assistant traffic with no referrer at all lands in Direct. Your measured number is a floor, not a total.

Manual prompt testing

Unfashionable but honest: keep a fixed set of 20–50 prompts a real buyer would type, run them monthly across each assistant, and log whether you were mentioned, cited with a link, or absent. Same prompts, same schedule, screenshots kept. Over six months that becomes the only trend data about your own brand that you fully control.

7. The 25-point AI-Ready audit

This is close to the checklist I work through on client audits. Ordered by impact, not effort.

8. Frequently asked questions

Jayant Solanki

AI-Ready SEO, GEO & AIO strategist based in Indore, India, working with eCommerce, local service and global brands across India, the UAE and the US. Ranked a client #1 for a 45,000/month commercial keyword; builds the measurement and automation behind the work.

More about Jayant →