Skip to content

What Is Query Fan-Out (and Why AI Cites Pages That Do Not Rank)

GEO/AEO · intro · 6 min read · last reviewed 2026-08-20

Query fan-out is how AI engines rewrite one prompt into several hidden sub-queries and retrieve each separately. Here is how it works, how to reconstruct your own fan-out footprint, and why Ahrefs found over a third of AI Overview citations skip the top 100 organic results entirely.

TL;DR

  • Query fan-out is the rewriting of one user prompt into several hidden sub-queries, each retrieved separately, then merged into one cited answer.
  • Ahrefs found only about 38% of AI Overview citations came from a page's own top 10 organic results, and roughly 37% of cited URLs were not in the top 100 organic results at all.
  • You can rank number one on the head term and be invisible, or rank nowhere and get cited, because retrieval happens per sub-query, not per head keyword.
  • Specific, narrow content that answers one sub-question outperforms broad content aimed only at the head prompt, because it matches a fan-out sub-query almost verbatim.
How query fan-out works in AI search One buyer prompt, best CNAPP for a fintech, is rewritten into four hidden sub-queries covering vendor list, pricing, Kubernetes coverage and fintech fit. Each is retrieved separately and merged into one cited answer, so winning any single sub-query earns a citation. Best CNAPP for a fintech Vendor list Pricing K8s coverage Fintech fit One answer, citations merged Win a sub-query, win a citation
Figure 2. One buyer prompt is rewritten into four hidden sub-queries, each retrieved separately and merged into one cited answer.

Query fan-out is how AI search engines rewrite one question into several hidden sub-queries, retrieve each separately, then merge the results into a single answer. It is why a page that ranks nowhere for the head keyword can still get cited, and why a page ranked number one can still be invisible. What matters is whether you own a passage that answers one of the hidden sub-queries, not the keyword the buyer actually typed.

What fan-out looks like from the inside

A buyer asks "best CNAPP for a mid-market fintech." The engine does not search that sentence verbatim. It rewrites it into candidate sub-queries: which vendors offer CNAPP, which of those support fintech compliance needs, which have strong Kubernetes runtime coverage, and what pricing looks like at that company size. Each sub-query runs its own retrieval pass. ChatGPT in particular runs a second round per candidate: round one builds the shortlist, round two fetches each vendor individually for pricing, coverage, and reviews. You need to win both rounds. Round one gets you named. Round two decides how you get described.

Google AI Overviews and AI Mode work the same way against Google Search, which is why keyword-rank thinking breaks down so badly on these two surfaces specifically.

This is why keyword-rank thinking breaks

You can rank number one and be invisible. You can rank nowhere and be cited. The old model, that a top-ranking page earns the citation, does not hold once retrieval happens per sub-query instead of per head term.

Ahrefs' analysis of AI Overview citations across roughly 863,000 keywords found only about 38% of cited URLs came from the page's own top 10 organic results, and roughly 37% of cited URLs did not appear in the top 100 organic results for that query at all. In Google's AI Mode specifically, 31% of cited URLs came from organic positions 11 through 100, and another 31% came from beyond position 100. Your organic rank on the head term and your odds of citation are, for a large share of queries, two separate games.

The practical consequence: a page that thoroughly answers one narrow sub-question, "Kubernetes runtime coverage for a fintech-sized CNAPP deployment," has a real shot at citation even with zero rank on "best CNAPP," because that sub-query is a distinct retrieval event the head-term ranking never touches.

How to reconstruct your own fan-out footprint

Different engines expose this differently, and none of them hand you a clean log.

Google AI Mode. Ask it directly: "What sub-questions did you research to answer that?" It is a reconstruction of what it did, not a verbatim log, so treat it as directional rather than exact.

Google AI Overviews. Expand the citation panel, then run the same head query in normal Google search and compare the two citation lists. The gap between them is your fan-out footprint: URLs that show up in the AI Overview but nowhere in the top organic results got there through a sub-query the head-term ranking never surfaces.

ChatGPT and Perplexity. Ask directly for every source used, then push further: "which specific source did each claim come from." Perplexity lists sources by default with per-claim attribution, which makes this the easiest engine to reverse-engineer.

What this means for content strategy

Optimizing only the head prompt while ignoring the fan-out is the single most common wasted effort in a GEO program. Two practical shifts follow.

Write for the sub-question, not just the page title. Every H2 on a page should be a self-contained answer to one narrow question a fan-out pass might generate. A reader, or a retrieval system, arriving at that H2 alone should get a complete answer without needing the rest of the page.

Specificity beats breadth. "Best CNAPP for a Kubernetes-heavy fintech under 500 employees" is worth more coverage effort than "best CNAPP." It has less competition, it matches a real fan-out sub-query almost verbatim, and the mechanism actively rewards content that answers narrow questions over content that gestures at a broad one. Building a prompt universe is how you find which narrow sub-questions your buyers actually generate, instead of guessing.

Fan-out and the freshness myth

Fan-out retrieval does not automatically favor new content. In a large sample of AI Overview citations, the median cited page skewed older than most teams assume, which means a well-structured page from a year ago can still win a sub-query it answers cleanly. Freshness helps, but structure and specificity carry more weight than a recent publish date alone.

Key takeaways

  • Optimizing only the head prompt while ignoring the fan-out is the single most common wasted effort in a GEO program.
  • Reconstruct your fan-out footprint by comparing an AI Overview's citation panel against the same head query's normal organic results; the gap is the fan-out.
  • Write every H2 as a self-contained answer to one narrow sub-question, since that is the unit an engine actually retrieves.
  • Freshness is a weaker lever than most teams assume; structure and specificity carry more weight than a recent publish date alone.

Frequently asked questions

What is query fan-out in AI search?
Query fan-out is when an AI engine rewrites a single user question into multiple hidden sub-queries, retrieves candidate sources for each one separately, then merges the results into one synthesized, cited answer.
Why does AI cite pages that do not rank in Google?
Because AI Overviews and AI Mode retrieve per sub-query rather than per head keyword. Ahrefs found roughly 37% of cited URLs do not appear anywhere in the top 100 organic results for the original query.
How do I see the sub-queries an AI engine generated?
Ask Google AI Mode directly what sub-questions it researched, or compare an AI Overview's citation panel against the same head query run in normal Google search; the URLs that appear only in the AI Overview reveal the fan-out.
Does ChatGPT use query fan-out too?
Yes. ChatGPT rewrites a query into candidate sub-queries to build a shortlist, then runs a second retrieval pass per candidate to fetch pricing, coverage, and review detail for each one.

Related

← All Explainers guides