SEO · 8 min read
See What Googlebot Does Without a Log File Analyzer
Summary
Every result for log file analysis SEO sells you a tool. For a 60-page service site, Google's free Crawl Stats report covers the 90% that matters.
By Hyder Shah, Founder & CEO · Published July 13, 2026 · Updated July 13, 2026
Search log file analysis seo and every result is a tool vendor or a glossary entry. Screaming Frog's Log File Analyser, JetOctopus, Oncrawl, Botify. All of them are real products. None of them are your first move if you run a 60-page plumbing, dental, or law-firm site.
The reason 'log file analysis seo free' keeps showing up in related searches is that the demand is real and the SERP does not answer it. Here is the free answer, plus the honest line at which paying for a log analyzer starts to make sense.
What can you learn from server logs that Search Console won't tell you?
Raw logs give you one line per request — timestamp, IP, user agent, requested URL, status code, bytes — for every bot and human, with no sampling and no 90-day cap. Search Console's Crawl Stats gives you Googlebot only, aggregated, with a handful of example URLs per bucket.
That gap matters on a 500,000-URL ecommerce catalog with faceted navigation. On a service site with 60 pages, it mostly does not. Google says so itself in the Crawl Stats report documentation: 'This report is aimed at advanced users. If you have a site with fewer than a thousand pages, you should not need to use this report or worry about this level of crawling detail.'
Read that as permission, not a ban. The report is still the fastest free way to catch a server problem before it eats your rankings. Just don't buy a $250/year tool to look at a site Google can crawl in one afternoon.
| Signal | Raw server logs | GSC Crawl Stats |
| Every Googlebot hit, unsampled | Yes | No — aggregated, sample URLs only |
| AI crawlers (GPTBot, ClaudeBot, PerplexityBot) | Yes | No — Googlebot only |
| History beyond 90 days | Yes, as long as you retain logs | No — 90-day window |
| Setup cost | Host access, parsing, storage | Zero, already in your GSC |
Where is the Crawl Stats report and what does each chart mean?
Crawl Stats lives under Settings in Google Search Console, in the Crawling section, and it covers the last 90 days. One catch: it only exists on root-level properties — a Domain property or a root URL-prefix property. If your GSC property is a subfolder, you will not see it.
Three charts sit at the top, and four groupings sit below them. Each one answers a different question.
| Total crawl requests | How many URL fetches Googlebot made | Sudden collapse = discovery or availability problem |
| Total download size | Bytes Googlebot pulled | A spike with flat requests usually means bloated pages |
| Average response time | How fast your server answered Googlebot | Rising latency throttles future crawling |
| By response | 200s, 301s, 404s, 5xx | 5xx and 429 are the ones that hurt |
| By file type | HTML, image, JS, CSS, PDF | Mostly-image crawling means Google is not fetching your money pages |
| By purpose | Discovery vs Refresh | Near-zero Discovery = Google has found nothing new |
| By Googlebot type | Smartphone, desktop, image, video | Smartphone dominance is normal and expected |
Above the charts sits Host status. Google's documentation defines it as a 90-day availability check: green means 'Google didn't encounter any significant crawl availability issues on your site in the past 90 days,' yellow means issues happened more than a week ago, and red means issues inside the last week. Red is the only one that should ruin your morning.
Which three crawl patterns mean something is actually broken?
Three patterns are worth acting on inside 48 hours; the rest of the noise in that report is normal variance. Google's own crawl budget guidance explains why: 'If the site responds quickly for a while, the limit goes up, meaning more connections can be used to crawl. If the site slows down or responds with server errors, the limit goes down and Google crawls less.' Your server's behavior directly sets your crawl ceiling.
| Pattern | What you see in Crawl Stats | Usual cause | First thing to check |
| 5xx spike | By response shows a bar of 500/502/503 where there was none | Shared hosting under load, a plugin crash, a bad deploy | Host error logs for the same timestamps |
| Crawl requests collapse | Total requests drops sharply and stays down | robots.txt returned a 5xx or started disallowing, or the server got slow | Fetch /robots.txt yourself and check response time trend |
| Wrong-page crawling | Sample URLs are tag archives, /page/7/, ?filter= URLs | Thin auto-generated archives eating crawl attention | Your CMS archive settings and internal link count per page |
A one-day blip of 503s during a host maintenance window is not an emergency. A week of them is. If host status is red and your rankings dipped in the same window, the cause is your server, not your content — and no amount of blog posting fixes it. That is exactly the kind of thing a technical SEO audit is supposed to catch before it costs you a quarter.
Is Googlebot wasting its visits on pages that don't matter?
Open the 'By purpose' grouping and the sample URLs under 'By response.' If more than a handful of the URLs Google is fetching are tag pages, author archives, paginated blog listings, or URLs with tracking parameters, Googlebot is spending its visits on pages that will never win you a customer.
This is the one thing a small site genuinely gets wrong. A WordPress site with 60 real pages can easily expose 400 crawlable URLs once you count /tag/emergency-plumber/, /author/admin/, /2025/03/, and every ?utm_source variant a newsletter ever produced.
The fix is boring and it works: noindex the archives you don't need, remove the internal links that feed them, and make sure your XML sitemap contains only the pages you actually want ranked. Then watch whether the sample URLs in Crawl Stats shift toward your service and location pages over the next month. That shift is the whole scoreboard.
Does a 60-page site have a crawl budget problem?
Almost certainly not. Google's crawl budget documentation is explicit about who needs to care: 'Large sites (1 million+ unique pages) with content that changes moderately often (once a week)' and 'Medium or larger sites (10,000+ unique pages) with very rapidly changing content (daily).' A 60-page HVAC site is not in either bucket.
There is one exception in that same document, and it is the one that bites small sites: sites with 'a large portion of their total URLs classified by Search Console as Discovered - currently not indexed.' If half your URLs sit in that state, the problem is not budget — it is that Google looked at your site and decided the pages weren't worth fetching. That is a quality and authority problem, and it is covered in our guide on reading Search Console like an operator.
So when an agency tells a 60-page contractor they need a crawl budget optimization retainer, they are selling you an enterprise problem you do not have. Ask them to show you the Crawl Stats screenshot that proves it.
How do you see whether AI crawlers like GPTBot are hitting your site?
Search Console will never show you this — it reports Googlebot only. AI crawler hits show up in exactly two places: your host's raw access logs, or your CDN's analytics (Cloudflare, Fastly, Vercel all expose bot traffic by user agent). Grep the log for the user-agent token and count the lines. That is the entire technique.
The tokens worth grepping for, taken from each vendor's own published documentation:
| Token | Operator | What it does |
| GPTBot | OpenAI | Crawls content that may contribute to training foundation models |
| OAI-SearchBot | OpenAI | Powers ChatGPT's search features; opt out and you are not shown in ChatGPT search answers |
| ChatGPT-User | OpenAI | Fetches a page because a specific user's prompt required it |
| ClaudeBot | Anthropic | Collects web content that could contribute to model training |
| Claude-SearchBot | Anthropic | Crawls to improve the relevance and accuracy of search responses |
| PerplexityBot | Perplexity | Surfaces and links websites in Perplexity search results |
| Perplexity-User | Perplexity | Visits a page to answer a specific user question, with a link back |
The distinction matters when you decide what to block. OpenAI's bot documentation says disallowing GPTBot 'indicates a site's content should not be used in training generative AI foundation models' — while 'sites that are opted out of OAI-SearchBot will not be shown in ChatGPT search answers, though can still appear as navigational links.' Perplexity's docs draw the same line: PerplexityBot 'is not used to crawl content for AI foundation models,' it exists to link you in results.
Our position: block the training bots if you want to, but never block the search bots. A service business that blocks OAI-SearchBot and PerplexityBot to 'protect its content' has just opted out of the fastest-growing referral surface on the internet. That trade is covered in more detail on our GEO service page.
At what point is a paid log file analyser worth the money?
Roughly at 10,000 URLs, or the moment you can name a specific question Crawl Stats cannot answer. Below that, a paid analyzer tells you things you already know, and the setup cost — getting access logs off a managed host, parsing them, keeping them — is real work you are not being paid for.
Buy the tool when one of these is true. Otherwise, don't.
- You have 10,000+ URLs, or faceted/filtered URL generation you can't fully count
- You are mid-migration and need to prove Googlebot is following the new 301s, URL by URL
- A large share of your URLs sit in Discovered - currently not indexed and you need to know whether Google ever fetched them at all
- You need to audit AI crawler behavior over time, not just a one-off grep
- You must verify which bots claiming to be Googlebot are real, at scale
That last one has a free version. Google's Googlebot verification guide tells you to run a reverse DNS lookup on the IP, confirm the domain is googlebot.com, google.com, or googleusercontent.com, then run a forward lookup on that domain and confirm it resolves back to the same IP. Google also publishes IP range files (common-crawlers.json, special-crawlers.json, user-triggered-fetchers.json) if you want to automate it. Anything failing that check is a scraper wearing Googlebot's name.
For most service businesses the whole crawl question is 20 minutes a month in Crawl Stats and a periodic sanity check of what Google is actually fetching. If your host status is red, your crawl requests fell off a cliff, or half your URLs are stuck at Discovered - currently not indexed, that is a technical problem worth a real diagnosis — start with our SEO audit service or just Get my free audit and we'll tell you which of the three it is.
Where does this fit in your stack?
If you're running a US service business, the playbook in this post pairs with our full services lineup and applies cleanly across our supported industries and US locations. If you want help implementing it, book a free strategy call — we'll review your current setup and prioritize the next three moves.
For the deeper engagement details, see our SEO service. New to the terminology here? Our SEO & marketing glossary defines every acronym in this post.
What are the most common questions about this topic?
Common questions readers send us about this topic.
Do I need Screaming Frog Log File Analyser for a small site?
No. For a site under about a thousand pages, Google's own Crawl Stats documentation says you 'should not need to use this report or worry about this level of crawling detail' — and a paid log analyzer goes deeper than that report. The tools are good; they solve a scale problem you do not have. Revisit the decision at roughly 10,000 URLs, during a migration, or when you cannot explain why pages sit unindexed.
Where do I find Crawl Stats in Google Search Console?
Open Search Console, click Settings in the left sidebar, then find the Crawling section and open the Crawl stats report. It shows the last 90 days. One gotcha: the report is only available on root-level properties — a Domain property or a root URL-prefix property. If you set GSC up on a subfolder or subdomain path, the report will not appear and you need to add the root property.
How often does Googlebot crawl a small business website?
There is no fixed number, and anyone who gives you one is guessing. Google's crawl budget documentation says crawl rate is set by crawl capacity (how fast and reliably your server responds) and crawl demand (perceived inventory, popularity, and staleness). A fast, frequently updated site with links pointing at it gets crawled more. Look at your own Total crawl requests chart rather than a benchmark someone made up.
What does a spike in 5xx responses in Crawl Stats mean?
It means your server failed to answer Googlebot. Google states that when a site 'slows down or responds with server errors, the limit goes down and Google crawls less' — so a sustained 5xx spike actively reduces how much of your site gets crawled. Match the timestamps against your host's error log. Usual suspects are shared hosting under load, a crashing plugin, or a bad deploy. A single-day blip is not an emergency; a week of it is.
Can I see ChatGPT or Perplexity crawling my site?
Yes, but not in Search Console — that reports Googlebot only. Look in your host's raw access logs or your CDN's bot analytics and search the user-agent field for GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-SearchBot, PerplexityBot, and Perplexity-User. Each vendor publishes those tokens in its own bot documentation. Counting lines per token per week is a perfectly good free AI-crawler report.
Does a slow server reduce how often Google crawls me?
Yes, directly. Google's crawl budget guide says the crawl capacity limit rises when 'the site responds quickly for a while' and falls when the site slows down or returns server errors. Your Average response time chart in Crawl Stats is therefore a leading indicator: if it climbs and total crawl requests fall in the same period, your hosting is throttling your own crawl rate. Fix the server before you blame the content.
How do I verify a bot claiming to be Googlebot is real?
Run a reverse DNS lookup on the IP address from your log and confirm the domain is googlebot.com, google.com, or googleusercontent.com. Then run a forward DNS lookup on that domain name and confirm it resolves back to the same IP. Google documents exactly this two-step check, and also publishes IP range files (common-crawlers.json, special-crawlers.json, user-triggered-fetchers.json) for automating it. Anything that fails is a scraper spoofing the user agent.
Do I have a crawl budget problem on a 60-page site?
Almost certainly not. Google names two categories that need to care about crawl budget: sites with 1 million+ unique pages that change weekly, and sites with 10,000+ pages that change daily. A 60-page service site is in neither. The one exception Google flags is sites where a large portion of URLs are classified as Discovered - currently not indexed — that is a quality and authority signal, not a budget one.
About the author
Hyder Shah
Founder & CEO, Foundgrove
Hyder Shah is the founder of Foundgrove, an SEO and GEO agency for US service businesses. See our editorial policy for how these guides are researched and reviewed.
Related reading
Other tactical pieces from the Foundgrove blog.
- SEO · 12 min read
Google Search Console for Service Businesses: A 2026 Guide
Google Search Console shows the real queries you rank for, which pages get clicks, and what blocks indexing—use it to mine quick on-page wins, free.
Read the seo playbook → - SEO · 12 min read
Technical SEO Audit for Service Business Websites (2026)
Run a technical SEO audit on a small service site: fix Search Console indexation errors, validate schema, and pass Core Web Vitals first.
Read the seo playbook → - SEO · 8 min read
What Do Technical SEO Services Include? 2026 Scope & Costs
Agencies hide technical SEO pricing behind sales calls. Here is the real 2026 scope — audits, Core Web Vitals, schema — and what each should cost.
Read the seo playbook → - SEO · 8 min read
Discovered - Currently Not Indexed on a New Domain
Discovered - currently not indexed means Google skipped the crawl, not your content. Here is the crawl-demand fix for a fresh service-business domain.
Read the seo playbook → - SEO · 8 min read
Googlebot Blocked by robots.txt: Find and Fix It Fast
Blocked by robots.txt stops crawling, not indexing. Here is how service-business sites block themselves by accident, and the 60-second fix.
Read the seo playbook → - SEO · 8 min read
Cloudflare and SEO: What Helps, What Blocks Googlebot
Cloudflare speeds your site up and can quietly challenge Googlebot at the same time. Here is the settings-by-setting keep, kill, or audit list.
Read the seo playbook →
Want help applying this to your business?
Book a free 30-minute call. We'll review your current acquisition stack and show you the three highest-leverage moves for your industry and state. Or read how our SEO service works.