robots.txt and AI crawlers: which bots should you allow?
By Vibeking · Published 30 September 2026 · Facts checked on 30 September 2026
Don't block all AI bots in one go. OpenAI, Anthropic and other AI companies use separate bots for training models and for search.
So you can refuse training and still stay visible in answers from ChatGPT, Claude and Perplexity. The condition is that you allow their search bots.
Three kinds of AI bots
- Training bots collect pages to train AI models. OpenAI explicitly says that this choice is separate from its search bot, and Anthropic uses separate bots for training and search.
- Search bots build the index from which an assistant draws its sources. If you block them, you are shown as a source in their answers much less often, or not at all.
- Bots that fetch on request open a page because a user asks for it. OpenAI and Meta say that robots.txt may not apply to them. Google and Perplexity say that such bots generally ignore robots.txt. Anthropic says that all its bots follow robots.txt.
Which bot does what
| Bot | From | Used for | What blocking does |
|---|---|---|---|
| GPTBot | OpenAI | Model training | You indicate that your content may not be used to train OpenAI's foundation models |
| OAI-SearchBot | OpenAI | Search in ChatGPT | You no longer appear in ChatGPT's search answers, at most as a navigation link; takes effect after about 24 hours |
| ChatGPT-User | OpenAI | Fetching on request | robots.txt may not apply |
| ClaudeBot | Anthropic | Model training | You indicate that new content may not be used for training |
| Claude-SearchBot | Anthropic | Claude's search index | Your content is not indexed for the search function |
| Claude-User | Anthropic | Fetching on request | Claude does not fetch your page when a user asks for it |
| PerplexityBot | Perplexity | Search results, not for training | You may no longer appear in Perplexity's search results |
| Perplexity-User | Perplexity | Fetching on request | Generally ignores robots.txt |
| Google-Extended | Not a separate bot but a token: training of Gemini and sources for the Gemini apps | No effect on Google Search or your ranking, but it does affect use in the Gemini apps | |
| Applebot-Extended | Apple | Token for training Apple models | Your pages stay in Apple's search results |
| CCBot | Common Crawl | Open web archive, a well-known source for AI training | Your pages no longer end up in new archives |
| meta-externalagent | Meta | Training and indexing for Meta products | Your content is no longer fetched for these purposes |
| meta-webindexer | Meta | Meta AI search results | Less visible in Meta AI |
Googlebot, Bingbot and Applebot are the regular search bots: always allow them. To appear as a source link in AI Overviews or AI Mode, a page must be indexed in Google Search and eligible to be shown with a snippet. Since 31 August 2026, you can use Search Console, under Settings > Search generative AI, to exclude your site from AI Overviews, AI Mode and the generative AI features in Discover without blocking Googlebot. That setting changes nothing about training; for that, you still need Google-Extended.
Microsoft has no separate AI token for robots.txt. For Bing's chat answers, Microsoft pointed to the NOCACHE and NOARCHIVE meta tags in 2023.
Refuse training, stay visible: an example
# No training
User-agent: GPTBot
User-agent: ClaudeBot
User-agent: Google-Extended
User-agent: Applebot-Extended
User-agent: CCBot
User-agent: meta-externalagent
Disallow: /
# Allow AI search services and fetching on request
User-agent: OAI-SearchBot
User-agent: ChatGPT-User
User-agent: Claude-SearchBot
User-agent: Claude-User
User-agent: PerplexityBot
User-agent: meta-webindexer
Allow: /
# All other bots, such as Googlebot, Bingbot and Applebot
User-agent: *
Allow: /
Sitemap: https://www.example.com/sitemap.xml
Three things to watch out for:
- A bot with its own group ignores the User-agent: * group. If that group contains a rule for a protected directory, such as Disallow: /account/, repeat it in every group.
- Blocking Google-Extended also stops your content from being used as a source in the Gemini apps. If you do want to be mentioned there, leave that line out.
- robots.txt applies per domain and per subdomain. OpenAI, Perplexity and Meta process a change within about 24 hours.
Watch out if you use Cloudflare
On 1 July 2026, Cloudflare announced that customers who block training there would, from 15 September, also block multi-purpose bots such as Googlebot, Applebot and Bingbot. On 15 September 2026, the Disallow AI Training setting was added. It puts a ban on training in your robots.txt, blocks training bots such as GPTBot and ClaudeBot, and allows Googlebot, Bingbot and Applebot for search. Cloudflare has converted existing training blocks to Disallow AI Training. Bing does not yet read that ban in robots.txt; according to Cloudflare, Microsoft aims to support it in early 2027.
If you choose Block under Training in Cloudflare, Googlebot, Bingbot and Applebot are also blocked for search and Google can no longer fetch your site. Block on pages with ads does the same on pages with advertisements. So always check that setting alongside your robots.txt.
On 24 September 2025, Cloudflare also introduced Content Signals: a line such as Content-Signal: search=yes, ai-input=yes, ai-train=no, which lets you indicate what your content may be used for. Cloudflare itself does not call it a technical block, and we found no AI company that has publicly committed to following the signals.
Is robots.txt legally binding?
Technically, robots.txt is an agreement, not a lock: the standard (RFC 9309) says that the rules are not a form of access authorisation. Legally, however, it can count.
Under article 4 of the European copyright directive (the DSM directive) and article 15o of the Dutch Copyright Act (Auteurswet), text and data mining is not permitted if the rightholder has expressly reserved it in an appropriate manner. For online content, this refers to machine-readable means. Since 2 August 2025, providers of general-purpose AI models must have a policy to identify and comply with such a reservation (AI Act, article 53). For models already on the market before that date, this applies by 2 August 2027 at the latest.
How courts weigh a rule in robots.txt is still in flux. In 2024, the Amsterdam District Court ruled in a case brought by DPG Media and Mediahuis against HowardsHome that a valid reservation had not been demonstrated, and the German Federal Court of Justice (Bundesgerichtshof) is expected to rule in a similar case on 17 December 2026. This article is not legal advice.
How to check it
Open yourdomain.com/robots.txt and look for the names from the table. If OAI-SearchBot, Claude-SearchBot or PerplexityBot falls under a Disallow: /, or if one of those bots has no group of its own while User-agent: * has a Disallow: /, you are excluding yourself from those AI search services. A block in Cloudflare or a firewall does not show up in robots.txt; check those separately.
The free Vibeking SEO check reads your robots.txt and reports whether you block OAI-SearchBot, Claude-SearchBot, Claude-User, PerplexityBot or Google-Extended. Google-Extended is included because that token also determines whether the Gemini apps use your content as a source. If you deliberately block it to refuse training, as in the example above, that finding is to be expected. The check shows training bots such as GPTBot, ClaudeBot, CCBot, Applebot-Extended and meta-externalagent for information only.
Sources
- OpenAI: crawlers and user agents
- Anthropic: crawlers and blocking (updated 7 April 2026)
- Perplexity: crawlers
- Google: common crawlers and Google-Extended (updated 14 July 2026), fetching on request (updated 19 August 2026), AI features and your website (updated 10 December 2025) and generative AI setting in Search Console
- Apple: about Applebot (4 September 2026)
- Common Crawl: CCBot and the GPT-3 paper that names Common Crawl as a training source (2020)
- Meta: web crawlers
- Bing: NOCACHE and NOARCHIVE for Bing Chat (22 September 2023)
- Cloudflare: Content Signals Policy (24 September 2025), new default settings (1 July 2026) and Disallow AI Training (15 September 2026)
- RFC 9309: Robots Exclusion Protocol (September 2022)
- Directive (EU) 2019/790, article 4, Dutch Copyright Act (Auteurswet), article 15o (Stb. 2020, 558) (in Dutch) and AI Act, article 53
- Amsterdam District Court, ECLI:NL:RBAMS:2024:6563 (30 October 2024, in Dutch) and Bundesgerichtshof, I ZR 281/25 (in German)
