Find out which AI bots are blocked from your site. GPTBot, PerplexityBot, ClaudeBot, Googlebot-Extended — all of them, in one click.
Every user-agent is checked against the exact rules in your robots.txt — no guessing, no heuristic.
GPTBot
OpenAI
ChatGPT-User
OpenAI
OAI-SearchBot
OpenAI
ClaudeBot
Anthropic
Claude-User
Anthropic
Claude-SearchBot
Anthropic
PerplexityBot
Perplexity
Perplexity-User
Perplexity
Googlebot-Extended
Applebot-Extended
Apple
Amazonbot
Amazon
meta-externalagent
Meta
Bytespider
ByteDance
Cohere-AI
Cohere
DuckAssistBot
DuckDuckGo
Type your root domain — fawnwear.com, not the full robots.txt URL. We handle the protocol and path.
A safe server-side request from a fixed BrandCitation user-agent. No JS execution, no redirect tricks.
Each user-agent group is matched against the known AI bot list. Allowed, blocked, or unmatched — with the exact line.
Blocked bots → copy a ready-to-paste allow block. Healthy robots.txt → see the per-bot breakdown for the record.
robots.txt is a plain-text file at the root of your domain that tells crawlers which paths they may or may not request. For AI engines like GPTBot, ClaudeBot, PerplexityBot, and Googlebot-Extended, an explicit allow rule is the difference between being cited in their answers and being invisible.
The ones that drive AI Overviews and answer engines: GPTBot, ChatGPT-User, OAI-SearchBot, ClaudeBot, Claude-User, Claude-SearchBot, PerplexityBot, Perplexity-User, Googlebot-Extended, Applebot-Extended, Amazonbot, meta-externalagent, Bytespider, Cohere-AI, and DuckAssistBot. This auditor checks all of them in a single fetch.
A bot is marked blocked if your robots.txt contains a User-agent: <bot> group with at least one Disallow rule that covers the path being fetched. Blocked bots cannot read your content, so they cannot cite it. The auditor surfaces the exact matched rule so you can decide whether to keep it.
Unmatched means your robots.txt has no User-agent: <bot> group, and no wildcard User-agent: * rule. Most well-configured sites use either an explicit allow for the bot or a wildcard allow. Unmatched is the safest fallback — the bot may still crawl, but you have not given it explicit permission.
No. Googlebot (traditional search) and Googlebot-Extended (AI Overviews) are separate user-agents. Blocking Googlebot-Extended only stops Google from training Gemini on your content or using it in AI Overviews — your normal Google Search rankings are unaffected.
A server-side fetch of https://<your-domain>/robots.txt from a fixed BrandCitation user-agent. We never execute JavaScript on your site, never follow malicious redirects, and never request paths outside the robots.txt endpoint. The check takes under 5 seconds.