AI crawlers use robots.txt to determine what they’re allowed to access. If you’re blocking them, even accidentally through a wildcard rule, you’re invisible to those AI search engines. Here is the exact configuration you need.
Why robots.txt Matters for AI Search Visibility
Before any AI crawler reads a single page on your site, it checks your robots.txt file for permission. Each major provider documents its crawlers: see the official pages from OpenAI, Anthropic, Perplexity, and Google. If you block an AI crawler’s user agent, either explicitly or through a wildcard rule, that AI engine cannot access your content, cannot train on it, and cannot cite it. Blocked pages are far less likely to be retrieved or cited, regardless of how well your content is written or how strong your SEO is.
Many sites accidentally block AI crawlers through misconfigured User-agent: * rules that were set up for other purposes. A Disallow: / rule under User-agent: * blocks every crawler including every AI bot. Checking and explicitly configuring AI crawler access is one of the highest-ROI technical GEO actions available. Our technical SEO audit checklist covers the rest of the technical foundation, and our simple guide to generative engine optimization explains why it matters.
⚠️ Check This First
Test your current robots.txt at yourdomain.com/robots.txt. If you see User-agent: * followed by Disallow: /, you are blocking every crawler including GPTBot, ClaudeBot, and PerplexityBot. If you see specific Disallow rules covering your main content directories under the wildcard agent, AI crawlers are blocked from that content.
The Main AI Crawlers and Their User Agents
| AI Crawler | User Agent Name | Powers | What It Does |
|---|---|---|---|
| OpenAI / ChatGPT | OAI-SearchBot | ChatGPT search results | Indexes pages so they can appear in ChatGPT search answers; not used for model training |
| OpenAI / ChatGPT | GPTBot | OpenAI model training | Crawls content that may be used to train OpenAI’s generative AI models |
| OpenAI / ChatGPT | ChatGPT-User | User-initiated visits | Fetches a page when a user asks ChatGPT about it; robots.txt rules may not apply to user-initiated visits |
| Anthropic / Claude | ClaudeBot | Claude model training | Collects public web content that may contribute to Claude model training |
| Anthropic / Claude | Claude-SearchBot | Claude search quality | Navigates the web to improve the relevance and accuracy of Claude search results |
| Anthropic / Claude | Claude-User | User-initiated visits | Fetches pages when a user asks Claude a question |
| Perplexity AI | PerplexityBot | Perplexity search results | Surfaces and links your pages in Perplexity answers; not used to train AI foundation models |
| Perplexity AI | Perplexity-User | User-initiated visits | Fetches a page when a user asks; because a user requested it, it generally ignores robots.txt |
| Google AIO / Gemini | Googlebot | Google Search and AI Overviews | Standard Googlebot handles AI Overview content, so no separate bot is needed; blocking Googlebot removes you from Search too |
| Google Gemini | Google-Extended | Gemini training and grounding | A robots.txt token that controls use of your content for Gemini models; it does not affect Search inclusion or ranking |
| Bing / Copilot | Bingbot | Bing AI, Microsoft Copilot | Standard Bingbot handles Copilot content retrieval |
| Meta AI | FacebookBot, meta-externalagent | Meta AI assistant | Crawls for Meta AI knowledge base and response generation |
| Common Crawl | CCBot | Many LLM training datasets | Massive public web crawl used to train many open-source and commercial LLMs |
Exact robots.txt Configurations
Configuration 1: Allow All AI Crawlers (Recommended for Most Sites)
The default configuration if you want maximum AI search visibility. Simply do not block AI crawlers, and if you have a wildcard Disallow rule, explicitly allow AI bots:
📋 robots.txt, Allow All AI Crawlers
User-agent: *
Disallow: /wp-admin/
Disallow: /private/
# AI search and retrieval crawlers, explicitly allowed
User-agent: OAI-SearchBot
Allow: /
User-agent: Claude-SearchBot
Allow: /
User-agent: Claude-User
Allow: /
User-agent: PerplexityBot
Allow: /
# AI training crawlers, allowed
User-agent: GPTBot
Allow: /
User-agent: ClaudeBot
Allow: /
User-agent: CCBot
Allow: /
Sitemap: https://yourdomain.com/sitemap.xmlConfiguration 2: Allow AI Search Crawlers, Block Training Crawlers
If you want your content cited in AI search but not used for model training, block the training crawlers and allow the search crawlers. OpenAI, Anthropic, and Perplexity each publish separate user agents for these purposes, so the settings are independent: blocking GPTBot does not remove you from ChatGPT search, which is controlled by OAI-SearchBot.
📋 robots.txt, Selective AI Access
# Block model training crawlers
User-agent: GPTBot
Disallow: /
User-agent: ClaudeBot
Disallow: /
User-agent: CCBot
Disallow: /
# Allow AI search and retrieval crawlers
User-agent: OAI-SearchBot
Allow: /
User-agent: Claude-SearchBot
Allow: /
User-agent: Claude-User
Allow: /
User-agent: PerplexityBot
Allow: /
Sitemap: https://yourdomain.com/sitemap.xmlConfiguration 3: Block All AI Crawlers (Publishers with Licensing Concerns)
Publishers concerned about AI training on their proprietary content may choose to block all AI crawlers. This trades AI citation potential for content protection, a valid decision for paywalled content or proprietary databases:
📋 robots.txt, Block All AI Crawlers
User-agent: OAI-SearchBot
Disallow: /
User-agent: GPTBot
Disallow: /
User-agent: ChatGPT-User
Disallow: /
User-agent: ClaudeBot
Disallow: /
User-agent: Claude-SearchBot
Disallow: /
User-agent: Claude-User
Disallow: /
User-agent: PerplexityBot
Disallow: /
User-agent: CCBot
Disallow: /
User-agent: meta-externalagent
Disallow: /
# Standard search engines still allowed
User-agent: Googlebot
Allow: /
Sitemap: https://yourdomain.com/sitemap.xmlAfter robots.txt: What Else to Check
- Verify
X-Robots-TagHTTP headers don’t includenoindexornofollowfor AI-targeted pages - Check that
<meta name="robots" content="noindex">is not set on any content pages you want cited - Submit your sitemap in robots.txt (last line:
Sitemap: https://yourdomain.com/sitemap.xml) to help AI crawlers discover your content structure - Consider adding an
llms.txtfile at your domain root, a plain-text file that guides AI models about your site’s content, key pages, and permissions
AI Crawlers & robots.txt, FAQs
Technical questions about configuring crawler access for AI search engines.
Need a Technical GEO Setup for Your Site?
A2Z Dev Center builds AEO and GEO content strategies for B2B and eCommerce brands through our web app development services, AI visibility audits, content optimization, technical GEO setup, and ongoing citation tracking.
Get Technical GEO Audit →Talk to a subject-matter expert
Web development, SEO, or digital marketing — tell us about your project and we'll get back within one business day. No obligation.
- Free scope & strategy session
- A senior specialist, not a sales rep
- Your details stay confidential