Optimizing for Google AI Overviews

Google AI Overviews is the one AI surface where the vendor has written the eligibility rule down in a sentence. Most AI Overviews advice skips that sentence and sells extras: schema, special files, rewritten paragraphs, rank tracking. Google's own documentation rules out most of them.

The rule is short and meeting it is not hard. What makes AI Overviews tricky is everything around it: a Search Console control most site owners have never opened, snippet directives inherited from templates, Overviews that often do not appear at all, and a report that cannot tell you whether any of it produced a click.

This lesson covers the rule, the controls, the overlap with organic rank and what Google lets you measure. The win is a ten-minute eligibility check on three of your own URLs.

The eligibility rule, in Google's words

Google's AI features page (last updated 2025-12-10) says: "To be eligible to be shown as a supporting link in AI Overviews or AI Mode, a page must be indexed and eligible to be shown in Google Search with a snippet, fulfilling the Search technical requirements. There are no additional technical requirements."

And again, for anyone selling extras: "There are no additional requirements to appear in AI Overviews or AI Mode, nor other special optimizations necessary."

So eligibility has two parts: indexed and snippet-eligible. Both are binary, both are checkable, and both can fail silently. Eligibility is not inclusion: the same page warns that "indexing and serving isn't guaranteed." But a page that fails either part cannot be a supporting link, whatever else you do.

One caution on the source. Google's statements are assertions, not measurements, and Google has its own reasons to frame its products a certain way. For Google's own surfaces they are still the best evidence available, and nothing in the research contradicts this one.

The controls: Googlebot, and a switch you may never have seen

There is no AI Overviews token

You cannot block AI Overviews in robots.txt and stay in Search. Google: "AI is built into Search and integral to how Search functions, which is why robots.txt directives for Googlebot is the control." Disallow Googlebot and you leave Search entirely.

Google-Extended does not change this. Google states it "does not impact a site's inclusion in Google Search nor is it used as a ranking signal." It governs the Gemini apps and Vertex AI, covered in Claude, Gemini and the Rest. Blocking it will not remove you from AI Overviews, and allowing it will not put you in.

The Search Console generative AI control

Google has added a Search Console control over whether a property appears in its generative features: AI Overviews, AI Mode and generative AI features in Discover. Three things about it matter:

• It is opt-out. Inclusion "is the default control for all properties." You do not need to do anything to be eligible.
• It inherits. For a child property the default is "Inherit control from parent." An opt-out set on a parent property, by a former agency or an old team, can silently cover every child.
• It is invisible from outside. No crawl and no API reveals it. Google is still rolling it out to "a subset of website owners", so many properties do not show it yet.

Google says the setting "isn't used as a ranking or inclusion signal affecting other parts of Search," and that opting out of display does not stop content being used "to power Google Search as a whole." It controls where you are shown, not whether Google reads you. If an AI Overviews audit skips this check, one setting can make the rest of the work pointless.

Snippets, rendering and the page itself

Snippet eligibility is where most accidental exclusions happen. Google names the on-page controls that limit how content appears in its AI features:

• <meta name="robots" content="noindex"> removes the page from the index, so it cannot be a supporting link.
• nosnippet stops any snippet, and with it, display in AI features.
• max-snippet:0 has the same effect: a zero-length snippet is no snippet.
• data-nosnippet on an element hides that section from snippets while the page stays indexed. Bing honors it too, and says marked content is "excluded from snippets and AI summaries" while remaining "available for ranking."

These arrive by accident more often than by choice: a template that wraps the main content in data-nosnippet to hide a cookie banner, or an X-Robots-Tag header set on a staging environment and carried into production. Check the served page source and the response headers, not the CMS settings. 99Visibility's Crawler Access check flags noindex, nosnippet, max-snippet:0 and data-nosnippet for you. More in Rendering, noindex and Snippet Controls.

Two things you can mostly stop worrying about on Google:

• JavaScript. Googlebot renders pages, so client-side content can reach Google's index. That does not hold for the ChatGPT, Claude or Perplexity crawlers, so server rendering still matters for every other engine.
• Page size. Google's Gary Illyes wrote on March 31, 2026 that Googlebot fetches up to 2MB per URL (64MB for PDFs) and ignores every byte past that. Google's own framing: "For the vast majority of the web, a 2MB HTML payload is massive, and you will never hit this limit." Check it only if a page is unusually heavy.

When Overviews appear, and which pages they cite

AI Overviews often do not trigger. For many queries Google shows no Overview at all, and 99Visibility skips those queries instead of counting them as misses. AI Mode is a different surface: Google says the two "may use different models and techniques" and return different links, so appearing in one says nothing about the other. That is why 99Visibility audits AI Mode as its own column. Behind both, Google may use "a 'query fan-out' technique — issuing multiple related searches across subtopics", so the searches that pick sources are not the one your buyer typed.

How much does organic rank predict citation? Less than most guides claim.

Read rank as a moderate, decaying proxy. It is not irrelevant, and the opposite folklore, "rank no longer matters", is equally unsupported. Ahrefs matches by URL, which penalizes large sites cited through a page that does not itself rank. What the evidence supports is narrower: be indexed, be snippet-eligible, and have pages that are relevant to the subtopics the fan-out searches cover.

Measuring AI Overviews honestly

Search Console has a generative AI performance report. It shows impressions only for AI Overviews and AI Mode, by page, country, date and device. It has no clicks, no click-through rate and no position, and the Search Analytics API does not cover it. Two traps: as of August 2026 the help page still described the report as reaching "a subset of website owners" though its rollout had finished, and a Google-side bug depressed impressions from about 2026-08-12. Do not draw a trend across that window without checking Google's notes.

AI Overviews also send no separate referral. Clicks from them arrive in analytics as ordinary Google organic traffic. Put that next to an impressions-only report, and Google's first-party tools cannot tell you whether AI Overviews visibility produced a single visit.

Third-party tools cannot fill that gap with a rank. Google's page on third-party SEO tools (2026-06-05) says they "don't have access to our internal ranking data" and "can't guarantee performance." There is no ground truth to validate an AI Overviews position against. 99Visibility records whether an Overview appeared for the query, whether it named you and which URLs it cited. It does not report a rank, because no one can measure one.

What does not get you in

• Schema. Google: "Structured data isn't required for generative AI search, and there's no special schema.org markup you need to add." Ahrefs' matched-control test (May 11, 2026) found no major uplift on any platform and a statistically significant 4.6% drop in AI Overview citations. One honest caveat: every page in that study was already heavily cited, so whether schema helps a page enter the set is untested. Details in Schema Markup for AI.
• FAQPage markup. Google's changelog shows FAQ rich results deprecated in May 2026 and the documentation removed in June.
• llms.txt and AI text files. Google's AI optimization guide (2026-07-10) says creating them "will neither harm nor help your site's visibility or rankings in Google Search, as Google Search ignores them."
• Chunking and long-tail variants. The same guide rejects chunking as a requirement and says "There's no ideal page length."
• An E-E-A-T score. Google says E-E-A-T "isn't a specific ranking factor." There is no number to raise. See E-E-A-T for AI.

Common mistakes

• Blocking Google-Extended to leave AI Overviews. It does not touch Search inclusion. Googlebot and the Search Console control are the levers.
• Never opening the Search Console control. An inherited opt-out cancels every other fix. Check the parent property too.
• Checking the CMS, not the output. Snippet directives arrive through templates and headers. Read the served HTML and the response headers.
• Counting no Overview as a miss. If Google shows no Overview, there was nothing to appear in.
• Treating AI Mode and AI Overviews as one surface. Google says they may use different models and return different links.
• Quoting the top-10 decline as a trend. The two endpoints came from different methods.