Skip to content
XUtilHub

Robots.txt Tester – Check if a URL Is Blocked

Test whether Googlebot, Bingbot or AI crawlers can crawl your URLs. Fetch any site's robots.txt or paste your own and see the exact matching rule.

  • Free, no sign-up
  • Fetches public pages only, nothing stored
robots.txt

About the Robots.txt Tester

Paste a robots.txt or fetch it from any website, then test a list of URLs for a chosen crawler. Each URL shows whether it's allowed or blocked and which line decided it, using the same matching rules as Google.

Key features

  • Fetch any site's live robots.txt or paste your own
  • Test hundreds of URLs at once
  • Choose Googlebot, Bingbot, AI crawlers or any bot
  • Shows the exact line that allowed or blocked each URL
  • Google's matching rules: longest match, wildcards and $
  • Flags syntax problems and lists declared sitemaps

Check exactly what your robots.txt blocks

One misplaced slash in robots.txt can block important pages, or fail to block the ones you meant to. Paste your file (or fetch it from a live site), enter some URLs and pick a crawler to see allowed or blocked, with the rule responsible.

Matching rules (RFC 9309)

RuleExampleMatches
Prefix matchDisallow: /admin/admin, /admin/, /administrator
Folder onlyDisallow: /admin//admin/ and below, not /administrator
WildcardDisallow: /*?sort=Any URL with ?sort=
End anchorDisallow: /*.pdf$URLs ending in .pdf, not .pdf?x=1
EmptyDisallow:Nothing (allows everything)

Example

User-agent: *
Disallow: /admin/
Allow: /admin/help/
URLResultWhy
/admin/settingsBlockedDisallow: /admin/
/admin/help/faqAllowedLonger Allow: /admin/help/ wins
/aboutAllowedNo rule matches

Testing tips

  1. Test your most important pages first: home, category and product pages.
  2. Test with Googlebot and *, as other search engines may fall back to *.
  3. Re-test after every change. A new wildcard can block more than you expect.
  4. Use Google Search Console's robots.txt report to see what Google last fetched.

Create a robots.txt with the Robots.txt Generator, or check a page's meta robots tag with the Meta Tag Checker.

How to use the Robots.txt Tester

  1. Enter the address of the page or website you want to check.
  2. Click the button. Our server fetches the public page (it can't reach private or local addresses).
  3. Review the results, starting with anything marked in red or amber.
  4. Fix the issues on your site, then run the check again to confirm.

Frequently asked questions

How does Google decide when Allow and Disallow both match?

The rule with the longest path wins, because it's the most specific. If an Allow and a Disallow rule are the same length, Allow wins.

Which group applies to Googlebot-Image?

A crawler uses the group with the most specific matching user agent. Googlebot-Image follows a Googlebot-Image group if one exists, otherwise the Googlebot group, otherwise the * group.

Is the robots.txt file case-sensitive?

Directive names like Disallow aren't, but paths are: Disallow: /Admin doesn't block /admin.

What if a site has no robots.txt?

If robots.txt returns 404, crawlers treat everything as allowed. A server error (5xx) can make Google pause crawling the site.

Do these tools store the pages I check?

No. Pages and robots.txt files are fetched on demand to analyze them and are not saved. The robots.txt generator, tester and meta tag generator run entirely in your browser.

Can I check pages on localhost or my intranet?

No. For security, our server only fetches public websites. For a private page, use the 'Paste HTML' option of the meta tag checker.

Do the tools respect robots.txt?

The sitemap crawler follows your robots.txt rules and skips pages marked noindex, just like a search engine would.

Last updated:

Related SEO tools