Skip to content

robots.txt tester for AI and search bots

Paste your robots.txt file and a page address to see which AI and search bots may visit that page, and the line that decides, if any.

Paste your file over this example
Its full address, like https://example.com/blog/post-1
Test other bots (optional)
Separate names with commas, like ExampleBot, AnotherBot

Follows RFC 9309, the robots.txt standard. Bot list checked to . How we check.

What the robots.txt tester shows

The example already in the form gives these results for 8 of the bots and tokens:

robots.txt
User-agent: *
Allow: /

User-agent: GPTBot
User-agent: CCBot
User-agent: Google-Extended
Disallow: /blog/

URL: https://example.com/blog/post-1

What the tester returns for this file and page
BotResultDecided by
GooglebotSearchAllowedallow: /line 2, group *
BingbotSearchAllowedallow: /line 2, group *
OAI-SearchBotAI searchAllowedallow: /line 2, group *
PerplexityBotAI searchAllowedallow: /line 2, group *
GPTBotAI trainingBlockeddisallow: /blog/line 7, group GPTBot
CCBotOtherBlockeddisallow: /blog/line 7, group CCBot
Google-ExtendedControl tokenBlockeddisallow: /blog/line 7, group Google-Extended
ChatGPT-UserUser-triggeredNo tokenNo documented robots.txt token

OpenAI says robots.txt rules "may not apply" to ChatGPT-User, which fetches pages when a person asks.

How to read your file by hand

  1. Find every group whose User-agent line names the bot (capital letters do not matter). Treat them as one group.
  2. If none does, try the bot's backup name, then the * group.
  3. Compare each rule with the part of the page address after the site name, from its first character.
  4. In a rule, a * matches anything, and a $ at the end means the address must end there.
  5. The longest matching rule wins. If an allow and a disallow rule are the same length, allow wins. If no rule matches, the bot is allowed.

The tester checks the 65 bots and tokens in the crawler list. The method covers encoding, size limits and what robots.txt cannot tell you.

Help with the results

What "Not applied" means

The operator says the crawler does not follow robots.txt, or usually does not, often because a person asked it to fetch the page. The tester still shows what the rules would say.

What "No token" means

The operator documents no robots.txt token for that fetcher, so there is no group to look up. Google's user-triggered fetchers are an example.

What "Depends" means

The operator's own documentation reads robots.txt differently from RFC 9309, and here the two readings disagree. The result shows both. The method lists these cases.

Why a bot is allowed when your * group blocks everything

A group naming it may allow the URL, or it may ignore the * group, as Google's AdsBot does. The "Decided by" column shows which.

What happens to your file

What you paste or type here stays in your browser. Our server fetches a site's /robots.txt only when this page's address ends in ?site= and a site name. The home page's check sends you there when a file is too long for a link. Our server fetches the file once and does not save it. A share link carries the file after the # in the address, and browsers do not send that part to servers.