Skip to main content
No API call

Check whether robots.txt lets a bot fetch a URL

Paste a link and see what the site's robots.txt says about that exact path — for URLpipe's user agent and for every crawler that has no group of its own — and which rule decides it.

  • No signup
  • No credit card
  • The rules URLpipe itself follows

Free · no signup · 2 runs every 10 minutes

…or try one of these

Your result will appear here.

Enter a URL above, or pick one of the example pages.

What you get

  • An allowed or disallowed verdict for URLpipe and for *
  • The user-agent group that applied and the rule that matched
  • The robots.txt file itself, as the site serves it

How it works

  1. 1We fetch the site's /robots.txt from our own network, following up to 5 redirects.
  2. 2Rules are read the RFC 9309 way: the group naming the agent applies, else the * group; the longest matching rule wins, and an allow beats a disallow of the same length.
  3. 3You see the verdict for each agent, the rule that decided it and the file.

What people use it for

  • Check a rule before you ship a robots.txt change
  • Find out whether URLpipe will fetch a page, before you ask it to
  • Debug * wildcards and $ anchors against a real path

Frequently asked

Yes, by default, on every project: before a page is visited, the site's robots.txt is checked for the URLpipe user agent, and a disallowed page is not fetched. A customer can turn that off for a project, and is then responsible for having the right to fetch those pages.

Ready to use it in production?

Get a free API key and call every endpoint from your own code — 1,000 credits a month, no credit card.