S
SCRAWL

Google Robots.txt Tester

Test any URL against your robots.txt rules. Simulate Googlebot, Bingbot, and other crawlers to verify allow and disallow directives. Free SEO tool, no login.

Step-by-step guide
Google Robots.txt Tester: Test Rules Before Blocking

# Test Your Robots.txt Against Googlebot Before You Block Everything One bad robots.txt rule can tank your search visibility overnight. You write a single `Disallow:` line, forget about it for six months, and Google stops indexing 40% of your site because you accidentally blocked a critical directory. You won't see traffic drop immediately—crawl budget gets wasted on pages that never show up in search results. The real issue is that most people write robots.txt rules in a text editor, upload them, and never actually test what Googlebot will see. They assume the syntax is correct. It isn't, half the time. What Is a Robots.txt Tester? Robots.txt Tester is a free browser-based tool that simulates how Googlebot interprets your robots.txt directives on specific URLs. You paste your robots.txt file or point it at your domain, enter a URL path you want to check, and it tells you whether that path would be crawled or blocked. No login needed. No installation. You get an instant yes/no answer with the exact rule that triggered the result. Think of it as a dry-run before you push a robots.txt change to production. You're testing the rule against Googlebot's actual parsing logic, not guessing based on what you remember from an old blog post. Why It Matters for SEO Robots.txt blocks are permanent until you fix them. Google recrawls most sites every 3 to 7 days, so if you block `/products/` by accident, that section stays invisible for at least a week. If your site has 100,000 pages and 20% of them are blocked by a typo in your robots.txt, you've just nuked 20,000 URLs from search visibility. The second issue is crawl budget waste. Googlebot allocates a fixed amount of bandwidth to crawl your site each day. If your robots.txt tells it to skip half…

Read the full guide

This Google robots.txt tester simulates Googlebot against your live robots.txt file. Enter your site URL and a page path to see whether crawlers are allowed or blocked — and which rule matched.

What is a Google robots.txt tester?

This tester fetches your live robots.txt and simulates whether Googlebot, Bingbot, or a wildcard user-agent is allowed to crawl a specific URL path. It parses Allow, Disallow, and Crawl-delay rules per user-agent block, then reports the matching rule so you know exactly why a path is allowed or blocked — before you ship a change that can wipe organic traffic.

When to run this test

Run it before every robots.txt edit, after staging-to-production deploys, and after CMS or CDN migrations. The most expensive failure mode is copying a staging robots.txt that Disallows all crawlers onto production — pages can drop from Google within a day or two. Also re-test when URL structures change (new /blog/ paths, faceted /filter/ URLs) because a broad Disallow pattern often blocks more than you intended.

How we check this (worked example)

Take a file that includes: User-agent: * Disallow: /admin/ Disallow: /search Allow: /search/help

What Should You Know Before Using Robots.txt Tester?

Testing /search/results against Googlebot should show blocked by Disallow: /search. Testing /search/help should show allowed by the more specific Allow rule. Testing /admin/login should show blocked. If your homepage unexpectedly shows blocked, look for Disallow: / or a staging leftover — that is the first place we look in post-migration audits.

What to do after you change robots.txt

Ship the file, wait for crawlers to re-fetch it (often within 24–48 hours), then confirm key URLs in Google Search Console URL Inspection. Pair this tester with the Google Index Checker and Bulk Meta Robots Checker: robots.txt controls crawl access, while meta robots and X-Robots-Tag control indexing after a page is fetched.

Frequently Asked Questions

How do I test my robots.txt file?

Enter your site's robots.txt URL and the specific page URL you want to test, then select the crawler to simulate. The tool fetches your live robots.txt, parses every rule, and tells you whether the page is allowed or blocked — and which exact rule matched the decision.

What happens if robots.txt blocks Googlebot?

If Googlebot is blocked from crawling a URL, that page cannot be indexed and will not appear in Google Search results. A common disaster is deploying a staging robots.txt (which typically blocks all crawlers) to production. Check immediately after any server change by testing your homepage and key pages.

What is the difference between robots.txt disallow and noindex?

Disallow in robots.txt prevents crawlers from fetching a URL but does not remove it from the index — Google may still index the URL if it sees links to it. A noindex meta tag (or X-Robots-Tag header) must be read by Googlebot to take effect, which requires the page to be crawlable in the first place.

Can robots.txt block specific crawlers?

Yes. Robots.txt uses user-agent directives to apply rules to specific crawlers. You can block Googlebot while allowing Bingbot, or block all crawlers with User-agent: * while creating exceptions for specific bots. The Robots.txt Tester lets you simulate any user-agent to see which rules apply.

Does robots.txt affect PageRank?

Disallowing a URL in robots.txt prevents Googlebot from crawling it, which means PageRank from links to that URL is not passed further to other pages it links to. If you want to prevent indexing without losing internal PageRank flow, use a noindex directive on a crawlable page rather than a robots.txt disallow.

Compare with SmallSEOTools — ad-free alternative