How to check whether AI crawlers can access a website
Choose which AI bots you want
OpenAI and Anthropic publish separate crawler names for different purposes. Allowing a search crawler does not necessarily allow model training, and blocking a training crawler does not necessarily remove a page from user-requested retrieval.
The checker keeps those jobs separate. It evaluates the submitted path against robots.txt for OAI-SearchBot, ChatGPT-User, GPTBot, Claude-SearchBot, Claude-User, and ClaudeBot, then reports the HTTP response received when Mydentify requests the page with each documented user-agent name.
- OAI-SearchBot and Claude-SearchBot support their providers' search discovery workflows.
- ChatGPT-User and Claude-User support user-requested page retrieval.
- GPTBot and ClaudeBot are documented for potential model-training collection.
Check more than your robots.txt file
robots.txt is the first public rule layer, but it is not the whole path. A CDN, WAF, rate limit, login, CAPTCHA, geography rule, redirect, or server error can still stop a request. Page-level robots meta tags and X-Robots-Tag headers can also restrict indexing after crawling is allowed.
The user-agent probe is deliberately labeled. It comes from Mydentify infrastructure rather than a verified provider IP, so it can expose obvious user-agent handling but cannot certify how an official crawler will behave.
Check the latest bot rules before changing access
Crawler names and provider policies can change. Review the linked primary documentation before changing production access rules, and decide separately whether you want to allow search discovery, user-directed retrieval, training, or none of them.
Allowing access does not guarantee crawling, inclusion, citation, traffic, or ranking. Blocking access can reduce what a provider can retrieve directly, but third-party indexes and previously collected information may still affect an answer.