Search Console gives you aggregate crawl stats, but it obscures page-level crawl frequency and hides the actual timestamped behaviour of the crawler. Server access logs are the only record of what actually happened — every line is a real HTTP request to your origin, recording exactly when a crawler hit a page, which user agent it used, and what status code came back.
Reading a log line
66.249.66.1 - - [30/Jul/2026:14:22:01 +0000] "GET /blog/javascript-hydration-seo HTTP/1.1" 200 45210 "-" "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)"
Three checks worth running
- 1Verify crawlers aren't spoofed. Fake scrapers routinely copy Googlebot's user-agent string. A reverse DNS lookup on the request IP will confirm whether it genuinely resolves to a Google-owned host.
- 2Cross-reference crawl frequency with page value. If your highest-converting category pages are crawled every couple of weeks while low-value tag archives get hit daily, your internal linking is misdirecting crawl priority — that's fixable, but only once you can see it.
- 3Filter for response-code anomalies. Repeated redirect hops and 5xx errors hit by a crawler both waste crawl budget and can suppress overall crawl rate if they persist.
Related articles
JavaScript Hydration & SEO: Why 'Rendered HTML' Still Fails Search Engines
"Google renders JS, so it's fine" misses two things: two-wave indexing, and AI crawlers that don't render JS at all. Here's where hydration actually breaks.
Debugging Crawl Budget Allocation on Large Sites
Crawl budget is capacity times demand. On large sites, most of the waste comes from a handful of repeatable structural mistakes.
Google Indexing API vs. IndexNow: A Practical Comparison
Passive sitemaps aren't enough for high-velocity publishing. Here's how the two push-based indexing protocols actually differ.
Monitoring AI Crawler Logs: SearchGPT, ClaudeBot, and Perplexity
A growing share of discovery is shifting to AI answer engines. Your log files already show whether they can see your site at all.

Written by
Paul Lovell
International SEO Consultant & Founder of Always Evolving SEO. 15+ years running technical audits, log-file analysis, and root-cause fixes for multimillion-dollar businesses — speaker at SMX London, Search & Content Summit, and SEMrush events.