Does Google-Extended Affect Google Search, Gemini, or AI Overviews?
Google-Extended is a robots.txt product token for certain Gemini training and grounding uses. Google says it does not affect Search inclusion or Search ranking.
Does Google-Extended Affect Google Search, Gemini, or AI Overviews?
Google-Extended should not be used as a Search opt-out: Google documents it as a standalone product token for certain Gemini training and grounding uses, while Googlebot and normal Search preview controls govern Google Search and its AI features.
Evidence: Google — common crawlers and Google-Extended · Google Search Central — AI features and publisher controls · Google — verify crawler and fetcher requests
Read this alongside Build search systems you can verify.
Google-Extended is easy to misread because its name looks like a crawler. Google says it has no separate HTTP User-Agent string. It is a robots.txt product token that tells Google whether content it crawls may be used for certain Gemini model training and grounding uses.
Google also says Google-Extended does not affect whether a site is included in Google Search and is not used as a Search ranking signal. That means it is not the right control for removing a site from Google results, AI Overviews, or AI Mode.
Scope and assumptions
Google changes product documentation over time. This note reports the documented scope of Google-Extended and Search AI controls as checked September 23, 2026. It does not claim that robots.txt can stop content already indexed from every downstream product use.
- Separate HTTP UA
- NO
- Affects Search inclusion
- NO, PER GOOGLE
- Search ranking signal
- NO, PER GOOGLE
- Gemini uses
- TRAINING + GROUNDING CONTROLS
What Google-Extended controls
Google documents Google-Extended as a publisher control for whether crawled site content can be used to train future generations of Gemini models powering Gemini Apps and the Vertex AI API for Gemini, and for specified grounding uses involving the Google Search index.
Because the token has no independent HTTP User-Agent, you should not expect a distinct “Google-Extended” request line in access logs. The control is read from robots.txt and applied within Google’s product systems.
What it does not control
Google explicitly says Google-Extended does not affect inclusion in Google Search and is not a Search ranking signal. Blocking it should therefore not be described as blocking Googlebot or opting out of organic Search.
If the goal is to prevent Google from crawling or indexing a page, use the normal Search mechanisms appropriate to that goal, such as robots.txt for crawl control, noindex for indexing control, or authentication for private content.
AI Overviews and AI Mode are Google Search features
Google’s Search documentation treats AI Overviews and AI Mode as Search features. Pages must be eligible for normal Google Search crawling and indexing to participate, and Search preview controls such as nosnippet can affect what Google displays.
So the important distinction is product boundary: Google-Extended is a Gemini-related publisher token; Googlebot and Search controls determine Search participation, including Search’s AI presentation layers.
Why log analysis cannot find a Google-Extended bot
There is no separate Google-Extended request User-Agent to count. Access logs will show the Google crawler/fetcher that actually made a request, not the product token Google later applies to downstream uses.
For Google crawler identity, Google publishes IP-based and DNS verification methods. Apply those to the actual request identity, then evaluate Google-Extended as a robots policy state rather than a network identity.
Google-Extended and Google Search are separate controls
Blocking Google-Extended does not remove a site from Google Search or act as a Search ranking signal according to Google. AI Overviews and AI Mode are Search features governed through normal Google Search crawl, index, and preview controls rather than a separate Google-Extended crawler.
Sources
- Google — common crawlers and Google-Extended
Verified Sep 23, 2026
- Google Search Central — AI features and publisher controls
Verified Sep 23, 2026
- Google — verify crawler and fetcher requests
Verified Sep 23, 2026
Supporting material
- AI crawler robots.txt policy guide
Copy-ready policy patterns for separating search discovery, training crawlers, and user-triggered fetchers.
- robots.txt access-control boundary
Why crawler policy is not authentication or authorization, with RFC 9309 context.