← all toolsTool
AI Crawler Access Matrix
Fetch any URL in parallel as ten AI crawlers and a default browser. See exactly which agents your site allows, blocks, redirects, challenges, or serves a different body to. Real HTTP fetches, real verdicts.
Tool
Examples
Click an example to run the tool with pre-filled inputs.
Why this matters for AI agents
Most agent-readiness problems show up here first. A site that blocks GPTBot at the WAF, redirects ChatGPT-User to /login, or serves a different body to PerplexityBot than to a browser will never show up in agent answers, and the only way to find out is to actually fetch as those agents.
This is the live equivalent of the journey.primary_probe check on a public scan, run on demand against any URL.
Common fixes
WAF blocks GPTBotIn Cloudflare bot management, allow GPTBot, ClaudeBot, and PerplexityBot explicitly. Their UA strings are documented and IPs are fixed.
Different body for bots than browserIf similarity drops below 0.80 between an agent and the Browser baseline, your CMS or edge layer is likely rendering a different variant. Audit any UA-conditional rendering rules, since agents often get the worst one.
Redirected to /loginRender server-side preview content for unauthenticated requests on landing pages. Agents cannot authenticate; they cite the auth wall.
Cloudflare challenge firesAdd the bot to Cloudflare’s allowed-bots list, or whitelist the published IP ranges for OpenAI, Anthropic, Perplexity.
Different canonical per UACanonical drift confuses agent dedupe. Audit any UA-conditional canonical rules; the canonical should be identical across all UAs.
Linked rubric checks
- journey.primary_probe
- robots_txt.allows_known_agents
- reachability.status
FAQ
Is this the same as the Agent UA tester?
Same backend pipeline, broader UA list. The UA tester runs 6 UAs to focus on cloaking detection. The Crawler Access Matrix runs 10, adding Claude-User, Google-Extended, Googlebot, Bingbot, and Common Crawl, to give a full picture of who can and cannot reach your site.
Why include Googlebot and Bingbot?
Because misconfigured WAFs frequently block them too. If your search visibility tanks, the matrix tells you whether the cause is your robots.txt, your bot manager, or your CDN, without you having to spelunk through logs.
What does "allowed-different" mean?
The agent got a 200 OK but the body content differs from the browser baseline by more than 20% (Jaccard similarity < 0.80). This is usually cloaking, paywall variants, or "render lite for bots" rules. Agents see worse content than humans.
Do you store the responses?
No. Each run is fetched live and discarded. The result page is rendered server-side; nothing persists.
How do redirects show up?
fetchWithHostPolicy follows up to 5 hops. The "redirected" column shows whether any redirect happened; the final URL column shows where it ended up. SSRF-protected, so every redirect is re-validated against the host policy.
Run a full agent-readiness scan
Full scanScore the entire site against 30 agent-readiness checks across discoverability, readability, structured data, actionability, and performance.
Get the full report →