Googlebot: robots token, verification and how to allow or disallow it
Googlebot is an AI crawler operated by Google. Its robots.txt token is Googlebot, and the vendor documentation we fetched on 2026-09-06 is the source for every statement on this page.
| Robots token | Googlebot |
|---|---|
| Vendor | |
| Purpose | search index |
| Documented verification | published IP ranges and reverse DNS |
| Vendor documentation last verified | 2026-09-06 |
| Share of read domains disallowing it for / | 0.8% of 128 |
| Last verified |
Identity
| Robots token | Googlebot |
|---|---|
| Matched as | googlebot |
| Vendor | |
| Purpose | search index |
| Documentation | https://developers.google.com/search/docs/crawling-indexing/googlebot |
| Documented verification | published IP ranges and reverse DNS: https://developers.google.com/static/search/apis/ipranges/googlebot.json (.googlebot.com, .google.com) |
Included because AI answers frequently ground on the Google index. The reverse DNS suffixes are the ones app/botverify.py already forward confirms.
Allow or disallow it
User-agent: Googlebot Allow: /
User-agent: Googlebot Disallow: /
A robots.txt rule is a request that a well behaved crawler honours. It is not an access control, and this page does not tell anyone what to choose.
Questions
Does Googlebot obey robots.txt?
The vendor documentation at https://developers.google.com/search/docs/crawling-indexing/googlebot states that Googlebot respects robots.txt. We fetched that page and it answered our checker on 2026-09-06. This records what the vendor documents, not what any individual request did.
How do I allow Googlebot in robots.txt?
Add this group to the robots.txt at the root of the host: User-agent: Googlebot Allow: /. The token is matched case insensitively as a substring of the user agent by RFC 9309, and the longest matching rule wins.
How do I disallow Googlebot in robots.txt?
Add this group to the robots.txt at the root of the host: User-agent: Googlebot Disallow: /. A robots.txt rule is a request that a well behaved crawler honours; it is not an access control.
How do I verify a request really came from Googlebot?
The vendor publishes both an IP range file (https://developers.google.com/static/search/apis/ipranges/googlebot.json) and a reverse DNS convention. Either check is documented; the address is what proves the request, never the user agent string.
What we measure
Of the 128 seeded domains whose robots.txt we have read, 1 disallow Googlebot for / and 127 allow it, which is 0.8% disallowed, week 2026-W37. Counts only: no domain is named.
The weekly AI crawler access index
Sources
| Source | Type | HTTP | Verified | Note |
|---|---|---|---|---|
| https://developers.google.com/search/docs/crawling-indexing/googlebot | vendor | 200 | 2026-09-06 | 35 occurrences of Googlebot in the common crawlers page fetched the same day |
| https://developers.google.com/search/docs/crawling-indexing/overview-google-crawlers | vendor | 200 | 2026-09-06 | crawler overview index page |
Free data
Check a domain against every token
AEO Watch is an independent, factual monitor. It is not affiliated with, endorsed by or speaking for any crawler vendor. Every statement is an observation with the date it was made and the raw evidence behind it: a robots.txt line, an HTTP status code, a header. There are no scores, no grades and no verdicts here, and nothing on this page is advice. A site opts out at any time and the opt out is honoured automatically and permanently.