AI Crawler robots.txt Generator, block GPTBot & other AI bots
Build a ready-to-paste robots.txt block that allows or blocks 25 AI crawlers, GPTBot, ClaudeBot, Google-Extended, PerplexityBot, CCBot and more. Pick per bot or use one-click presets. Runs entirely in your browser, nothing uploaded, sources cited below.
How it works
This is a template generator, not a numeric calculator. It maps AI-crawler user-agent tokens to Allow or Disallow rules and emits a robots.txt block that follows the Robots Exclusion Protocol standardised as RFC 9309. Every token comes verbatim from the crawler operator's own published documentation, nothing is invented, so the generated file does exactly what each vendor documents.
The registry sorts each crawler into one of three purposes, which drives the presets:
- Training (13 bots), harvests pages for model training datasets. Examples: GPTBot, ClaudeBot, Google-Extended, CCBot.
- AI search (4 bots), fetches pages so an AI answer engine can cite them, which can send you referral clicks. Examples: OAI-SearchBot, PerplexityBot.
- Assistant (8 bots), user-triggered fetches when a person pastes your URL into a chatbot. Examples: ChatGPT-User, Perplexity-User.
The emitter runs four steps:
- Preset → rule map."Block all AI" sets every bot to Disallow; "Block training, allow AI search" sets training bots to Disallow and the rest to Allow; "Allow all" emits an explicit Allow line; Custom lets you toggle each token.
- Validate the path. The path must begin with
/and contain no spaces. An empty selection shows a hint and emits nothing. - Emit one stanza per bot, in a stable operator-then-token order so the output is reproducible: an optional
# operator, purposecomment, aUser-agent:line, then the chosenDisallow:orAllow:line. - Cross-check. The generated text is re-parsed by an independent validator that confirms every stanza has exactly one User-agent line, exactly one Allow/Disallow line, a known token, and a path starting with
/. The green "Valid" badge above only appears when that round-trip passes, the same two-method verification approach used across this site's tools.
One caveat worth stating plainly: robots.txt is honour-based. It records your preference, and the major operators publicly commit to obeying it, but the file is not a firewall. A crawler that disregards robots.txt can only be stopped server-side (a WAF rule, IP block, or user-agent block), a separate, harder measure that is out of scope for this browser-only tool.
Worked examples
Frequently asked questions
Sources & references
- IETF RFC 9309: Robots Exclusion Protocol (the robots.txt standard)
- OpenAI: GPTBot, OAI-SearchBot, ChatGPT-User documentation
- Anthropic: ClaudeBot and how site owners can block the crawler
- Google: Google-Extended and the full list of Google crawlers
- Perplexity: PerplexityBot and Perplexity-User
- Common Crawl: CCBot and its robots.txt behaviour
- ai.robots.txt: community-maintained AI crawler reference (secondary corroboration)
Every user-agent token is taken from the operator's own published docs; a handful of less-documented tokens are corroborated against the community ai.robots.txt reference. The registry was last cross-checked on 2026-07-03 and is reviewed on a roughly quarterly cadence. Each row in the tool links directly to its source.
Related tools
Comments & feedback
Spotted a bug or want an improvement? Tell us, our team reviews every comment, and good ideas get built. Comments are public and anonymous.
Spotted a new AI crawler, a renamed token, or a bug in the output?
Email me at [email protected] , the registry is updated on review.