AI Overviews SEO: What Google Says It Takes to Be Eligible

Google's documentation for site owners is unusually direct. Its AI features page (last updated December 2025) states: "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."

The same page adds: "There are no additional requirements to appear in AI Overviews or AI Mode, nor other special optimizations necessary."

Google's July 2026 guide to optimizing for generative AI features goes further. It says you don't need new machine-readable files, AI text files, markup or Markdown, because Google Search doesn't use them. It says you don't need to write in a specific way for generative AI search, and that there's no ideal page length.

What this means: there is no separate AI Overviews ranking system you can target with a special technique. If a page can appear in regular Search with a snippet, it can be considered. If it can't, nothing else you do will help. For the wider picture of Google's stance, see Google's stated position on AI and SEO.

One caveat. Google's statements are assertions about its own systems, not independent measurements. They are still the best evidence available for Google surfaces, and nothing in the published research contradicts them.

It helps to split the process into stages, because you control some and not others.

Access

Googlebot must be allowed to fetch the page. Google has no separate robots.txt token for AI Overviews. Its position is that robots.txt directives for Googlebot are the control. That also means blocking Google-Extended does not take you out of AI Overviews; it governs Gemini apps and training, as explained in whether Google-Extended affects AI Overviews.

Index and snippet eligibility

The page must be in Google's index and allowed to show a snippet. A noindex or nosnippet directive ends eligibility.

Triggering

For each query, Google decides whether to show an overview at all. Google says AI Overviews often do not trigger. No setting on your site changes that.

Retrieval and selection

When an overview does trigger, Google may use a "query fan-out" technique, issuing multiple related searches across subtopics. It then picks which eligible pages to link. You can't see those fan-out queries, and Google doesn't publish how it selects.

The practical takeaway: the first two stages are yours to get right. The last two belong to Google.

Google is explicit that "Indexing and serving isn't guaranteed." A perfectly eligible page can go months without appearing in an overview, for three reasons.

• The overview may not exist. Many queries never show one.
• Other pages may be chosen. Google links a handful of sources from a much larger eligible pool.
• The surface varies. Results differ by location and language, and Google says AI Overviews and AI Mode "may use different models and techniques" and return different links. The AI Overviews vs AI Mode comparison covers the differences.

Organic ranking is related but not decisive. Ahrefs found in March 2026 that 37.9% of URLs cited in AI Overviews also appeared in the first 10 results, with the rest split between positions 11 to 100 and beyond 100. Ahrefs changed its method between studies, so earlier and later figures aren't a measured trend. Ranking well helps your odds of being in the candidate pool. It doesn't decide the outcome.

So set the right goal. You can guarantee eligibility. You can't guarantee a link.

The Search Console control deserves attention. As of October 2026, inclusion in AI Overviews, AI Mode and Discover generative AI features is the default for all properties. The control is an opt-out, still rolling out to a subset of owners, and child properties inherit from the parent by default. A property can be excluded without anyone on the current team having touched it, and no outside crawl can see it.

Work from the hard gates down. Each step either confirms eligibility or finds the block.

1. Check robots.txt for Googlebot. Make sure no rule disallows Googlebot from the pages that matter. A blanket AI block aimed at other bots sometimes catches it too.
2. Confirm index status. Use URL Inspection in Search Console on your key pages: pricing, product, category and top guides.
3. Audit snippet directives. Look for noindex, nosnippet, max-snippet:0 in meta robots tags and HTTP headers, and data-nosnippet on page elements. Templates often carry these for a cookie banner or staging site. Google documents them as the controls that keep content out of snippets and AI features.
4. Check the generative AI inclusion control. If your property shows it, confirm it is set to include, and check what child properties inherit.
5. Check page size only if pages are heavy. Googlebot fetches up to 2MB of HTML per URL and ignores anything after that. Google says most of the web never hits this limit.
6. State your key facts in plain sentences. A price, a number or a one-line definition on a fetchable page gives the engine a sentence it can quote. This is the only on-page approach with any positive experimental signal, and it promises nothing.
7. Earn mentions where Google already looks. When overviews for your buyer queries cite other sites, being named on those sites is associated with appearing in the answer. It's an association, not a guaranteed effect.

Here is a directive worth searching your templates for, because it quietly removes a page from snippets and AI features:

<meta name="robots" content="max-snippet:0">

Measurement is where most AI Overviews SEO advice breaks down.

Google's Search Console generative AI report shows impressions for AI Overviews and AI Mode. Per Google's help documentation, it has no clicks, no CTR and no position dimension. Google also states that third-party tools don't have access to its internal ranking data. That means no tool can validate an "AI Overview position" against anything.

What you can do honestly:

• Track presence, not rank. For a fixed list of queries, record whether an overview appears and whether your page is linked.
• Fix location and language. Overviews vary by both, so changing them changes the result.
• Read impressions as a trend, not a verdict. Separate them from your classic Search data.
• Check traffic separately. The traffic impact guide covers what you can and can't attribute.

To see what Google shows for a specific query right now, the free AI Overview checker gives a snapshot. It's a point-in-time view, not continuous tracking.

If you also track ChatGPT, Perplexity or Gemini, keep AI Overviews in its own column. Each surface uses different models and sources, so a blended score hides more than it shows.

Adding FAQ or other schema to get cited

Google says structured data isn't required for generative AI search. Ahrefs tracked 1,885 pages that added schema against matched controls and found AI Overview citations fell 4.6%. Every page in that study already had 100 or more AI Overview citations, so whether schema helps a page enter the pool is untested. FAQ rich results were deprecated in May 2026. Existing markup does no harm. It just isn't a lever for AI Overviews.

Publishing an llms.txt for Google

Google says Search ignores it and that it will neither help nor harm visibility.

Rewriting for AI or chunking pages

Google says you don't need to write a specific way for generative AI, cover every long-tail variant, or hit an ideal length.

Chasing an E-E-A-T score

Google says E-E-A-T isn't a specific ranking factor, and there is no score to raise. Rater ratings don't position individual results, as covered in whether quality raters decide AI Overviews.

Mass-publishing thin AI pages

In OtterlyAI's 2026 experiment, Google deindexed two new sites of roughly 1,000 AI-generated posts each, with no manual action shown. After removal, Google's AI surfaces almost never cited them. Google's spam policies name generating many pages with AI "without adding value for users" as scaled content abuse.

Hiding text for crawlers

Hidden text, cloaking or injected instructions aimed at AI systems are illegitimate. They breach Google's spam policies and put the whole site at risk.