Does blocking Google-Extended remove you from AI Overviews and AI Mode?

Q: Will blocking Google-Extended hurt my Google rankings?

Google says Google-Extended does not affect inclusion in Google Search and is not used as a ranking signal.

Published 2026-11-12

Short answer

No, according to Google's documentation. Google-Extended controls use of your content for Gemini model training and for grounding in Gemini Apps and Vertex AI. AI Overviews and AI Mode use pages that Googlebot crawls for Search. To limit them, Google points to snippet controls, noindex, and a Search Console setting that excludes a site from these features.

Google-Extended is often described as the way to keep your site out of Google's AI. That is only partly true, and the gap causes confusion in both directions: some sites block it expecting to disappear from AI Overviews and see no change, others avoid it for fear of losing search traffic. Google's own documentation is fairly specific about what each control does. Here is what it says, where the pages are not fully consistent, and what to check on your site.

On this page

What is Google-Extended?
Does blocking Google-Extended affect AI Overviews or AI Mode?
What does control whether you appear in AI Overviews and AI Mode?
What happens if I block Googlebot instead?
How do I check what Google sees on my site?
Where do I see AI Overviews traffic?

What is Google-Extended?

Google describes Google-Extended as a standalone product token that publishers can use in robots.txt. It has no crawler and no user agent string of its own; Google's existing crawlers fetch the pages, and the token controls how that content may be used.

According to Google's crawler documentation, it covers two uses: training future generations of Gemini models that power Gemini Apps and the Vertex AI API for Gemini, and grounding, meaning content from the Google Search index given to the model at prompt time, in Gemini Apps and in Grounding with Google Search on Vertex AI. The same page says Google-Extended does not affect a site's inclusion in Google Search and is not used as a ranking signal.

User-agent: Google-Extended
Disallow: /

Does blocking Google-Extended affect AI Overviews or AI Mode?

Google's documentation does not list AI Overviews or AI Mode among the uses Google-Extended controls. Google's guide to AI features says a page is eligible to appear as a supporting link in AI Overviews or AI Mode if it is indexed and eligible to be shown in Google Search with a snippet, with no additional technical requirements. It names robots.txt rules for Googlebot, not Google-Extended, as the control for crawling in Search.

So by Google's description, a page that Googlebot may crawl and index, and that may show a snippet, can still appear in AI Overviews and AI Mode when Google-Extended is disallowed.

There is one nuance worth stating plainly. Google's Search Console help page for its newer AI control says that to limit training of the models used to generate responses in Search's generative AI features, you should use Google-Extended. Google's crawler documentation for the token mentions only Gemini Apps and Vertex AI. The two pages describe the scope differently. Neither says that blocking the token removes a site from AI Overviews.

What does control whether you appear in AI Overviews and AI Mode?

Google documents these controls, from the narrowest to the broadest:

nosnippet: Google says this rule also prevents the content from being used as a direct input for AI Overviews and AI Mode. It also removes the normal text snippet in search results.
max-snippet: the length limit also applies to how much content may be used as a direct input for AI Overviews and AI Mode.
data-nosnippet: excludes marked parts of a page from snippets. Google's documentation of it does not mention AI Overviews or AI Mode specifically.
Search Console's Search generative AI setting: a site-wide control with Include, Exclude and, for child properties, Inherit options. Excluded content does not appear in AI Overviews, AI Mode or generative AI features in Discover, and gets no traffic or impressions from them. Google says it rolled the control out to all websites worldwide as of August 31, 2026, that exclusion typically takes effect within 1 to 2 days, and that it is not a ranking or inclusion signal for the rest of Search.
noindex or a Googlebot disallow: these take the page out of Google Search entirely, which removes it from the AI features too.

Google also says there is no special schema.org markup or other optimization required to appear in AI Overviews or AI Mode.

What happens if I block Googlebot instead?

Blocking Googlebot is the bluntest option. Google says crawl preferences addressed to it affect Google Search, including Discover and all Search features. A site that disallows Googlebot loses its normal search results along with its AI Overviews and AI Mode citations.

Few large sites do this. In our study of the robots.txt files of the 1,000 most popular domains, 94 of the 518 sites with a robots.txt (18.1%) disallowed the home page for Google-Extended, while only 14 (2.7%) did so for Googlebot. The study covers robots.txt rules for the home page only, and it cannot show what those sites expected the rule to do.

How do I check what Google sees on my site?

If your pages are missing from AI Overviews or AI Mode, work through the same chain as for normal search results:

Indexing: use the URL Inspection tool in Search Console to confirm the page is indexed and that Googlebot could fetch it.
Snippets: check the page's robots meta tag and X-Robots-Tag header for nosnippet, a small max-snippet value or noindex.
The Search generative AI setting in Search Console: check it for your domain property, and remember that child properties inherit from their parent by default.
robots.txt: make sure the Googlebot group, or the * group if there is no Googlebot group, allows the page. A Google-Extended group does not change this.
Firewall: make sure your CDN or bot protection does not block or challenge Google's crawlers. Verify Googlebot by reverse DNS or Google's published IP ranges before allowing it.
Rendering: Google renders JavaScript, but text in the initial HTML is still the safest choice, and it is what most other AI crawlers need.

Even when every check passes, Google decides which pages to show for each query. Being eligible is not the same as being shown.

Where do I see AI Overviews traffic?

Google says traffic from sites appearing in AI features is included in the overall search traffic in Search Console's Performance report. With the 2026 controls, Google also announced generative AI insights in Search Console, which show impressions and which pages appear in AI responses, and said more metrics would follow. You cannot see Google-Extended in your server logs, because it has no user agent of its own.

AISeeWhy checks your robots.txt for both Googlebot and Google-Extended, tests whether Google's crawler gets the same page as a browser, and reports nosnippet and noindex rules that would keep a page out of AI Overviews and AI Mode.

Frequently asked questions

Will blocking Google-Extended hurt my Google rankings?

Google says Google-Extended does not affect inclusion in Google Search and is not used as a ranking signal.

How do I keep my site out of AI Overviews but stay in Google Search?

Google offers a Search generative AI setting in Search Console that excludes a site from AI Overviews, AI Mode and generative AI features in Discover without affecting the rest of Search. nosnippet and max-snippet also limit use as a direct input, but they change normal snippets too.

Does the Search Console AI setting stop AI training?

No. Google's help page says the setting does not cover training and points to Google-Extended for that.

Do I need special markup to appear in AI Overviews?

Google says there are no additional requirements or special schema.org structured data needed. The page must be indexed and eligible to show a snippet.

Is Google-Extended a crawler I can block in my firewall?

No. It has no user agent of its own, so a firewall cannot see it. It only works as a robots.txt token. Blocking Google's actual crawlers at the firewall would affect Search.