Googlebot and robots.txt: the token, the rules, and how to verify a request

Googlebot obeys robots.txt. Control it with `User-agent: Googlebot`, but blocking it stops Google Search from crawling your pages; Google-Extended is the separate AI token. Google says its common crawlers "always obey robots.txt rules when crawling automatically", so a wrong rule costs you traffic, and a request that only claims to be Googlebot has to be verified by reverse DNS or IP range.

By the Crawlerpeek editorial team · Updated · How we check

Does Googlebot obey robots.txt?

Yes. Google's list of common crawlers, which includes Googlebot, says they "always obey robots.txt rules when crawling automatically". Google reads the file at the top of each host, caches it for up to 24 hours (longer if it cannot refresh it), and ignores content after 500 KiB. (Sources: Google, List of Google's common crawlers and How Google interprets the robots.txt specification, read 26 October 2026.)

Google's user-triggered fetchers are a different group. Google says that because the end user triggers the fetch, they ignore robots.txt rules. That is why Googlebot rules do not cover, for example, Google Site Verifier.

Which robots.txt token controls Googlebot?

TokenAffects, per Google
GooglebotGoogle Search, including Discover and all Search features, and other products such as Google Images, Video mode, Google News and Discover
Googlebot-ImageCrawling for image search; Google lists it as its own token
Google-ExtendedWhether content Google crawls may be used to train future Gemini models and for grounding in Gemini Apps and Vertex AI; it "does not impact a site's inclusion in Google Search"

You need to match only one of a crawler's tokens for a rule to apply, and a more specific token wins. Google's own example: with groups for googlebot-news, * and googlebot, Googlebot News follows the googlebot-news group and Googlebot (web) follows the googlebot group. Groups for a named crawler are not combined with the * group. The general rules are in robots.txt explained.

What is the robots.txt for Googlebot?

Allow everything for Googlebot while blocking one directory for other crawlers:

User-agent: Googlebot
Allow: /

User-agent: *
Disallow: /private/

Block a section from Googlebot only (Google's example syntax uses Allow for an exception inside a blocked path):

User-agent: Googlebot
Disallow: /archive
Allow: /archive/1Q84

When rules conflict, Google applies the most specific rule by path length, and for ties the least restrictive one. Paths are case-sensitive. Disallow: / under User-agent: Googlebot blocks the whole site from Search crawling.

Does Googlebot have anything to do with AI?

Yes, indirectly. Google says AI is built into Search, which is why robots.txt directives for Googlebot are the control for how your site is crawled for Search, including AI Overviews and AI Mode. To limit how much of a page shows in Search, Google points to nosnippet, data-nosnippet, max-snippet and noindex. To limit AI training and grounding in some of Google's other systems, it points to Google-Extended. (Source: Google, AI features and your website, read 26 October 2026.) So the choice is not symmetrical: blocking Google-Extended leaves Search and its AI features alone, while blocking Googlebot stops Search from crawling your pages. See the Googlebot and Google-Extended pages for each in short.

How do I check that a request really is Googlebot?

The user-agent string can be spoofed, Google warns. Google offers two methods. For one-off lookups, run a reverse DNS lookup on the address in your log, check that the name ends in googlebot.com, google.com or googleusercontent.com, then run a forward lookup on that name and confirm it returns the original address. For large scale, compare the address with Google's published JSON ranges.

TypeReverse DNS maskIP ranges filerobots.txt
Common crawlers (Googlebot)crawl-***-***-***-***.googlebot.com or geo-crawl-***-***-***-***.geo.googlebot.comcommon-crawlers.jsonAlways obeyed for automatic crawls
Special-case crawlersrate-limited-proxy-***-***-***-***.google.comspecial-crawlers.jsonMay or may not be
User-triggered fetchers***-***-***-***.gae.googleusercontent.com or google-proxy-***-***-***-***.google.comuser-triggered-fetchers.json, user-triggered-fetchers-google.json, user-triggered-agents.jsonIgnored

Googlebot Smartphone and Desktop send these user agents (Chrome version shown as W.X.Y.Z): Mozilla/5.0 (Linux; Android 6.0.1; Nexus 5X Build/MMB29P) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/W.X.Y.Z Mobile Safari/537.36 (compatible; Googlebot/2.1; +http://www.google.com/bot.html) and Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; Googlebot/2.1; +http://www.google.com/bot.html) Chrome/W.X.Y.Z Safari/537.36. The IP checker and the user-agent lookup help with a single line from your log.

How often is the name Googlebot faked?

On four small sites on one server, 1,785 requests naming Googlebot between 19 and 25 October 2026 came from addresses in Google's published IP lists and 81 (4.3 percent) did not. Those 81 are requests that borrowed the name. The result describes new, small sites in one week; it does not give a rate for yours. The method and a script are in the 48-hour log study.

How do I test whether my robots.txt blocks Googlebot?

Enter a page address in the checker. It evaluates your robots.txt for 24 crawlers, Googlebot and Bingbot among them, and shows which may fetch that page. A missing robots.txt allows everything. If Googlebot is allowed but pages are still missing from Google, see why Google may not be crawling your site and the usual robots.txt mistakes.

Checked 26 October 2026

Sources are Google's pages on common crawlers, verifying Google crawlers, the robots.txt specification and AI features, all read on 26 October 2026. We paraphrase and quote short phrases. Google can change them. The request counts are our own aggregates of four small sites on one server, addresses counted and not stored.

Follow-up questions

Does Googlebot obey robots.txt?

Yes. Google says its common crawlers, including Googlebot, always obey robots.txt rules when crawling automatically. Its user-triggered fetchers ignore robots.txt because a user requested the fetch.

Does blocking Googlebot stop Google using my content for AI?

It stops Google crawling the page for Search, and Google says robots.txt directives for Googlebot are the control for how your site is crawled for Search, where AI Overviews and AI Mode are built in. It also stops Search from crawling your pages. To limit AI training and grounding in some other Google systems, Google points to Google-Extended, which does not affect Search.

What is the robots.txt token for Google Search?

Googlebot. Its rules affect Google Search including Discover and all Search features, and other products such as Google Images, Video mode and Google News.

How do I verify a Googlebot request?

Run a reverse DNS lookup on the address, check that the host ends in googlebot.com, google.com or googleusercontent.com, run a forward lookup on that host and confirm it returns the same address. Or compare the address with Google's common-crawlers.json.

How long does Google take to see a robots.txt change?

Google generally caches robots.txt for up to 24 hours, and may cache it longer when it cannot refresh it, for example after timeouts or 5xx errors.

See how your own site does.Run the checker

Keep reading