Agent readiness audit
A full audit of what AI agents can and cannot do on your site
Every check in the published rubric, run against your site by hand rather than by heuristic, with the raw evidence attached to every finding.
What we actually look at
We fetch your homepage and the pages that matter commercially: product, pricing, docs, contact, checkout. Each is fetched twice. Once as raw HTML, the way most agents see it, and once fully rendered in a real browser. The gap between those two fetches is where the majority of serious problems live, and it is invisible to anyone testing in a browser.
We then re-fetch under the GPTBot, ClaudeBot and PerplexityBot user agents and record what comes back. This is the step that catches edge and CDN blocking, which is both the most common failure we find and the one clients are most surprised by, because their robots.txt is usually perfect.
Beyond access, we check whether a machine can understand the page (schema coverage and validity, semantic landmarks, heading structure, text-to-markup ratio) and whether it can act: real form labels, correct input types, buttons that are actually buttons, search that an agent can construct a URL for, and whether any machine-readable endpoint exists at all.
Why manual, when there is a free scanner
The automated score is deliberately shallow: six pages, a fixed set of probes, no judgement. It is excellent at telling you that something is wrong and roughly how much it costs you.
The audit is where we go deeper than a crawler safely can. We follow the actual purchase or signup path, read your templates rather than inferring them, and separate the findings that matter commercially from the findings that are merely true. A scanner will tell you that 40% of your images lack alt text. The audit tells you which of them are on the pages that convert.
What you get at the end
A score against the published rubric, a full findings list with captured evidence for each one, and a ranked remediation plan ordered by impact against effort, so the work that is cheap and valuable is unambiguous.
We will also tell you plainly when something is not worth fixing. An audit that recommends everything is an audit that has not done its job.
What you get
- Score against the published rubric, with per-pillar breakdown
- Every finding backed by captured evidence: request, response, and what we saw
- Ranked remediation plan, impact against effort
- Rendering-parity analysis: what an agent sees versus what a browser sees
- Bot access report across GPTBot, ClaudeBot and PerplexityBot
- A 60-minute walkthrough call with whoever will do the work
- Typical timeline
- 5 business days
- Investment
- From $2,000
We scope against architecture, not page count. How we price
The rest of what we do
- Implementation
We make the fixes, in your codebase or your CMS
Done-for-you remediation of agent readiness findings, from schema to rendering to machine endpoints, delivered as reviewable pull requests or CMS changes.
- Monitoring
Standards move. We tell you what broke, before a customer does
Ongoing re-scanning against the evolving agent readiness rubric, with alerts when a deploy, a CDN setting, or a new standard breaks something.