Launch
Robots.txt Checker
Visit
Example Image

Robots.txt Checker

Free tool to test if a URL is blocked by robots.txt

Visit

Paste your robots.txt, pick a bot and a URL, and see whether the URL is allowed or blocked, which rule decided it, and any errors. Free, no sign-up. It cannot fetch a live file from another domain, so you paste the contents. Google handles * and $ wildcards but not every crawler does, so confirm in Search Console too.

Example Image
Example Image

Features

Allowed or blocked verdict, deciding rule shown, syntax errors flagged, user-agent matching with wildcard fallback, longest rule wins with Allow winning ties, free, no sign-up.

Use Cases

Testing a Disallow rule before deploying it, finding out why a page is not being crawled, checking a staging robots.txt.

Comments

Showing which rule decided the verdict is the useful bit. Most testers just say allowed or blocked and leave you guessing. Since AI crawlers are a common reason people edit robots.txt now, would you consider adding GPTBot, ClaudeBot and similar user-agents to the bot picker?

Showing the deciding rule is the right call. One pitfall I'd love the tool to flag: when a bot matches its own user-agent group (say Googlebot), it ignores the * group completely, so the Disallow lines under * no longer apply to it. People add a Googlebot group for one tweak and accidentally unblock everything else. A note like "this bot uses group X, the * group is ignored" next to the verdict would catch that.

Showing the longest-matching rule and the Allow-wins-ties behavior is exactly how Google resolves conflicts, so this is a good way to debug a staging file. Would you consider letting people add several URLs at once to test a whole sitemap section?

Premium Products
Social Links

Comments

Showing which rule decided the verdict is the useful bit. Most testers just say allowed or blocked and leave you guessing. Since AI crawlers are a common reason people edit robots.txt now, would you consider adding GPTBot, ClaudeBot and similar user-agents to the bot picker?

Showing the deciding rule is the right call. One pitfall I'd love the tool to flag: when a bot matches its own user-agent group (say Googlebot), it ignores the * group completely, so the Disallow lines under * no longer apply to it. People add a Googlebot group for one tweak and accidentally unblock everything else. A note like "this bot uses group X, the * group is ignored" next to the verdict would catch that.

Showing the longest-matching rule and the Allow-wins-ties behavior is exactly how Google resolves conflicts, so this is a good way to debug a staging file. Would you consider letting people add several URLs at once to test a whole sitemap section?

Premium Products