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.
What each row means
- GPTBotchallengedAWS WAF challenge served. Compliant agents cannot solve it and will not see the real page.
- ChatGPT-UserchallengedAWS WAF challenge served. Compliant agents cannot solve it and will not see the real page.
- ClaudeBotchallengedAWS WAF challenge served. Compliant agents cannot solve it and will not see the real page.
- Claude-UserchallengedAWS WAF challenge served. Compliant agents cannot solve it and will not see the real page.
- PerplexityBotchallengedAWS WAF challenge served. Compliant agents cannot solve it and will not see the real page.
- Google-ExtendedchallengedAWS WAF challenge served. Compliant agents cannot solve it and will not see the real page.
- GooglebotchallengedAWS WAF challenge served. Compliant agents cannot solve it and will not see the real page.
- BingbotchallengedAWS WAF challenge served. Compliant agents cannot solve it and will not see the real page.
- CCBotchallengedAWS WAF challenge served. Compliant agents cannot solve it and will not see the real page.
- BrowserchallengedAWS WAF challenge served. Compliant agents cannot solve it and will not see the real page.
Copyable summary for sharing with infra owners or filing an issue with your CDN.
AgentSpeed AI Crawler Access Matrix Target: https://huggingface.co Run: 2026-07-26T02:33:25.607Z Per-agent verdict: - GPTBot challenged status=200 sim=1.00 bytes=176019 - ChatGPT-User challenged status=200 sim=1.00 bytes=176019 - ClaudeBot challenged status=200 sim=1.00 bytes=176019 - Claude-User challenged status=200 sim=1.00 bytes=176019 - PerplexityBot challenged status=200 sim=1.00 bytes=176019 - Google-Extended challenged status=200 sim=1.00 bytes=176019 - Googlebot challenged status=200 sim=1.00 bytes=176019 - Bingbot challenged status=200 sim=1.00 bytes=176019 - CCBot challenged status=200 sim=1.00 bytes=176019 - Browser challenged status=200 sim=1.00 bytes=176019 Run again at: https://agentspeed.com/tools/ai-crawler-access-matrix
Watch this URL — get alerted when this changes
Turn this one-off check into a scheduled watch. We re-run it, diff the result, and alert you on a regression through the same channels as your agent alerts. Watches are a paid feature.
Manage watches at /watches. You’ll be asked to sign in if you haven’t already.
Click an example to run the tool with pre-filled inputs.
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.
Is this the same as the Agent UA tester?
Why include Googlebot and Bingbot?
What does "allowed-different" mean?
Do you store the responses?
How do redirects show up?
Score the entire site against 30 agent-readiness checks across discoverability, readability, structured data, actionability, and performance.
Get the full report for huggingface.co →