What does your robots.txt tell AI crawlers?

It fetches the robots.txt file for the domain you submit, then evaluates — separately for each supported AI crawler — which rule group applies to that crawler and whether the page path you submitted is allowed or blocked under those rules. The evaluation follows the RFC 9309 robots exclusion conventions: most-specific matching user-agent group, longest matching path rule wins, and Allow overrides Disallow at equal length.

Eight robots.txt tokens covered by the Optimus Pass visibility engine: Googlebot, OAI-SearchBot, PerplexityBot and Claude-SearchBot for search and discovery; GPTBot, Google-Extended and ClaudeBot for model training and other AI uses; and OAI-AdsBot for ChatGPT Ads landing-page validation. Each is reported with its purpose so you do not confuse a training crawler with a search crawler.

No — the checker cannot tell you that. robots.txt controls whether a crawler may request your pages. Whether an AI system retrieves, ranks, or cites your content depends on many factors outside robots.txt, and no tool can measure those from a robots file. Allowed means the door is open, not that anyone walked through it.

Not by itself. OpenAI documents OAI-SearchBot and GPTBot as independent controls: OAI-SearchBot surfaces sites in ChatGPT search results, while GPTBot crawls content that may be used for model training. You can allow one and block the other. The checker shows both states separately so the distinction stays visible.

The checker could not read a robots.txt file for that origin — it was missing, unreachable, or did not return readable text. In that case the engine reports every crawler as not evaluated instead of assuming access. That is a deliberate honesty rule: no evidence, no confirmation.

Yes. Run it on any public domain or page URL with no account and no credit card. The full visibility audit — which adds SEO, AEO, and GEO diagnostics alongside this crawler view — also has a free snapshot.