Googlebot

Google · AI search indexer

Google Search's main crawler. Google publishes IP lists for Googlebot, its special crawlers and user-triggered fetchers.

User-agent contains
Googlebot
robots.txt token
Googlebot
Respects robots.txt
Yes, per operator docs
Official IP ranges
2,161 prefixes

How to verify Googlebot

Matching the user agent isn't enough, because any client can send it. A real Googlebot request comes from an IP address inside Google's published list:

The quickest way to check a whole log is our free log checker. It runs in your browser and splits Googlebot requests into real and fake.

First 20 prefixes
2001:4860:4801:10::/64
2001:4860:4801:11::/64
2001:4860:4801:12::/64
2001:4860:4801:13::/64
2001:4860:4801:14::/64
2001:4860:4801:15::/64
2001:4860:4801:16::/64
2001:4860:4801:17::/64
2001:4860:4801:18::/64
2001:4860:4801:19::/64
2001:4860:4801:1a::/64
2001:4860:4801:1b::/64
2001:4860:4801:1c::/64
2001:4860:4801:1d::/64
2001:4860:4801:1e::/64
2001:4860:4801:1f::/64
2001:4860:4801:20::/64
2001:4860:4801:21::/64
2001:4860:4801:22::/64
2001:4860:4801:23::/64

Block or allow Googlebot in robots.txt

User-agent: Googlebot
Disallow: /

Use Allow: / instead to explicitly permit it, or build a full file with the AI robots.txt generator. robots.txt is a request, not a lock: it only works for bots that honor it, and only real Googlebot traffic would.

Source: Google documentation

Verify Googlebot automatically

One API call tells your app, WAF or middleware whether a request claiming to be Googlebot really comes from Google's official IP ranges.

Get a free API key10,000 checks/month free · Pro $19/month for 1M

Other Google bots