Agent readiness
Your next customer is not a person.
AI shopping agents choose products from structured data, not from your homepage design. Most stores are invisible to them. Scan yours and find out in twenty seconds.
Readiness score
- Discovery35
- Crawl access88
- Product schema58
- Merchant data47
- Content quality70
- Failllms.txt published and substantive
- PassGPTBot is allowed
- FailGTIN or MPN populated
- WarningShipping terms are machine readable
Scan your store- free, no signup

The problem
Nothing breaks. You just stop being an option.
There is no error page for this. A store can trade normally for a year while being unreadable to every agent that would have recommended it.
A single line locks the door
Crawler blocks get added during a scraping scare, or arrive as a plugin default, and then nobody revisits them. We check five AI crawlers by name against your real rules, at the site root and on an actual product path.
User-agent: *Disallow: /cartUser-agent: GPTBot- Fail
Disallow: / User-agent: ClaudeBot- Pass
Allow: /
One line, added by a plugin default years ago, removes the store from every OpenAI surface. Nobody notices, because nothing breaks.
Valid schema is not useful schema
Most stores that have structured data have it in name only: a Product node with an empty SKU, no GTIN and one image. It validates. It cannot be matched against the same product anywhere else, which is the entire job.
"@type": "Product",- Pass
"name": "Harbour Shell Jacket", - Pass
"offers": { "price": "289.00" }, - Fail
"sku": "", - Fail
"gtin13": missing, - Fail
"aggregateRating": missing, - Warning
"image": [ 1 of 6 ]
A validator passes this. An agent trying to decide whether your jacket is the same jacket it found on three other sites cannot.
Readiness score
A sample report for a fictional store. Yours takes about twenty seconds.
- Discovery35
- Crawl access88
- Product schema58
- Merchant data47
- Content quality70
- Failllms.txt published and substantive
- PassGPTBot is allowed
- FailGTIN or MPN populated
- WarningShipping terms are machine readable
- PassOrganization schema on the homepage
- FailDescriptions at least 500 characters
The report
Forty checks. Every failure ships with its fix.
Five categories, weighted by what actually blocks a sale. Crawl access and product schema carry the most because they are gating: if a crawler cannot get in, or a page has no structured data, nothing else can be seen.
- 01Discovery
- Can an agent find the machine readable entry points to your store.
- 02Crawl access
- Are AI crawlers allowed in, over a fast and secure connection.
- 03Product schema
- Is each product described in structured data an agent can trust.
- 04Merchant data
- Are returns, shipping and business identity resolvable without a human.
- 05Content quality
- Is there enough substance for an agent to compare and recommend you.
The fix path
From invisible to recommended
The scan is free and complete. Nothing is held back to force a sales call.
Scan
Paste your URL. Forty checks in about twenty seconds, no signup, nothing installed.
Report
A score, a grade, and every failing check with the evidence we found and the fix written out.
Fix
Implement it yourself from the report, or have us do the whole list for a fixed fee.
Visible
Agents can find, read, compare and recommend you. Rescan any time to prove it stuck.
Done for you
Fixed priceGBP 300 to 500 fixed
We implement the fixes on your store and hand it back scoring in the As.
- Everything in the free scan
- llms.txt, agents.md and UCP manifest written and deployed
- Product and Organization schema implemented
- robots.txt opened to AI crawlers
- Rescan and a written handover
What it looks like
Full tiers and questions on the pricing page.
Measured, not promised.
40
checks per scan
5
weighted categories
Live
crawl every time, nothing cached
Questions
Before you scan
- What does 'agent readiness' mean?
- Whether an AI shopping agent can find your store, read your products as structured data rather than prose, and trust your returns and shipping terms enough to recommend you. It is not a score you can talk your way into. Either the crawler is let in and the schema is there, or it is not.
- What does the scan actually check?
- Forty checks across five categories: discovery files such as llms.txt and agents.md, whether AI crawlers are allowed in by robots.txt, product structured data, machine readable returns and shipping, and content depth. Every check comes back with the evidence we found and the fix, not just a number.
- Does the scan change anything on my store?
- No. It only reads what is already public: your homepage, robots.txt, sitemap, a sample of product pages and your policy pages. Nothing is installed, no account is created, and nothing on your store is written to.
- What does it cost to fix what the scan finds?
- The scan and its fixes are free to read and free to implement yourself. If you would rather we did it, done for you implementation is a fixed GBP 300 to 500 depending on platform and catalogue size, agreed before we start.
- How long does a scan take?
- Usually 15 to 30 seconds. We fetch your homepage, six discovery files, your sitemap and up to five product pages, three requests in flight at a time so we are not hammering your server.
Free scan
Find out where you stand
One URL, twenty seconds, the whole report. Free, no signup, and shareable with whoever maintains your store.
Scan your storeDone for you
Have us fix it
GBP 300 to 500 fixed, agreed before we start. We implement every failing check we can, rescan, and hand it back in writing.
Get it fixed