Robots.txt Tester
Fetch a site's robots.txt or paste your own, then test any URL. See which crawlers may visit it, Googlebot and the AI bots alike, and which line decides.
- Free, no sign-up
- Google's matching rules
- Googlebot + AI crawlers
- Paste mode stays in your browser
Testing: /. Paths are case-sensitive.
How to use the robots.txt tester
- Fetch the live file: enter the site or any page on it; the tester loads
/robots.txtfrom that host. Or paste rules to test a change before you publish it. - Enter the URL or path to test. Paths are case-sensitive, and the query string counts:
/shop/?sort=priceis a different path from/shop/. - Read the table. Each crawler is Allowed or Blocked, with the line that decided and the user-agent group it used. The deciding line for Googlebot is highlighted in the file.
How Google reads robots.txt
The tester follows Google's documented rules:
- Groups. A group starts with one or more
User-agentlines followed by rules. A crawler uses the group for the most specific user agent that matches it; if none matches, the*group. Several groups for the same user agent are merged. A crawler with its own group ignores the*group completely, which is the most common surprise: rules you wrote for everyone don't apply to Googlebot once you add a Googlebot group. - Longest match wins. Within the group, the rule whose path matches the most characters decides. When an
Allowand aDisalloware equally long,Allowwins. - Wildcards.
*matches any run of characters;$marks the end of the URL.Disallow: /*.pdf$blocks/guide.pdfbut not/guide.pdf?download=1. - Supported fields. Google reads
user-agent,allow,disallowandsitemap. It ignorescrawl-delayand anything else; the tester lists those lines. - Size. Google reads the first 500 KiB of the file.
Some Google crawlers obey more than one token. Googlebot-Image, for example, follows a Googlebot-Image group if there is one and otherwise the Googlebot group.
When robots.txt itself fails
| robots.txt returns | Google's behavior |
|---|---|
| 200 | Applies the rules |
| 404 or other 4xx (except 429) | Treats the site as having no rules: everything may be crawled |
| 5xx, or the server doesn't respond | Stops crawling the site for up to 12 hours, then uses its last cached copy for up to 30 days |
A robots.txt that errors out is worse than having none at all. Search Console's robots.txt report shows when Google last fetched your file and whether it could parse it.
Blocking crawling is not blocking indexing
Disallow stops crawlers from fetching a page. It doesn't keep the URL out of Google: a blocked page that other sites link to can still be indexed, usually with no description, and Search Console reports “Indexed, though blocked by robots.txt”. To keep a page out of search results, let Google crawl it and add noindex. Our redirect & indexability checker checks both for any URL.
AI crawlers
AI companies crawl with their own user agents, so you can decide about them separately from search:
| Crawler | What it's for |
|---|---|
| GPTBot | Collecting content for OpenAI's models |
| OAI-SearchBot | ChatGPT's search results |
| ClaudeBot | Anthropic's crawler |
| PerplexityBot | Perplexity's search index |
| Google-Extended | A control token: whether Google may use your content for Gemini. Google says it doesn't affect Google Search |
| Applebot | Apple's Siri and Spotlight search |
Blocking one of them doesn't affect Googlebot. If being cited by ChatGPT or Perplexity matters to your business, check that their search crawlers are allowed; it is one of the first things we look at in AI search optimization.
Robots.txt tester FAQ
Google uses the group of rules for the most specific user agent that matches its crawler, or the * group if none does. Within that group, the rule with the longest matching path wins, and when an Allow and a Disallow are equally long, Allow wins. A crawler with its own group ignores the * group entirely.
No. robots.txt stops crawling, not indexing. A blocked URL can still be indexed from links, usually without a description, and Search Console then reports “Indexed, though blocked by robots.txt”. To keep a page out of Google, allow crawling and add a noindex tag.
Yes. AI crawlers have their own user agents: GPTBot and OAI-SearchBot (OpenAI), ClaudeBot (Anthropic), PerplexityBot. Google-Extended controls whether Google may use your content for Gemini; Google says it doesn't affect inclusion or ranking in Google Search. Blocking these doesn't touch Googlebot.
A 404 or other 4xx (except 429) means “no rules”: crawlers may crawl everything. A 5xx error is serious: Google stops crawling the site for up to 12 hours, then works from its last cached copy of the file for up to 30 days.
No. Google reads only user-agent, allow, disallow and sitemap. The tester lists every line Google ignores, including crawl-delay and unsupported fields like noindex.
Not sure what to block?
We review robots.txt, sitemaps and crawl settings as part of a technical SEO audit, including which AI crawlers to allow, and send a prioritized list of fixes.