Does blocking Google-Extended remove my site from AI Overviews?

Blocking Google-Extended leaves your AI Overviews eligibility unchanged. Google's common crawlers documentation (updated 2026-07-14) says Google-Extended "does not impact a site's inclusion in Google Search nor is it used as a ranking signal." AI Overviews and AI Mode are features of Search, so a token that sits outside Search cannot reach them.

Google-Extended is a product token, not a separate crawler. It tells Google whether content fetched by its crawlers may be used to train Gemini models and to ground answers in Gemini Apps and Vertex AI. Disallowing it looks like this:

User-agent: Google-Extended
Disallow: /

That rule opts you out of Gemini training and Gemini Apps grounding. It does nothing to Googlebot, which keeps crawling and indexing your pages for Search, including the pages AI Overviews draw on. The comparison of Google-Extended and Googlebot sets out each control side by side.

Google states that a page must be "indexed and eligible to be shown in Google Search with a snippet" to appear as a supporting link in AI Overviews or AI Mode, and that "there are no additional technical requirements" (AI features documentation, last updated 2025-12-10). Google also says robots.txt directives for Googlebot are the control, because AI is built into Search. There is no separate AI Overviews crawler to block.

As of October 2026, these are the levers that work:

• Googlebot in robots.txt. Blocking Googlebot removes you from AI Overviews, but also from regular Search. Few sites want that trade.
• noindex. Keeps a page out of the index, and so out of every Search surface.
• nosnippet and max-snippet. Limit or remove snippet text, which removes the snippet eligibility AI Overviews depend on.
• data-nosnippet. Excludes a specific block of content from snippets and AI display while the rest of the page stays eligible.
• Search Console's AI features control. Covers AI Overviews, AI Mode and generative AI features in Discover. The guide to the Search Console control covers how it works.

Each of these is subtractive. They can take you out of AI Overviews. None of them can put you in.

Inclusion in Google's generative surfaces is opt-out. Google describes inclusion as "the default control for all properties," so you do not need to opt in to appear in AI Overviews. As of October 2026 the toggle is still rolling out, so many owners will not see it yet.

Three details catch people out:

1. Inheritance. Child properties default to "Inherit control from parent." A parent property opted out can silently remove a child from AI Overviews, AI Mode and Discover generative AI.
2. It is invisible from outside. No crawler or third-party tool can see whether a property has been opted out. Only someone with Search Console access can check.
3. Display is not use. Google says opting out of display does not stop your content being used to power Search as a whole, such as helping its systems understand user queries.

Google also says the control is not used as a ranking or inclusion signal for other parts of Search.

Google-Extended is the right control when your goal is about Gemini, not Search. It cuts training use and grounding for Gemini Apps and Vertex AI. That makes it the tool for sites that want to block AI training but stay in AI search.

Keep the paths separate in your head. Google runs several generative retrieval paths: AI Overviews, AI Mode, Gemini Apps, and the Gemini API's developer-invoked Grounding with Google Search. Google-Extended touches the Gemini side. Googlebot and the Search controls touch the Search side. Whether blocking it changes what the Gemini app says about you is a separate question, covered in does blocking Google-Extended change Gemini's brand answers.

One limit applies to everyone: no robots.txt rule reaches what a model already learned before its knowledge cutoff. Training opt-outs affect future use only.

Decide what you want first, then pick the matching control.

• Stay in AI Overviews, keep out of Gemini training: disallow Google-Extended, allow Googlebot, and leave snippet directives alone.
• Stay in Search, keep out of AI Overviews: use nosnippet, max-snippet or data-nosnippet on the relevant content, or the Search Console control once you have it.
• Unsure why you are missing from AI Overviews: check that pages are indexed, that no template adds nosnippet or max-snippet:0 by accident, and that no Search Console property has been opted out by inheritance.

Also confirm your robots.txt says what you think it says. A blanket AI block copied from a template can reach further than intended. The robots.txt Checker for AI Crawlers shows how each AI user agent resolves against your file. Remember that eligibility is not inclusion: Google says indexing and serving are not guaranteed.

Is Google-Extended a separate crawler I can see in my logs? No. Google-Extended is a product token you use in robots.txt. Google's existing crawlers do the fetching, and the token tells Google whether that content may be used for Gemini training and grounding in Gemini Apps and Vertex AI. You will not see a distinct Google-Extended user agent hitting your server, so judge its effect by your robots.txt rules, not your access logs.

Does blocking Google-Extended hurt my Google rankings? Google says no. Its common crawlers documentation states that Google-Extended does not affect inclusion in Google Search and is not used as a ranking signal. That is a first-party assertion rather than an outside measurement, but it is the best evidence available, and nothing in the published evidence contradicts it. Your Search visibility depends on Googlebot access and index eligibility.

Can I block AI Mode but keep AI Overviews? Not with robots.txt. Neither surface has its own token, and Googlebot rules apply to all of Search. The Search Console AI features control covers AI Overviews, AI Mode and Discover generative AI together, as of October 2026. Snippet directives such as data-nosnippet work at the content level, but they apply to Google's AI display generally, not to one surface.

If Google deindexes my site, can AI Overviews still cite it? Google says a page must be indexed and snippet-eligible to appear as a supporting link. The Otterly experiment fits that rule: after Google removed two test sites from its index, Google's AI surfaces almost never cited them, while Microsoft Copilot, which grounds on Bing, kept citing them. Index status is the gate, so check it engine by engine.