Robots.txt Tester

Robots.txt Tester

Test crawler access rules by user-agent and path. Check if URLs are allowed or blocked by your robots policy.

Robots Test Result

About the Robots.txt Tester Online Free Tool

The Robots.txt Tester Online Free Tool checks whether a requested path is allowed or blocked for a selected crawler user-agent. You can fetch a website's /robots.txt file or paste rules directly, then review the matching rule and the tool's allow or block result.

This robots.txt checker recognizes user-agent groups, Allow and Disallow directives, * wildcards, $ end anchors, comments, and sitemap declarations. It is a practical debugging simulator, not a guarantee that every search engine or crawler will interpret every rule identically.

How to Test a Robots.txt Rule

  1. Enter the website URL to fetch its root /robots.txt file, or open the additional options and paste the file contents.
  2. Enter the crawler name you want to test, such as Googlebot.
  3. Enter the path beginning with a slash, such as /private/page.
  4. Select Test Rule.
  5. Review the source, normalized path, final result, parsed group count, sitemap count, and matched rule.

Choosing the Correct Inputs

Fetched or pasted rules:
If pasted robots.txt content is present, the tester uses it instead of fetching the website. URL mode sends a request through the site's utility endpoint to retrieve the public /robots.txt file.

User-agent:
Test the crawler name relevant to your investigation. A rule group for one crawler may produce a different result from the wildcard * group or another named crawler.

Path:
Enter a direct path when possible. If you paste a full HTTP or HTTPS URL, the tool evaluates its pathname. For a rule involving a query string, enter the path and query directly, such as /search?type=private.

How the Result Is Chosen

The tester gathers matching rules from the user-agent groups recognized by its parser. Among matching path rules, it selects the rule with the longest pattern. If equally long Allow and Disallow patterns match, Allow is preferred. Empty Disallow values do not block the path.

Common Robots.txt Checks

  • Finding an accidental crawl block before publishing a robots.txt change.
  • Comparing Googlebot access with a wildcard crawler group.
  • Testing wildcard and end-anchored rules against a specific path.
  • Confirming which rule the tester selected for an allowed or blocked result.

Robots.txt Tester FAQ

Does blocking a URL in robots.txt remove it from search results?
No. Robots.txt primarily controls crawling and does not guarantee that a URL will be removed from an index.

Can robots.txt protect private content?
No. Compliant crawlers may honor it, but it is not access control. Protect sensitive content with authentication or another server-side restriction.

Does the tester support Crawl-delay?
No. It evaluates Allow and Disallow path access. Other directives are not used to decide the result.

Are sitemap declarations tested?
No. Sitemap lines are counted and displayed, but they do not affect the path access decision.