Test robots.txt Allow and Disallow rules
This robots.txt tester follows the supported RFC 9309 decision path: it selects exact product-token groups, falls back to wildcard groups only when needed, normalizes URL octets, and chooses the longest matching rule. The pasted file never leaves your browser.
What this tester does not do
The tool does not fetch a remote /robots.txt file, imitate a live crawler, or verify that a search engine has refreshed its cached policy. robots.txt is crawl guidance and is not a security boundary.
robots.txt Tester FAQ
- How does the tester select a crawler group?
- It combines every group whose User-agent value exactly matches the entered product token, ignoring case. If no exact group exists, it combines wildcard groups. It never adds wildcard rules to a specific match.
- How is the winning robots.txt rule chosen?
- Matching begins at the first path octet and includes the query. The longest matching pattern wins, and an Allow rule wins an equal-specificity tie. The tool supports * and a terminal $.
- Are encoded URLs and Unicode paths supported?
- Yes. The tester applies RFC percent-encoding comparison rules, decodes percent-encoded unreserved ASCII, encodes Unicode as UTF-8 octets, keeps the query, and removes the fragment.
- Does this tool fetch robots.txt from my website?
- No. Paste the content you want to inspect. The static browser tool makes no fetch or XMLHttpRequest call, avoiding cross-origin and remote-content risks.
- Can robots.txt protect private pages?
- No. robots.txt asks compliant crawlers not to visit certain URLs, but it does not authenticate requests or prevent direct access. Protect sensitive content with real authorization.