SEO

Robots.txt Validator

Validate robots.txt syntax and check whether a specific URL is allowed or blocked for a given crawler.

Last reviewed by the Radiatus Cloud team

Robots.txt Validator

Validate the syntax of your robots.txt file content.

Need this done properly for your business?

Radiatus delivers secure cloud, DevOps & compliance engineering.

Book a free consult

Robots.txt controls crawling, not indexing

This is the distinction that causes the most damage. Disallow stops a compliant crawler fetching the page; it does not remove the page from search results. A blocked URL with external links pointing at it can still be indexed, appearing with no description because the crawler was never allowed to read it. To keep a page out of the index you need a noindex meta tag or header — which requires the page to be crawlable. Blocking a page you also want deindexed guarantees the opposite of the intent.

Specificity beats order

Google resolves conflicting rules by the length of the matching path, not by which appears first. Given Disallow: /admin/ and Allow: /admin/public/, the longer Allow wins for URLs under /admin/public/. When two rules are the same length, the least restrictive wins. Writing rules in a particular order to get a particular result is a misunderstanding.

User-agent groups do not merge

A crawler obeys exactly one group: the most specific one matching its name. If there is a Googlebot group and a wildcard group, Googlebot reads only the Googlebot group and ignores every rule under the wildcard, including ones you assumed applied to everyone. Rules meant for all crawlers must be repeated in each named group.

Wildcards and the end-of-string anchor

An asterisk matches any sequence and a dollar sign anchors to the end of the URL. Disallow: /*.pdf$ blocks PDFs but not /file.pdf?download=1, because the query string means the URL no longer ends in .pdf. Query parameters routinely defeat rules written without them in mind.

Never block CSS and JavaScript

Google renders pages to evaluate them. Blocking the stylesheets and scripts means it renders a broken page and judges it accordingly, including for mobile usability. The old habit of disallowing /assets/ or /wp-includes/ actively damages rankings on a modern site.

Location and scope are strict

The file must be at the root of the host, served as plain text, and it applies only to that exact host and protocol. A robots.txt at the www subdomain does not govern the apex, and the HTTPS file does not govern HTTP. A 404 means everything is allowed; a 500 means Google may treat the whole site as disallowed, which makes robots.txt availability a genuine uptime concern.

Related tools

  • Meta Tag Analyzer — Check a page's meta tags for the problems that actually affect indexing and click-through.
  • Redirect Chain Checker — Trace the full path of redirects (301/302) to find loops or lost link juice.
  • Sitemap Generator (Lite) — Generate a valid XML sitemap with lastmod dates and correct structure, and learn which URLs belong in it and which do not.
  • Broken Link Checker (Lite) — Scan a page for broken links (404s) to improve SEO.

Frequently Asked Questions

Does robots.txt remove a page from Google?

No. It stops crawling, not indexing. A blocked URL with inbound links can still appear in results with no description. Deindexing needs a noindex tag, which requires the page to be crawlable.

How are conflicting rules resolved?

By the length of the matching path, not by order. A longer Allow beats a shorter Disallow, and when two rules are equally specific, the least restrictive wins.

Do wildcard rules apply to named crawlers?

No. A crawler obeys only the most specific matching group. If a Googlebot group exists, Googlebot ignores the wildcard group entirely, so shared rules must be repeated.

Should I block CSS and JavaScript?

Never. Google renders pages to evaluate them, so blocking assets makes it render a broken page and judge it accordingly, including for mobile usability.

What happens if robots.txt returns an error?

A 404 means everything is allowed. A persistent 500 can make Google treat the whole site as disallowed, so the file's availability is a real uptime concern.

Privacy & Security

Runs in your browser. Nothing you enter is uploaded or stored.

Data: None
Server-side-Side
Active
v1.0

About This Tool

This tool runs entirely in your browser. No data is sent to any server, ensuring complete privacy. Simply use the interface above to get started — no registration or login required.

Disclaimer: This tool is provided "as is" without warranty of any kind. Results are for educational and utility purposes.