AI crawler log analysis: which bots fetch your pages, and which they skip
An AI crawler log analysis tool reads your server or CDN access logs and reports which AI crawlers fetched which pages, how often, and what status they got back. Attensira’s crawler logs do the same at your edge, where JavaScript never runs, so you can separate crawl coverage from citation rates on the questions you track.
7 days free · card required
- Meta · Meta-ExternalAgentTraining
- 126,349 · 866 pages
- OpenAI · GPTBot, OAI-SearchBot, ChatGPT-User86% search index, 11% training, 3% live answer
- 7,465 · 428 pages
- ByteDance · BytespiderTraining
- 3,344 · 121 pages
- Perplexity · PerplexityBotSearch index
- 621 · 331 pages
- Anthropic · ClaudeBot, Claude-User66% search index, 34% live answer
- 103 · 48 pages
- Google AI Overview, GeminiNo visits seen in the window
- 0
Agents are as each request named itself; none is presented as verified.
Analystattensira.com workspace, read over the Attensira MCP · · 30 days
Analyst · Reads which pages bots fetch, and flags tracked questions whose pages no crawler reaches.
Researcher · Turns pages bots fetch with no prompt behind them into questions worth tracking.
What should a log analysis report, in order?
Whether you use a one-off log parser or continuous edge logging, the same fields answer whether AI bots can reach the pages you care about.
Identity
Which named crawler made the request, verified against the operator’s published IP ranges — a user-agent string alone is easy to spoof.
Coverage
Which URLs were fetched. A page that should answer a tracked question and was never fetched is a different problem from one that was fetched and passed over.
Outcome
Status codes per crawler. A wall of 403 responses is usually robots.txt or a WAF, not a content-quality problem.
Volume and spoofing
Requests over time, by site section, plus hits from addresses outside the operator’s published ranges.
What does one line of the log say?
When the request came, which agent it named, which page it asked for and what the site answered. A page that answers a crawler with a 403 or a redirect is worth checking first: robots rules, a login wall or a moved URL.
| Time | Agent | Path | Status |
|---|---|---|---|
| OAI-SearchBot, operated by OpenAI | /pricing | 200 | |
| ChatGPT-User, operated by OpenAI | /compare/ledgerly-vs-invoicely | 200 | |
| ClaudeBot, operated by Anthropic | /guides/vat-on-invoices | 403 | |
| PerplexityBot, operated by Perplexity | /blog/invoice-numbering-rules | 200 | |
| GPTBot, operated by OpenAI | /old-pricing | 301 |
Which log analysis tools are worth knowing?
These are the tools answer engines name when buyers ask for AI crawler log analysis. Each reads a different surface; pick the one that matches where your traffic is logged.
| Tool | What it reads | Best for | |
|---|---|---|---|
| Cloudflare AI Crawl Control | Cloudflare AI Crawl Control | Cloudflare edge logs | Sites already on Cloudflare; separates training crawlers from answer crawlers |
| Crawl Lab | Crawl Lab | Apache or Nginx logs, parsed in the browser | A first look without uploading the log file |
| Screaming Frog Log File Analyser | Screaming Frog Log File Analyser | Large log files, desktop | Big datasets and URL-level crawl analysis |
| LogLens | LogLens | Cloudflare, Apache and Nginx logs | Continuous monitoring with crawler verification |
| Attensira crawler logs | Attensira | Your edge middleware | Ongoing AI traffic beside prompt tracking, with pages no bot reached flagged |
What do crawler logs not prove?
Training crawlers and answer crawlers are not the same visit. GPTBot and ClaudeBot often collect for training; OAI-SearchBot, PerplexityBot and Claude-SearchBot fetch so an answer can cite a source. Being crawled for training does not mean you will be quoted.
- A crawl is not a citation. Report crawl coverage and citation rates separately, or a healthy log reads like a win when answers still ignore you.
- User agents are self-reported and easy to spoof unless you verify IP ranges.
- Nothing appears until a crawler fetches a page; on a low-traffic site that can take days.
- Browser analytics never sees AI crawlers; only server or edge logging can.
Why did each crawler fetch the site?
Volume alone does not say which fetches can lead to an answer. The traffic log labels each request by why that user agent fetches: training, search indexing or a live answer.
- of OpenAI's requests were search indexing
- 86%
- n=7,465 requests
- of Anthropic's requests fetched for a live answer
- 34%
- n=103 requests
- of Meta-ExternalAgent's requests were training
- 100%
- n=126,349 requests
Analyst · Labelled every requestattensira.com AI traffic log, read over the Attensira MCP on 4 Oct 2026 · labelled by the user agent each request claimed · to What else do people ask about crawler logs?
What is an AI crawler log analysis tool?
What is the best AI crawler logs analysis tool?
Why does my analytics show no AI crawler traffic?
Which plans include crawler logs?
Does more crawling mean more citations?
What is the difference between GPTBot, OAI-SearchBot and ChatGPT-User?
Is any personal data kept?
See which bots read you, and which pages they never reach.
7 days free · card required