28 AI Crawlers · Free · No Signup

Can ChatGPT, Claude and Perplexity actually read your site?

Most sites that blocked “AI bots” blocked the wrong ones. This checks all 28 against your robots.txt, separates the crawlers that cost you visibility from the ones that do not, and gives you the exact fix.

Checks 28AI and search crawlers against the site's robots.txt. Free, no signup. Enter a full URL to test a specific page.

What this tool checks

Four signals decide whether an AI assistant can find, read and cite your pages. Every other “AI bot checker” treats them as one list. The distinction is the whole point.

Search crawlers

Googlebot and Bingbot. Blocking either removes you from classic search and from the AI layers built on top of it — AI Overviews, AI Mode and Copilot all read what these crawlers fetched.

AI answer engines

OAI-SearchBot, ChatGPT-User, PerplexityBot, Perplexity-User, Claude-SearchBot, Claude-User, Applebot and more. These fetch your pages so an assistant can answer a question about you and link back.

AI training crawlers

GPTBot, ClaudeBot, CCBot, Google-Extended, Bytespider and others. Blocking these protects your content from model training and costs you no visibility — the tool marks them separately for exactly that reason.

Signals beyond robots.txt

Whether you publish an llms.txt, and whether the page returns an X-Robots-Tag header that restricts indexing regardless of what robots.txt permits.

The most expensive mistake

Blocking GPTBot does not do what most people think.

In 2023 and 2024, a wave of advice told site owners to block AI crawlers. Thousands of businesses pasted a block list into robots.txt and moved on. Most of those lists made no distinction between the crawler that trains a model and the crawler that lets an assistant find and cite you today.

They are separate agents with separate tokens. GPTBot gathers training data. OAI-SearchBot builds the index ChatGPT searches. ChatGPT-User fetches a page the moment a real person asks about it. Anthropic splits the same way with ClaudeBot, Claude-SearchBot and Claude-User. Perplexity splits into PerplexityBot and Perplexity-User.

So a site that blocked “AI” broadly usually achieved the opposite of what it wanted: its content still shows up in models trained before the block, while the assistants that could have sent it live referral traffic now get a 403 and describe a competitor instead.

Block training if you want to. Do not block the engines that answer questions about your business. Those are different decisions, and this tool is built to keep them apart.

A robots.txt that gets this right

# Keep our content out of model training
User-agent: GPTBot
Disallow: /

User-agent: ClaudeBot
Disallow: /

User-agent: CCBot
Disallow: /

User-agent: Google-Extended
Disallow: /

# But let assistants find and cite us
User-agent: OAI-SearchBot
Allow: /

User-agent: ChatGPT-User
Allow: /

User-agent: PerplexityBot
Allow: /

User-agent: Claude-SearchBot
Allow: /

User-agent: Applebot
Allow: /

User-agent: *
Allow: /

Sitemap: https://example.com/sitemap.xml

Order does not technically matter — crawlers pick the most specific group that matches their token, not the first one they read. But keeping specific groups above the wildcard makes the intent obvious to whoever edits the file next.

How to read your results

Green across answer engines

Nothing is standing between you and an AI citation at the crawl layer. That does not guarantee you get cited — that depends on whether your content actually answers the question and whether your entity is consistent across the web — but the door is open.

Blocked training crawlers only

This is a deliberate posture, not a problem. You have opted out of model training while staying visible to assistants. If you did not intend it, the usual cause is a block list pasted from an article — worth confirming it matches what you actually want.

Blocked answer engines

Every red row here is a place your business cannot appear. Fix these first. The most common cause is a blanket wildcard Disallow with no specific groups above it, or a security plugin that added an AI block list without telling anyone.

No robots.txt at all

Everything is allowed by default, so nothing is blocked — but you also have no way to express a preference, and you lose the Sitemap directive that helps crawlers find your URL inventory. Publishing a minimal robots.txt is worth the five minutes.

Frequently asked questions

Does blocking GPTBot stop ChatGPT from finding my website?

No, and this is the single most common misunderstanding in AI SEO. GPTBot collects training data. A completely different crawler, OAI-SearchBot, builds the search index ChatGPT uses to find and cite live sources, and ChatGPT-User fetches a page when a user asks about it directly. You can block GPTBot to keep your content out of model training while remaining fully visible and citable inside ChatGPT. Blocking OAI-SearchBot is what makes you invisible.

Should I block AI crawlers at all?

It depends entirely on which kind. Blocking training crawlers (GPTBot, ClaudeBot, CCBot, Google-Extended) is a legitimate business decision with no visibility cost — publishers with licensable archives often should. Blocking answer engines (OAI-SearchBot, PerplexityBot, Claude-SearchBot, Applebot) removes your business from the assistants people increasingly use instead of search. For almost every commercial site trying to get found, answer engines should be allowed.

Does Google-Extended hurt my Google rankings?

No. Google-Extended is a robots.txt token, not a crawler. It controls only whether content Googlebot already fetched may be used to train and ground Gemini. Google has stated it has no effect on Search ranking or on inclusion in AI Overviews. Disallowing Google-Extended is a safe way to opt out of model training without touching your search visibility.

Why does the tool say a bot is allowed when I have Disallow: / in my robots.txt?

Because robots.txt matching is per-group and most-specific-wins. If you have a User-agent: * group with Disallow: / but a separate, more specific group for that crawler, the crawler follows its own group and ignores the wildcard one entirely. The tool shows you which line decided each verdict so you can see exactly which group applied.

Does a blocked crawler actually respect robots.txt?

The major crawlers from OpenAI, Anthropic, Google, Microsoft, Apple and Perplexity all publish their tokens and honour robots.txt. Some crawlers are widely reported to ignore it. robots.txt is a published instruction, not enforcement — if you need to guarantee a crawler cannot reach you, block it at the network or WAF layer. This tool reports what you are instructing crawlers to do, which is what determines the behaviour of every well-behaved one.

What is llms.txt and do I need one?

llms.txt is a proposed plain-text file at your site root that gives AI crawlers a curated map of your most important pages in a clean, readable form. It is not an official standard and no engine is required to read it. It costs almost nothing to publish and helps AI systems find your best content, so we treat it as a positive signal rather than a requirement.

Is this tool free and does it store the sites I check?

It is free with no signup and no limit worth mentioning. We fetch three public files from the domain you enter — robots.txt, llms.txt, and the response headers of the page — and we do not log the domains checked or store results. The URL you enter is used for that request and nothing else.

Crawlable is the floor.
Cited is the goal.

Letting the crawlers in is a five-minute fix. Being the source they choose to quote is a strategy — entity consistency, structured answers, and content built for how these engines actually retrieve.

Get a Free AI Visibility Audit