Meta Tag Analyzer
Paste a page and get every meta tag audited in one report.
Check which URLs your robots.txt actually allows and blocks.
A crawler reads only the one group that matches it best, and ignores every other group entirely.
The Robots.txt Tester matches your URLs against your rules the way a crawler does: longest matching path wins, Allow beats Disallow at equal length, wildcards and dollar anchors are honoured, and only the single best-matching user-agent group applies. Each URL shows the exact line that decided it, not just the verdict.
Paste your robots.txt, list the URLs you want to check, and each one is matched against the rules the way a crawler matches them — longest matching rule wins, allow beats disallow at equal length, and wildcards and dollar anchors are honoured.
The reason a tester is worth having is that robots.txt matching is not intuitive. The rules are prefix matches, not path segments, so <span>Disallow: /admin</span> also blocks /administrator and /admin-guide. A crawler only reads the one user-agent group that matches it best and ignores every other group entirely, which is why a rule under the wildcard group can appear to do nothing once a Googlebot group exists. And the specificity contest is decided by the character length of the matching path, not by the order the lines appear in. This tool shows you which rule won for each URL, not just the verdict.
Longest match wins and Allow beats Disallow at equal length — line order is irrelevant, exactly as Google treats it.
Asterisks and trailing dollar signs are interpreted properly rather than compared as plain text.
Pick a user agent and only the group that applies to it is used, which is where most surprises come from.
Rules outside a group, unknown directives and misspelt fields are reported with their line numbers.
Each result names the winning rule, so a surprising block is traceable in one step.
The whole file. Fetch it from yourdomain.com/robots.txt and copy it in.
One per line — full URLs or paths. Both work.
Googlebot, Bingbot or any other agent, so the right group of rules is applied.
Each URL shows allowed or blocked, and the exact line that decided it.
No, and this is the most consequential misunderstanding about it. It stops a crawler fetching the page. A blocked URL can still be indexed from links pointing at it, appearing with no description at all. To keep a page out of the index, allow crawling and use a noindex directive.
Because the rules are prefix matches, not folder matches. Disallow: /admin blocks /admin, /administrator and /admin-guide alike. Add a trailing slash to limit it to the directory, or a dollar sign to anchor the end of the path.
Exactly one — the most specific group whose name matches. If a Googlebot group exists, Googlebot reads only that group and ignores the wildcard group completely, including rules you assumed were global. That surprises people constantly, which is why this tool asks which crawler you are testing as.
Not for Google. Within the group that applies, the rule with the longest matching path wins, and when an Allow and a Disallow match at the same length the Allow wins. Line order has no effect at all.
What people who use the Robots.txt Tester think of it. Reviews come from visitors and are posted as written.
No ratings yet
Yours would be the first.
0 reviews
Newest first
No reviews yet
Be the first to rate the Robots.txt Tester. It takes half a minute and no account.
Write the first reviewPaste a page and get every meta tag audited in one report.
Build an image sitemap so Google can find pictures it would miss.
Build a Google News sitemap with the 48-hour rule applied.
Turn a list of old and new URLs into Apache redirect rules.
Build the short link that opens your review box directly.
Build a negative keyword list from a search terms report.
VideoObject markup with duration, thumbnail and key moments.
Build a map embed that does not slow the page down.