Paste a robots.txt file and test whether a specific URL path is allowed or blocked for a given crawler, using the same longest-match, wildcard-aware rules Google actually applies.
Paste the contents of a robots.txt file and this parses it into user-agent groups, then tests a given path against those groups using the same rules real crawlers apply: the most specific matching rule wins regardless of Allow/Disallow order, and "*" / "$" act as wildcards the way Google's own documentation describes. It tests the text you paste, not a live fetch of any site's actual robots.txt.
No, you paste the file's contents in directly. That means you can test edits before you ever publish them, but you're responsible for keeping the pasted text in sync with what's actually live at yoursite.com/robots.txt.
It's treated as allowed by default. Crawlers assume access is permitted unless a Disallow rule specifically matches the path, which is exactly how this tool evaluates it too.
When multiple Allow and Disallow rules in a group match the same path, the rule with the longer (more specific) path pattern takes precedence, not whichever rule appears first in the file. That's why an `Allow: /wp-admin/admin-ajax.php` line can carve out an exception inside a broader `Disallow: /wp-admin/` block.