Etoolio

Server Log AI-Crawler Analyzer

Free server log analyzer for AI crawlers. Upload an nginx or Apache access log to see how much traffic comes from GPTBot, ClaudeBot, PerplexityBot and others, and spot crawl-budget waste. 100% in your browser.

What the server log analyzer does

Upload your nginx or Apache access log and this tool shows, in seconds, how much of your traffic comes from AI crawlers versus search bots and real humans. It classifies each request by user-agent, GPTBot, ClaudeBot, PerplexityBot, CCBot, Bytespider, Googlebot and more, gives you an AI-traffic share, lists your most-crawled pages, and flags crawl-budget waste. Everything runs in your browser, so your log (which can contain IPs and URLs) is never uploaded.

Why analyse your logs

Your access log is the ground truth of who actually visits your site, no sampling, no JavaScript tracking gaps. As AI crawlers grow into a real share of web traffic, logs are the only reliable way to see them. And logs reveal problems analytics can't: crawlers wasting their budget on the wrong URLs.

Crawl-budget waste (the ?_rsc= trap)

Modern frameworks generate prefetch URLs, for example Next.js React Server Component requests ending in ?_rsc=. If crawlers spend their limited budget hammering those instead of your real pages, large parts of your site can go uncrawled and unindexed. This exact trap has silently derailed big migrations. The analyzer counts how many such requests are in your log and which paths they hit, so you can block *?_rsc=* in robots.txt if needed.

How to use it

  • Download your access log from your server (nginx: /var/log/nginx/access.log; Apache: /var/log/apache2/access.log).
  • Upload it here. It's parsed instantly on your device.
  • Read the report: AI-traffic share, per-bot counts, top pages, and any crawl-budget waste.

Good to know

  • Supports the standard Common and Combined Log Formats; unrecognised lines are skipped.
  • Nothing is uploaded, logs stay private on your machine.
  • Pair it with the AI Crawler Access Checker to control which of these bots you allow.

Good to know

Server Log AI-Crawler Analyzer, frequently asked questions

What does the server log analyzer do?

Upload your nginx or Apache access log and it classifies every request as a human, a search bot, an AI crawler (GPTBot, ClaudeBot, PerplexityBot, CCBot, Bytespider and more) or another bot. It shows your AI-traffic share, a per-bot breakdown, your most-crawled pages, and any crawl-budget waste, all in your browser.

What is crawl-budget waste?

It's when crawlers spend their limited requests on URLs that aren't real content, for example Next.js React Server Component prefetch URLs ending in ?_rsc=. If bots burn budget on those, your actual pages can go uncrawled and unindexed. The tool flags how many such requests appear in your log and which paths.

Which log format is supported?

The Common and Combined Log Formats used by default in nginx and Apache access logs (IP, timestamp, request line, status, size, referrer and user-agent). Lines that don't match are skipped, so it works on most standard access logs.

Is my log uploaded anywhere?

No. Logs can contain IP addresses and URLs, so everything is parsed locally in your browser. Nothing is uploaded or stored, which is the safe way to analyse server data.

Why should I care about AI crawler traffic?

AI crawlers are becoming a meaningful share of web traffic as AI answers grow. Knowing who crawls you, how often, and whether they waste budget helps you decide what to allow, what to block, and what to fix, using tools like the AI Crawler Access Checker.

Is it free?

Yes, completely free and unlimited with no signup, because the analysis runs on your device.