Pre-deployment policy test
Paste proposed rules and test important public and private paths before replacing the live file.
Test whether a named crawler can request a path under the declared robots rules. The result shows the selected group and longest matching rule so the decision is inspectable.
Paste proposed rules and test important public and private paths before replacing the live file.
See which exact group and rule applies to a named crawler.
Test representative paths after moving a staging configuration into production.
The tool processes what you enter, shows a plain-language result, and gives you a safer next step. Make the change on your website, deploy it, then test the live page again.
Paste proposed rules and test important public and private paths before replacing the live file.
See which exact group and rule applies to a named crawler.
Test representative paths after moving a staging configuration into production.
The crawler uses default open behavior unless a wildcard group applies.
The most specific matching path wins, and Allow wins when matching rules have equal length.
Clear CDN caches and re-fetch the public /robots.txt response before relying on the change.
No. It controls crawling and is not a guaranteed removal or noindex mechanism.
Yes, when you choose a documented crawler name. Declared access still does not prove visits or citations.
Path matching is generally case-sensitive, while user-agent matching is handled without case sensitivity.