Why your site isn't showing in AI Overviews (and how to fix it)

You can rank on page one and still watch the AI Overview cite three other sites. The cause is almost always one of six fixable problems: an indexing gap, snippet suppression, JavaScript-trapped content, no liftable passage, uncovered fan-out strands, or authority below the bar. Here is each blocker, the diagnosis and the fix.

Key finding: AI Overviews are assembled from passages, not positions. A custom Gemini model grounded in Google’s Search index retrieves candidate pages, then cites only the ones it can quote cleanly and trust. In SearchScore’s SAVI benchmark of 850,000+ sites, technical foundations average 70.1/100 while on-page structure averages 23.1/100: sites rank fine and are semantically invisible to the answer at the top of the page. This is the AI Overviews failure mode a classic SEO audit will never flag.

Why your rankings dashboard cannot see the problem

For twenty years the goal was a high blue-link position. AI Overviews change the finish line: the summary sits above your ranking, and inclusion is decided by extraction and trust rather than position alone. Your rankings look healthy, your traffic report looks fine, and yet the most valuable real estate on the page, the answer users read first, never mentions you.

Two independent things now have to be true: you have to be rankable, and you have to be quotable. The six blockers below break one or the other.

Reason 1: the page is not indexed, or not readable

AI Overviews can only cite what Googlebot has already crawled and indexed; there is no separate AI crawl. A page missing from the index, or one whose content only exists after client-side JavaScript runs, is ineligible regardless of quality.

The fix: check Search Console coverage for your target pages, fix crawl errors, and confirm your main content is present in the raw HTML. This is the entry ticket; everything else waits behind it.

Reason 2: snippet suppression is silently excluding you

The one control that genuinely keeps a page out of an Overview is the snippet family. nosnippet, data-nosnippet or max-snippet:0 means Google cannot lift a passage from the page into the summary. Plenty of sites throttled snippets years ago to protect content, then wonder why they never surface in the answer while their rankings stay perfect.

Note the twin misconception: blocking Google-Extended does not remove you from Overviews. It is a training and grounding opt-out for Google’s generative models; Overview citations come from the standard Search index. Sites block it believing it hides them, and it changes nothing.

The fix: audit meta robots tags and headers on the pages you want cited, and remove blanket snippet restrictions. Keep them only where you deliberately accept losing featured snippets and Overview citations together.

Reason 3: no passage the model can lift

From the candidates, the model favours pages it can extract a clean, direct passage from. A correct answer spread across five paragraphs of build-up loses to a source that states it in one self-contained sentence. This is the most common blocker in the SAVI data, and the least visible from any rankings tool.

The fix: open each target page and apply the lift test: is there one sentence, under a question-shaped heading, that answers the query outright and survives out of context? If not, restructure: answer first, expansion after, one idea per paragraph.

Reason 4: you have not covered the fan-out

Google quietly decomposes one question into several related sub-queries, runs them in parallel, and stitches the Overview from whichever pages best satisfy each strand. If your page answers only the headline term while rivals answer the cost, comparison and suitability strands, they get cited and you do not, even from lower positions.

The fix: map the sub-questions around your topic and answer each explicitly, with its own question-format heading, on the page or across a linked cluster. Fan-out coverage is how pages get cited without ranking first.

Reason 5: the model cannot resolve your entity

Citations attach to entities. Thin or inconsistent Organisation, Person and author schema, or brand details that differ across the web, leave the model unable to say confidently who your page speaks for, so it cites a source it can identify.

The fix: implement Organisation and author schema with exact, consistent details everywhere. Make each page’s subject explicit: who you are, what question this page answers.

Reason 6: your authority is below the bar for the topic

From extractable candidates, the model cites sources it deems authoritative enough to stand behind: named authors with credentials, cited data, reviews, third-party references. On YMYL topics (health, finance, legal) the bar is sharply higher, and anonymous or thin content is effectively excluded however well it ranks.

The fix: add real bylines with credentials, cite your data, earn third-party references, and build genuine topical depth. This lever is slow but lifts your classic rankings and your Gemini visibility at the same time.

The priority order for fixes

Priority Fix Time Why
1 Fix indexing and rendering Hours to days Ineligible pages cannot be cited
2 Remove snippet suppression 30 minutes The one control that truly excludes you
3 Rewrite key sections answer-first 1-2 days Extraction decides the citation
4 Cover the fan-out sub-questions Days How you win without ranking first
5 Pin your entity with schema 2-4 hours Citations attach to entities
6 Raise E-E-A-T for the topic Ongoing Trust picks the final source

How to confirm which blockers apply to you

The free Google AI Overviews Visibility Checker inspects each layer separately on any URL: index inclusion, snippet eligibility, citable structure, fan-out coverage, entity and schema clarity, and authority signals. About 60 seconds, no signup, ranked fix list at the end. Run it on your domain, then on the competitor the Overview keeps citing: the gap between the scores tells you which of the six gaps is yours.

How common are these blockers really?

The SAVI benchmark suggests the answer is: nearly universal. Across 850,000+ sites, only 0.2% score as fully AI-Ready, and the structural signals that decide extraction average 23.1/100 against technical foundations of 70.1/100. When SearchScore audited 1,038 UK accountancy firms, 97% were crawlable yet only 18 covered all five AI-readiness basics. Most of your competitors have the same six problems you do, which means fixing yours in priority order is a genuine, available advantage rather than a hygiene exercise.

Related articles

Sources & Further Reading

Frequently asked questions

Why does the AI Overview cite lower-ranked sites instead of mine?

Because Overviews are stitched from passages, not positions. Query fan-out lets a page that cleanly answers one sub-question get cited from page two, while extraction preference means a quotable paragraph beats a higher-ranked wall of prose. How AI Overviews choose their sources walks through all four mechanics.

Did blocking AI training bots remove me from AI Overviews?

Almost certainly not, and this is the most common false lead. Google-Extended governs generative training and grounding, not Overview citations, which are sourced from the standard Googlebot index. Check for snippet suppression instead: `nosnippet` or `max-snippet:0` is the control that actually excludes you.

How long do these fixes take to show results?

Snippet and indexing fixes take effect on Google's next recrawl of the affected pages, typically days to weeks. Structure rewrites follow the same cycle. Fan-out and authority work compounds over weeks to months. Judge progress on a basket of queries, not a single search: Overview presence varies by query and over time. The full step-by-step is in how to appear in Google AI Overviews.

Should I opt out of AI Overviews instead of competing for them?

Only if you accept the blunt trade. The one effective opt-out is the snippet family (nosnippet, data-nosnippet, max-snippet:0), and it simultaneously strips your featured snippets and shortens your normal result snippet, which usually costs clicks. Blocking Google-Extended does not opt you out of Overviews, and blocking Googlebot removes you from Google entirely. For most businesses the realistic options are compete or concede the answer box to rivals.

Part of Plain English Guide — see all guides in this series →