Log Health Trends — Upload a .log to see Googlebot hits, 404 crawls and orphan pages | SEO-GEO
Stalled indexing and flat rankings often start at the crawl layer: Googlebot visits fade, 404s eat crawl budget, orphan pages burn fetch cycles. Upload one access log and three signal cards plus a trend chart show you the direction first.
The current build labels its numbers as mock data: a deterministic seed derived from file name and size keeps repeat uploads consistent so you can learn the metric definitions. When the real log-parsing engine ships, the page structure and metric definitions stay identical — only the data source changes, and the data nature is always labelled on the page.
What can you check or produce?
- Drag-and-drop .log / .txt upload, up to 10MB, Nginx & Apache
- Googlebot hit count with week-over-week delta
- 404 crawl volume and share, highlighted in red when heavy
- Orphan-page fetches: crawled pages with no internal inlinks
- Dual-line 7-day crawl-frequency trend chart
- Complements the paste-based Crawler Log Analyzer: that one maps multi-UA depth, this one tracks health trends
How should you interpret results and choose the next action?
The current build labels its numbers as mock data: a deterministic seed derived from file name and size keeps repeat uploads consistent so you can learn the metric definitions. When the real log-parsing engine ships, the page structure and metric definitions stay identical — only the data source changes, and the data nature is always labelled on the page. Reading the three core signals: Googlebot hits reflect real crawl activity; a high 404 share means crawl budget is being wasted on dead URLs; orphan-page fetches reveal pages with no internal links that only get indexed when a crawler stumbles onto them. If you need per-bot depth across GPTBot / PerplexityBot and other AI crawlers, use the Crawler Log Analyzer (paste log text, multi-UA detection) alongside this tool; both live under the Diagnose category and do not replace each other.
Frequently asked questions
Why the "mock data" badge?
The real log-parsing engine is still being wired in. Current stats are deterministically generated from file name and size to demonstrate the metrics; the page always labels the data nature and never passes demo numbers off as real.
Which log formats are supported?
.log / .txt access logs from Nginx and Apache, up to 10MB per file. Split larger logs by day first.
How is this different from the Crawler Log Analyzer?
That tool takes pasted log text and maps fetch depth across multiple user agents (Googlebot / GPTBot / PerplexityBot). This tool takes an uploaded file and focuses on three Googlebot health signals plus a 7-day trend. They complement each other.
By the 23SEOGEO team · Last updated: