AI Bot Checker

Check whether GPTBot, ClaudeBot, PerplexityBot and other AI crawlers are blocked in robots.txt, then paste access logs to see which bots hit which paths.

Enter a site URL to fetch robots.txt, or paste the file yourself. This checks policy only — it does not prove a bot has crawled you.

Paste access-log lines below. Matching is by user-agent string in your browser — the log text is not uploaded. Spoofed UAs are possible; for IP verification against vendor ranges, use the botcheck runbook.

What this looks like

One request per line. You need path, status, and User-Agent at minimum. nginx “combined” format and JSON lines both work.

203.0.113.10 - - [14/Oct/2026:12:00:00 +0000] "GET /pricing HTTP/1.1" 200 4821 "-" "Mozilla/5.0 (compatible; GPTBot/1.2; +https://openai.com/gptbot)"
198.51.100.22 - - [14/Oct/2026:12:00:01 +0000] "GET /docs HTTP/1.1" 403 210 "-" "Mozilla/5.0 AppleWebKit/537.36 (compatible; ClaudeBot/1.0; +claude.com)"
{"path":"/blog/launch","status":200,"userAgent":"Mozilla/5.0 (compatible; PerplexityBot/1.0; +https://perplexity.ai/perplexitybot)"}

Where people get this at work

Edge or origin access logs — Cloudflare, Fastly, Akamai, CloudFront, ALB, Vercel log drains, or the corporate reverse proxy. Product analytics (GA4, Adobe) usually strip bots, so they are the wrong source.

Most SEOs do not have this access by default. That is normal. How to ask for access logs for SEO and AEO — why they matter, who to ask, and a copy-paste email for platform / security.

Free tool for technical SEO and AI-search work. Need a deeper audit? AI search consulting.