Reflyma / Robots.txt Analyzer

Read your robots.txt like a search engine does.

We parse every directive, spot silent conflicts and translate technical rules into plain English — with AI-crawler awareness built in.

  • Free to run
  • No account required
  • Live results
  • Evidence-backed
Robots.txt Analyzer
Enter a URL above to run this tool
Ready to run
yourbrand.com · robots.txt analyzerready to run
Enter a URL above to run this tool.
How it works

From URL to evidence-backed result.

  1. Fetch robots.txt

    Follow redirects and validate delivery.

  2. Parse directives

    Group by user agent, resolve precedence.

  3. Flag issues

    Warn on ambiguous, conflicting or dangerous rules.

What you get

Built for AI search visibility.

Silent-issue detection

Catches mistakes that leave AI bots blocked without you knowing.

AI-crawler aware

Special reporting for GPTBot, ClaudeBot, PerplexityBot and Google-Extended.

Safe recommendations

Every suggestion is scoped so it can't accidentally deindex your site.

Field guide

Reading robots.txt the way a crawler does

robots.txt is four lines of text that can quietly remove an entire site from search results and AI answers. This analyzer fetches the live file, parses every group, and reports how each rule applies to the crawlers that matter — including the AI agents that most generated robots.txt templates never mention.

How the file is parsed

Rules are grouped by user-agent. A crawler uses the most specific group that names it and ignores the others entirely — it does not merge a specific group with the wildcard group, which is the source of most surprises.

Within a group, the longest matching path wins, and Allow beats Disallow at equal length. We apply those rules literally so you see the outcome rather than the intention.

  • Group structure and user-agent matching
  • Allow and Disallow precedence by path length
  • Sitemap declarations and their absolute URLs
  • Crawl-delay and unsupported directives
  • Syntax errors, encoding issues and stray HTML

The failures that cost the most

A production file still carrying 'Disallow: /' from a staging deployment is the classic catastrophic case. Less obvious, and far more common, is a specific AI user-agent group that allows nothing because its author assumed the wildcard rules still applied.

Blocking asset directories is the quiet one: when CSS or JavaScript is disallowed, renderers cannot lay the page out and may misjudge what the page contains.

  • Never ship 'Disallow: /' to production
  • Repeat needed Allow rules inside specific agent groups
  • Keep CSS, JS and image paths crawlable
  • Declare your sitemap with an absolute URL
  • Serve the file as plain text with a 200 status

What robots.txt cannot do

It is not a security control and not a reliable way to keep a page out of an index. Disallowed URLs can still be listed if other sites link to them; use noindex or authentication for anything that must stay private.

It is also advisory. Well-behaved crawlers comply, unnamed scrapers do not, and blocking those is a job for your firewall.

Keeping it correct over time

Treat robots.txt as code: keep it in version control, review changes in pull requests, and re-run this analyzer after each deploy. Most damaging robots.txt incidents are deploys, not decisions.

Pair the check with the AI bot access checker to confirm the specific answer engines you care about can still reach your pages.

FAQ

Questions, answered.

Does robots.txt hide a page from search?+

No. It asks crawlers not to fetch it. Use a noindex directive or authentication to keep a page out of results.

Do wildcard rules apply to a named crawler?+

No. If a crawler has its own group, only that group applies. Repeat any rules it still needs.

Should I add AI crawlers explicitly?+

Only if you want different rules for them. Otherwise the wildcard group already covers them.

Where must the file live?+

At the root of each host and protocol you serve, returned as plain text with a 200 status.

Does Disallow block AI training?+

For most vendors, yes — but not all. We flag per-bot behaviour so you don't rely on assumptions.

Where should robots.txt live?+

At the root: /robots.txt on your primary domain, served over HTTPS with a 200 response.

Reflyma

Track your brand across ChatGPT, Gemini, Perplexity and Claude.