RevealTheme logo

robots.txt Inspector

Fetch a live robots.txt from any URL and see its directives grouped by user-agent. The tool reads the file as published and lays out the Allow, Disallow, and Sitemap lines for each crawler block.

How to use this tool

  1. 1

    Enter a site URL, for example https://example.com. If you leave off the path, the tool appends /robots.txt automatically.

  2. 2

    Click Analyze. The server fetches that site's live robots.txt and returns it.

  3. 3

    Read the raw file at the top, then scroll the parsed cards below to see Allow, Disallow, and Sitemap entries grouped by User-agent.

  4. 4

    Adjust the URL and analyze again to compare another host or a different environment.

What does the robots.txt Inspector actually do?

robots.txt is a plain-text file served at the root of a domain (for example example.com/robots.txt) that tells web crawlers which paths they may or may not request. Defined informally since 1994 and standardized as RFC 9309 in 2022, it groups directives under one or more User-agent lines, each followed by Allow and Disallow rules plus optional Sitemap references. This inspector fetches the live file from a URL you supply and parses it line by line: it splits each line on the first colon, ignores blank lines and comments that start with #, and recognizes four directives — User-agent, Allow, Disallow, and Sitemap. It then groups those into per-crawler cards and shows the raw file (truncated at 5000 characters) above them. The parser is deliberately simple. It does not interpret wildcards, evaluate path precedence, or test whether a specific URL would be allowed for a given bot. Non-standard lines such as Crawl-delay and Host are silently skipped, and each User-agent line starts a fresh group rather than merging consecutive agents. Treat it as a fast way to read and audit what a site actually publishes, not as a compliance validator.

Common use cases

  • Confirm a production site is not accidentally serving Disallow: / that blocks every crawler before a launch.

  • Audit a competitor's robots.txt to see which sections they keep out of search engines.

  • Check that your Sitemap directive is present and points at the correct sitemap URL.

  • Compare the robots.txt on a staging host against production to catch a stray block before deploy.

  • Verify that a specific bot, such as GPTBot or Bingbot, has its own group with the rules you expect.

  • Quickly inspect any third-party domain's crawl rules when debugging why a page is missing from search results.

Frequently asked questions

Does this test whether a specific URL is blocked for a crawler?
No. It lists and groups the directives a site publishes but does not evaluate wildcard matching or path precedence. For allow/block testing against a real bot, use Google Search Console's robots.txt report.
Can I paste robots.txt text directly?
Not currently. The tool takes a URL and fetches the live file from that host, so you cannot check an undeployed draft this way. Deploy the file first, then inspect the URL.
Is my data uploaded anywhere?
The URL you enter is sent to this site's server, which fetches that domain's robots.txt on your behalf and returns the result. The fetch happens server-side, not in your browser.
Why is the Crawl-delay or Host line missing?
The parser only recognizes User-agent, Allow, Disallow, and Sitemap. Non-standard directives like Crawl-delay and Host are skipped in the parsed cards, though you can still see them in the raw file shown above.
Where does robots.txt have to live?
At the root of the domain, such as example.com/robots.txt. A file in a subdirectory is not honored. If you omit the path, this tool appends /robots.txt to the URL you enter.
What is the difference between Disallow and noindex?
Disallow asks crawlers not to request a path, while noindex (a meta tag or header) asks them not to index it. A disallowed page can still appear in results from external links, so they are not interchangeable.
Why is a Sitemap line not showing up?
Sitemap entries are attached to the current User-agent group, so a Sitemap line that appears before any User-agent block, or one you expected to be global, may not display as you assume. Check the raw file to confirm the exact placement.

Related tools