Search 110+ free tools… (e.g. json, vpn, password) ⌘K
Link Tools Dereferer Hide Referrer Link URL Shortener Affiliate Cloaker PayPal Links PayPal DonationPayPal Links Privacy Tools Password Generator Cloudflare Resolver My Referrer Torrent Tools Magnet → Torrent Torrent → Magnet Torrent Editor Pirate Bay Proxies Movierulz Proxies ExtraTorrent Proxies Dev Tools Base64 Encoder Hash Generator HTTP Headers Disposable Email Checker Company Blog About Us Contact Anonymize Free
Webmaster Tool

Robots.txt Tester

Fetch any site's robots.txt and test whether a URL is allowed or blocked for Googlebot, Bingbot and other crawlers.

What is robots.txt?

robots.txt is a plain text file placed at the root of your domain that tells search engine crawlers which parts of your site they may request. It follows the Robots Exclusion Protocol, which every major crawler — Googlebot, Bingbot, DuckDuckBot and others — reads before fetching your pages. The file is public: anyone can view it at yoursite.com/robots.txt, so it should never be used to hide sensitive URLs.

How the Directives Work

User-agent selects which crawler the following rules apply to, with * meaning all of them. Disallow blocks a path prefix, while Allow carves out an exception inside a blocked directory. An empty Disallow: permits everything. Rules are matched by prefix, not by exact URL, so Disallow: /admin also blocks /administrator — a common and costly mistake. Where rules conflict, most crawlers apply the most specific match rather than the first one listed. Adding a Sitemap: line pointing at your XML sitemap helps crawlers discover your pages faster.

Blocking Is Not the Same as Deindexing

This is the single most misunderstood point about robots.txt. Disallowing a URL stops crawlers from reading it, but the URL can still be indexed if other sites link to it — appearing in results with no description. Worse, if a page is blocked in robots.txt, Google cannot see a noindex tag on it, so blocking actively prevents removal. To keep a page out of search results, allow crawling and use a noindex meta tag or an X-Robots-Tag header instead. Use robots.txt to manage crawl budget, not to control indexing.

Frequently Asked Questions

Where does robots.txt have to be located?+
It must sit at the root of the domain, for example https://example.com/robots.txt. A file placed in a subdirectory is ignored entirely. Each subdomain needs its own file, and it must be served over the same protocol and host that crawlers request.
Will Disallow remove a page from Google?+
No. Disallow prevents crawling, not indexing. A blocked URL can still appear in search results if other pages link to it, usually without a description. To remove a page, allow crawling and add a noindex meta tag or X-Robots-Tag header so Google can actually read the instruction.
Do I need a robots.txt file at all?+
Not necessarily. If you want everything crawled, you can omit it and crawlers will proceed normally. A missing file returns 404 and is treated as permission to crawl everything. It is still worth adding one to declare your sitemap location and to block genuinely wasteful paths like internal search results.
Why is my Disallow rule being ignored?+
The usual causes are: the rule sits under a User-agent block that does not match the crawler, a more specific Allow rule overrides it, the path prefix is wrong, or the file is not returning HTTP 200. Some crawlers also cache robots.txt for up to 24 hours, so recent edits may not have taken effect yet.
Can robots.txt hide private content?+
No, and it should never be used that way. The file is publicly readable, so listing a path there advertises its existence to anyone looking. Genuinely private content needs authentication, IP restrictions, or server-side access control.
Done!