How this free tool helps
Robots.txt controls crawling, not guaranteed indexing. This tester evaluates observable User-agent: * rules for the path you provide.
Test how a website’s robots.txt rules apply to a specific URL path and understand whether crawling is allowed or blocked. Use it to spot restrictive directives before they interfere with important pages.
Robots.txt controls crawling, not guaranteed indexing. This tester evaluates observable User-agent: * rules for the path you provide.
A robots file can contain different groups and path rules, so test the exact user-agent and URL path that matters rather than reading one line in isolation.
A permitted path is not guaranteed to be crawled, and a blocked path can still be known from links elsewhere. Crawl control and indexing are related but different.
Correct overly broad directives, retest representative paths and keep sensitive content behind authentication instead of relying on robots rules.
It reads a public robots.txt file and evaluates whether a supplied path appears allowed or disallowed under the relevant crawler rules supported by the tool.
No. Allowing crawling only means robots.txt is not presenting that particular restriction. Crawlers independently decide when and whether to request a URL.
No. robots.txt is public and is not an access-control system. Sensitive resources should be protected with authentication or other server-side security.
Only when the matching user-agent group applies. Specific crawler groups can override what you might assume from a general User-agent: * section.
URL path matching can be case-sensitive because URL paths themselves may be case-sensitive. Test the exact path and rule you intend to deploy.
Continue technical SEO diagnosis using SEO Audit, Indexability Checker, Googlebot Crawl & JavaScript Dependency Test and Robots.txt Generator. Each check covers a different aspect of your website, so compare the evidence before making changes.