No Upload, No Wait
Everything runs on your own device, so there is no queue and no server round-trip.
Paste a robots.txt, give it a crawler and a URL path, and this tells you whether the crawler is allowed — and, more usefully, which single rule decided it. Rule precedence is the part people get wrong, and most testers never show their working.
Path only, starting with a slash — not the full address.
This is the single most common misunderstanding about robots.txt, and it causes real damage in both directions — pages blocked that should not be, and pages crawled that were meant to be private.
Three things decide the outcome, in this order:
A crawler obeys exactly one group of rules: the one whose User-agent line matches it most specifically. If your file has a block for * and a block for Googlebot, then Googlebot follows only the Googlebot block and ignores the wildcard block completely — including any Disallow lines you assumed applied to everyone.
This trips people constantly. Adding a small Googlebot group to set a crawl delay silently exempts Googlebot from every rule in your wildcard group.
Within that group, order on the page is irrelevant. The rule with the longest path pattern wins. That is why this works:
| Rule | Length | Outcome for /wp-admin/admin-ajax.php |
|---|---|---|
Disallow: /wp-admin/ | 11 | Matches, but shorter |
Allow: /wp-admin/admin-ajax.php | 27 | Wins — crawling allowed |
If two rules match with the same length and disagree, the crawler is permitted.
* matches any run of characters. $ anchors the rule to the end of the path.
The trap is that Disallow: /*.pdf$ blocks /report.pdf but not /report.pdf?v=2, because the query string means the path no longer ends at .pdf. If you are trying to keep PDFs out of search, that is a gap worth knowing about.
A rule without a trailing slash is also a prefix, not a folder. Disallow: /search blocks /searchable-page too.
It is not a privacy control and it does not remove pages from Google. A blocked URL can still appear in results if other sites link to it — Google just cannot read the page to describe it. To keep something out of the index, allow crawling and use a noindex tag; to keep something private, put it behind a login. Blocking a page in robots.txt actually prevents Google from seeing a noindex tag on it.
No. The parsing happens entirely in your browser. You can disconnect from the internet once the page has loaded and it still works.
Because it does. A crawler obeys only the most specific group that matches it. Once a Googlebot group exists, Googlebot stops reading the group for * entirely. Any rule you want to apply to Googlebot must be repeated inside its own group.
No. Within a group, the longest matching path wins regardless of where it appears. Ties go to Allow.
Disallow: with nothing after it places no restriction at all, which is the same as allowing everything for that group.
No. It stops Google reading the page, but the URL can still be listed if other pages link to it. Use a noindex tag on a crawlable page to remove it from the index.
It implements the behaviour described in Google’s robots.txt specification: most-specific group, longest match, ties to Allow, plus * and $ wildcards. Other crawlers vary, and some ignore robots.txt entirely.
Everything runs on your own device, so there is no queue and no server round-trip.
What you enter never leaves your browser. We could not see it even if we wanted to.
No account, no email, no usage limit. Open it and use it.
Any modern browser on desktop, tablet or phone. Nothing to install.