What is Google-Extended? How to allow or block Google's crawler

Google-Extended is Google's web crawler for collecting AI training data. Controls use of content for Gemini and Vertex AI training, separate from Googlebot.

As a robots.txt token rather than a crawler, honoring your directive is its entire function; Google documents it officially.

Add "User-agent: Google-Extended" followed by "Disallow: /" to your robots.txt file. The change takes effect the next time the bot fetches your robots.txt.

No. Google-Extended is separate from Googlebot, which handles Google Search indexing. Blocking Google-Extended has no effect on your traditional search rankings.

Search your server access logs for the string "Google-Extended" — for example: grep -i "Google-Extended" /var/log/nginx/access.log | wc -l. Our free AI Bot Log Analyzer does this in your browser: paste a log file and it counts hits per AI crawler, including Google-Extended, with per-path breakdowns.

You don't — Google-Extended isn't a tool you run. It's Google's own crawler, operated by Google, that visits your site from their infrastructure. The only control you have over it is whether you allow or block it, via robots.txt or a server rule. If you're looking to crawl other sites yourself, you'd write your own crawler or use a crawling library; sending "Google-Extended" as your user agent would be impersonating Google.

Almost certainly not. Crawl-delay was never part of the original robots.txt specification — Google has publicly said it ignores the directive, and the AI crawlers that model their parsers on Google's do the same. Google publishes no position on crawl-delay for Google-Extended, so treat it as unsupported. If Google-Extended is hitting your site harder than you want, rate-limit it at the server or CDN instead: a Cloudflare rate-limiting rule or an nginx limit_req zone matched on the user agent will actually be enforced, whereas a crawl-delay line is only a request that this agent likely never reads.

Google states Google-Extended honors robots.txt, so if you are still seeing hits the cause is usually one of four things rather than the bot misbehaving. First, robots.txt is cached — Google may be working from a copy fetched up to 24 hours before your change. Second, the rule may not match: robots.txt user-agent matching is on a prefix of the token, and a typo or a trailing character breaks it silently. Third, the block may sit under a different user-agent group than the one this bot reads, since a bot obeys only the most specific group that matches it, not the wildcard group as well. Fourth, the traffic may be something else sending Google-Extended as its user agent, which anything can do.

Treat it as no unless Google says otherwise. Rendering JavaScript costs an order of magnitude more than fetching HTML, and most AI crawlers — unlike Googlebot, which runs a full headless Chrome — read the raw HTML response and stop there. The practical consequence: anything your page loads client-side after the initial response is likely invisible to Google-Extended. If your main content is client-rendered, server-render it or pre-render it so the text exists in the first response.

Google publishes them as JSON at https://developers.google.com/static/crawling/ipranges/common-crawlers.json, updated as their infrastructure changes. Fetch that file rather than hard-coding the prefixes, and match the request IP against it to confirm a visit is genuinely Google-Extended. This is the only reliable check — the user-agent header is self-declared, so a scraper can send "Google-Extended" while coming from anywhere.

There is no published schedule, and no operator commits to one. Training crawlers like Google-Extended typically sweep in bursts rather than at a steady rate — quiet for weeks, then hundreds of requests over a day or two as a collection run reaches your domain. Larger and more-linked sites are revisited more often. The only way to know for your own site is to measure it: grep your access log for the user agent, or paste the log into our AI Bot Log Analyzer, which breaks hits down by date and path in your browser.

Google publishes it at https://developers.google.com/search/docs/crawling-indexing/overview-google-crawlers. That page is the authoritative source for the user-agent string and Google's stated crawling policy, and Google also publishes Google-Extended's IP ranges as JSON at https://developers.google.com/static/crawling/ipranges/common-crawlers.json so you can verify requests rather than trusting the header.