What you’ll need
Paste a robots.txt file and paths, or fetch a public site.
Test paths against robots.txt and see the matching rule.
Free to use · No saved inputsPaste a robots.txt file and paths, or fetch a public site. New here? Start with “Try an example”.
Paste a robots.txt file and paths, or fetch a public site.
RFC-style crawler grouping, longest matching rule and allow-on-tie. Live robots failures are reported separately.
Rules describe crawler permission, not indexing or whether a crawler actually obeys them.
An important page is missing from search, or a new robots.txt rule might block more than you intended. Start by checking the exact path against the intended crawler. This robots.txt tester shows the rule behind its answer so you can change a specific directive rather than removing every restriction. It is useful before a launch, migration or crawler-policy update.
Paste the robots.txt rules you want to check, or choose a live check for a public website. Keep a copy of the current file before editing it.
Add the paths you care about and select the crawler. Include both a page that should be accessible and one that should remain restricted.
Run the test and inspect the matching rule for each path. After making a change, test the same paths again before publishing the file.
Allowed means the supplied robots rules permit crawling for that agent and path. It does not mean the page is indexed, healthy or accessible through every security layer. A failed live request is different from a confirmed disallow rule; investigate unknown results before changing policy.
If permission looks correct but content is still missing, inspect the page response, canonical and noindex directives with Fetch & Render.
Rules describe crawler permission, not indexing or whether a crawler actually obeys them.
Do not use robots.txt as a reliable removal method. A crawler may still discover a blocked URL. Indexing controls and access protection address different problems; check Google’s documentation before combining them.
Several rules can match a path. This tester evaluates the selected agent group and matching specificity, then shows the decisive directive. Test query strings and trailing slashes exactly as they appear in your URLs.