Google AI Overviews changed the SERP in two months. Queries that previously returned ten blue links now return a synthesized answer at the top, with citations inline. Click-through to the cited sources is real but smaller than to traditional organic positions; citation share inside the Overview is the metric that matters for visibility. The content that gets cited follows a structural pattern, and the pattern is reproducible.
What AI Overviews actually does
For a given query, Google decides whether to render an AI Overview based on query type (informational queries trigger it more often than transactional or navigational), confidence (the model needs to feel reasonably sure it can synthesize a coherent answer), and SERP composition (some queries are deemed too commercially sensitive to synthesize).
When the Overview renders, the answer is synthesized from a small set of cited sources. The citation count is typically 3–5, much lower than the top-10 ranking surface. The cited sources almost always come from within the top-20 organic results but not necessarily from the top-3; structural quality can lift a position-7 result into the citation set.
The six structural moves
1. The first definitional passage
A 40–60 word passage in the first 100 words of the page that defines the central entity comprehensively. The passage gets cited disproportionately. Bury the definition below the fold and the page often gets used as a source without citation; surface it at the top and the citation rate rises.
2. Entity-named headings
Every H2 and H3 names its entity explicitly. “How to measure topical authority” works; “How to measure it” does not get retrieved against the same set of query reformulations. Pronoun-loaded headings are a near-universal weakness in pages that fail to capture Overviews citations.
3. Comparison tables on bridge queries
Any query that compares two entities (“X vs Y,” “Difference between X and Y”) tends to render an Overview that includes a table. The table content gets cited directly. Pages that handle the same comparison in prose lose the citation to pages with explicit tables.
4. Misconception blocks
Where the topic has training-time ambiguity (multiple definitions in the wild, conflicting frameworks), an explicit misconception block raises the page’s scoring as an authoritative source. The model treats the page as resolving the ambiguity rather than perpetuating it.
5. FAQ sections with verbatim query language
FAQ questions should use the exact phrasing the audience uses, pulled from real query data. AI Overviews regularly cites FAQ answers directly when the user’s query closely matches the question.
6. Visible author attribution and updated dates
E-E-A-T signals at the page level. The Overview’s scoring favors sources with visible authorship; the structural cost of adding the byline is trivial.
What does not work
- Heavy schema markup without structural matches. FAQ schema helps when the FAQ section is also present in the page body; FAQ schema on a page without an actual FAQ produces minimal lift.
- Keyword stuffing for the head term. AI Overviews evaluates passage-level relevance through embeddings; lexical density on the head term contributes less than entity coverage across the cluster.
- Long prose without clear passage boundaries. The retrieval system needs extractable chunks; long uninterrupted prose retrieves poorly. Sectioning with named headings is the structural fix.
- Isolated optimization on a single page. Network signals (entity consistency, cluster coverage) contribute to source scoring; single-page work without cluster context underperforms.
A one-afternoon restructure
Most existing cluster pages benefit from the six moves above; most do not need to be rewritten. The restructure usually takes an afternoon per cluster.
- For each cluster page, write the 40–60 word definitional passage and move it into the first 100 words. Push the narrative setup below the fold.
- Audit headings; rewrite to name entities explicitly throughout.
- On bridge pages, add a comparison table covering the comparison the page is meant to resolve.
- On pages where the topic has known ambiguity, add a misconception block that names and resolves the ambiguity.
- Expand the FAQ section using verbatim query language pulled from real search data.
- Surface or update the author byline and modified date in the page metadata.
Citation capture starts moving in 2–6 weeks. Faster than Google ranking lift, because the retrieval system reads the structural signals directly.