Quick answer: AI companies run different agents for different jobs. Search crawlers and user-triggered fetchers decide whether assistants like ChatGPT, Claude and Perplexity can show and cite your pages. Training crawlers decide whether future models learn from your content. Control tokens like Google-Extended are not crawlers at all. Treat each group as a separate decision.
This directory lists the 20 agents that matter most for AI visibility in 2026, with a page for each covering what it does, what blocking it changes, exact robots.txt rules, how to verify genuine traffic, and a live check against your own site.
Search crawlers
Build the indexes AI assistants search when they answer. Blocking these costs visibility.
User-triggered fetchers
Open a specific page because a person asked. Robots.txt is often not a guaranteed block.
Training crawlers
Collect content for model training. Blocking them does not remove you from AI search answers.
robots.txt control tokens
Not crawlers at all. Switches that tell a search crawler's operator how the content may be used.
All 20 agents at a glance
| Agent | Operator | Type | Follows robots.txt |
|---|---|---|---|
| GPTBot | OpenAI | Training crawler | Yes |
| OAI-SearchBot | OpenAI | Search crawler | Yes |
| ChatGPT-User | OpenAI | User-triggered fetcher | Not guaranteed, fetches are user-initiated |
| OAI-AdsBot | OpenAI | Ad landing page checker | No, per OpenAI's documentation |
| ClaudeBot | Anthropic | Training crawler | Yes |
| Claude-User | Anthropic | User-triggered fetcher | Yes, per Anthropic's documentation |
| Claude-SearchBot | Anthropic | Search crawler | Yes, per Anthropic's documentation |
| PerplexityBot | Perplexity | Search crawler | Yes |
| Perplexity-User | Perplexity | User-triggered fetcher | Generally no, fetches are user-initiated |
| Google-Extended | robots.txt control token | Yes, it only exists in robots.txt | |
| Googlebot | Search engine crawler | Yes | |
| Bingbot | Microsoft | Search engine crawler | Yes |
| Applebot | Apple | Search crawler | Yes |
| Applebot-Extended | Apple | robots.txt control token | Yes, it only exists in robots.txt |
| Meta-ExternalAgent | Meta | Training crawler | Yes |
| Bytespider | ByteDance | Training crawler | Widely reported as inconsistent |
| CCBot | Common Crawl | Open dataset crawler | Yes |
| Amazonbot | Amazon | Search and AI crawler | Yes |
| DuckAssistBot | DuckDuckGo | AI answer crawler | Yes |
| MistralAI-User | Mistral AI | User-triggered fetcher | User-initiated, treat robots.txt as a request |
A visibility-first robots.txt
This setup keeps every search crawler and user fetcher in, which is what most businesses that want AI citations need. Add a Disallow: / group for any training crawler you want to exclude, and remember that a bot with its own group ignores your User-agent: * rules.
User-agent: *
Allow: /
User-agent: OAI-SearchBot
Allow: /
User-agent: ChatGPT-User
Allow: /
User-agent: Claude-SearchBot
Allow: /
User-agent: Claude-User
Allow: /
User-agent: PerplexityBot
Allow: /
User-agent: Perplexity-User
Allow: /
User-agent: DuckAssistBot
Allow: /
User-agent: Bytespider
Disallow: /
Sitemap: https://yourdomain.com/sitemap.xml
Robots.txt is only one layer. Firewalls and CDN bot protection can block crawlers that robots.txt allows, and no robots.txt line will reveal that. The AI crawler checker reads your file, and the ChatGPT visibility checker also tests whether your page can actually be fetched.
Frequently asked questions
Check all of them on your site
The free AI SEO audit tests 12 of these agents against your robots.txt, plus schema, llms.txt and content, in a few seconds.
Run the free AI SEO audit