How to verify Googlebot
The Googlebot user agent is widely spoofed, so a request claiming to be Googlebot should be verified, not trusted. Google documents two methods: a reverse-DNS check that resolves into googlebot.com or google.com confirmed by a matching forward lookup, and matching the source IP against Google's published crawler IP ranges.
The two verification methods
Google documents two ways to confirm Googlebot. The first is reverse DNS: look up the source IP and confirm the hostname resolves into googlebot.com or google.com, then run a forward lookup on that hostname and confirm it returns the original IP. Both directions must match.
The second is IP matching: Google publishes downloadable lists of its crawler IP ranges. A genuine Googlebot request originates from one of those ranges. This is useful when you want to verify without per-request DNS lookups.
- Reverse DNS must resolve into googlebot.com or google.com
- Forward lookup must return the original IP (both directions)
- Or match the IP against Google's published crawler ranges
Why this matters
Scrapers and abusive clients routinely copy the Googlebot user-agent string to slip past rules that allow search crawlers. If you make decisions — serving full content, relaxing rate limits, trusting log entries — based on the string alone, you can be fooled.
Verification turns a claim into a fact. Apply it especially before any decision where treating a fake Googlebot as real would cause harm, such as bypassing a paywall or rate limit.
How it appears in analytics and logs
A user agent that says Googlebot is only a claim. Verification tells you whether the request truly came from Google's infrastructure. An unverified Googlebot string from outside Google's ranges is fake Googlebot — common from scrapers trying to bypass blocks.
Diagnostic use case
Confirm a request that claims to be Googlebot is genuinely Google before trusting it for log analysis, access decisions, or serving behaviour.
What WebmasterID can help detect
WebmasterID classifies crawlers server-side and separates verified search crawlers from spoofed ones, so you can see genuine Googlebot coverage without manually running DNS checks on every request.
Common mistakes
- Trusting the Googlebot user-agent string without reverse-DNS or IP verification.
- Doing only a reverse lookup and skipping the forward-confirm step.
- Hardcoding IPs instead of using Google's published, updated ranges.
Privacy and accuracy notes
Verification operates on the request's IP and DNS records, not on any human identity — a crawler is not a person. WebmasterID treats verified crawlers as bot events kept out of human analytics.
Frequently asked questions
- Is reverse DNS or IP matching better for verifying Googlebot?
- Both are valid and Google documents both. Reverse DNS needs no maintained list but adds a per-request lookup; IP-range matching avoids lookups but requires keeping Google's published ranges current. Many operators combine them.
Related pages
- Googlebot Smartphone — Google's mobile-first crawler
Googlebot Smartphone is the mobile user-agent variant of Googlebot and, under mobile-first indexing, Google's primary crawler for most sites. It uses the Googlebot robots.txt token and can be verified through reverse DNS and Google's published crawler IP ranges.
- How to verify Bingbot
The Bingbot user agent is commonly spoofed, so a request claiming to be Bingbot should be verified rather than trusted. Microsoft documents a reverse-DNS method: the source IP should resolve into search.msn.com, confirmed by a forward lookup back to the same IP. Bing also publishes IP information for verification.
- Fake search-bot traffic
Because search-engine crawlers are widely allowed, abusive clients copy the Googlebot or Bingbot user-agent string to slip past rules meant for real crawlers. This fake search-bot traffic is identified by verifying the source: genuine crawlers pass reverse-DNS and published-IP checks, spoofed ones do not.
- Bot intelligence
Verified crawler classification separated from human traffic.
Sources and verification notes
- Google — Verifying Googlebot and other crawlersDocuments reverse-DNS verification and published crawler IP ranges.
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.