Product Schema: What Google Requires for Product Snippets and Merchant Listings
Product schema tells search engines the facts of a product: its name, images, price, stock and ratings. Google uses it for two different features with two different lists of required properties. This guide puts both lists side by side, verified against Google's documentation on November 21, 2026, with a complete JSON-LD example and the mistakes that show up on real stores.
Product Snippets or Merchant Listings
Google's introduction to Product structured data splits product markup into two features:
| Product snippets | Merchant listings | |
|---|---|---|
| For pages where | Product reviewed or compared | Product can be bought |
| Shows | Stars, price, pros and cons | Price, stock, shipping, returns |
| Price above zero needed | – | ✓ |
| Currency needed | – | ✓ |
| Images needed | – | ✓ |
| Variants supported | ✓ | ✓ |
A shop's product page wants merchant listings. A review site or a comparison page wants product snippets. Google notes that a page with the merchant listing properties can also be eligible for product snippets, so one good block on a shop page covers both.
Product Snippet Properties at a Glance
From Google's product snippet documentation. The one rule people miss: name alone is not enough. You need at least one of review, aggregateRating or offers.
| Type | Required | Recommended |
|---|---|---|
| Product | name | aggregateRating, offers, review |
| Product | One of review, aggregateRating, offers | All three |
| Offer | price | availability, priceCurrency, priceValidUntil |
| AggregateOffer | lowPrice, priceCurrency | highPrice, offerCount |
| AggregateRating | ratingValue, ratingCount or reviewCount | bestRating, worstRating |
| Review | author, reviewRating.ratingValue | datePublished, bestRating, worstRating |
The rating rules come from Google's review snippet documentation. A reviewer's name must be a real person or team, under 100 characters. Pros and cons, through positiveNotes and negativeNotes, show only for editorial review pages, not for a merchant's own product page.
Merchant Listing Properties at a Glance
From Google's merchant listing documentation. Three properties are required on the Product, and the Offer needs a price and a currency.
| Type | Required | Recommended |
|---|---|---|
| Product | name, image, offers | brand.name, description, sku |
| Product, identifiers | None | gtin or gtin13, mpn |
| Product, variants | None | color, size, material, pattern |
| Product, ratings | None | aggregateRating, review |
| Offer | price, priceCurrency | availability, itemCondition, url |
| Offer, policies | None | shippingDetails, hasMerchantReturnPolicy |
| Offer, dates | None | priceValidUntil, validFrom, validThrough |
The numbers that matter:
| Rule | Value |
|---|---|
| Price for merchant listings | Greater than 0 |
| Currency format | ISO 4217, 3 letters |
| Image aspect ratios | 16x9, 4x3, 1x1 |
| Brand names per product | 1 |
| sku values | 1, no spaces |
| availability, itemCondition | 1 value each |
| Return policy, finite window | merchantReturnDays needed |
If both offers.price and offers.priceSpecification are set, Google uses offers.price. For a sale, only the original price carries priceType StrikethroughPrice; the price you charge carries none.
A Complete Product Schema JSON-LD Example
A shop product page with a price, stock, rating, free shipping and a 30 day return window. It meets the merchant listing requirements and so also qualifies for product snippets.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Product",
"name": "Trail Running Shoe TR2",
"image": [
"https://www.example.com/img/tr2-16x9.jpg",
"https://www.example.com/img/tr2-4x3.jpg",
"https://www.example.com/img/tr2-1x1.jpg"
],
"description": "Lightweight trail shoe with a 6 mm drop and a grippy outsole.",
"sku": "TR2-BLU-42",
"gtin13": "0614141123452",
"brand": {
"@type": "Brand",
"name": "Example Outdoor"
},
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": 4.6,
"reviewCount": 128
},
"offers": {
"@type": "Offer",
"url": "https://www.example.com/shoes/tr2",
"price": 89.0,
"priceCurrency": "USD",
"availability": "https://schema.org/InStock",
"itemCondition": "https://schema.org/NewCondition",
"shippingDetails": {
"@type": "OfferShippingDetails",
"shippingRate": {
"@type": "MonetaryAmount",
"value": 0,
"currency": "USD"
},
"shippingDestination": {
"@type": "DefinedRegion",
"addressCountry": "US"
},
"deliveryTime": {
"@type": "ShippingDeliveryTime",
"handlingTime": {
"@type": "QuantitativeValue",
"minValue": 0,
"maxValue": 1,
"unitCode": "DAY"
},
"transitTime": {
"@type": "QuantitativeValue",
"minValue": 2,
"maxValue": 5,
"unitCode": "DAY"
}
}
},
"hasMerchantReturnPolicy": {
"@type": "MerchantReturnPolicy",
"applicableCountry": "US",
"returnPolicyCategory": "https://schema.org/MerchantReturnFiniteReturnWindow",
"merchantReturnDays": 30
}
}
}
</script>
Every value here must match what the visitor sees: the same price, the same stock, the same rating count. Google allows return and shipping policies to be set once on your Organization markup instead, with the Offer overriding them only for products that differ. SEO ProCheck's product schema for e-commerce guide goes further into variants and feeds.
Product Schema Errors That Show Up on Real Stores
Product markup is generated by templates, so a single empty field breaks it on hundreds of pages at once. The usual ones:
| Error | Typical cause | Fix |
|---|---|---|
| Price missing | Price shown as a range | Use AggregateOffer |
| Price 0 | Price on request products | Leave out the Offer |
| Price differs from page | Cached markup, live price | Print from one source |
| priceValidUntil in the past | Old sale end date | Update or remove |
| InStock on sold out items | Stock not passed to template | Map stock status |
| Ratings with no reviews shown | App injects ratings only | Show reviews on page |
| Several Product blocks | Theme plus plugin | Keep one |
The last one is very common on Shopify and WordPress: the theme prints a Product block and an SEO plugin prints another, with different prices or ratings. SEO ProCheck's Offer schema check lists the Offer fields one by one.
Markup Injected by JavaScript
Many stores add product markup with JavaScript, through a review app or a tag manager. Google can read it after rendering, but rendering happens later than the first crawl and can fail. Google's guide to structured data with JavaScript also warns that merchant markup added only by JavaScript can make Shopping crawls less frequent and less reliable, which matters most for price and stock that change often.
To see what your markup looks like before and after rendering, crawl once without JavaScript and once with it, and compare the Schema Types of each product page. The JavaScript SEO crawler guide explains how.

How to Check Product Schema Across a Whole Store
- Crawl every product page, with rendering on if any markup comes from JavaScript.
- Fix syntax errors first. A block that does not parse hides every property in it.
- Group pages by template and find product pages that lack the Product type their siblings carry.
- Check required properties for merchant listings, then the recommended ones.
- Compare markup with the page: price, stock and product name.
- Look for expired dates in
priceValidUntil. - Watch Search Console for merchant listing and product snippet errors after each release.
The schema markup validator guide covers the single page tools.
Check Product Schema With Neova
Neova reads JSON-LD, microdata and RDFa from every HTML page of a crawl and gives each type on a URL a verdict. The checks that matter for products:
- Structured Data Lacks Required Properties or Differs From Visible Text, also when under 70% of the words of a product name are in the visible text
- Product Price in Structured Data Is Not Shown on the HTML Page, in any usual number format
- Offer priceValidUntil Date Has Passed
- Structured Data Lacks Recommended Properties
- HTML Page Lacks Rich Result Markup Its Page Group Carries, for the product page whose template forgot the markup
- Product Feed Item Disagrees With Its Landing Page, for feeds that say in stock while the page says otherwise
- Rich Result Is Invalid, from URL Inspection when Search Console is connected
The Free plan crawls up to 1,000 URLs with every check. See Features or download Neova.
Questions
What are the required properties for product schema?
For product snippets: name plus one of review, aggregateRating or offers. For merchant listings: name, image and offers, with an Offer that has a price above zero and a currency.
Can product schema have a price of 0?
Product snippets accept it, but merchant listings need a price greater than zero. For products sold on request, leave the Offer out rather than set the price to 0.
Should I use Offer or AggregateOffer?
Use Offer when you sell the product at one price. Use AggregateOffer when several sellers offer it at different prices, with lowPrice and priceCurrency. Google says not to use AggregateOffer for product variants.
Does product schema help rankings?
Google presents it as a way to become eligible for search features, not as a ranking boost, and does not promise the feature will show. It makes a page eligible for product snippets and merchant listings, which can change how the result looks and how often it is clicked.
Where do shipping and return policies go?
In the Offer, as shippingDetails and hasMerchantReturnPolicy, or once in your Organization markup. Offer level policies override the Organization ones for that product.