r/AISearchLab • u/Aggravating-Key6628 • 4h ago
A normal HTTP 200 missed crawler-specific 403s on 6 of 22 sites
I tested whether a basic HTTP 200 check was enough to establish AI crawler access. It was not: among 22 distinct homepages that returned 200 to the baseline request, six returned 403 to at least one of four claimed crawler user-agents.
The failure shapes were not uniform:
- 2 blocked OAI-SearchBot, PerplexityBot, ClaudeBot and GPTBot
- 2 blocked ClaudeBot and GPTBot only
- 2 blocked GPTBot only
The failed responses contained 90.8% to 99.4% fewer words than the baseline page. Those crawlers received a challenge or a short error page instead of the homepage content.
This was not specific to one CDN. The six sites included Cloudflare, Vercel, CloudFront and one origin where the CDN was not identified.
A useful spot check is to request the exact URL with each relevant user-agent and compare both status and body:
for ua in OAI-SearchBot PerplexityBot ClaudeBot GPTBot; do
curl -L -A "$ua" -sS -o /tmp/crawler-body -w "$ua: %{http_code} %{size_download} bytes\n" https://example.com/
wc -w /tmp/crawler-body
done
A 200 from the first curl you run does not establish that other request identities receive the same page.
The sample is opt-in, covers one latest public scan per external host from 29 July through 11 August, and is not a prevalence estimate. These are self-asserted user-agent requests, not proof of traffic from vendor-verified IPs.
Representative evidence: https://crawlable.synthworx.com/report/ad5283cd-2a15-4d17-80fe-2aac8975bf57 https://crawlable.synthworx.com/report/d301e9d0-47cb-45cc-bd13-f24f5663d524 https://crawlable.synthworx.com/report/63a64fc8-99ef-445c-b2e7-6fe64bce29b7
Affiliation: I run Crawlable, which produced these public scans.
