AI Search Crawler Inspector
Fetch any URL as ChatGPT, Claude, Perplexity, and Google. See exactly which AI bots can read your page — and which are blocked.
Why AI Search Crawler Inspector matters
If GPTBot, ClaudeBot, or PerplexityBot cannot reach your page, no amount of SEO will get you cited. Cloudflare challenges, a stray robots.txt directive, a JavaScript-only render, and a 403 served only to bots all kill AI visibility silently, and none of them show up in a browser. This tool fetches your URL as thirteen different bots side by side and shows you who actually got the page.
How it works
- 01
We read your robots.txt
Your live file is fetched and parsed the way a crawler parses it, matching each bot's token against your user-agent blocks with wildcard fallback. Rules people believe they wrote and rules that actually apply are frequently different.
- 02
We fetch your page as each bot
Eleven crawlers get a real request carrying their published user-agent string, in parallel. What comes back is what they would see.
- 03
We compare the results
Status code, response size, whether the body contains real content, and the robots.txt verdict, laid out per bot so a single blocked crawler is obvious rather than buried.
What it checks
- HTTP status per bot
- A 200 for your browser and a 403 for GPTBot is a common and completely invisible failure. Here the two sit in the same table.
- Was there content in the response
- A 200 is not a pass. We check the returned body for an H1 and real paragraphs, which is how a JavaScript-only page or a bot challenge served with a 200 gets caught.
- Robots.txt verdict
- Whether each bot is allowed at that specific path, evaluated against your live file rather than assumed from the file's intent.
- Training-only tokens
- Google-Extended and Applebot-Extended never fetch anything themselves; they are robots.txt tokens that govern training use. We report their directive and say so, rather than inventing a fetch result.