Google-Extended: Does Blocking It Affect Google Search?

No. Blocking Google-Extended doesn't affect Google Search. Google says it "does not impact a site's inclusion in Google Search nor is it used as a ranking signal in Google Search". Google-Extended isn't a crawler at all: it's a robots.txt token that tells Google whether content it already crawls may be used to train future Gemini models and for grounding in Gemini Apps and Vertex AI. It does not control AI Overviews or AI Mode in Search; those follow the normal Googlebot and snippet rules.

What Google-Extended covers

From Google's common crawlers documentation:

Google-Extended is a standalone product token that web publishers can use to manage whether content Google crawls from their sites may be used for training future generations of Gemini models that power Gemini Apps and Vertex AI API for Gemini and for grounding (providing content from the Google Search index to the model at prompt time to improve factuality and relevancy) in Gemini Apps and Grounding with Google Search on Vertex AI.

Two points in there:

• Training of future Gemini models.
• Grounding in Gemini Apps and in Grounding with Google Search on Vertex AI: content from the Search index given to the model when it answers.

And it has no user agent of its own: "Google-Extended doesn't have a separate HTTP request user agent string. Crawling is done with existing Google user agent strings; the robots.txt user-agent token is used in a control capacity." You'll never see Google-Extended in your logs, and you can't block it in a firewall by user agent. robots.txt is the only switch.

What it doesn't cover

You want to control…	Google-Extended?	What to use
Gemini model training	Yes	User-agent: Google-Extended + Disallow: /
Grounding in Gemini Apps and Vertex AI	Yes	Same
Appearing in Google Search	No	Googlebot rules, noindex
AI Overviews and AI Mode in Search	No	nosnippet, data-nosnippet, max-snippet, noindex
Search ranking	No; "nor is it used as a ranking signal"	Nothing to do
AdSense	No	Mediapartners-Google rules

Google's AI features documentation is direct about AI Overviews: "AI is built into Search and integral to how Search functions, which is why robots.txt directives for Googlebot is the control for site owners to manage access to how their sites are crawled for Search." To limit what's shown, it points to nosnippet, data-nosnippet, max-snippet or noindex, and says nosnippet "will also prevent the content from being used as a direct input for AI Overviews and AI Mode" (robots meta tag). Those rules also shorten or remove your normal search snippet, so use them where you mean it.

How to block it

User-agent: Google-Extended
Disallow: /

Or only part of the site, as in Google's own example:

user-agent: Google-Extended
allow: /archive/1Q84
disallow: /archive/

Don't do this instead:

User-agent: Googlebot
Disallow: /

That removes your site from Google Search, including AI Overviews, and does nothing extra for Gemini training beyond what Google-Extended already does.

A noai meta tag isn't a substitute either. Google's list of supported robots meta values doesn't include it; the noai meta tag guide explains where it came from.

Should you block it?

It depends on what you want from Gemini. Blocking it keeps your content out of future Gemini training and out of grounding in Gemini Apps and Vertex AI, with no documented effect on Search. Allowing it means your pages can be used in those answers. No Google page we found says allowing Google-Extended brings traffic or rankings, so the choice is about how you want your content used. The should I block AI training bots guide covers the wider decision.

Plugins and platforms that add it

Several tools add a Google-Extended group for you:

• Yoast SEO Premium: Settings > Advanced > Crawl optimization > Block unwanted bots has a toggle for "Google Gemini and Vertex AI bots (or: Google-Extended bot)" (Yoast).
• Squarespace: the "Block known artificial intelligence crawlers" box adds Google-Extended among others (Squarespace).
• Cloudflare managed robots.txt includes Google-Extended in its list (Cloudflare).

Each of these writes a Google-Extended group. Check that none of them also adds a rule for Googlebot or User-agent: * that you didn't intend; the robots.txt precedence guide explains how the groups interact.

Google-Extended and AdSense

Blocking Google-Extended doesn't affect AdSense. The AdSense crawler is Mediapartners-Google, which only reads robots.txt groups that name it (robots.txt and AdSense). A free Approvalens scan checks that robots.txt doesn't block Mediapartners-Google or Googlebot.

Check your robots.txt

The free AI crawler checker shows whether Google-Extended and the other AI training tokens are allowed or blocked in your robots.txt, next to the AI search bots, so you can confirm you blocked training without touching search. Google-Extended has no user agent, so for it the check is robots.txt only; for bots that do have one, our page requests simulate their user agent from our server. The robots.txt tester checks Googlebot and Mediapartners-Google in the same file.

FAQ

Will blocking Google-Extended remove me from AI Overviews?

No. AI Overviews are part of Search and follow Googlebot and snippet controls. Use nosnippet if you want your content kept out of them, knowing it also affects your normal snippet.

Why don't I see Google-Extended in my logs?

It has no separate user agent. Google crawls with its normal crawlers and applies the Google-Extended rule when deciding how the content may be used.

Does Google-Extended affect Google Discover or News?

Google's documentation describes it only in terms of Gemini training and grounding, and says it doesn't affect inclusion in Google Search.

Can I block it in my firewall?

No. There's no request to block, since crawling is done with existing Google user agents. Blocking those would block Google Search.