urldiagnostics.com

Free · Server-side scan

AI Bot Access Checker

Paste a domain and see whether robots.txt allows GPTBot, ChatGPT-User, ClaudeBot, Perplexity, Googlebot, Bingbot, and other crawlers — with exact rule evidence and copy-paste fixes.

🔒 Server-side scan: our server fetches the public robots.txt file in memory and refuses private, local, or reserved network targets. Checked URLs are not stored or logged.

What this means

robots.txt, without the folklore

robots.txt is a polite instruction file at the root of a site. Crawlers read it before fetching pages, then match their user-agent against Allow and Disallow rules. The longest matching rule wins, and an Allow wins ties. This checker makes that decision visible for the bots people are currently asking about.

What does this checker actually test?

It fetches the site's public /robots.txt file and applies standard longest-match robots.txt rules for major search, live-answer, and training crawlers. It shows the directive and line number that made each decision where possible.

Does allowing a bot guarantee AI visibility?

No. It only means robots.txt is not blocking access. Whether an AI product cites, indexes, or trains on your content depends on many other systems and policies. We are checking the gate, not promising the party inside, regrettably.

Why separate live-answer bots from training crawlers?

Many site owners want public pages available for search and answer engines while limiting broad training crawls. The preset reflects that common policy: allow live retrieval/citation bots and block training-oriented crawlers if that is your preference.

Is the checked URL stored?

No. The server fetches robots.txt because browsers are blocked by CORS on many sites. The check runs in memory, rejects private/internal targets, and does not store or log submitted URLs.