How robots.txt allow/disallow matching works
Crawlers pick the most specific matching Allow or Disallow rule for their user-agent group. This tester applies a practical subset of common matching rules so you can spot accidental blocks before deploy.
Test how a robots.txt file treats a path for a given user-agent. See the matched agent group and a short reason for allow or disallow.
Fill in the form fields the tool shows.
Change modes or toggles if available.
Copy the generated output when it looks right (often updates live).
Crawlers pick the most specific matching Allow or Disallow rule for their user-agent group. This tester applies a practical subset of common matching rules so you can spot accidental blocks before deploy.
Complete the fields in robots.txt Tester. Output is produced in your browser from those inputs — copy it when ready.
Empty optional fields if you want a minimal result. Invalid combinations should surface an error message.
Whenever possible, robots.txt Tester processes your data locally with JavaScript in this page. That means drafts, secrets, and unfinished work stay on your device by default. Prefer this workflow when you do not want to upload sensitive text, tokens, passwords, or files to a third-party service.
No. Paste the file contents yourself—nothing is fetched from your site.
It covers common Allow/Disallow patterns with wildcards. Edge cases in crawler implementations may still differ.
For most FlyUtils tools, no. Processing happens in your browser with JavaScript. If a tool ever needs a server, that will be stated clearly on the page.
Yes. robots.txt Tester is free, with no sign-up and no artificial usage caps for normal personal and work use.
Yes. The page is mobile-first, so you can paste input, tweak options, and copy results from a phone or tablet.