Google AI Overviews now appear in 25.11% of all Google searches as of Q1 2026 — and that share is climbing. When an AI Overview shows up, it pushes the first organic result down ~600px on desktop and often below the fold on mobile. Brands cited inside the Overview win the click. Brands not cited become invisible for that query, even if they rank #1 organically below it.

This piece is the working method we use on every Citable engagement to land brands inside AI Overviews. Not “best practices.” The actual sequence.

What an AI Overview is, exactly

An AI Overview is a Google-generated summary that synthesizes 3 to 8 web sources into a multi-paragraph answer at the top of the SERP. It includes:

• A 2 to 4 sentence direct answer to the query
• A bulleted list of supporting points (sometimes)
• A row of source citation cards — usually 4 to 6 sources, expandable to more
• A “Show more” toggle that reveals additional sources

The mechanic: Google’s Gemini model retrieves indexed pages, picks the ones that most directly answer the query, and synthesizes a response. Source cards link to the pages it cited. Your goal as a brand is to be one of those source cards.

What signals Google AI Overviews actually weigh

The honest answer first: this is partially a black box. Google has not published the exact weighting. What follows is derived from 6+ months of Citable engagement data plus public reverse-engineering work by SEO researchers (Aleyda Solis, Lily Ray, Mike King, Mordy Oberstein).

Strong signal (consistently moves citation frequency):

1. Already ranking in the top 10 organic results for the query. ~80% of pages cited in AI Overviews rank in positions 1–10 for the underlying query. Google does not invent citations from page 11.
2. Direct-answer paragraph in the first 200 words of the page. Pages that lead with a declarative answer (e.g., “Generative Engine Optimization is the discipline of…”) get cited disproportionately over pages that bury the answer.
3. FAQPage schema with question-format H2s. Pages with FAQPage schema where the question matches the searcher’s intent are extracted preferentially.
4. HowTo schema for procedural queries. “How to X” queries pull from HowTo-marked content much more than from prose.

Medium signal (helps when other signals are present):

5. Page-level entity clarity. Organization, Person, or Product schema with sameAs chains to authoritative sources.
6. Author attribution. Article schema with a real author (not “Admin”) and a Person schema linked from the author bio.
7. Domain authority for the topic. Not generic DA — topic-specific authority. A 10-year-old food blog won’t rank for SaaS queries even with DA 80.
8. Recency. dateModified within the last 12 months for evergreen topics; within 6 months for time-sensitive ones.

Weak signal (assumed but unverified):

9. Backlink quality. Probably matters as part of overall page quality, but specific link counts don’t seem to correlate strongly with AI Overview citation.
10. Brand mentions in third-party authoritative sources. Probably weighted via the entity layer, not directly.

What does NOT matter:

• Word count (long pages don’t win automatically)
• Stuffing the H1 with the exact query
• Meta description optimization (AI Overviews extract from body content)

The 5-step playbook

Step 1 — Find the queries you can realistically win

Run your current top 50 commercial-intent keywords through Search Console. Filter to queries where you rank position 1–8. These are your candidate queries. Pages ranking position 11+ are not realistic AI Overview targets in the next 90 days; focus there separately.

For each candidate query, search it manually in Google. Note:

• Does an AI Overview appear at all? If no, this query is not a target. Move on.
• If yes, who is currently cited? Save the URLs. These are the pages you need to displace.
• What format is the AI answer? Direct answer, list, comparison, definitional?

A spreadsheet with columns: query | your rank | AIO present | cited sources | format. This is your battle map.

Step 2 — Reverse-engineer the cited pages

For each cited URL, open the page and look at:

• Opening paragraph. Does it directly answer the query in the first 2 sentences? Almost always yes for cited pages.
• H2 structure. Are headings in question format (“What is X?”, “How does Y work?”, “Why does Z matter?”)? Almost always yes.
• Schema markup. View source. Are FAQPage, HowTo, Article, or Product schemas present? Usually yes.
• Page age. When was it last meaningfully updated? Most cited pages are <18 months old or have a recent dateModified.

You are not copying these pages. You are reading the format Google currently rewards for that query.

Step 3 — Restructure your competing page

For each candidate query, take your existing ranking page and:

1. Rewrite the opening 200 words to lead with the direct answer. First sentence: declarative answer. Second sentence: the most important elaboration. Third sentence: why this matters. Then expand below.
2. Convert top-level H2s into the question form the searcher uses. If the query is “how to set up X,” your H2 reads “How to set up X” — exactly. Not “X setup guide” or “Getting started with X.”
3. Deploy FAQPage schema with a mainEntity array of 5–10 questions covering the main query and adjacent intent. The schema name field MUST match the H2 text on the page exactly.
4. Add HowTo schema if the query is procedural. Use real <HowToStep> entries with text that reads like a step, not a paragraph.
5. Update dateModified in your Article schema to reflect the actual edit. Stale dateModified on a refreshed page is one of the most common reasons Google ignores a refresh.

We covered the schema templates in detail in Schema markup for AI: the complete JSON-LD reference. Use those.

Step 4 — Make the page extractable

AI extractors give up early. Beyond the opening 200 words, restructure the body for paragraph-level extractability:

• Each H2 section should answer one question. The first 2 sentences of each section are the answer. The rest is supporting depth.
• Avoid burying definitions inside parentheses or footnotes. Definitions live in the first sentence after the H2 that introduces them.
• Use bulleted or numbered lists for enumerable answers (steps, criteria, options). AI Overviews pull list-formatted answers more than prose for these query types.
• Keep sentences short enough to be quotable. ~20 words is a good ceiling for the answer-bearing sentences.

This is the most labor-intensive part. It is also the part with the most compounding returns: the same page now performs better for human readers, classic SEO ranking, and AI extraction simultaneously.

Step 5 — Wait, measure, iterate

AI Overviews reflect ranking and indexing changes within 2 to 6 weeks for most sites. Re-search your candidate queries every 2 weeks. Log:

• Did your page enter the AI Overview cited sources? (Y/N)
• If yes, what position? (cited sources are ordered)
• If your page entered, did a competitor get displaced?

Track this in the same spreadsheet from Step 1. You will see patterns within 60 days: queries where the playbook works for you, queries where it doesn’t (usually because Google’s preferred answer for that query is structurally different from what your page provides).

For the queries where the playbook does not move the needle in 90 days, the issue is almost always one of:

• The query has weak commercial intent and Google prefers Wikipedia / definitional sources
• Your page lacks topic authority (the rest of your site does not signal that you cover this domain)
• Your domain itself is too new or too thin to be a credible source

The first two are fixable with content production around the topic. The third is fixable with time and digital PR.

What we do not bother with

A few things you will hear elsewhere that we have not seen move AI Overview citation:

• Pure keyword density tuning. AI Overviews are not keyword-matched; they are intent-matched.
• Schema spam. Adding 12 schemas to a page does not help. The schemas need to match the page’s actual content. Mismatch is flagged by Google’s quality systems.
• Auto-generated content. Google’s helpful content system is increasingly good at detecting low-effort AI-written pages and suppresses them. The cited pages we observe are almost always editorially produced with real expertise on display.

Tracking AI Overview appearance properly

Search Console now reports AI Overview impressions and clicks separately if you have the new performance reporting enabled. As of Q2 2026:

• Filter Search Type to “Web”
• Open the Performance report
• Use the “Search appearance” filter and select “AI Overview”
• Compare CTR for queries where you appear in the Overview vs. queries where you only appear in classic results

For brands without GSC AI Overview data yet (smaller properties, newer domains), the workaround is monthly manual sampling: re-run your top 50 queries, screenshot the Overview, log presence/absence. Tedious but reliable.

This is what Citable does on every GEO Growth retainer — the monthly Share of Answer report includes AI Overview appearance as one of the four tracked surfaces. Methodology covered in How to measure Share of Answer.

When this actually moves a business

For most B2B brands, AI Overview citations are worth more than classic organic positions for the same query, because:

• Click-through rate from a cited source card in an AI Overview is roughly comparable to position 1 organic
• The user has already received an answer; clicks signal high intent
• Citation positions you as the source of truth for that query, which compounds across the buyer journey

A B2B SaaS client we worked with in Q1 2026 went from 0 AI Overview citations to 11 in 90 days using this playbook. The 11 cited queries collectively drove ~340 sessions/month at conversion rates 2.4× their classic SERP traffic. Documented in From invisible to cited by ChatGPT in 90 days.

Where to start, concretely

This week:

1. Pull your top 50 commercial keywords from GSC.
2. Search each one manually. Mark which show AI Overviews. Save the cited source URLs.
3. Pick 3 queries where you rank 1–8 organically and an Overview appears.

Next week: 4. Restructure those 3 pages per Step 3. Lead with answers, question-format H2s, FAQPage schema, fresh dateModified. 5. Submit the 3 URLs for re-indexing in GSC.

In 4–8 weeks: 6. Re-search the 3 queries. Note any movement. Iterate on the ones that didn’t move.

If you want this run end-to-end on your top 50 prompts across ChatGPT, Perplexity, Gemini, AND Google AI Overviews — with documented Share of Answer measurement — that is what the AI Visibility Audit does. 1,200 EUR. Five business days.