geo/aeoplaybooks
Check your visibility →
Free · alerts only on change

AI Access Watchdog

Two plain-text files decide whether AI engines can see you at all: robots.txt and llms.txt. Both change silently — a WAF preset, a plugin update, a migration. The watchdog checks them daily and emails you only when something changed. No dashboard to remember, no weekly digest. Silence means you're fine.

Free · one domain per email · double opt-in · unsubscribe in one click.

What triggers an alert

robots.txt

Any tracked AI crawler flips between allowed and blocked. A blanket Disallow: / from a WAF or plugin is the most common way sites go invisible without anyone noticing.

llms.txt

The file appears or disappears. SPAs and migrations love to quietly replace it with an HTML 404 — we classify that as gone, same as our validator does.

Reachability

Your files become unreachable to a datacenter probe. If we can't fetch them, AI crawlers likely can't either — this failure mode once cost this very site 90 points. Post-mortem.

New bots

A new AI crawler joins our tracked registry — you get one note saying whether your current robots.txt allows or blocks it. The registry update itself becomes your alert.

Currently tracked crawlers

Robots verdicts follow the same rule as the Bot Access Matrix: a bot counts as blocked only on a blanket Disallow: / with no Allow: / override. WAF-level blocks don't show in robots.txt — check those live in the matrix.

Frequently asked questions

How often do you check, and what exactly?
Once a day we fetch your robots.txt and llms.txt and compare them with the stored baseline. For robots.txt we evaluate the verdict for each tracked AI crawler (blanket Disallow: / with no override counts as blocked); for llms.txt we track whether a real file is being served at all.
Will you email me a weekly summary?
No. The whole point is the opposite: silence means nothing changed. You get an email only on a change — a crawler blocked or unblocked, llms.txt appearing or disappearing, your files becoming unreachable, or a new AI bot joining our tracked registry.
Why would my robots.txt change without me knowing?
More often than you'd think: a CDN or WAF preset update, a CMS plugin "optimizing" crawl budget, a staging config shipped to production, a migration dropping the file. Our own checker once scored this site 10/100 because of an edge rule nobody looked at — that incident is why this tool exists.
What does it cost?
Nothing — one domain per email address, double opt-in, unsubscribe in one click in every email. If you want the full 5-signal score and real AI answers watched too, that's the paid Monitor (from $20).