medicalnewstoday.com blocks GPTBot
Browser: HTTP 200 · control fetch
| AI crawler | robots.txt | Live HTTP | Verdict |
|---|---|---|---|
| GPTBotOpenAI (ChatGPT) | Disallow: / | HTTP 200 | Blocked |
| ClaudeBotAnthropic (Claude) | Disallow: / | HTTP 200 | Blocked |
| PerplexityBotPerplexity | — | — | Accessible |
| Google-ExtendedGoogle (Gemini/Vertex) | — | — | Accessible |
| CCBotCommon Crawl (training data) | Disallow: / | — | Blocked |
| anthropic-aiAnthropic (legacy token) | Disallow: / | — | Blocked |
robots.txt found
What the check found on medicalnewstoday.com
Measured on 16 November 2026, 04:40 UTC: robots.txt of medicalnewstoday.com read, homepage requested with the GPTBot and ClaudeBot user agent, and with a browser as control (HTTP 200).
- GPTBot: robots.txt blocks GPTBot with “Disallow: /” in a group of its own, “User-agent: GPTBot”. Yet the server still serves it the homepage with HTTP 200, so the block holds only as long as the crawler obeys robots.txt.Collects content that may be used to train OpenAI’s models.
- ClaudeBot: robots.txt blocks ClaudeBot with “Disallow: /” in a group of its own, “User-agent: ClaudeBot”. Yet the server still serves it the homepage with HTTP 200, so the block holds only as long as the crawler obeys robots.txt.Collects content that could contribute to training Anthropic’s models.
- CCBot: robots.txt blocks CCBot with “Disallow: /” in a group of its own, “User-agent: CCBot”. The check does not run a live request for this crawler.Builds Common Crawl’s open web archive, which is freely accessible and is also used for AI training.
- anthropic-ai: robots.txt blocks anthropic-ai with “Disallow: /” in a group of its own, “User-agent: anthropic-ai”. The check does not run a live request for this crawler.Older token that some robots.txt files still contain. It is no longer listed in Anthropic’s current crawler docs.
No rule of their own in robots.txt and no live request: PerplexityBot, Google-Extended.
Excerpt from the robots.txt of medicalnewstoday.com
The groups that apply to one of the checked AI crawlers, as the check read them.
User-agent: * Disallow: /linkfwd.php Disallow: /counters.php Disallow: /articles/mnt-* Disallow: /program/mnt-* Disallow: /api/* Disallow: */null$ Disallow: */inline$ Disallow: */healthy/ User-agent: GPTBot Disallow: / User-agent: anthropic-ai Disallow: / User-agent: CCBot Disallow: / User-agent: ClaudeBot Disallow: /
Verify it yourself
curl -A "GPTBot/1.2" -s -o /dev/null -w "%{http_code}\n" https://medicalnewstoday.comGPTBot can’t load medicalnewstoday.com. OpenAI uses GPTBot for training data; ChatGPT search relies on a separate crawler, OAI-SearchBot, which this check does not test. If the block sits in the hosting layer (CDN, WAF, site builder) and filters bots by user agent, it may hit that crawler as well. Most blocks like this are 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 medicalnewstoday.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.