Six passes, in the order an agent makes them
Not a checklist we invented. This is the sequence a shopping assistant actually walks when it meets a store it has never seen — reach it, read it, understand the catalogue, time it, then look for it.
Your storefront
The same anonymous request an assistant makes — no browser, no cookies, no login. If it cannot reach you, nothing else matters.
What AI is allowed to read
Your own robots.txt, sitemap and llms.txt, fetched live and read the way a crawler reads them.
Your catalogue
The products an agent actually receives when it asks your store what you sell — and the ones it cannot price, picture or describe.
How fast it really loads
What your store takes to answer, plus whatever Google holds on your origin. An agent runs no browser, so your answer time is its whole load time.
Where you rank
AI retrieval reads Google page one, so search and AI are one problem rather than two. We run the searches your buyers make.
Buying without a browser
Whether an agent can complete a purchase from your store directly, rather than handing the shopper back to a checkout form.
From a store URL to a focused plan
01
Give us the domain
No install, no plugin, no account, and no access to your admin. Everything we read, an assistant could read.
02
Watch it happen
Six passes, in the order an agent would make them, showing the actual bytes your store returned at each one.
03
Keep the report
What is already working, what is not, and what we could not check — with the evidence beside each line.
No single score to inflate
A check we could not run is not a failure
Anything we could not measure is named as a gap and left out of the arithmetic. A store below Google’s reporting threshold has no field speed data — that is a statement about sample size, not about your store being slow.
Every number comes with the thing it was read from
Your own robots.txt, your own sitemap, the actual response headers, the products an agent actually receives. Nothing on the report is a drawing of a claim.
Before you run the audit
What it costs, what it reads, and why there is no single number at the end.
Yes, and there is nothing to install. You give us a domain and we read your store from the outside, exactly the way a shopping assistant does. No credit card, no account.
No — the audit runs on any store. WooCommerce and Shopify get more detail because we can read their catalogues directly, and the report always states which parts we could not check on your platform.
Around two to three minutes. You watch each pass land as it happens rather than staring at a spinner, and the report is a permanent link you can send to whoever maintains the site.
We read public pages — the same ones a crawler fetches. There is no login, no cookie and no access to your admin at any point. We never sell your data.
Because one 0–100 would mean "you did the work" on one platform and "your platform did the work" on another, from identical arithmetic. The report separates what passed, what failed, and what we could not measure — and a check we could not run is never counted against you.
You get a ranked list of findings, ordered by what each one costs you rather than by how hard it is to fix, plus the evidence for each. Most merchants either ship the top few themselves or connect xpay and let the pipeline emit the feeds, llms.txt and agent-checkout endpoints for them.
Find what the assistants overlook
Three minutes, no install, and the evidence beside every line.









