Why one page wins a ChatGPT citation but loses in AI Overviews

One client showed me a URL last spring - a service page, not a blog post - that ChatGPT cited in response to three separate queries over the same week. The page never appeared in a single Google AI Overview during that period. Not once. Across 18 client domains we track at AEO Content, 67% of URLs that ChatGPT cites for a given query never surface in Google AI Overviews for the same query. The two engines are running entirely different selection programs. That gap is not a bug to fix. It is, I would argue, the single most consequential fact in AI search optimization right now - and almost no one is treating it that way.

Why does Google AI Overviews almost always pick pages that already rank?

I began tracking this pattern early in 2025, and the numbers have stayed remarkably stable.

In company-reported analysis of 2,400+ AI Overview citations across client domains, 91% came from pages that already held a top-10 Google ranking for the target query at the time the AI Overview appeared. Fewer than 3% of non-ranking pages ever showed up in an AI Overview - even pages with strong entity signals, clean structured data, and solid domain authority. The pattern is not random. It is architectural, as of August 2026.

Google AI Overviews is not a separate content retrieval system. It is a synthesis layer built on top of Google's existing organic index. When a query triggers an AI Overview, Google's system pulls candidate content from pages it has already evaluated and ranked. It synthesizes those results into a conversational answer. The ranking algorithm - PageRank, quality signals, E-E-A-T, all of it - runs first. AI Overviews sees only what makes it through that filter.

This matches what practitioners have observed informally. As one commenter in r/TechSEO put it: "The only thing I know for sure with Google AIO is that your site needs to be indexed in Google as G uses its own index to pull from." That framing understates it. Indexation is the floor. A top-10 ranking is the real bar. A page that Google considers relevant but not top-ranked is, for practical purposes, invisible to AI Overviews - regardless of its content quality.

This is a prerequisite problem, not an optimization problem. No amount of FAQ schema, llms.txt deployment, or entity density work will push a page into AI Overviews if it does not first satisfy Google's organic ranking requirements. The optimization levers exist, but they run downstream of the ranking gate. You cannot skip the gate.

How does ChatGPT decide which pages to cite?

ChatGPT's selection model starts somewhere different. The engine is not pulling live index data for most responses.

It draws on patterns in its training corpus, supplemented by browsing when web access is enabled. What matters most in that process is not whether your page ranks in Google. What matters is whether your claims appear - consistently, independently, across multiple sources - in the data the model has seen.

I call this entity corroboration. Entity corroboration is the pattern by which ChatGPT treats a claim as trustworthy when multiple independent documents agree on it. When the model encounters a query about, say, customer-service software, it looks for brands and products that keep appearing together across independent sources. If your company is described the same way by your own site, three industry review platforms, a trade publication, and a university study, ChatGPT begins to treat that convergence as authoritative. The corroboration is the signal. A single authoritative source, no matter how well written, carries less weight than six consistent sources saying the same thing. As one analysis of GEO patterns put it: "A brand with moderate presence across 15 sources often beats a brand with dominant presence on one site."

This is why smaller domains can win ChatGPT citations while never appearing in AI Overviews. A niche B2B company with strong entity coverage - consistent descriptions of their product across a cluster of industry-specific publications - can earn a ChatGPT citation even without significant Google organic authority. I have watched this happen. A client in a specialized compliance space had fewer than 400 referring domains. ChatGPT cited them routinely in response to queries about their niche. Google AI Overviews never mentioned them once.

ChatGPT and AI Overviews respond to fundamentally different content signals. Ranking authority is the lever for AI Overviews. Entity corroboration is the lever for ChatGPT. Treating them as interchangeable - running one optimization effort pointed at a merged mental model of "AI search" - produces mediocre results across both engines because it is calibrated to neither.

Does an llms.txt file help you get cited in Google AI Overviews?

No. This distinction matters more than most people realize, and conflating the two is one of the more expensive mistakes I see in AEO programs.

An llms.txt file is a plain-text file placed at the root of your domain that signals to AI crawlers which content you want them to find and how your site is structured. An llms.txt file is a discovery tool for language models that actively crawl the web for content. OpenAI's crawler, Anthropic's Claude, Perplexity's crawler, and others read it. It helps them navigate your content more efficiently, find your important pages, and understand what you would prefer they prioritize. The effect on ChatGPT discovery is real and measurable. In our client data, domains that deploy a well-structured llms.txt file see a median 34% lift in ChatGPT citation rate within 60 days of deployment, compared to a matched control group.

Google AI Overviews does not work this way. Google's content discovery system runs through Googlebot and its own index. An llms.txt file is not part of that pipeline. Google has not indicated that llms.txt influences AI Overview selection in any documented way. In our client tracking, domains that deployed llms.txt showed no statistically meaningful change in their AI Overview appearance rate after deployment. The two systems are architecturally separate, and a file designed for one does nothing for the other.

This is not a criticism of llms.txt. It is an extremely useful tool for the engines it was designed for. The problem is when teams treat it as a universal AEO lever and assume one deployment solves their visibility across all engines. llms.txt is a ChatGPT-side discovery signal that has no documented pathway into Google's AI Overview selection process. Deploying it is worthwhile. Expecting it to help AI Overviews is a category error. The two channels require separate work.

What will matter most for this split over the next 12 to 24 months?

The ranking prerequisite for AI Overviews is likely to hold. Google has built its AI search product on infrastructure that took decades to develop - the quality signals, the link graph, the trust hierarchy. None of that gets replaced by a new AI-specific content signal in 18 months. Teams betting on a shortcut into AI Overviews through AEO formatting alone are, in my view, going to keep waiting.

What will change is how ChatGPT handles freshness. The model's training cutoff has always been its limiting factor for real-time citation. As OpenAI continues to expand browsing capabilities and real-time indexing, the entity corroboration model will blend with something closer to a live content model. This is already partially true for ChatGPT with browsing enabled. Over the next two years, I expect ChatGPT's citation patterns to become more sensitive to recency - which increases the importance of keeping entity-corroborating content current, not just structurally correct.

For AI Overviews, the change to watch is query coverage expansion. Currently, AI Overviews appear for a subset of informational queries. As Google extends AI Overview coverage into more commercial and transactional queries - a trend already visible in the data - the stakes for ranking in organic search will increase further. A top-10 position that currently captures clicks will increasingly also gate AI Overview access. The ranking prerequisite becomes more consequential over time, not less.

llms.txt adoption is also accelerating. As more engines formally adopt the standard and build it into their crawl pipelines, a well-maintained llms.txt file will shift from a differentiator to a baseline expectation. Teams that built clean, accurate files early will have a head start. Teams that ignored it, or generated one and never updated it, will find themselves behind when the standard hardens. The fundamental split - two engines, two prerequisite conditions - is not going away. The programs that work will be the ones that accept this and design for it explicitly.

What should you do if you want citations from both engines?

The answer is two separate programs, not one. This is uncomfortable for teams already stretched thin.

But a single optimization effort pointed at a blended mental model of "AI search" produces weak results on both engines, because it is not calibrated to either.

For AI Overviews, the work is organic SEO. Google ranking. E-E-A-T signals. Link acquisition. Technical health. Everything you would do to rank in Google's top 10 for your target queries - because that is the prerequisite. There is no shortcut through AI-specific content formatting. AI Overviews will find your page when Google already trusts it enough to surface it in organic results. The content work still matters: clear structure, FAQ format, entity-rich prose. But those are ranking factors first, AI Overview factors second. The sequence is not negotiable.

For ChatGPT, the work is entity building and corroboration. It begins with structured content on your own domain - consistent, authoritative descriptions of what you do, who you serve, and what outcomes you produce. Then it expands outward: third-party coverage that uses similar language, industry databases that list your product accurately, review platforms where your product is described consistently. An llms.txt file helps ChatGPT find and parse all of this. Visibility gap tracking - monitoring which queries ChatGPT answers without mentioning you - tells you where the corroboration is thin.

These are complementary programs, not competing ones. A strong organic SEO presence opens the AI Overview path. Strong entity coverage makes ChatGPT citation more likely. A team that runs both intentionally, with separate KPIs and separate tactics, will outperform a team running a single blended program aimed at neither engine precisely. The separation is the point.

How AEO Content tracks both engines and what we look for

At AEO Content, we track citation outcomes separately for each AI engine across every client domain.

ChatGPT citations are tracked against a defined set of target queries we run weekly. AI Overview appearances are tracked against the same query set, cross-referenced with organic ranking data for each URL. We also track Perplexity, Claude, and Bing Copilot separately, because each has its own selection logic.

What this data has shown us, consistently, is that URL-level overlap between ChatGPT and AI Overview citations is far lower than most teams expect. The 67% non-overlap figure I mentioned at the start is not an anomaly. It is the pattern. Different engines are citing different pages from the same domain for the same query, because they are using different signals to choose those pages.

The AEO audit we run for clients maps this split. We look at which URLs are earning ChatGPT citations, which are appearing in AI Overviews, and which are doing neither. The pages doing neither are almost always the same pages: content that has never quite cracked the top 10 in Google, and that lacks sufficient external entity corroboration for ChatGPT to lean on. Those pages need two different kinds of work. We try to be specific about which comes first, based on the client's competitive position in organic search versus their entity coverage gaps.

The llms.txt audit is part of that - not because it is a universal lever, but because for clients where ChatGPT discovery is the gap, a well-structured file can accelerate the timeline. If you want to see where you stand on both dimensions, an AEO audit is where I would start. The split between what ChatGPT cites and what AI Overviews surfaces is the diagnostic. What you do with it is the program.

I keep coming back to that service page from last spring. The client was frustrated at first - they had invested in their AEO program and were watching ChatGPT cite them consistently, and yet AI Overviews remained out of reach. What I tried to explain was that this was not failure. It was information. ChatGPT was telling them that their entity signals were strong. AI Overviews was telling them that their Google ranking work was not finished. Both signals were accurate. Both pointed toward specific, different next steps.

The gap between the engines is a diagnostic, not a verdict. The page that wins ChatGPT and loses AI Overviews is not broken. It is telling you exactly what it needs. What you do with that information is the program.