Two things happened this year that quietly broke the old playbook. In January 2026, Google made Gemini 3 the default model behind AI Overviews, deepening the query fan-out that splits a single search into a cluster of related sub-searches. Then Ahrefs re-ran its citation study across 863,000 keyword SERPs and found that only 38% of cited pages still rank in the top 10 for the query they were cited on — down from 76% a year earlier. Ranking first no longer buys you a citation. Here is what does.
| Quick answer: Earn AI Overview citations by covering every sub-question Google’s fan-out generates, answering each one in a self-contained 40-to-60-word block under a plain question heading, keeping the page indexed and snippet-eligible, and building enough depth across the surrounding cluster that your site is the obvious source for the whole topic. |
| How we compare: we test tactics on our own library before we publish them, track citations weekly across a fixed set of seed queries, and check every claim here against Google’s published documentation or a large-sample independent study — never a single agency case study. Affiliate disclosure: some tool links on TechieHub are affiliate links. We may earn a commission at no extra cost to you, and no vendor pays for placement or a favourable verdict. |
Table of Contents
What are Google AI Overviews, and what changed in 2026?
AI Overviews are the generated answers that sit above the organic results, synthesised from multiple pages that Google then cites as clickable links. They began life as the Search Generative Experience; they now reach over a billion people and hand off into AI Mode for follow-up questions.
The mechanic that matters is query fan-out. Rather than matching your page to one query, Gemini 3 issues a spread of related sub-searches concurrently — definitions, comparisons, edge cases, pricing — and assembles the answer from whatever performs best across that spread. You are no longer competing for a keyword. You are competing for coverage of a question cluster, which is exactly the logic behind generative engine optimization.
Why doesn’t ranking first guarantee a citation?
Because the retrieval that feeds an Overview is no longer the ten blue links. Ahrefs analysed 4 million AI Overview URLs across 863,000 keyword SERPs and found the citations split almost into thirds: 38% of cited pages rank in the top 10, 31.2% rank somewhere between positions 11 and 100, and 31.0% do not appear in the top 100 at all. The equivalent top-10 figure in July 2025 was 76%.
Read that carefully, because Ahrefs is honest about the caveat: its citation parsing improved between the two studies, so the datasets are not strictly comparable, and part of the drop is measurement rather than movement. But the direction is unambiguous, and fan-out explains it. A page ranking 40th for the head term can still be the single best answer to sub-query seven — and that is enough to get quoted.
The traffic maths has shifted too. Pew Research Center tracked 68,879 real searches from 900 US adults and found users clicked a traditional result on 8% of searches with an AI summary versus 15% without, and clicked a link inside the summary on just 1% of visits. Citation is now a brand-visibility play as much as a traffic one, which is the same argument we make in our guide to answer engine optimization.
How to rank in Google AI Overviews: a seven-step method
The method below follows the retrieval in order: work out which questions Google will ask on your behalf, then make each answer easy to lift out intact. None of it is a trick, and Google’s own guidance is explicit that no special markup exists — this is simply what “genuinely good, genuinely structured coverage” looks like in practice.
Step 1: Map the fan-out before you write anything
Google no longer answers your query — it decomposes it. Before drafting, collect the sub-questions it will generate: the People Also Ask box, the “related” chips on an existing Overview, and the follow-ups AI Mode offers when you prompt it conversationally. Search Console’s query report adds the long-tail phrasings real users bring. Write that list down first. It is the specification for the page, and most pages fail here rather than at the writing stage — they answer the head term thoroughly and six of its eight sub-questions not at all.
Step 2: Give every sub-question its own question-shaped heading
Each sub-question earns an H2 or H3 phrased the way a person would ask it, not as a noun phrase. “How much does it cost?” beats “Pricing.” This is not a styling preference: the retrieval step matches a sub-query against passages, and a heading written as a question makes the match obvious rather than inferred. It also produces the scannable structure that wins featured snippets and People Also Ask, which is why those two remain the most reliable leading indicator you have.
Step 3: Answer in a self-contained 40-to-60 word block
Directly beneath each question heading, answer it completely in roughly 40 to 60 words, then expand underneath. The constraint that matters is self-containment: no “as we saw above”, no “this approach”, no pronoun whose antecedent is two paragraphs back. A passage gets lifted out of its page and dropped into a summary alone, so any sentence that depends on its neighbours to make sense is a sentence that cannot be quoted.
Step 4: Front-load specifics a summary can actually carry
Generative summaries extract facts, not adjectives. Numbers, dates, prices, version names, named entities and explicit trade-offs survive the compression; “powerful”, “seamless” and “industry-leading” do not. Where a figure is contested or moving, say so and date it — a model reproducing your sentence carries the caveat with it, and a hedged accurate claim outlives a confident stale one. This is the single biggest difference between pages that get quoted and pages that merely rank.
Step 5: Keep the page technically eligible
Nothing above matters if the page cannot be used. It must be indexed, and it must be snippet-eligible: nosnippet, data-nosnippet and a restrictive max-snippet all remove you from consideration, and plenty of sites carry them by accident from an old template. Content injected client-side may not survive rendering. Check the live URL in Search Console rather than assuming, because this failure is silent — you simply never appear, with nothing in any report to explain why.
Step 6: Bring evidence a model cannot synthesise
When ten pages say the same correct thing, the tiebreak is what only you have: original testing, first-party data, a documented methodology, named authorship with real credentials. A model can paraphrase consensus from anywhere, so consensus earns no citation. Screenshots, dated results and a stated sample size give a summary something specific to attribute — and attribution is the mechanism by which your name appears at all. Our answer engine optimisation tools roundup covers the tracking side of this.
Step 7: Build the cluster, not the page
Single pages rarely own a topic. Fan-out spreads one search across many sub-questions, and a site with genuine depth across all of them becomes the obvious source for several at once rather than a lucky match for one. Interlink the cluster with descriptive anchors so the relationships are explicit. This is the same compounding logic behind large language model optimisation, and it applies equally to Perplexity and the other answer engines — the work transfers, which is what makes it worth doing.
What does Google officially tell you to ignore?
This is the most useful and least-read document in the field. Google’s official AI optimization guide states plainly that there are no additional requirements to appear in AI Overviews or AI Mode and no special optimisations necessary, because the generative features are rooted in core Search ranking systems. It then names four things you can safely ignore: publishing an llms.txt file or other “special” markup, chunking content into tiny fragments, rewriting pages purely for AI systems, and chasing inauthentic mentions.
Structured data is the nuance people get wrong. Google does not require it for AI features, so it is not a citation cheat code — but it still earns rich results and still describes your entities unambiguously, which is why it stays in our LLMEO checklist. Use it because it is correct, not because you think it buys you a quote.
How do AI Overviews compare with other answer surfaces?
| Surface | What decides whether you are cited | Where you verify it |
| Google AI Overviews | Gemini 3 fan-out across sub-queries; page must be indexed and snippet-eligible | Search Console generative AI report plus manual SERP checks |
| Google AI Mode | Same index, deeper fan-out, longer conversational chains | Manual prompting; impressions land in the same report |
| ChatGPT search | Its own retrieval layer plus whatever the model absorbed in training | Referral traffic and repeated manual prompts |
| Claude with web search | Live retrieval; Opus 5 tends to quote sources with explicit dates and figures | Manual prompts; referrals are sparse but high-intent |
| Perplexity | Live retrieval with a numbered citation attached to nearly every claim | Referral traffic and manual prompts |
Case study: how one founder earned three citations
Astrid Nilsen runs a two-person payroll-software comparison site. Her task was blunt: her best page ranked fourth for “payroll software for small business” and had never once been cited. We mapped the fan-out and got fourteen sub-questions — pricing tiers, contractor payments, multi-state filing, migration from spreadsheets — of which her 2,400-word page properly answered four.
She did not write a longer page. She restructured the existing one into eleven question headings, each opening with a self-contained answer, and moved three sub-questions into their own spoke articles linked from the pillar. She also added her own dated pricing table, gathered from real vendor invoices.
Six weeks later she was cited in AI Overviews for three of the fourteen sub-queries — none of them the head term she had been chasing for two years. Sessions barely moved. Demo requests rose noticeably, because the people who did click had already read her answer and arrived pre-qualified.
This example is a composite of the citation-earning projects we see most often, not a single client account; the figures are typical rather than measured from one engagement.
How do you measure AI Overview visibility?
You finally have first-party data. In June 2026 Google launched Search generative AI performance reports in Search Console, giving dedicated impression views for AI Overviews and AI Mode, broken out by page, country, device and date. The limits are real: impressions only, with no clicks, CTR or query data yet, and a phased rollout that has not reached every property.
So triangulate. Spot-check your priority queries by hand each month and log whether you appear. Watch featured snippets and People Also Ask as leading indicators, since the same extractable structure feeds all three. Third-party trackers automate the sampling if the budget exists, but treat every vendor’s “visibility score” as directional rather than truth.
Frequently Asked Questions
Can I pay to appear in Google AI Overviews?
No. There is no paid placement, submission form or priority queue for AI Overview citations. Google selects sources from its organic index, so anyone selling guaranteed inclusion is selling something they cannot deliver. Ads may appear near an Overview, but they are labelled separately and are not citations.
Do I need schema markup to rank in AI Overviews?
Not strictly. Google’s own guidance says structured data is not required for AI features, and over-focusing on it is listed as a low-value tactic. It still earns rich results and clarifies your entities, so keep accurate markup in place — just stop treating it as the lever that produces citations.
How long does it take to get cited in an AI Overview?
Expect four to twelve weeks after a substantial restructure, assuming the page is already indexed and ranking somewhere. Citations also churn: pages appear, vanish and return as Google re-runs its fan-out. Judge progress over a rolling quarter, not week to week, and log appearances rather than trusting memory.
Do AI Overviews destroy my organic traffic?
They reduce it on affected queries. Pew’s tracked-browsing data found clicks on traditional results fell from 15% to 8% of searches when an AI summary appeared. The realistic response is to accept fewer, better-qualified visits, and to measure assisted conversions and brand searches alongside raw sessions.
Can a small site get cited alongside major brands?
Yes, and the 2026 data supports it. Roughly 31% of cited pages do not rank in the top 100 for the query at all, which means depth on a narrow sub-question can beat domain size. Specificity is the small publisher’s genuine structural advantage here.
Is optimising for AI Overviews different from normal SEO?
It is an extension, not a replacement. Google states the generative features run on core Search ranking systems, so crawlability, quality and authority still decide eligibility. What is genuinely new is the emphasis on fan-out coverage, self-contained answer blocks and snippet eligibility as a hard prerequisite.
Conclusion
The uncomfortable truth of 2026 is that the tactic most teams still lead with — push the page to position one and wait — now explains fewer than four in ten citations. What replaced it is less glamorous and more durable: understand the cluster of questions behind a search, answer each one cleanly enough to be lifted out intact, keep the page technically eligible, and bring evidence a summary cannot manufacture. Google has told us in writing that there is no secret markup and no shortcut. Treat citation as the outcome of genuinely good, genuinely structured coverage, measure it honestly in the new Search Console report, and let the shortcut-sellers waste their quarter on llms.txt.
