This article is for site owners, bloggers and marketers who want to know what they can and cannot control when Google shows their content in AI Overviews and AI Mode. It sticks to what Google’s own documentation says, and it marks clearly where the documentation is silent.
How pages become eligible for AI Overviews and AI Mode
Google’s documentation on AI features and your website is short on purpose. It says a page must be indexed and eligible to be shown in Google Search with a snippet, and that there are no additional requirements to appear in AI Overviews or AI Mode. It also says indexing and serving are never guaranteed, so meeting the requirements does not promise a placement.
In practice, eligibility comes down to the basics of being a normal search result:
- Googlebot can crawl the page. Check robots.txt and any CDN or host-level rules that might block it.
- The page is indexed and not carrying a
noindexornosnippetrestriction. - Important content is available as text, not only inside images or video.
- Structured data, if you use it, matches the visible text on the page.
- Merchant Center and Business Profile data are kept current, if they apply to you.
The same page says you do not need new machine-readable files, special AI text files, extra markup or particular schema.org types. If a vendor sells you an “AI Overview schema”, Google’s documentation gives no support for it.
Google also explains that both features may use query fan-out, which runs related searches across subtopics while an answer is generated. The documentation says this can surface a wider and more diverse set of helpful links. It adds that AI Overviews appear only when Google’s systems judge them additive to classic results, and that the two features may use different models, so the links they show can differ. For site owners, the takeaway is that covering a subtopic well can matter as much as targeting one exact phrase.
Preview controls: what each one does
Google’s AI features page points to four existing controls for limiting what is shown from a page: nosnippet, data-nosnippet, max-snippet and noindex. The details come from the separate robots meta tag documentation.
| Control | What the documentation says | Main trade-off |
|---|---|---|
nosnippet | Blocks text snippets and video previews. Applies to web search, Images, Discover, AI Overviews and AI Mode, and stops the content being used as direct input for the two AI features. A static thumbnail may still appear. | Your result also loses its normal text snippet in classic search, which can reduce clicks. |
max-snippet:[number] | Caps the text snippet length in characters and limits how much content can be used as direct input for AI Overviews and AI Mode. 0 equals nosnippet; -1 lets Google choose. It does not apply where a publisher has separately granted permission, such as through in-page structured data or license agreements. | A very low number shortens the snippet shown to searchers everywhere. |
data-nosnippet | An HTML attribute that keeps specific text out of snippets. Works only on span, div and section elements. | Good for one paragraph or a paywalled block. The page does not say whether it affects AI Overviews or AI Mode, so treat that as unconfirmed. |
noindex | Keeps the page out of search results entirely. | Removes the page from classic results too. The documentation does not explicitly address AI features, though an unindexed page is not eligible to appear with a snippet. |
Practical notes on using them
- Rules are read only when a URL is crawled. A robots.txt disallow stops Google reading the rule at all, so do not combine a disallow with a meta tag and expect the tag to work.
- Changes take effect after recrawling. Google says this can take several days to several months, and you can request a recrawl. Use URL Inspection in Search Console to confirm Googlebot sees your control.
- For
data-nosnippet, write valid HTML with closed tags. Google warns that an unclosed tag can pull in all the content that follows. Do not add or remove the attribute with JavaScript; include it when elements are first inserted. - If rules conflict, the more restrictive one applies.
- For PDFs and images, use the
X-Robots-TagHTTP header.
Here is how the page-level tags look in the head of a page: <meta name="robots" content="max-snippet:50"> limits the text snippet (the value 50 is only an example), while <meta name="robots" content="nosnippet"> removes it. To hide one block, wrap it: <div data-nosnippet>...</div>.
What Google-Extended does and does not control
Google-Extended is frequently misunderstood. Google’s crawler documentation describes it as a standalone product token used in robots.txt, not a separate crawler. Publishers can use it to control whether content Google crawls may be used to train future generations of Gemini models and for grounding in Gemini Apps and Grounding with Google Search on Vertex AI. It has no separate HTTP user agent string; crawling still uses existing Google user agents.
The key sentence for SEO: Google-Extended does not impact a site’s inclusion in Google Search and is not used as a ranking signal. The crawler page does not mention AI Overviews, so blocking Google-Extended should not be treated as a way to opt out of them. Google’s AI features page sends site owners to nosnippet, data-nosnippet, max-snippet and noindex for that purpose.
The syntax in Google’s documentation looks like this: user-agent: Google-Extended followed by a line such as disallow: /archive/.
How AI feature traffic appears in Search Console
According to Google, sites appearing in AI Overviews and AI Mode are included in overall Search traffic, and the data appears in the Performance report under the Web search type. Nothing in the documentation describes a filter that isolates AI Overview or AI Mode clicks. For the reporting basics, see our walkthrough of the Search Console Performance report.
Google also says clicks from AI Overviews tend to be higher quality, with users more likely to spend more time on the site. That is Google’s own statement on its page, and it comes without figures, so check it against your own analytics before relying on it.
A reported change to links, and what is still unknown
Industry coverage in mid-October 2026 reported changes to how links appear. Search Engine Roundtable, a secondary source, reported on October 15, 2026 that Google is placing more links within AI responses, in some cases higher up, highlighting one or two relevant pages for some queries, expanding timely-news carousels, and testing publisher and creator names on videos that link to Search profiles. The same article says Google has not added click data to its AI reporting, quotes Google as saying it will introduce additional metrics over time, and notes that the “won’t show click data” framing is the author’s assessment rather than a Google statement.
Because this comes from one trade publication and not from the Google documentation pages listed below, treat it as a report. Rollout details and any traffic impact are not established.
Practical content advice from Google’s own pages
Google’s advice for AI features is the same as its advice for Search generally: create helpful, reliable, people-first content, and keep pages technically sound and policy-compliant. There is no separate AI optimization checklist. A sensible routine:
- Confirm key pages are indexed using URL Inspection in the property you verified in Search Console.
- Put the main answer in plain text near the top, and support it with relevant images or video.
- Cover related subtopics a reader would ask next, since fan-out searches look across subtopics.
- Make author and sourcing information honest; see our guide to bylines and author pages.
- Avoid manipulative tactics; our spam update checklist covers what to review.
- Decide deliberately before adding snippet restrictions, because they affect classic results too.
Key takeaways
- Eligibility for AI Overviews and AI Mode requires being indexed and snippet-eligible; Google lists no extra requirements and no guarantee.
nosnippetandmax-snippetare documented as limiting use as direct input for AI features;noindexremoves the page from results.- Google-Extended governs Gemini training and grounding use, not Search inclusion or ranking, and the crawler page does not address AI Overviews.
- AI feature traffic is part of Web search type data in the Performance report; no AI-only click breakdown is described.
- Reports of link changes in October 2026 come from a trade publication and should be read as reports.
FAQ
Do I need special markup to appear in AI Overviews?
No. Google’s documentation says no additional machine-readable files, AI text files, markup or special schema.org types are required.
Does blocking Google-Extended remove my site from AI Overviews?
Google’s crawler documentation does not say so. It describes Google-Extended as controlling Gemini training and grounding use, and says it does not affect inclusion in Google Search.
Can I see AI Overview clicks separately in Search Console?
Google’s documentation says AI feature traffic is counted within the Web search type in the Performance report. It does not describe a separate AI-only view. Trade coverage reports that Google plans more metrics over time.
Which control should I use to limit what is shown?
It depends on the goal. nosnippet or max-snippet limit text used from the page, data-nosnippet targets specific passages, and noindex removes the page from results. Each has costs for classic search visibility.
