1 product page read, 1 with Product data, stating 8 of the 12 fields a cart reads on average. Read October 22, 2026.
Each field the store's products leave out, the most products first. One change to the store's product template fixes every product at once.
Give each product its barcode (GTIN), or at least its SKU, from the product itself.
Say each product is new, or how it is used or refurbished.
State what delivery costs, where it goes and how long it takes, once for the store or on each offer.
State the return policy: the window, the countries and who pays, once for the store.
The fewest fields first. The price and stock on each listing are what its data states, not what the page shows.
$129 USDStock stated
See the product page| Name | Stated |
|---|---|
| Image | Stated |
| An offer | Stated |
| Price | Stated |
| Currency | Stated |
| In stock or not | Stated |
| Brand | Stated |
| Product identifier | Missing |
| Description | Stated |
| Condition | Missing |
| Shipping | Missing |
| Returns | Missing |
2 Product blocks on one page. Two answers for one product is worse than one: an app and the theme often each write their own.
A count of fields says what a page's data states, read before any script runs. It does not decide eligibility: Merchant Center and Google's own review decide whether a product shows in merchant listings, Universal Cart or any other Google feature.
Every page of elegante.net against mttr's rulebook: 100 pages read.
The Shop Ready skill works in your store's own theme with Claude Code, Codex or Cursor, writes every field from the product's own data, and checks the live pages with mttr after. On Shopify, mttr can do it from the admin: that is in beta.