AI Agent Readiness Checker

What it costs you when this is wrong

• Checkout stops at a div that looks clickable

  An Add to cart built from a styled div with a click handler is not a control at all to something reading the page programmatically, so the run halts there. Because the order never reaches your server, there is no abandoned basket and no failed payment to investigate — only a shortfall you cannot attribute to anything.

• The form gets filled in, with wrong values

  A field with no label and no autocomplete token forces an agent to infer what it wants from a placeholder or whatever text sits nearby. It guesses, and the booking goes through with the phone number in the address line and the wrong date. You find out from the customer, and you refund it.

• Your catalogue has a depth of one screen

  A menu that only opens on hover, links pointing at href="#", a listing that loads more rows only when someone scrolls — each is a dead end for a visitor with no pointer and no patience for scrolling. The agent reports back on what it could actually reach, which is roughly your homepage, and recommends a shop whose products it could enumerate.

Why run it here

• It scores the page, not the discovery files

  All 28 rules are assertions about the rendered document: real buttons, accessible names, labelled fields, reachable menus, announced errors, text that exists as text rather than pixels. Said plainly, that means the other half is missing. Nothing here inspects capability manifests, content negotiation, bot authentication or API catalogues, and the free agent-readiness scanners released in 2026 cover that side rather than this one. If you need both, run both.

• Judged after the JavaScript has run

  The document these rules are evaluated against is the one that exists once scripts have executed, which is the document an agent actually operates on. On a site that assembles its interface in the browser, the untouched server response contains almost no controls at all. That raw response is kept separately and used for markup conformance, never for these checks.

• Ten of the 28 are reported, never scored

  There is no published specification for agent readiness, so the rules encoding observation rather than a standard are declared as such and kept out of the score. Ten run, appear in your report and cannot cost you a point. Among those that do score, a rule resting on early evidence carries 0.3 of its weight against 1.0 for one backed by a specification. A missing test identifier therefore cannot outrank an unlabelled checkout field.

This check runs on its own here, and as part of the full audit alongside the other 985 rules. Either way the findings carry their evidence and their citation, and the report is never published or kept.

1. 1

   Use real <button> and <a> elements. A div with a click handler is invisible to an agent looking for something to press.

2. 2

   Label every form field and add the correct autocomplete tokens, so an agent can tell which field wants an email and which wants a postcode.

3. 3

   Make sure your cookie banner can be dismissed programmatically and does not trap focus. It is where most agent journeys end.

4. 4

   Replace hover-only menus with something operable by click and keyboard — an agent has no pointer to hover with.

5. 5

   Give every control a clear accessible name that says what it does. 'Submit' is weaker than 'Book table'.

1. 1

   Enter your address

   Just the domain is enough — example.com, with or without the https. No account, no card, no crawl of your whole site.

2. 2

   We render it like a visitor

   Your page opens in a real browser and JavaScript runs to completion, so what gets audited is the page a person actually sees — not the raw HTML your server sent. A screenshot comes back with the report as evidence of exactly what we measured.

3. 3

   You get findings you can act on

   Up to 986 checks run against that rendered page. Each finding names the rule, quotes the evidence found on your page, cites the public specification behind it, and says what to change. Nothing is a judgement call — run it twice on an unchanged page and the score is identical.

What runs this check

• Real browser rendering

Named because provenance is the product. Every finding in your report says which of these produced it, so you can check the reasoning rather than take a score on faith.

Also checks

This page answers these searches too — they are the same job, so they share one page rather than being split across near-identical ones:

• agentic browsing test
• ai agent compatibility
• operator ready website
• computer use website test

Other checkers

• HTML ValidatorW3C markup conformance, checked by a real parser
• CSS ValidatorStylesheets parsed and checked against the W3C property grammars
• Schema Markup ValidatorJSON-LD parsed, expanded to real schema.org IRIs, and checked
• Rich Results TestWhich search features your structured data qualifies for
• Website Scam DetectorThe trust signals people and payment processors check before believing a site
• AI ValidatorWhether AI models can find, read, quote and operate your site
• Broken Link CheckerEvery link on the page requested, with blocked and broken told apart
• SEO CheckerTitles, meta, canonicals, indexability and internal linking
• Accessibility CheckerTwo WCAG engines — one in a real browser, one on your markup
• Security Headers CheckerResponse headers, CSP quality, and the TLS certificate underneath
• Core Web Vitals CheckerMeasured for real, plus the page-weight causes behind the numbers
• W3C ValidatorMarkup and stylesheet conformance in one pass
• Answer Engine CheckerWhether AI answer engines can quote you, and attribute it
• AI Crawler CheckerWhich AI crawlers your robots.txt actually lets in
• SSL Certificate CheckerA real handshake: certificate, expiry, protocol and cipher
• robots.txt CheckerWhat your robots.txt actually allows, group by group
• Meta Tag CheckerTitles, descriptions, canonicals and robots directives
• Open Graph CheckerHow your link looks when someone shares it
• Image SEO CheckerAlt text, dimensions, formats and lazy loading
• Mobile-Friendly TestViewport, tap targets and responsive behaviour
• Website CheckerEvery module, one scan, one prioritised fix list