Google-Extended is a specific user-agent token that acts as a granular opt-out mechanism, entirely separate from the general Googlebot indexer. By adding a User-agent: Google-Extended directive with a Disallow rule in a site's robots.txt file, webmasters can explicitly block Google's crawlers from scraping their content for the purpose of improving Bard and Vertex AI foundation models, without affecting the site's appearance in standard Google Search results.
Glossary
Google-Extended

What is Google-Extended?
Google-Extended is a standalone product token used in robots.txt to control whether a site's content can be used to train Google's generative AI models, including Bard and Vertex AI.
This token addresses the critical distinction between search indexing and generative AI training data ingestion. Unlike broad IP-based blocks that risk disrupting legitimate search traffic, Google-Extended provides surgical control over model training consent. It represents a shift toward transparent, crawler-level governance where a single Disallow: / directive prevents proprietary text and images from being incorporated into the weights of Google's commercial generative systems.
Key Features of Google-Extended
Google-Extended is a discrete user-agent token that governs content ingestion specifically for Google's generative AI model training, operating independently from the standard Googlebot indexer.
Independent Crawler Identity
Google-Extended functions as a standalone product token, completely separate from the primary Googlebot crawler. This architectural separation allows site owners to permit standard search indexing while explicitly blocking AI training ingestion. The token is transmitted in the User-Agent HTTP header and can be targeted directly within robots.txt directives without affecting a site's presence in Google Search results.
Robots.txt Governance
Control is implemented through the Robots Exclusion Protocol using a dedicated user-agent record. The directive User-agent: Google-Extended followed by Disallow: / blocks all generative AI training ingestion across the entire domain. Granular path-level control is supported, allowing organizations to expose public documentation while protecting proprietary code repositories or premium content archives from model training.
Model Training Scope
This token specifically governs content used to train Bard (now Gemini) and Vertex AI foundation models. It does not control:
- Standard search indexing (handled by Googlebot)
- Google News or Discover crawling
- Google AdsBot or other marketing crawlers
- Image or video search indexing The token's scope is narrowly defined to generative AI training pipelines, providing precise opt-out granularity.
Verification via Reverse DNS
Authentic Google-Extended crawler traffic can be verified through forward-confirmed reverse DNS lookup. Requests originate from IP addresses that resolve back to hostnames within the *.googlebot.com or *.google.com domains. This verification mechanism prevents spoofed User-Agent strings from bypassing robots.txt directives, ensuring that only legitimate Google infrastructure respects the crawl rules.
No Indexing Side Effects
Blocking Google-Extended has zero impact on search visibility. Unlike disallowing Googlebot, which removes pages from search results, restricting Google-Extended only prevents content from being used in generative AI training datasets. This decoupling was a direct response to publisher concerns that opting out of AI training would harm organic search performance, a fear that is explicitly unfounded with this token architecture.
Implementation Precedence
Google-Extended respects standard robots.txt precedence rules. The most specific matching directive applies, and the crawler honors Disallow, Allow, and Crawl-delay directives. Unlike some AI crawlers that ignore robots.txt entirely, Google-Extended is a compliant implementation of the Robots Exclusion Protocol. The token was publicly announced in September 2023 as part of Google's commitment to transparent AI data governance.
Frequently Asked Questions
Clear answers to the most common technical and strategic questions about the Google-Extended user-agent token and its role in controlling generative AI ingestion.
Google-Extended is a standalone user-agent token that acts as a specific directive for controlling whether a website's content can be used to train Google's generative AI models, including Bard and Vertex AI foundation models. It operates entirely independently from the standard Googlebot crawler, which handles indexing for Google Search. When a web server receives a request with the Google-Extended user-agent string, it checks the site's robots.txt file for rules targeting this specific token. If the path is disallowed, Google's AI training pipeline will not ingest that content, even if the same content remains accessible to the general search indexer. This separation allows content owners to maintain search visibility while opting out of contributing to Google's generative model training corpus.
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Google-Extended vs. Googlebot vs. GPTBot
A technical comparison of Google's general indexer, Google's AI training crawler, and OpenAI's training crawler across access control, purpose, and identification attributes.
| Feature | Google-Extended | Googlebot | GPTBot |
|---|---|---|---|
Primary Purpose | Training generative AI models (Bard, Vertex AI) | Indexing web pages for Google Search | Training and improving OpenAI generative models |
User-Agent Token | Google-Extended | Googlebot | GPTBot |
Full User-Agent String | Google-Extended | Googlebot/2.1 (+http://www.google.com/bot.html) | Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko); compatible; GPTBot/1.0; +https://openai.com/gptbot |
Respects robots.txt | |||
Respects noindex | |||
Respects noarchive | |||
Crawl Frequency | Variable; lower volume than Googlebot | High; continuous recrawling based on PageRank | Variable; on-demand based on training corpus needs |
IP Range Documentation | Published in Google's crawler IP list | Published in Google's crawler IP list | Published at openai.com/gptbot |
Reverse DNS Pattern | crawl----.googlebot.com | crawl----.googlebot.com | No standardized rDNS pattern published |
Content Usage | Generative AI model training only | Search index, featured snippets, knowledge graph | Foundation model pre-training and fine-tuning |
Opt-Out Mechanism | Disallow in robots.txt | Disallow in robots.txt or noindex meta tag | Disallow in robots.txt |
Caching Behavior | Does not cache for public search | Caches pages for search result snippets | Ingests content into training corpus; no public cache |
Impact on Search Visibility | None; blocking does not affect ranking | Direct; blocking prevents indexing and ranking | None; blocking does not affect search visibility |
First Documented | September 2023 | Original Google crawler; operational since 1998 | August 2023 |
Related Terms
Understanding Google-Extended requires familiarity with the broader landscape of AI crawler identification, access control protocols, and the specific bots used by major model providers.
User-Agent String
A text string sent by a web client in the HTTP request header that identifies the browser, operating system, and rendering engine to the server. It serves as the primary mechanism for crawler self-identification. Google-Extended appears as a token within Google's broader user-agent structure, allowing granular control. Server-side parsing of user-agent strings enables:
- Conditional access rules per bot
- Logging and audit trail generation
- Traffic pattern differentiation between indexers and AI scrapers
AI Training Bot
A specialized web crawler explicitly designed to scrape and ingest large volumes of internet text, images, and structured data for the purpose of pre-training or fine-tuning foundation models. These bots differ from search indexers in key ways:
- They prioritize content completeness over freshness
- They often execute JavaScript to capture dynamic content
- They may ignore caching directives that search bots respect
- They target diverse file types including PDFs, JSON, and media Google-Extended is a canonical example of a training-specific bot token.
Crawler Allowlist
A curated list of verified bot signatures, IP ranges, and user-agent tokens that are explicitly permitted to access a web property. This approach inverts the default-deny posture common in bot management. For AI governance:
- Googlebot (search) may be allowed while Google-Extended (training) is blocked
- Legitimate partners like Internet Archive can be selectively permitted
- Unknown or spoofed user-agents are rejected by default Allowlists provide stronger security than robots.txt alone but require ongoing maintenance as new AI crawlers emerge.

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us