Skip to content

AI search

AI crawlers and robots.txt: which to allow, from OAI-SearchBot to GPTBot

Let the right bots in.

AI crawlers follow the rules in your robots.txt file, and each AI company runs separate crawlers for search, for training and for fetching a page a user asked about. Block a search crawler such as OAI-SearchBot or PerplexityBot and that assistant can't cite you.

Block a training crawler such as GPTBot and you only stay out of future models. For a business that wants to be recommended, the safe default is to allow the search and user crawlers and decide on training separately. Check your bot protection too, because it can turn away crawlers your robots.txt allows.

Josef Winstone, Founder & Managing Director, Foundry Agency

By Josef WinstoneFounder & Managing Director · 8 min readUpdated

Which AI crawlers should you allow in robots.txt?

If you want to be found and recommended by AI assistants, allow their search and user crawlers: OAI-SearchBot and ChatGPT-User, Claude-SearchBot and Claude-User, PerplexityBot and Perplexity-User, plus Googlebot and Bingbot. Training crawlers are a separate choice.

The mistake we see most is a blanket block. Someone reads that AI companies are scraping the web, adds a rule to keep them all out, and the business quietly disappears from ChatGPT, Claude and Perplexity answers. The table further down lists each crawler, what it does and what happens if you block it.

What's the difference between search, training and user crawlers?

They do three different jobs, and blocking one doesn't block the others.

  • Search crawlers fetch pages so an assistant can find them and cite them in answers. OAI-SearchBot, Claude-SearchBot and PerplexityBot are examples. Block these and you drop out of that assistant's search answers.
  • Training crawlers collect pages to train future models. GPTBot, ClaudeBot and CCBot are examples, and Google-Extended and Applebot-Extended are tokens that control training use. Blocking them keeps your content out of future training data, but doesn't stop you being cited in search.
  • User agents fetch a page when someone asks an assistant to read it, such as ChatGPT-User, Claude-User and Perplexity-User. OpenAI and Perplexity say robots.txt may not apply to these, because a person made the request.

How do robots.txt rules work for AI crawlers?

A crawler reads your robots.txt, finds the group that names it, and follows only that group. If no group names it, it follows the catch-all group under User-agent: *.

That detail trips people up. If you have a strict catch-all group and a separate group naming GPTBot, GPTBot follows its own group and ignores the catch-all. And if your catch-all says Disallow: / and nothing names OAI-SearchBot, you've blocked ChatGPT search without meaning to.

robots.txt is a request, not a lock. Reputable crawlers from OpenAI, Anthropic, Google, Microsoft and Perplexity say they follow it. It won't stop a bad actor, and it isn't the place for anything private.

Should you block GPTBot and other training crawlers?

It depends on what your content is worth to you on its own. For most service businesses, being known by future models helps more than it costs.

A publisher, a course provider or anyone who sells their writing has a real reason to keep it out of training data. A plumber, an accountant or an agency mostly wants AI tools to know they exist and what they do. We allow every reputable crawler on our own site, training ones included, because being in model knowledge helps people find us.

Whatever you decide, decide it per crawler, on purpose. Don't let an old rule or a plugin decide for you.

What else can block AI crawlers?

Plenty, even when robots.txt says yes. These are the usual suspects.

  • Bot protection: some hosting and security services can block AI crawlers, and some switch that on by default. Check the settings.
  • Firewalls and rate limits that treat unfamiliar crawlers as attacks.
  • CAPTCHAs and JavaScript challenges on pages that should be public.
  • Content that only appears after scripts run, a cookie wall or a login.
  • A noindex tag or a robots meta tag left over from a staging site.

How do you check and fix your robots.txt, step by step?

Eight steps. Most sites can be checked in half an hour.

  1. Open yourdomain.co.uk/robots.txt in a browser and read it top to bottom.
  2. Look for Disallow: / under User-agent: *, and check whether any AI crawler is left relying on that group.
  3. Check every group that names an AI crawler, and what it allows.
  4. Paste the file into our AI crawler robots.txt checker to see which crawlers are let in.
  5. Check your hosting, CDN and security settings for AI crawler or bot blocking.
  6. Decide on training crawlers one by one, and write a rule for each.
  7. Publish the new file, keeping your sitemap line at the bottom.
  8. Check your server logs or analytics over the next few weeks for visits from the crawlers you allowed. Changes aren't instant.

Does llms.txt control AI crawlers?

No. llms.txt describes your site for AI tools. It can't allow or block anything. Access is still controlled by robots.txt and your server settings.

Which AI crawler does what?

The main crawlers and tokens, from each company's own documentation. Names change, so check the vendor's page before you edit.

NameCompanyWhat it's forIf you block it
OAI-SearchBotOpenAIFinds pages for ChatGPT searchYour pages can't appear in ChatGPT search answers
GPTBotOpenAICollects data to train future modelsKept out of training. ChatGPT search isn't affected
ChatGPT-UserOpenAIFetches a page a user asked ChatGPT to readOpenAI says robots.txt may not apply to user requests
Claude-SearchBotAnthropicImproves Claude's search resultsClaude's search may not show your pages
ClaudeBotAnthropicCollects data to train modelsKept out of training only
Claude-UserAnthropicFetches a page a user asked Claude to readClaude can't read your page for that user
PerplexityBotPerplexityBuilds Perplexity's search indexYour pages can't be found or cited in Perplexity
Perplexity-UserPerplexityFetches a page for a user's questionPerplexity says it generally ignores robots.txt
GooglebotGoogleGoogle Search, including AI Overviews and AI ModeYou drop out of Google Search entirely
Google-ExtendedGoogleA token for Gemini training and groundingGemini may not use your pages. Search isn't affected
BingbotMicrosoftBing search, which Copilot usesMissing from Bing and from Copilot's answers
Applebot-ExtendedAppleA token for Apple's AI model trainingKept out of training. Siri and Spotlight search aren't affected
CCBotCommon CrawlAn open web archive used by many AI training setsKept out of that archive

What does an AI-friendly robots.txt look like?

Here's a version that lets search engines and AI assistants in, with training crawlers in their own group so you can switch them off. Change the sitemap URL, and change Allow to Disallow in the training group if you want to opt out of training.

robots.txt
# Everyone else
User-agent: *
Allow: /

# Search engines (Googlebot also covers AI Overviews and AI Mode)
User-agent: Googlebot
User-agent: Bingbot
Allow: /

# AI search and user fetches
User-agent: OAI-SearchBot
User-agent: ChatGPT-User
User-agent: Claude-SearchBot
User-agent: Claude-User
User-agent: PerplexityBot
User-agent: Perplexity-User
Allow: /

# Gemini training and grounding. Blocking this can keep you out of Gemini answers.
User-agent: Google-Extended
Allow: /

# Training only. Change Allow to Disallow to opt out.
User-agent: GPTBot
User-agent: ClaudeBot
User-agent: Applebot-Extended
User-agent: CCBot
Allow: /

Sitemap: https://www.example.co.uk/sitemap.xml

How does Foundry set up AI crawler access?

Crawler access is the first thing we check on any AI SEO project, because nothing else counts until assistants can get in. We read your robots.txt, your security and CDN settings and your server logs, then agree with you which training crawlers to allow.

On our own site, robots.txt lets every major search and AI crawler in, and we don't run bot protection that would turn them away. Then we move on to the work that gets you named: clear facts, structured data, listings and digital PR.

Our averages. Not our best days.

Our averages

  • 5days

    Website, kick-off to live

  • 20mins

    Average reply time

AI crawler FAQs

  • No. GPTBot collects training data. ChatGPT search uses OAI-SearchBot. You can block GPTBot and still appear in ChatGPT search, as long as OAI-SearchBot is allowed.

  • No. Google-Extended controls Gemini training and grounding, not Google Search. AI Overviews use normal Googlebot. Blocking it can keep your pages out of Gemini's answers, though.

  • Copilot uses Bing, so the crawler that matters is Bingbot. If Bingbot can crawl your site and your pages are in Bing's index, Copilot can find them.

  • It's a voluntary standard. The major AI companies say their crawlers follow it, though OpenAI and Perplexity say user-requested fetches may not. It isn't a security measure.

  • Not instantly. Crawlers re-read robots.txt on their own schedule, so allow a day or more. Then watch your logs for the crawlers you've let in.

  • Most builders let you, sometimes under SEO settings. Some also have their own AI crawler setting. If you can't find either, ask the platform's support, or try our checker on the live file first.

Want the right bots in? Get moving.

Tell us what you need. We'll reply within the hour (working hours), and most websites go live about 5 days after kick-off.

We'll reply within the hour (working hours).

Or email hello@foundryagency.co.uk

Analytics cookies are off until you accept. We use them to see which pages help. Cookie notice