Skip to main content

Home / Tools / AI Crawler Access Checker

Free AI crawler access checker

Paste a URL and see, engine by engine, whether the AI crawlers behind ChatGPT, Claude, Perplexity and Gemini are allowed to read that page.

Reads the site's robots.txt and evaluates the path you pasted for five AI crawlers.

What this tool checks

The checker downloads /robots.txtfrom the URL's origin, parses it into user-agent groups, and evaluates the path you pasted against each of the five AI crawlers separately. It applies the same matching rules Google documents: the group whose user-agent token best matches the bot wins (longest token, with * as the fallback), and within that group the most specific pattern applies — longest Allow/Disallow pattern wins, and Allow beats Disallow on a tie. Wildcards (*) and end-anchors ($) are supported. Each result also tells you whether the verdict came from a rule that names the bot or from the catch-all group.

Why AI crawler access matters

Answer engines are becoming a real referral channel, and unlike classic search they do not need to send a click to have already decided whether you exist. If ChatGPT cannot fetch your pricing page, it cannot recommend your product when someone asks for options. If Perplexity cannot read your comparison article, it will cite a competitor's instead. The gate for all of this is one public text file that almost nobody re-reads after launch.

The failure mode is rarely a considered decision. It is a Disallow: /left over from staging, a CMS "discourage search engines" toggle, a security plugin that added a blanket AI-bot block, or a CDN bot-management rule that someone enabled to stop scrapers and never revisited. Each of those looks identical from the outside: your content simply stops appearing in AI answers, with no error and no notification.

How to fix what you find

To allow an engine, remove the Disallow from its group, or add an explicit group that permits it — a named group always beats the catch-all, so User-agent: ClaudeBot followed by Allow: / re-opens access even while User-agent: * stays restrictive. To block training but keep citations, block GPTBot and Google-Extended while leaving OAI-SearchBot allowed. Check a real content URL, not just the homepage: rules are path-based, so /blog/post and /can have opposite verdicts. And remember robots.txt is only half of it — a page that is crawlable but returns thin server-rendered HTML still gives an AI engine nothing to quote, which is what a full audit's AI-readiness checks measure.

Frequently asked questions

Which crawlers does this check?

The five that matter for AI answers today: GPTBot and OAI-SearchBot (OpenAI), ClaudeBot (Anthropic), PerplexityBot (Perplexity) and Google-Extended (Gemini and AI Overviews). Each gets its own verdict, because robots.txt rules can name them individually.

Is Google-Extended the same as blocking Googlebot?

No, and this is the single most misunderstood rule in the file. Googlebot controls ordinary Search crawling and ranking. Google-Extended only controls whether your content can be used for Gemini and AI Overviews. Blocking Google-Extended does not remove you from Search; blocking Googlebot does.

Should I block AI crawlers?

It depends on where your traffic comes from. If people find you through recommendations and comparisons, being fetchable is how an assistant can cite you at all — blocking is throwing away a distribution channel. If your content is the product (paywalled research, a licensed dataset), blocking training crawlers while allowing the search-facing ones (OAI-SearchBot) is a reasonable middle path.

Why does it say "blocked via the catch-all"?

Because no rule names that bot, so it fell through to the User-agent: * group. That distinction matters: a catch-all block is usually accidental (a staging config or a blanket Disallow: /) while an explicitly named bot is normally a deliberate policy decision.

Does robots.txt actually stop AI companies?

It stops the well-behaved crawlers that publish a user-agent and honour the file — which is all five checked here. It is not an access control. Anything that must not be read by a machine needs authentication, not a line in a public text file.

Want the full picture?

This tool checks one thing. A full RankVitals audit runs a Lighthouse speed test plus 50+ SEO and AI-readiness checks on your whole site — free, no signup.

Run a full site audit →