Search the published literature for a study showing that pillar-and-spoke architecture makes an AI engine more likely to cite you, and you will not find one. The claim is everywhere in GEO advice and rests on nothing measured in public. Google's own documentation points the other way, stating that there are no additional requirements or special optimizations to appear in AI Overviews and AI Mode, and no new machine readable files or markup are needed. The defensible case for topic clusters is smaller: clustering is a planning discipline that produces question coverage and a consistent entity description, and while neither guarantees a citation, coverage at least addresses the queries a documented fan-out issues.
The reason to care is where buying now starts. 51% of software buyers now start research with an AI chatbot more often than with Google, G2 found AI chatbots and review sites are now the two biggest influences on B2B shortlists, and 6sense found the average buying-group member knows 75% of the vendors on the shortlist by the time it is filled. Owning a territory means being present when those questions get asked.
Do AI engines reward pillar pages and topic clusters?
No published study supports that, and the strongest evidence on content tactics generally is unflattering. C-SEO Bench, published at NeurIPS 2025, tested ten conversational-SEO methods and found most of them largely ineffective and often harmful to citation rank, and the benchmark ran across two tasks and six domains. Rewriting pages mostly did nothing, and site structure was never tested.
Google's guidance has the same shape. It asks for helpful, reliable, people-first content, and its AI features documentation states that AI Overviews and AI Mode use a query fan-out technique. Google's AI Mode announcement and updates from I/O 2025 cover the same feature set. Nothing in either says a hub page scores higher than a single page that answers the question well.
So drop the authority story. What survives is a checklist that stops you leaving buyer questions unanswered, and one description of your company on every page.
What does a cluster actually do for retrieval?
It changes what there is to retrieve. Google documents a query fan-out technique for its AI features, and OpenAI documents that ChatGPT search turns a conversation into one or more targeted queries. Each of those queries is answered by a passage on some page, which may or may not be yours. Neither company documents a preference for site architecture.
Position inside a document matters too. Liu et al. showed that models use long contexts unevenly, with relevant text buried in the middle used less reliably than text near the edges. A dedicated page that answers one question in its first screen beats the same answer at paragraph 40 of a 3,000-word overview.
The second input is identity. An audit of 443 entity-oriented retrieval configurations on a TREC newswire test collection found that once entity selection was kept independent of the relevance judgments used for evaluation, none of its 437 unsupervised configurations beat a BM25 baseline of 0.292 MAP. Consistent naming is hygiene rather than a retrieval lever: three pages describing your company three different ways make resolution harder and buy nothing for it.
How do you choose the territory worth covering?
Start from the decisions a buyer has to make before choosing, not from a keyword export. Write down the five to fifteen questions in your category that a real evaluation forces: what the category is for, what the alternatives are, what it costs, what breaks, what it connects to, who it is wrong for. That list is your territory.
Then check who currently answers each one. Profound found more than 4 in 10 AI citations point to sources brands do not control, so for some questions the answer already lives on a publisher's page or forum thread a new page will not displace. Seer found 87% of SearchGPT citations matched Bing's top results in a sample of 500, which makes the contest for a passage the existing top of search.
Where a third party owns the answer, the work changes. AirOps' March 2026 analysis of 548,534 pages ChatGPT retrieved found only 15% were cited in the final answer, and G2's research reports that a third of buyers said an AI chatbot led them to choose a vendor they hadn't considered. A question whose answer sits on somebody else's property is not a page you can commission; it is presence you have to earn.
An absence is a finding. It becomes an assignment only when you can answer the question with evidence. Some gaps describe a buyer you do not serve, and the right response is no page at all.
How do you decide which questions deserve their own page?
Give a question its own page when a buyer would ask it separately and the answer needs evidence of its own. Consolidate when two questions share the same evidence and the same decision.
Whatever you publish has to carry proof. The GEO study published at KDD 2024 found that adding statistics, quotations and citations raised citation visibility in its benchmark while keyword stuffing did not, and scarcity and exclusivity framing measurably reduces how often a model recommends a product. Sales language on a cluster page is a cost, not a neutral choice.
Page count on its own is a weak bet, and the two things it buys come apart under measurement. 38% of AI Overview citations rank in the organic top 10 across 4 million AI Overview URLs, so ranking and being cited are different outcomes rather than one prize. Separately, the top-ranking page now sees a 58% lower average clickthrough rate when an AI Overview is present. Publishing more spokes buys neither result by itself.
How do you keep your entity description consistent across a cluster?
Write the description once and reuse it without edits. One sentence for what the company is, one for the category, one for who it is built for, and identical product names in identical casing on every page.
Say the same facts in markup. Schema.org's getting started documentation and Google's explanation of structured data define types for organization, product and FAQ facts, and the types Google Search supports are published in full. No published study we could find shows markup changing what an AI engine cites.
Then confirm a machine can read any of it. Vercel's crawler research with MERJ documented that OpenAI's and Anthropic's crawlers do not render JavaScript, while Google's Gemini leverages Googlebot's infrastructure, which does. Cloudflare's scan of the 200,000 most visited domains found the standards agents use thinly adopted: 4% of sites declared AI usage preferences in robots.txt, and 3.9% served Markdown to agents that asked for it. A cluster rendered client side is an empty shell to every crawler in the first group.
How do you build and link the first cluster?
Once the question list is written and run, take three adjacent questions, give each a page that carries its own evidence, and link every page to at least two others in the set. 6sense found nearly four out of five competitors are named to the shortlist on day one, so the questions that decide a shortlist get asked early; build those first.
Links are how a crawler reaches a new page at all. Google publishes an overview of its crawlers and user agents and OpenAI documents four relevant user agents; neither documents internal linking as a citation input. Google's stated conditions for its AI features are that a page be indexed and snippet-eligible.
Put each link where the reader reaches the edge of what this page answers, and make the anchor the question on the other side: "How to price an annual contract" rather than "read more." No source we found shows anchor text changing retrieval.
How do you tell whether the territory is actually covered?
Measure appearance per question across repeated runs, never once. SparkToro and Gumshoe tested how consistently AI engines recommend brands and found them highly inconsistent, and Search Engine Land's write-up of the same study reports that AI recommendation lists rarely repeat exactly.
A 2026 variance-components study found run-to-run noise large enough to swamp real differences in small samples, and work on quantifying uncertainty in AI visibility argues for confidence intervals instead of point readings. Neither paper sets a run count. Several weeks of answers per question, across phrasings and engines, is the floor we use before calling a question covered or missing.
Report it question by question. The IAB framework separates presence, prominence, portrayal and persuasion, which are different outcomes with different fixes. A territory with eight of twelve questions answered and four absent gives you a work list; a single composite score hides which four.
How does Trovance help you own a question territory?
Trovance treats the territory as a set of tracked questions rather than a content calendar. You define the questions your buyers ask before choosing, and the platform runs them repeatedly across AI engines, preserving each answer run as a snapshot that records who was mentioned, who was cited, who was recommended, and which sources carried the answer. Share of answer is then reported per question, so you can see which parts of the territory are answered without you.
That record separates the two problems a cluster is supposed to solve. A question where competitors appear and you do not is a coverage gap, and the snapshots show whether the winning answer was built on the competitor's own page or on a third-party source you would have to earn. A question where the answer describes your company inaccurately is an entity problem, and your Brand Core holds the claims you are entitled to make, the proof behind each one, and the description that every page in the territory should reuse.
From there the work becomes specific. Recommended actions name the asset the evidence record says is missing, drafts are produced from approved claims rather than from a topic prompt, and a person reviews everything before it publishes. After a page goes live, the next analysis cycle reruns the same tracked questions so you can compare answers against the ones you preserved and see whether coverage moved.
Trovance will not tell you that a pillar-and-spoke structure causes citations, because no published evidence we could find supports that. It does not promise guaranteed citations, rankings or recommendations, it does not produce a universal visibility score, and it does not publish without human approval. What it offers is a durable record of what the engines said about your territory over time, and honest attribution of what changed after you acted.
What should you do this week?
Write the question list first, before any page. Twelve questions your buyers actually ask, in their words, with a note on who answers each one today. That single document does more for coverage than a diagram of hubs and spokes.
Then ask each question in two or three phrasings on at least two engines, every week, and record appearance and sources. Fix the mechanical failures the runs expose: pages an AI crawler cannot read, product names that vary across the set, claims with no evidence attached. Only then commission new pages, one per question that needs evidence of its own.
Be honest about pace. Retrieval fixes show up only when engines next fetch the page, earned third-party presence takes longer, and early readings will wobble either way. If you want the question list run continuously instead of by hand, start a free Trovance trial and watch coverage question by question.
Plan the territory
A visibility gap is not a content brief - why an absence does not automatically justify a page.
How to run an AI citation gap analysis - finding the questions you are missing from.
Can likely buyer questions improve AI retrieval? - what the evidence says about predicted questions.
The prompt panel is measuring the wrong question - how to choose the questions you track.
Make each page usable
A named entity is not a retrieval signal - why a name is not the same as being resolved.
Do headings help AI retrieve long documents? - what structure does and does not do inside a page.
A relevant page can still miss the proof - relevance without evidence loses the passage.
The most-quoted study in AI search, quoted correctly - what the GEO benchmark actually tested.
