hospitalbagchecklist.online · scanned
403 Forbidden
Blocked at the firewall
hospitalbagchecklist.online turns automated visitors away, including one identifying as ChatGPT’s crawler.
The site answered HTTP 403 before serving any page, so there was nothing to score. That is a firewall or bot-protection rule, not an outage: people in a browser can still see the site.
What each visitor got
same page, same moment
- AIOScanBot our scannerHTTP 403, bot challenge instead of the page
- GPTBot ChatGPT’s crawlerHTTP 403, bot challenge instead of the page
What this means for AI
AI crawlers such as GPTBot, ClaudeBot and PerplexityBot announce themselves as bots and crawl from cloud servers, the two things this rule reacts to. If they get the same answer, ChatGPT, Claude and Perplexity can’t read the site, so they can’t quote it or recommend the business from it. Some firewalls check the genuine AI crawlers by the network they come from and let them through, so treat this as a strong warning rather than proof, and look at the setting.
How to fix it
usually one setting
- Find the rule. It usually lives in bot protection: Cloudflare (Security, then Bots), or the security settings in Wix, Squarespace, Shopify or your host. Step-by-step for each platform.
- Allow the AI crawlers you want to be found by: GPTBot, ClaudeBot and PerplexityBot. On Cloudflare, allow verified bots rather than switching protection off.
- Scan again. The full 21-check report appears as soon as the page is served.
Not your site to change? Copy summary above and send it to whoever runs it.