The inspector finds five crawler claims, three 4xx responses and one 5xx response. It cannot tell that one Googlebot claim comes from a documentation-only address rather than a verified Google range.
The file is deliberately small and slightly deceptive
All addresses use IANA documentation ranges, all paths are invented and no person or production system appears in the sample. Eleven rows match the Apache Combined-style parser. One malformed line is intentional and must be reported as rejected.
The file contains two ordinary Googlebot strings, one Bingbot string, one GPTBot string and one copied Googlebot string attached to 203.0.113.77. The parser groups all five as crawler claims because it has no DNS or published-range verification step.
203.0.113.77 - - [28/Aug/2026:08:01:07 +0000] "GET /pricing HTTP/1.1" 200 1450 "-" "Googlebot/2.1 (+http://www.google.com/bot.html)"Expected local result
Run the sample without editing it. These counts are a deterministic check of the current parser, not an estimate.
- Accepted rows
- 11
- Rejected rows
- 1
- Unique addresses
- 8
- Claimed crawler requests
- 5
- 4xx responses
- 3
- 5xx responses
- 1
Download the sample from the next-step panel and use “Analyse locally”. Nothing in the file needs a live network request.
The useful finding is the mismatch, not the bot total
One Googlebot claim receives a 301 on /old-guide and the following request reaches /guides/new-guide with 200. That pair is evidence of two server responses. It does not prove that Google consolidated the URLs or indexed the destination.
Bingbot receives a 404 on /missing-product. GPTBot receives 429 on /api/export. Those are specific investigation leads: confirm whether the URLs should exist and whether the throttling rule is intended for that verified requester.
What the local parser cannot settle
The 203.0.113.77 row looks like Googlebot to a text classifier and stays labelled as a claim. To attribute it to Google, follow Google's current verification method using published ranges or reverse and forward DNS. The address in this synthetic file is reserved for documentation, so it is intentionally not a real Google crawler address.
The sample also cannot answer whether JavaScript rendered, whether a URL entered an index, which canonical an engine selected or why the 500 occurred. Each of those needs different evidence.
Reproduce the check
- Download the synthetic Combined-style access log.
- Open the Log File Inspector and load or paste the file.
- Run the local analysis and compare the six counts with the expected result above.
- Open the crawler table and keep all five rows labelled as claims.
- Use the operator-specific verification method before changing a firewall rule or publishing an attributed bot count.