Schema markup for products: product snippets versus merchant listings
Pick the right Google product class, match the visible page price and verify JSON-LD fields with the Product Schema Checker.
·3 min read
Schema markup for products is JSON-LD or microdata added to a product page so search engines and AI shopping systems can read price, currency, availability, brand, GTINs and ratings directly. Google splits this markup into two classes: product snippets for non-checkout pages such as editorial reviews, and merchant listings for pages where shoppers can buy directly.
Product snippets versus merchant listings
Choosing the wrong target class is a common reason store pages miss shopping enhancements. According to Google Search Central, each class asks for a different minimum set of fields:
| Feature | Product snippets | Merchant listings |
|---|---|---|
| Page type | Review, editorial or non-checkout product page | Storefront page where a customer can buy |
| Minimum fields | name plus a review, rating or offer |
Full product info including an offer with price and ISO currency |
| Extras supported | Editorial pros and cons, ratings | Apparel sizing, shipping details, return policy |
| Eligibility overlap | Eligible on its own | Satisfying merchant listings generally qualifies for product snippets too |
Google also recommends nesting business-level policies (MerchantReturnPolicy and loyalty program data) under Organization markup, and using product variant structured data when a parent item comes in multiple colors or sizes.
Why visible page parity breaks schema
Search engines expect structured data to describe what a human shopper actually sees. The seogeoaeo.ai Product Schema Checker tests both JSON-LD and microdata against Google's product snippet and merchant listing rules, including whether the marked-up price appears on the rendered page.
Four errors catch teams out repeatedly:
- Currency formatting mistakes: Writing
$29insidepriceCurrencyinstead of an ISO 4217 code such asUSD. - Stale cached prices: A sale changes the visible price in the template while old JSON-LD still outputs the list price.
- Invalid GTIN check digits: Typing a barcode with a wrong final check digit fails validation silently on many platforms.
- Missing shipping or return fields: Store pages that omit shipping costs and return policy miss merchant listing enhancements even when price and stock are valid.
Checking one page before rolling out a template
A single product page test costs 5 credits on seogeoaeo.ai (as of November 2026, displayed before the run starts) and runs from the web tool, over REST API or through MCP with a workspace API key. It inspects price format, ISO currency, availability, GTIN check digits, brand, shipping, return policy, ratings and visible price parity on that URL.
Know what a single-URL check will not do: it does not validate a Google Merchant Center feed, pull competitor pricing, or crawl every SKU across an entire catalog in one run. For full-store eligibility, Google recommends combining clean on-page structured data with a Merchant Center feed so both sources reinforce each other.
Practical rollout order
- Confirm whether your pages belong in product snippets or merchant listings.
- Fix one representative template page so
name, price, ISO currency, availability, brand and valid GTINs pass. - Verify that your rendered price matches the markup on every currency and sale variant.
- Add
Organization-level return policy markup, then re-test after theme or pricing changes.
FAQ
Which Product fields does Google require at minimum?
Product snippets need a name and at least one of a review, a rating or an offer. Merchant listings require fuller product details, including an offer with both a numeric price and an ISO currency code.
Must the structured data price match what is shown on the page?
Yes. Markup has to reflect what shoppers see on the page, and validators check that the marked-up price appears visibly.
Does product schema replace a Google Merchant Center feed?
No. Google notes that providing both structured data on product pages and a Merchant Center feed gives the widest eligibility across search and shopping surfaces.