Industry benchmark · Q4 2026 edition · snapshot of 2026-08-20
Magento stores are not ready for shopping agents.
We ran the same 8 agent-readiness checks against 1,854 live Adobe Commerce and Magento storefronts — no volunteers, no sign-ups, no self-selection. This is what an AI shopping agent finds when it arrives at a typical Magento store today.
Check by check
Where the storefronts fail.
Each bar is the share of stores passing that check, counted only across stores where the check could be decided. The two product-data checks are the ones that decide whether an agent can quote your price and promise delivery.
-
UCP-01 /.well-known/ucp profile conforming to UCP 2026-04-08 +0.4 pp 0.4%
5 pass · 1,340 fail · 509 not decidable
-
MCP-01 Advertised MCP endpoint reachable +0.2 pp 0.3%
5 pass · 1,849 fail
-
BOT-01 robots.txt policy for AI shopping crawlers 44.5%
819 pass · 1,021 fail · 14 not decidable
-
AGENT-01 AI agent user-agents served at the edge 36.4%
665 pass · 1,161 fail · 28 not decidable
-
CRAWL-01 Crawl limits on search and faceted URLs 31.4%
578 pass · 1,262 fail · 14 not decidable
-
LLMS-01 /llms.txt present +0.5 pp 10%
182 pass · 1,644 fail · 28 not decidable
-
FEED-01 Product structured data completeness (25+ agent attributes) +0.7 pp 22.2%
305 pass · 1,068 fail · 481 not decidable
-
SCHEMA-01 Product, Offer, AggregateRating JSON-LD on a product page +5 pp 46%
632 pass · 741 fail · 481 not decidable
Since Q3 2026
What moved in a quarter.
Compared against the edition published 2026-08-18, on the same checks and the same method. Only checks measured in both editions are compared — a check added in between did not "rise from zero", it simply was not measured before.
- -13 stores in the sample
- +0.72 average checks passed
- -17.2 pp stores passing nothing
- +0.4 pp pass rate on UCP-01
- +0.2 pp pass rate on MCP-01
- +0.5 pp pass rate on LLMS-01
- +0.7 pp pass rate on FEED-01
- +5 pp pass rate on SCHEMA-01
Distribution
How many checks a store passes.
Readiness is not a bell curve. Most storefronts sit at the bottom of the range, which is why a store that fixes even the product-data layer moves ahead of most of its category.
| Checks passed | Stores | Share | Bar |
|---|---|---|---|
| 0 / 8 | 310 | 16.7% | |
| 1 / 8 | 558 | 30.1% | |
| 2 / 8 | 545 | 29.4% | |
| 3 / 8 | 267 | 14.4% | |
| 4 / 8 | 134 | 7.2% | |
| 5 / 8 | 35 | 1.9% | |
| 6 / 8 | 4 | 0.2% | |
| 7 / 8 | 1 | 0.1% | |
| 8 / 8 | 0 | 0% |
Does traffic help?
Bigger stores are not more ready.
Split by whether the domain appears in the Chrome UX Report — Google's public dataset of sites with enough real-user traffic to be measured. Being a large, busy store does not by itself make a catalog legible to an agent.
In CrUX (measurable real traffic)
1.73/8
1,822 stores · 16.4% pass nothing
Not in CrUX
1.34/8
32 stores · 37.5% pass nothing
Method
How this was measured.
The sample
Domains were assembled from public sources — the HTTP Archive / Chrome UX Report crawl, public top-site lists and agency portfolios — then verified as running Magento or Adobe Commerce by fetching the homepage and reading platform fingerprints. Stores were not contacted and did not opt in, so the sample is not biased toward merchants already interested in agentic commerce.
The checks
Eight checks, scored — each one named with its pass rate in the table above, and each a thing an AI shopping agent needs in order to find, read or transact with a store. A store's score is the number of those it passes; a check that could not be decided on a given store is excluded from that check's pass rate rather than counted against the store.
Refusals are not failures
When a store answered our request with 401, 403, 429 or 503, we recorded a refusal rather than a failed check — we never observed the artifact, so asserting anything about it would be a claim the merchant can see is wrong. Those 20 stores sit outside the pass-rate figures above.
Editions do not change
Each edition is a frozen snapshot: the figures on this page were computed on 2026-08-20, published on 2026-10-01, and are never recalculated. New scans and new checks land in the next quarterly edition, at its own address, with the change from this one stated. A number cited from this page stays checkable here.
What is not published
Only aggregates. No domain, brand or individual result appears on this page or in any material derived from it — a scanned store's result belongs to its owner, and we publish it only with permission. If your store is in this sample and you want its result, run the scan yourself and it is yours.
Reuse
The figures are free to quote and republish with attribution to Expanding Web and a link to the edition. The machine-readable edition is at /benchmark/2026-q4.json.
Citation
Cite this edition.
Expanding Web (2026). Agentic Commerce Readiness Benchmark — Adobe Commerce & Magento, Q4 2026 edition (n=1,854). https://expandingweb.com/benchmark/2026-q4
Data: /benchmark/2026-q4.json · Licence: terms · Snapshot: 2026-08-20
Research notes
- Half of live Magento stores put no Product schema on their product pages 2026-08-28 · n=1,854
Your store
See where you sit against these numbers.
The scan is free, takes about fifteen seconds and runs eight checks against your storefront@if (count(\App\Agentic\Scanner::CHECKS) > $scoreChecks) — the eight scored here plus the newest ones, which this edition's sample had not been measured on yet@endif. You get your score against this benchmark; the full findings come by email after an engineer has reviewed them.
Scan your store