Test

Robots.txt Tester

Paste the contents of a robots.txt file, enter a URL or path and a crawler such as Googlebot, and see whether it is allowed or blocked — with the matching group, the deciding rule and its length. Nothing is fetched.

Back

1. robots.txt & URL

Pasted text only

Use the crawler’s product token, e.g. Googlebot or Bingbot, or * for all crawlers.

2. Result

RFC 9309 matching
Paste robots.txt, enter a URL or path and a crawler, then press Test.

Crawl-delay is shown for information only and never blocks a URL. Blocking crawling does not by itself remove a page from search results.

About this tool

About Robots.txt Tester

Robots.txt Tester checks a URL or path against the rules in a robots.txt file you paste, for the crawler you name. It selects the matching user-agent group, evaluates every Allow and Disallow rule with * wildcards and $ end anchors, and reports the deciding rule, its length and whether the URL is allowed or blocked. Nothing is fetched.

A single misplaced slash or wildcard in robots.txt can block important pages from being crawled. Testing a draft before publishing it shows exactly which rule decides each URL.

How to use

Step by step

  1. Paste the contents of your robots.txt file.
  2. Enter a full URL or a path that starts with /.
  3. Enter the crawler’s user-agent token, such as Googlebot, or * for all crawlers.
  4. Press Test URL.
  5. Read the result, matching group and deciding rule, then copy or download the summary.
Key features

What it offers

  • Case-insensitive user-agent groups with fallback to *
  • Groups for the same crawler combined, as the standard requires
  • * wildcards and $ end-of-path anchors
  • Longest matching rule wins; Allow wins a tie
  • Crawl-delay and Sitemap lines shown for information
  • Parser notes for unknown fields and misplaced rules
Best practices

Tips for best results

  • Test a page you want crawled and a page you want blocked after every change.
  • Remember that robots.txt rules are case-sensitive for paths.
  • Use noindex rather than robots.txt to keep crawlable pages out of results.
  • Keep a “User-agent: *” group as a sensible default.
Benefits

Why people use it

Explainable

See the exact rule that decides.

Standards-based

Follows RFC 9309 matching.

Safe

Test drafts before they go live.

Private

Nothing is fetched or sent.

FAQ

Common questions

It finds every Allow and Disallow rule in the crawler’s group that matches the path, then the longest rule (by number of characters) decides. If an Allow and a Disallow rule are equally long, Allow wins. If no rule matches, the path is allowed.
The group whose User-agent line matches the crawler’s product token, ignoring case — for example “googlebot” matches “Googlebot”. Several groups for the same crawler are combined. If no group names the crawler, the “User-agent: *” group is used; if there is none, everything is allowed.
“*” matches any sequence of characters, including none, and “$” at the end of a rule means the path must end there. For example, “Disallow: /*.pdf$” blocks /files/report.pdf but not /files/report.pdf?download=1.
No. Crawl-delay only asks some crawlers to wait between requests. The tester shows it for information, but it never changes the Allowed or Blocked result, and several major crawlers ignore it.
Either. For a full URL the tester uses the path and query string (everything after the domain) and ignores any #fragment. Paths must start with /.
Not necessarily. robots.txt controls crawling, not indexing; a blocked URL can still appear in results if other pages link to it. Use a noindex directive on a crawlable page to ask for it to be left out.
No. It only tests the text you paste. No website, robots.txt file or search engine is contacted.
Private by design

This runs entirely in your browser

No file or text you enter here is uploaded. Encoding and decoding happen on your device using native browser APIs — close the tab and nothing remains on a server.

Install Toolisco Add it to your device for offline, one-tap access.