Query fan-out is Google’s own name for what AI Mode does before it answers you. It takes your question, writes a set of related searches of its own, runs them at the same time, and builds one answer out of what comes back.
You type one question. Several searches run. You never see them.
That’s the whole mechanic, and it quietly breaks the thing most SEO reporting is built on. You’re no longer competing for the query you typed into the rank tracker. You’re competing across a handful of questions Google wrote for you, which you cannot see, and which change depending on who is asking.
What Google has actually said
Google introduced the term itself when it launched AI Mode, describing a technique that breaks a question into subtopics and issues a volley of queries on the user’s behalf. The useful part of that description is the admission buried inside it. The search you optimised for is an input to the process, and the contest happens somewhere you can’t see.
What Google has not published is the number of sub-queries, how they are chosen, or which sources survive. You will find all three stated confidently across the industry. Those figures come from vendors inferring from samples, not from Google, and I would not build a strategy on them.
What’s safe to work from is narrower, and still useful:
- The question is decomposed before anything is retrieved.
- The sub-queries are resolved against Google’s index, so existing rankings matter.
- The answer is assembled from passages, not whole pages.
- You cannot see any of it from the outside.
Why one page per keyword stopped working
The old model was clean. One page, one primary query, one position, one click. You could draw a straight line from the phrase to the money.
Fan-out puts a layer in the middle. Somebody asks whether they need a GEO agency. Google turns that into questions about what a GEO agency does, what it costs, how it differs from SEO, whether it can be done in-house, and how long it takes. Your page is now judged against five questions when you wrote it to answer one.
A page built to rank for one phrase will often satisfy exactly one of those sub-queries and get dropped from the rest. A page that covers the cluster properly can survive several.
This is why we stopped planning content around keyword lists and started planning it around question clusters. Same research, different unit.
How to reconstruct the fan-out for your own queries
You can’t see the sub-queries, so you approximate them. This takes about twenty minutes per query cluster, and it’s the most useful hour of GEO work most businesses aren’t doing.
Ask the question properly. Put your real commercial query into AI Mode, then into ChatGPT, then into Perplexity. Do not read the answer for whether you appear. Read it for what it resolves. Every answer silently settles a set of sub-questions: the definition, the comparison, the price, the timeline, the risk, the alternative, who it is not for.
Write those sub-questions down. That list is your approximate fan-out. Three assistants will produce an overlapping set, and the overlap is the reliable part.
Check it against Search Console. Filter to the page you care about and read the long-tail queries already reaching it. Those are real questions from real people, and they tend to confirm or correct your guesses.
Then find the ones you answer badly. Not the ones you miss entirely. The ones where your page has a sentence that technically addresses the question and would never be chosen as the answer.
One caution on the Search Console step, because it has cost us real analysis time. A large share of the queries in there are not human. We built a classifier to separate machine-generated query patterns from genuine human searches on our own data, and the difference it makes to the picture is substantial. If you skip that, you will plan content around questions nobody asked.
What to change on the page
Fan-out rewards pages that can be taken apart. Most pages cannot.
Make each section answer one question completely. If a section only makes sense after the section above it, it cannot be lifted out, and lifting out is the entire retrieval step. Write each part so a stranger could read it cold.
Use headings that state the question. A heading is the strongest signal of what a passage answers, and it travels with the passage when it is extracted. “How long it takes” beats “Timeline”. “Why ChatGPT ignores most local businesses” beats “Local considerations”.
Answer first, then explain. The direct answer in the first sentence or two of a section, the reasoning after. A section that builds to its answer in the last paragraph has buried the only part that would get quoted.
Cover the uncomfortable sub-queries. Price, limitations, who should not buy, what the competition does better. These are a large share of real fan-out and most commercial pages dodge all four. A page that answers them is eligible for questions your competitors have excluded themselves from.
Keep the organic foundations. Schema, internal links, crawlability, speed. The sub-queries run against Google’s index, so a page that cannot be crawled or has no business ranking is not in the running whatever its prose does.
The mistake that makes it worse
The obvious move once you understand fan-out is to build a page for every sub-query you found. It’s the wrong move, and it’s the one I’d most want to talk somebody out of.
Thin pages split authority between near-identical URLs, and every one of them consumes crawl budget. We measured our own site wasting a sixth of its crawl requests on redirects, errors and blocked URLs, and in the middle of that a substantial new article sat uncrawled for three weeks with three internal links pointing at it. Google had simply not got to it. Adding forty more pages would not have helped.
One page that answers the cluster beats ten that answer fragments. If a sub-query genuinely deserves its own page, it is because it has its own audience and its own buying question, not because it appeared in a list you generated.
What this does not fix
Fan-out explains retrieval. It does not explain selection, and the gap between the two is where most GEO promises quietly live.
Surviving the sub-queries makes you eligible. Which of the eligible sources gets named, and whether it gets attributed with a link or paraphrased without one, depends on corroboration accumulating on sources the models already trust. That’s slow, and it sits outside the page. No amount of heading discipline compels a model to quote you.
The honest position is that this work moves you from invisible to eligible, reliably and fairly quickly. The step from eligible to cited takes months and depends on third parties.
Where to start
Pick your single most commercially important query. Reconstruct its fan-out with the three assistants, cross-check it against Search Console, and find the two sub-questions your page answers worst. Fix those two properly on the page you already have.
Do that before you write anything new. Most sites already own the page that should be winning.