# Fake Googlebot

Category: [Log Files](https://seo-geo-glossary.com/en/glossary/category/log-files/) › [Identifying & managing bots](https://seo-geo-glossary.com/en/glossary/category/log-files/identifying-managing-bots/)

A **fake Googlebot** is a client that identifies itself as Googlebot in the user agent but does not come from Google. Operators use the disguise to get past access rules that let search engine crawlers through, or to make scraping and probing look less suspicious.

## Why the user agent proves nothing

The user agent is a free-text HTTP header. Any client can write "Googlebot" into it. For real Google crawlers, the verification page points to the IP address and its reverse DNS name rather than the user agent string.

## How impostors are detected

Google describes two ways. In the manual way, a reverse DNS lookup on the IP from your log must return a name ending in `googlebot.com`, `google.com` or `googleusercontent.com`, and a forward lookup of that name must return the same IP. In the automatic way, you match the IP against the crawler ranges Google publishes as JSON.

Rule sets on the web server side use the same idea. The Fake Bot plugin for the OWASP Core Rule Set compares the user agent of large search engines with a reverse DNS lookup. It adds to an anomaly score and does not block on its own.

## Example

Two lines from a log (sample data) carry the same user agent but come from different addresses:

```txt
192.0.2.31 - - [06/Oct/2026:08:01:10 +0000] "GET /admin/ HTTP/1.1" 403 199 "-" "Googlebot/2.1"
198.51.100.7 - - [06/Oct/2026:08:01:12 +0000] "GET /products/ HTTP/1.1" 200 20412 "-" "Googlebot/2.1"
```

Only checking the IP addresses shows which of the two belongs to Google.

## Common mistakes

- **Tying exceptions to the user agent alone.** Rules that exempt "Googlebot" from rate limits, logins or bot protection then apply to anyone who writes that text into the header (a conclusion from the freely settable header).
- **Skipping the forward lookup.** Google requires that the forward lookup of the host name returns the original IP, not just a matching host name in the reverse lookup.
- **Counting fake requests in the analysis.** If a log analysis counts every line with a Googlebot user agent, impostors end up in the crawl statistics (practical experience).

## FAQ

**Can I block everything that calls itself Googlebot?** A block based on the user agent alone also hits real requests if the imitation looks identical. A decision based on verification is safer.

**How do I verify Googlebot?** Use reverse and forward DNS or Google's published IP ranges.

*Diagram: Is it really Googlebot?.* Both DNS lookups have to match. For large-scale lookups, Google recommends matching against its published IP lists automatically. Sample values from Google’s documentation.

## Related terms

- [Googlebot](https://seo-geo-glossary.com/en/glossary/googlebot/index.md)
- [Googlebot Smartphone](https://seo-geo-glossary.com/en/glossary/googlebot-smartphone/index.md)
- [Bot verification](https://seo-geo-glossary.com/en/glossary/bot-verification/index.md)
- [Crawler IP ranges](https://seo-geo-glossary.com/en/glossary/crawler-ip-ranges/index.md)
- [Reverse DNS lookup](https://seo-geo-glossary.com/en/glossary/reverse-dns-lookup/index.md)
- [User agent](https://seo-geo-glossary.com/en/glossary/user-agent/index.md)
- [Bot management](https://seo-geo-glossary.com/en/glossary/bot-management/index.md)
- [Bad bots](https://seo-geo-glossary.com/en/glossary/bad-bots/index.md)

## Sources

- [Verifying Google crawlers and fetchers – Google Search Central](https://developers.google.com/crawling/docs/crawlers-fetchers/verify-google-requests)
- [Introducing the Fake Bot Plugin – OWASP CRS](https://coreruleset.org/20220209/introducing-the-fake-bot-plugin/)
- [What is Googlebot (impostor)? – Crawler Zoo (secondary)](https://crawlerzoo.com/bots/fake-googlebot)

---

Last updated: October 8, 2026
URL: https://seo-geo-glossary.com/en/glossary/fake-googlebot/