Guide · AI crawlers · 2026

Which AI crawlers should you allow? The distinction most robots.txt files get wrong.

GPTBot is not OAI-SearchBot. ClaudeBot is not Claude-SearchBot. Confusing the two is how sites end up absent from AI answers while believing they protected their content. Here is the full list, the 2026 numbers, and a file you can copy.

Short answer

There are two kinds of AI crawler and they need opposite decisions. Training crawlers (GPTBot, ClaudeBot, CCBot, Google-Extended, Applebot-Extended) collect content to train models — blocking them is a legitimate choice with no traffic cost. Answering crawlers (OAI-SearchBot, Claude-SearchBot, PerplexityBot, Perplexity-User) fetch pages to cite in AI answers and send referral traffic — blocking them removes you from those answers. For most businesses the right setting is: allow everything on public pages, block only private areas.

The split that decides everything

Every major provider now runs at least two separate user-agents, and they are governed by separate robots.txt rules. A single line written in 2023 to “keep AI out” usually names only the training bot, or names both and silently removes the site from AI answers.

AI user-agents by purpose, 2026
ProviderTraining crawlerAnswering crawlerSends referral traffic
OpenAIGPTBotOAI-SearchBot, ChatGPT-UserYes, via ChatGPT search
AnthropicClaudeBot, anthropic-aiClaude-SearchBot, Claude-UserYes, via Claude citations
PerplexityPerplexityBot, Perplexity-UserYes, sources are listed
GoogleGoogle-ExtendedGooglebot (feeds AI Overviews)Yes
AppleApplebot-ExtendedApplebotYes, via Siri and Spotlight
Common CrawlCCBotNo
ByteDanceBytespiderNo — documented ignoring robots.txt

Note the Google row: Google-Extended controls training only. AI Overviews are fed by ordinary Googlebot crawling, so blocking Google-Extended does not remove you from them — and blocking Googlebot removes you from Google entirely.

What sites actually do

The 2026 data shows the market converging on a middle path rather than a blanket block:

The plateau is the interesting part. The first wave of blocking was reflexive; the second wave was informed, and it stopped at the line between training and answering.

Decide by what your content is

What to allow, by business type
Your situationTraining crawlersAnswering crawlersWhy
Small or mid-sized business, marketing siteAllowAllowYou have far more to gain from being described and cited than to lose from being in a training set.
Local services (trades, clinics, agencies)AllowAllowLocal recommendation questions are answered from pages the answering bots can reach.
Publisher or media, content is the productBlockAllowThe middle path: keep the archive out of training, stay in the answers that drive readers.
Paid courses, research, proprietary dataBlockAllow marketing pages onlyPut the product behind authentication; let the crawlers see what sells it.
Anything with personal or client dataBlockBlockNot a robots.txt question: it needs authentication.

A robots.txt you can copy

This is the allow-everything-public, block-everything-private pattern — the right default for most businesses. Repeat the block for each user-agent you care about; wildcards in User-agent are not reliably supported.

Pattern for a business site
DirectiveMeaning
User-agent: GPTBotAllow: /Public pages readable; repeat the block per user-agent.
Disallow: /app/, /admin/, /api/, /account/Private areas closed to every crawler.
Allow: /llms.txtNeeded if you use Disallow: / with an allow-list.
Sitemap: https://example.com/sitemap.xmlDiscovery, once at the end of the file.

Three mistakes we see constantly: a CDN or security plugin blocking AI user-agents without anyone knowing; a Disallow: / allow-list that forgets /llms.txt and the CSS the page needs to render; and a login wall that returns HTTP 200 with a sign-in page for every unknown path, so a crawler records your whole site as one login form.

robots.txt is a request, not a lock

The major providers document their user-agents and honour robots.txt. Bytespider and stealth crawling attributed to Perplexity have both been documented ignoring it. Anything that genuinely must not be read needs authentication or an IP rule — a disallow line is a polite notice, and it is published for anyone to read.

Frequently asked questions

Should I block AI crawlers?

It depends which. Training crawlers (GPTBot, ClaudeBot, CCBot, Google-Extended, Applebot-Extended) collect content to train models. Answering crawlers (OAI-SearchBot, Claude-SearchBot, PerplexityBot, Perplexity-User) fetch pages to cite in AI answers and send traffic back. If you want to appear in AI answers, allow the answering crawlers.

What is the difference between GPTBot and OAI-SearchBot?

GPTBot collects content for training. OAI-SearchBot crawls for ChatGPT's search feature, which cites sources and links back. Separate user-agents, separate rules: blocking GPTBot does not remove you from ChatGPT search; blocking OAI-SearchBot does.

How many sites block AI crawlers?

GPTBot is the most blocked, named in about 5.5% of disallow rules in Q1 2026. Among top sites, GPTBot blocking rose from ~5% in early 2023 to ~25% and has been flat since; roughly 30% now block training bots while allowing answering bots.

Do all AI crawlers respect robots.txt?

No. The major providers do; Bytespider and stealth crawling attributed to Perplexity have been documented ignoring it. Use authentication for anything that must not be read.

Does blocking AI crawlers hurt my SEO?

Not your Google rankings — Googlebot and Google-Extended are separate. But blocking answering crawlers removes you from AI answers, where a growing share of qualified traffic starts.

What should a small business allow?

Everything on public pages; block only accounts, APIs, dashboards and checkout.

Free diagnostic

Not sure what your robots.txt is actually doing?

We check which crawlers reach your pages, what the AI engines say about your business today, and where the two disagree. Remote, worldwide, in English or French.

Request the diagnostic →Read the llms.txt guide

Sources