Robots.txt Generator
Say what crawlers may read, and copy a robots.txt that does exactly that. Every file is tested before you publish it.
One per line. A path matches everything that starts with it; * matches any characters and $ marks the end.
Your robots.txt
User-agent: * Allow: /
Upload it to the root of the site, so it answers at https://your-site/robots.txt.
Test this file before you publish it
Allowed by Allow: / on line 2
What the Generator Checks
Read back by a real parser
The file is parsed with the same RFC 9309 engine as our robots.txt checker, and every path, exception and blocked crawler is tested against it.
Rules that would not work
An Allow that loses to a longer Disallow, a Disallow cancelled by an equal Allow: you are told before you upload, not after a crawl.
Nothing injected
A path containing a line break or a space is refused, so a paste can never add a directive you did not write.
A tester built in
Type any path, pick a crawler, and see whether it is allowed and which line decides it, using Google's longest-match rule.
How the Rules Combine
A crawler obeys only the group that names it most specifically. If the file has a group for GPTBot, GPTBot ignores the User-agent: * group entirely, which is why the generator gives blocked crawlers a group of their own with Disallow: / and leaves everyone else on the shared rules.
Inside a group, the rule with the longest matching path wins, and Allow wins a tie. Disallow: /admin/ with Allow: /admin/help/ keeps crawlers out of the admin area except the help pages. A * matches any run of characters and a final $ anchors the end, so /*.pdf$ blocks PDF files and nothing else. The robots.txt syntax guide walks through every directive, and the robots.txt checker tests the file once it is live.