loom.com blocks GPTBot
Browser: HTTP 200 · control fetch
| AI crawler | robots.txt | Live HTTP | Verdict |
|---|---|---|---|
| GPTBotOpenAI (ChatGPT) | Disallow: / | HTTP 200 | Blocked |
| ClaudeBotAnthropic (Claude) | — | HTTP 200 | Accessible |
| PerplexityBotPerplexity | — | — | Accessible |
| Google-ExtendedGoogle (Gemini/Vertex) | — | — | Accessible |
| CCBotCommon Crawl (Trainingsdaten) | — | — | Accessible |
| anthropic-aiAnthropic (Legacy-Token) | — | — | Accessible |
robots.txt found
Verify it yourself
curl -A "GPTBot/1.2" -s -o /dev/null -w "%{http_code}\n" https://loom.comA block here has a hard effect: if OpenAI’s crawler can’t load loom.com, the page can’t be cited in ChatGPT — no matter how good your content is. Most blocks like this come from the hosting layer (CDN/WAF/site builder), not a deliberate choice, so they go unnoticed. The fix is usually a single allow-rule; the harder question is whether you’re then actually cited.
Related check
Is loom.com actually cited in ChatGPT?Crawlability is only step one — a reachable site still has to be named in the AI answer to win the customer.