Syntax
01Find malformed directives, missing user-agent groups, and conflicting path rules.
Generate a clean file or check the one already live. See exactly which search and AI-answer crawlers can access your site.
Choose who can crawl, then add the paths you want to keep private.
Search crawlers
Google, Bing, and other general crawlers
OpenAI crawlers
ChatGPT search, user visits, and GPTBot
Anthropic crawlers
Claude search, user visits, and ClaudeBot
Perplexity crawlers
PerplexityBot and user-requested visits
Other training crawlers
Common Crawl, Google-Extended, and Bytespider
One path per line.
Optional, but useful for discovery.
Edit anything before you publish it at /robots.txt.
Enter your domain to track brand mentions, competitor positions, and cited sources across ChatGPT, Gemini, Perplexity, AI Mode, and AI Overviews.
What gets checked
Find malformed directives, missing user-agent groups, and conflicting path rules.
Summarize effective rules for search, AI-answer, and training crawlers.
Extract and validate every sitemap URL declared in the file.
Confirm the public file exists and is served with a sensible response and content type.
robots.txt generator FAQ
A robots.txt file tells compliant crawlers which paths they may request. It is a crawling directive, not a security control, and blocked URLs can still appear in search results.
Yes. Many answer engines publish distinct crawler tokens for search, user-requested visits, and model training. The generator creates separate groups so you can choose a policy for each use.
Publish it at the root of the exact host it covers, such as https://example.com/robots.txt. A file in a subdirectory does not control the rest of the site.
No. It makes one bounded request to the public /robots.txt file and analyzes the returned text without a model or search API.