Google-Extended vs. Googlebot: what each one actually controls
Published 7/1/2026
Google operates Googlebot for Search indexing and
Google-Extended as a separate opt-out token for generative AI
training use (Gemini, Vertex AI). These are frequently confused because they come from the same
operator and are often configured in the same robots.txt file.
The decision
- Disallow
Googlebotonly if you want to leave Google Search entirely — this is rarely the right choice for a public website that depends on organic search traffic. - Disallow
Google-Extendedif you want to opt specific content out of generative AI training while keeping full Search visibility.
Common mistake CrawlPact flags
Copying a “block all AI” robots.txt snippet from a general audience article often disallows
Googlebot by accident, alongside AI-specific tokens. CrawlPact’s conflict detector raises this
as a high-severity finding when a preset that expects search visibility is combined with a rule
that blocks Googlebot.
Check which of the two your own site currently allows or blocks with the AI crawler checker.
Related guides
Amazonbot vs. Amzn-SearchBot vs. Amzn-User: which should you block?
Amazon documents three separate crawler tokens with different purposes and, critically, different robots.txt compliance. A decision guide for configuring each independently.
Applebot vs. Applebot-Extended: Search/Siri vs. Apple Intelligence
Apple separates its long-standing search crawler from a newer, generative-AI-specific opt-out token. A decision guide for telling them apart.
Blocking AI training while staying visible in AI search
Choosing between CrawlPact's presets when the goal is opting out of model training without losing AI-search discoverability.
See how this applies to your own site
Run a free audit to check your declared AI crawler policy against your own domain.
Audit a domain