HTTP bot accessibility
ia.bot-accessibility · 1.8
Why it matters
AI crawlers and agents must be able to fetch your pages via HTTP. If bots are blocked, AI systems cannot index or interact with your content.
How to fix it
Return HTTP 200 to legitimate bots and do not block them in the WAF or CDN.
-
Request the home page with a bot user agent and record the HTTP status.
-
When the status is 401 or 403, add a WAF or CDN rule that allows known AI user agents.
map $http_user_agent $is_ai_bot { default 0; "~*GPTBot" 1; "~*ClaudeBot" 1; } -
Keep rate limits, but do not answer verified AI crawlers with a challenge page.
Verify
curl -s -o /dev/null -w '%{http_code}\n' -A 'GPTBot/1.0' https://{domain}/
Expected: 200
Run a new scan for this checkpoint:
isagentready results {domain} --checkpoint ia.bot-accessibility
Details Mapping, lifecycle and references
- AR mapping
- Full match
- Evidence source
- agentready.org AR-FIND-01
- Score role
- Core
- Introduced
- 2026-08-24
- Methodology version
- 2026-10-22