GitHubDownload ZIP
301→302301→302
A temporary redirect where a permanent one belongs.
Found by Redirect checker →
redirect loopredirect loop
The URL redirects back to itself and never settles.
Found by Redirect checker →
Data sources

Server log file analyzer

Analyse Apache, Nginx and IIS access logs: which bots crawl where, which codes they get and how much budget is wasted, with optional bot verification by forward-confirmed reverse DNS.

View on GitHubQuick start
  • Terminal: seohead log-analyze

Server log file analyzer

Verify bots

--verify-bots checks authenticity via forward-confirmed reverse DNS.

Server log file analyzer

Budget waste

Where bot requests go compared with the pages you want crawled.

How it works

Three steps, one saved scan

  1. Point it at an access log

    Give it one Apache, Nginx or IIS W3C log file, plain or gzip-compressed. The format is detected from the first lines.

  2. Group requests by bot

    Hits, bytes, unique IPs, status codes and visited sections for each bot family, from Googlebot and Bingbot to AI crawlers and SEO tools.

  3. Verify bot identity

    With --verify-bots, each bot IP gets a forward-confirmed reverse DNS check: verified, failed or unavailable. A user agent alone is never taken as proof.

How to run it

One command

bash
seohead log-analyze --path ./access.log --verify-bots

Install first: installation guide. Every command also runs as an MCP tool for AI agents.

Learn more

From the blog and glossary

Server log file analysis for SEO: complete guide

Blog

Crawl Budget: a practical guide for large platforms

Blog

Log File Analysis

Glossary

Googlebot

Glossary
Data sources

More in this group

Google Search Console integration

Feature

GA4 and Yandex Metrika data

Feature

Yandex Webmaster integration

Feature

CrUX Core Web Vitals report

Feature

Backlink checker for known donors

Feature
FAQ

Questions

Server log file analyzer
No. The log is read from your disk and nothing is written. Only --verify-bots makes network requests, and those are DNS lookups for bot IPs.
Run with --verify-bots. The reverse DNS name must end in googlebot.com, google.com or googleusercontent.com, and resolve back to the same IP. If DNS is blocked, the tool reports verification as unavailable instead of marking every bot fake.
Apache and Nginx in Common or Combined format, and IIS W3C Extended. IIS columns are read from the #Fields line, so a changed field order still works. Gzip files are read directly.
Per bot family, the tool reports the share of 4xx and 5xx responses. Above 10% it notes that the family is wasting crawl budget. It does not compare bot hits with your sitemap or a list of URLs you want crawled.

Check your redirects locally

Download ZIPAll features