What is Robots.txt Tester?
A robots.txt tester evaluates whether a crawler is permitted to request a particular path according to the rules published at the site's /robots.txt location. It is a crawl-control check, not an indexing check. A URL can be allowed by robots.txt and still carry a noindex directive, canonicalize elsewhere, return an error, or remain unindexed for other reasons.
Robots rules are easy to misread because matching depends on user-agent groups, path prefixes and the most specific applicable rule. A single broad Disallow can prevent search crawlers from fetching templates, sections or resources that the site owner expected to be accessible. Testing the exact URL and crawler is safer than scanning the file by eye.
How to use the Robots.txt Tester
- 1Enter the full URL you want to test, not only the domain.
- 2Choose or enter the crawler name that matters to your audit, such as Googlebot.
- 3Run the test and review the fetched robots.txt file, matching group and winning Allow or Disallow rule.
- 4If no rule matches, remember that the default outcome is normally allowed.
Understanding the results
- Allowed means the tested crawler is not blocked by the applicable robots.txt rules for that path.
- Blocked means a matching Disallow rule wins for the selected crawler and path.
- No robots.txt or a fetch failure is different from an explicit Allow. Read the fetch message before drawing a conclusion.
Common problems
- Blocking an entire directory when only one private path was intended.
- Testing Googlebot while the file contains a more specific Googlebot-News or AdsBot group.
- Assuming robots.txt removes a URL from search results.
- Using robots.txt to protect confidential content.
How to fix them
- Narrow broad Disallow patterns and retest the exact affected paths.
- Use meta robots or X-Robots-Tag when the requirement is about indexing rather than crawling.
- Use authentication for private content; robots.txt is publicly readable and is not an access-control system.
robots.txt best practices
- Keep rules as simple as the site architecture allows.
- Retest after migrations, CMS changes and staging-to-production releases.
- Link your sitemap from robots.txt when useful, but do not assume that makes every sitemap URL indexable.
Practical example
What this tool cannot tell you
This tool evaluates published robots rules and the requested crawler. It does not prove that Google has crawled, indexed or ranked the URL, and it cannot override server-side bot blocking that happens outside robots.txt.
Frequently asked questions
Does robots.txt prevent indexing?+
Not reliably. Robots.txt primarily controls crawling. A blocked URL can still be known from links and may appear without a normal fetched snippet.
What happens when there is no matching rule?+
The crawler is generally allowed to request the path, assuming no separate network or server restriction blocks it.
Can robots.txt block CSS and JavaScript?+
Yes. That can interfere with rendering and should be intentional rather than inherited from an old configuration.
Is robots.txt case-sensitive?+
Path matching can be case-sensitive because URLs themselves may be case-sensitive on the server. Test the exact URL used by the site.
Can I use robots.txt for private pages?+
No. Use authentication or access controls for private content.
Related SEO tools
Robots.txt Validator
Fetch and validate a site's robots.txt file for directive syntax, formatting problems and crawl-control mistakes.
Robots.txt Generator
Build a clean robots.txt file from crawler rules, blocked paths and sitemap locations without hand-writing directives.
Noindex Checker
Detect noindex directives in meta robots markup and relevant HTTP response headers on a live URL.
X-Robots-Tag Checker
Inspect X-Robots-Tag response headers and explain indexing directives delivered outside the HTML document.
Indexability Checker
Review the technical signals that influence whether a page is eligible for indexing without pretending to know Google's live index state.