A Free Chrome Extension to Audit llms.txt, robots.txt, ACP, and UCP Readiness on Any Site

A Free Chrome Extension to Audit llms.txt, robots.txt, ACP, and UCP Readiness on Any Site

If you've shipped an llms.txt file recently, you've probably asked yourself the same question I did: does this actually work, or did I just create a file that returns a 404 with a 200 status code?

There's no linter for llms.txt yet. There's no curl one-liner that checks whether your Markdown alternates resolve, whether your robots.txt is blocking the wrong agents, or whether your product catalog exposes anything an ACP- or UCP-aware shopping agent could parse. So most of us either skip the verification step entirely or write a throwaway script and forget to maintain it.

Clustova AI Readiness Inspector is a Chrome extension that does this verification for you, on demand, on whatever page you currently have open.

Link: Clustova AI Readiness Inspector on the Chrome Web Store

The problem it solves

AI agents and answer engines now consume websites through a few emerging channels that traditional SEO tooling doesn't check:

Signal What it is Why it's easy to get wrong
llms.txt A root or path-scoped file that tells AI systems what content is available and how it's structured Easy to publish with broken links or malformed sections, no standard validator
llms-full.txt An optional convention exposing a fuller, single-file version of a site's content New and inconsistently adopted, easy to forget to update
Markdown alternates A .md version of an HTML page, or content that converts cleanly to Markdown HTML-to-Markdown conversion quality varies a lot depending on markup
robots.txt / sitemaps Classic crawl directives, still relevant to AI crawlers Often written years ago for search bots only, never revisited for AI agents
UCP Universal Commerce Protocol discovery and profile metadata Requires public metadata most sites haven't published
ACP Agentic Commerce Protocol product or integration evidence New enough that most teams haven't heard of it yet

None of these are things a Lighthouse audit or a standard SEO crawler checks for you.

How the extension works, technically

The extension is scoped narrowly on purpose:

It runs only on the active tab, and only after you click it. No persistent background access to every domain you visit.
The scan logic runs locally inside the extension.
Where it needs to verify something public, like fetching robots.txt, checking for llms.txt, or sampling a linked resource, it sends the request directly from your browser to the site being inspected. Nothing routes through a Clustova server for the core scan.
It does not load or execute remote JavaScript or WebAssembly.
It doesn't touch cookies, passwords, form data, or browser history, and it can't create checkout sessions or submit order data even on commerce sites.

That last point matters if you're evaluating this for use inside a team or agency: it's a read-only, publicly-observable-evidence tool, not something that mutates state on the sites it inspects.

What a scan actually returns

Run the extension on a page and you get a structured report covering:

llms.txt discovery and validation — root-level and path-scoped detection, structural validation, and a sample check on linked resources
llms-full.txt check — whether the optional full-content file exists
Markdown readiness — detection of Markdown versions of the current page, a review of Markdown media types and content quality, and how well the HTML converts to Markdown
Crawl and index basics — robots.txt, XML sitemap presence, HTTPS, and public metadata
UCP discovery — public commerce profile metadata, if present
ACP evidence — public product or integration signals for agentic commerce, if present (these checks only trigger when the site looks commerce-related)

Each check comes back with the evidence found, a status, any relevant limitations, and remediation guidance where something's missing or malformed.

From there you can:

Open the full findings in Chrome's side panel
Export the report as Markdown or JSON, which is genuinely useful if you want to pipe it into a CI check, paste it into a GitHub issue, or hand it to a teammate
Keep a local history of recent scans in Chrome, so you can diff a site before and after a fix

There's also an optional Deep scan link into Clustova's web-based checker for a more exhaustive review, but that runs on their site under their own policy, separate from the local extension scan.

A quick workflow for developers
Ship or update your llms.txt.
Open the page in Chrome and run the extension.
Export the JSON report.
Fix whatever comes back red, broken links in llms.txt, a missing sitemap entry, a Markdown alternate that 404s.
Re-scan and diff against the local history to confirm the fix landed.
Repeat before every major content or catalog change, the same way you'd re-run a Lighthouse audit after a perf change.

If you're on an e-commerce stack and exploring agentic checkout, steps 2 through 5 are exactly what you'd want to run before and after wiring up ACP or UCP metadata, since there's currently no other quick way to confirm those signals are actually publicly visible.

Be clear about what it isn't

Worth stating directly, because the extension's own documentation says this too: a clean report doesn't guarantee AI search ranking, citation, inclusion, protocol compliance, or transaction eligibility. It confirms that the publicly observable groundwork is in place, which is a prerequisite, not a promise. Treat it the way you'd treat a passing schema.org validator: necessary, not sufficient.

Try it

Install it from the Chrome Web Store, run it on your own site first, then run it on a competitor's. The gaps you'll find are usually more informative than the passes.

Clustova AI Readiness Inspector