A broken robots.txt can silently de-index your whole site. Paste your robots.txt or fetch it from a URL — we lint it for the dangerous and the obsolete. (For AI-bot specifics, use the AI access checker.)
A robots.txt validator lints the plain-text file at your domain's root that tells crawlers which paths they may fetch, flagging rules that are dangerous — like an accidental whole-site block — or obsolete, meaning directives search and AI engines no longer honor. Because ChatGPT, Perplexity, and Google's crawlers read robots.txt before touching a page, a single stray `Disallow: /` can make your whole site invisible to the engines that would otherwise cite it. This check catches those errors and missing signals like the Sitemap line before they cost you crawling and citations.
An accidental `Disallow: /` under `User-agent: *` — it blocks every crawler from your whole site, so nothing gets indexed or cited. It's usually a staging rule that shipped to production.
Yes. AI crawlers read robots.txt first, so a whole-site `Disallow` or a bot-specific block keeps ChatGPT, Perplexity, and similar engines from reading and citing your pages.
Google and most AI crawlers ignore `Crawl-delay`; only some engines such as Bing still honor it (Yandex dropped the directive in favor of a crawl-rate setting in Yandex.Webmaster). The validator flags it so you don't rely on a directive that does nothing where it matters most.
No — robots.txt controls crawling, not indexing. A blocked URL can still appear in results without a snippet; to keep a page out of the index, use a `noindex` meta tag instead.
Free tools show you WHAT to fix. The full audit + the autonomous team of 20 AI agents fix it end-to-end — strategy, content, GEO, internal links, publishing and day-2 upkeep.
All free tools →cookies
The Matrix already knows everything about you — cookies are small change by comparison. The choice, as always, is yours: