AnswerFix

Free tools / AI Robots.txt Generator

AI Robots.txt Generator

Choose allow or disallow for all 16 named AI crawlers, from GPTBot to Bytespider, and get a correctly formatted robots.txt with a wildcard group for everything else and an optional sitemap line.

Everything else (the wildcard group)

Applies to any crawler not named individually below, including ordinary search engines.

GPTBot

Crawls pages OpenAI may use to train future ChatGPT models.

OAI-SearchBot

Finds and cites your pages in ChatGPT's search results. Not used for training.

ChatGPT-User

Fetches one page live when a person asks ChatGPT to open or browse it.

PerplexityBot

Crawls and indexes pages so Perplexity can link to them in its answers.

Perplexity-User

Fetches a page live when a person's question makes Perplexity read it.

ClaudeBot

Anthropic's crawler that collects web content for Claude's model training.

Claude-User

Fetches a page when someone using Claude asks a question that needs it.

Claude-SearchBot

Crawls to improve the relevance of Claude's search-grounded answers.

anthropic-ai

Anthropic's original crawler name. Retired and replaced by ClaudeBot.

Google-Extended

Controls use of your content for Gemini training and grounding. Does not affect Search ranking.

CCBot

Builds the open Common Crawl dataset that many AI models train on.

Applebot-Extended

Controls whether Apple may use already-crawled content to train Apple Intelligence.

Bingbot

Crawls and indexes pages for Bing search and Copilot answers.

Amazonbot

Amazon's crawler for product and service data. Eligible for use in Amazon AI model training.

meta-externalagent

Meta's crawler that indexes content for AI training and product features.

Bytespider

ByteDance's crawler for AI training data. ByteDance publishes no official public documentation for it.

Your robots.txt

16 of 16 named AI crawlers allowed. Upload this file at your site root so it resolves at yoursite.com/robots.txt, replacing what is there now.

User-agent: GPTBot
Allow: /

User-agent: OAI-SearchBot
Allow: /

User-agent: ChatGPT-User
Allow: /

User-agent: PerplexityBot
Allow: /

User-agent: Perplexity-User
Allow: /

User-agent: ClaudeBot
Allow: /

User-agent: Claude-User
Allow: /

User-agent: Claude-SearchBot
Allow: /

User-agent: anthropic-ai
Allow: /

User-agent: Google-Extended
Allow: /

User-agent: CCBot
Allow: /

User-agent: Applebot-Extended
Allow: /

User-agent: Bingbot
Allow: /

User-agent: Amazonbot
Allow: /

User-agent: meta-externalagent
Allow: /

User-agent: Bytespider
Allow: /

User-agent: *
Allow: /

Every user-agent name above was checked against that company's own current documentation. See the sources list below the tool for the exact page checked for each one.

Robots.txt access is binary: a named crawler either can read your site or it cannot, and each of the 16 bots listed above is matched by its own exact name, not by a single blanket rule. This tool writes one group per bot so the intent is explicit, then adds a wildcard group at the end for every other crawler, including ordinary search engines.

Every name in the list, and the one-line description next to it, was checked against that company's own current documentation before publishing, listed below. Two are worth calling out plainly: anthropic-ai has no current documentation of its own, since Anthropic's support article now documents only ClaudeBot, Claude-User, and Claude-SearchBot, and industry reporting describes anthropic-ai as retired in that bot's favor. Bytespider has no reachable official ByteDance documentation at all; its row says so rather than pointing at a source that does not exist.

A wildcard rule that disallows everything also disallows every AI crawler on this list by default, unless a more specific rule names that bot separately. That is the single most common accidental block, and it is why this tool always writes an explicit line for each named bot rather than leaving it to inherit from the wildcard group.

AI robots.txt generator questions

Why are there 16 crawlers instead of the usual short list?
Most lists only cover the training crawlers. This one adds the separate user-triggered and search-indexing bots each major AI company now runs, plus Bing, Amazon, Meta, and ByteDance, since a rule that blocks a company's training bot does not automatically block its other named agents.
Should I just disallow everything to protect my content?
That is a real, defensible choice, but understand the tradeoff. Blocking a search-oriented bot like OAI-SearchBot or PerplexityBot removes you from that engine's live, cited answers, not just training. Blocking a training-only bot like GPTBot or CCBot protects content without affecting whether you get recommended today.
What does the wildcard group actually control?
The wildcard group (User-agent: *) is the fallback rule for every crawler not named specifically above it, including Googlebot for ordinary search and any bot this list does not cover. Leaving it on Allow keeps your site visible to standard search engines regardless of what you choose for the named AI bots.
A crawler says it ignores robots.txt. Why include it here at all?
Perplexity-User, Claude-User, and ChatGPT-User fire only when a real person's question makes that engine fetch your page live, and each company's own documentation notes these can bypass robots.txt for that one request. Listing them anyway keeps this tool's coverage honest and matches what each vendor actually publishes.

Now see whether ChatGPT recommends you

Being crawlable is step one. The free score checks whether it is working.