Google AI Overviews are the panel of generated text that appears at the top of a search result page for a lot of queries now. They cite sources. Those sources get traffic — and increasingly, brand recognition. Here's what the data says about who gets picked and why.

What AI Overviews actually are

AI Overviews are Google's generative answer panels. They sit above the traditional blue-link results for queries Google decides are "informational" or "comparative." A typical Overview is two or three paragraphs of synthesised text, with three to seven cited sources displayed as clickable cards below or beside the answer.

The reach has gone from "occasionally" to "background condition" in eighteen months. As of early 2026 AIO appears on more than 50% of all Google queries and reaches roughly 1.5 billion users per month across 200+ countries (Google's own I/O 2025 disclosure). Click-through rates from AIO citation cards run at roughly half what equivalent top-3 organic positions get — but the brand exposure (your name appearing above the blue links) is uncapped.

How Google chooses what to cite

We have a few data points that are public, and a few patterns that are obvious from watching what gets cited.

1. Top-10 ranking is the entry ticket. Roughly 92% of AI Overview citations come from pages that were already ranking in the top 10 organic results for the underlying query, per the Ahrefs December 2025 study of 75,000 brands. If you're not in the top 10, you have an 8% chance — not zero, but you're betting against the base rate.

2. The cited page is not always the highest-ranked. Within the top 10, the citation often goes to position 4, 6, or 9 instead of 1 or 2. The same Ahrefs analysis puts about 47% of AIO citations on pages ranking below position 5. The selection logic is clearly different from organic ranking.

3. Passage extractability matters more than page authority. Pages that get cited tend to have a clean, self-contained answer chunk somewhere in the middle — usually 134-167 words long. AIO seems to look for "lift this paragraph and the answer is complete" rather than "this page is the most authoritative."

4. Structured data is a tiebreaker. Among pages with comparable passage quality, the ones with valid Article + FAQPage JSON-LD get cited more often. The mechanism is straightforward: structured data tells Google exactly what each chunk is (a question, an answer, a definition), so the extractor doesn't have to guess.

5. Recency is weighted, but not how you'd expect. AIO doesn't always pick the newest source. It picks the newest source that also passes the other filters. A six-month-old post with a clean answer block, an Article schema, and a recent dateModified will beat a one-week-old post that's a wall of text.

The five rewrites that earn AIO citations

Watching what gets cited in any given niche for six months, a few patterns repeat.

1. Lead with a definitional answer

The first paragraph after the H1 should be a 130-150 word self-contained answer. Start with "X is Y." Then explain what it does, what it costs (or what the constraint is), and what makes it different. AI Overviews disproportionately quote this opening passage.

2. Use question-shaped H2s

If your H2 is "Pricing structure," it's competing with every other "Pricing structure" page. If your H2 is "How much does X cost in 2026?" it's now a candidate for any query that resembles that question. AIO pattern-matches headings to user queries. Match the query phrasing.

3. Put one specific number in every paragraph

Vague claims do not get cited. Specific claims do. "Our customers see significant growth" earns zero citations. "Our customers averaged a 38% lift in organic clicks in the first 90 days" gets pulled into AIO answers about content marketing ROI. The number doesn't have to be impressive — it has to be specific and attributable.

4. Add a FAQ section with FAQPage schema

Even though Google restricted FAQ rich results to government and healthcare sites in August 2023, FAQPage schema is still parsed by the AIO extractor. Adding 5-8 FAQs with valid schema is one of the highest-ROI changes for a marketing page, because each question becomes an extractable Q&A unit.

5. Update the post and bump dateModified

AIO weights recency, but only as a tiebreaker. If your post already has a clean answer block and Article schema, refreshing it (and updating the schema's dateModified) will often promote it from "in the top 10 but not cited" to "cited."

What doesn't work

A few things teams keep trying that we haven't seen move the needle:

  • Keyword stuffing in H2s. AIO is reading the prose, not the keyword density.
  • HowTo schema. Google deprecated rich results for HowTo in September 2023 and AIO doesn't seem to weight it. Use Article instead.
  • AI-generated content with no human pass. AIO appears to dampen citation rates on pages that look AI-generated — the patterns the humanizer guide flags as "AI tells" (em dash overuse, rule-of-three padding, signposting phrases, vague attribution). Whether it's a deliberate downweight or a side effect of the trust signals AIO uses, the result is the same: clean it up.

How to track AIO citations

There isn't a perfect tool yet. The two practical options:

  1. Manual sampling. Pick your 20 highest-priority queries. Once a month, log into a fresh browser session (no personalisation), search each one, and record whether AIO appeared and whether you were cited. It takes about 45 minutes.
  2. Specialist tooling. SE Ranking, Ahrefs, and a few smaller tools now offer "AI Overviews tracking" as a feature. They're spotty for niche queries but reasonable for broad ones.

Bottom line

Top-10 ranking is the entry ticket. Once you're inside, AIO re-ranks on passage quality, structured data, factual specificity, and recency. The teams getting cited aren't necessarily ranking #1 — they're writing in a way that's easy to lift, labelling their content with JSON-LD, and refreshing it on a deliberate cadence.

If you can only do three things, do these: write a 130-150 word self-contained answer at the top of every cornerstone page, add Article + FAQPage schema, and bump dateModified whenever you genuinely update the content.

Related reading

Sources