Robots.txt Tester
Check whether a URL is blocked for Googlebot, Bingbot, AI crawlers and more.
- Runs in your browser
- Nothing is uploaded
- Free, no sign-up
Using the rules for User-agent: *
| Path | Result | Decided by |
|---|---|---|
| / | Allowed | No rule matches |
| /admin/settings | Blocked | Disallow: /admin/ (line 2) |
| /admin/help/faq | Allowed | Allow: /admin/help/ (line 5) |
| /blog/how-to-sort-lines | Allowed | No rule matches |
| /search?q=shoes&sessionid=42 | Allowed | No rule matches |
| /assets/logo.png | Allowed | No rule matches |
Sitemaps declared: https://example.com/sitemap.xml
About this tool
Paste a robots.txt, choose a crawler and list the URLs you care about. For each one you see whether it is allowed or blocked, and exactly which line decided it. The file is also checked for the mistakes that quietly cost sites their traffic.
How to use it
- Paste your robots.txt, or edit the sample.
- Pick the crawler to test as, then list URLs or paths, one per line.
- Read the verdicts, and check any warnings under the table.
How a crawler reads the file
A robots.txt is a list of groups. Each group starts with one or more User-agent lines and is followed by the Allow and Disallow rules for those crawlers.
- The crawler picks the group whose user-agent matches its own name, ignoring case. If there is none, it uses the
*group. It uses only that group: a specific group replaces*completely, it does not add to it. - Within the group, every rule whose pattern matches the URL's path and query is considered.
- The longest matching pattern wins. If an Allow and a Disallow match with the same length, Allow wins.
The order of lines inside a group does not matter, which surprises people used to firewall rules.
Pattern syntax
Patterns are matched from the start of the path, so they are prefixes unless you say otherwise. Two special characters exist: * matches any run of characters and $ marks the end of the URL.
| Rule | Blocks | Does not block |
|---|---|---|
Disallow: /shop |
/shop, /shop/, /shopping |
/store |
Disallow: /shop/ |
/shop/shoes |
/shop, /shopping |
Disallow: /*.pdf$ |
/files/a.pdf |
/files/a.pdf?dl=1 |
Disallow: /*?sessionid= |
/page?sessionid=9 |
/page?x=1&sessionid=9 |
Disallow: / |
everything | nothing |
Disallow: (empty) |
nothing | everything |
Paths are case-sensitive: /Admin and /admin are different.
What robots.txt does not do
It does not remove pages from search. A blocked URL can still be indexed, as a bare link with no description, if other pages link to it. To keep a page out of the index, leave it crawlable and add a noindex robots meta tag or an X-Robots-Tag header. If you block the page, Google never sees the tag.
It is not security. The file is public, and well-behaved crawlers choose to obey it. Anything private needs authentication.
It no longer supports noindex. Google stopped honouring that line in 2019. If you have one, it does nothing.
Controlling AI crawlers
Several AI companies publish a crawler name you can address in its own group:
- GPTBot is OpenAI's crawler for training data.
- ClaudeBot is Anthropic's.
- CCBot is Common Crawl's, whose data many models are trained on.
- Google-Extended is a control token, not a separate crawler. Blocking it stops your content being used to train Google's Gemini models, and has no effect on Search.
Compliance is voluntary, though the major operators document that they follow it. To block one of them from the whole site, give it its own group with Disallow: /, as in the sample.
Frequently asked questions
Why is a page I blocked still in Google's results?
Blocking stops crawling, not indexing. If other sites link to the URL, Google can list it without ever visiting. Use a noindex tag on a crawlable page to remove it from results.
Can I test my live robots.txt by entering my domain?
Browsers do not allow one site's page to fetch another site's file, so paste the contents instead. Open yourdomain.com/robots.txt in a tab and copy it across.
Do I need a robots.txt at all?
No. Without one, crawlers assume everything is allowed. You need it to block sections, to point crawlers to your sitemap, or to address specific bots.
Does this match exactly what Google does?
It follows RFC 9309 and Google's published rules, including wildcards and longest-match precedence. For a final check on a live site, also use the robots.txt report in Search Console.
Related tools
Robots.txt Generator
Build a robots.txt with per-crawler rules and sitemap entries.
XML Sitemap Generator
Create a valid XML sitemap from a list of URLs, split automatically when large.
Meta Tag Generator & SERP Preview
Write titles and descriptions with a live Google preview.
Redirect Generator
Turn a list of old and new URLs into redirect rules for your server or host.