Product Schema Markup: 5 Smart, Essential Types That Win Rich Results
By Istiak Ahmed Soikot, Founder and CEO, Rank OG
Last reviewed: November 10, 2026.
Product schema markup is JSON-LD code that tells Google what a page sells, what it costs, and whether it is in stock. Add the right type, keep every value true to the page, and your listing can earn price, stock, and star rich results.
Who this is for: owners and marketing leads who run an online store and want product pages to stand out in Google Search. You will learn the five types that matter, the rules Google sets, and a safe way to test your work.
What Is Product Schema Markup?
Product schema markup is structured data written in JSON-LD, the format Google recommends for structured data. It sits in your page code and labels the product name, image, description, brand, SKU or GTIN, price, currency, and stock status. Schema.org defines the shared vocabulary, and Google decides which parts it will use.
Picture a store with 300 product pages and no structured data. Google can still crawl them, yet it must work out price and stock from page text alone. Product schema markup gives Google the same facts in a clean, labeled form. It does not change what shoppers see, and it does not push a page up the rankings by itself.
How Does Product Schema Markup Win Rich Results?
A rich result is a search listing with extra detail, such as a price, an in stock note, or a star rating. Product schema markup wins rich results by making your page eligible for them. That is not a promise: Google says it does not guarantee structured data will show up in search results, even when the markup is valid.
Google can use your product data in a product snippet, a shopping knowledge panel, popular product results, and annotated images in Google Images. You can also upload a data feed with Google Merchant Center and opt into free listings, or do both. Google says providing both maximizes your eligibility and helps Google correctly understand and verify your data.
What Are the 5 Types of Product Schema Markup That Win Rich Results?
These five types cover almost every product page. Start with the first two, then add the rest where they fit. Product schema markup works best as a set, not as a single block pasted on one page and forgotten.
| Type | What it adds | Best for | Rich result it powers |
|---|---|---|---|
| Product and Offer | Name, image, price, currency | Every page where shoppers can buy | Price and merchant listing |
| AggregateRating and Review | Average score and review count | Pages with real reviews on the page | Star rating |
| ProductGroup for variants | Size, color, and material variants | Products sold in many options | Variant information in listings |
| Shipping and return policy | Shipping cost and return terms | Stores that ship orders | Shipping and returns detail |
| Product snippet for review pages | Reviews, pros, and cons | Pages where shoppers cannot buy | Product snippet with review detail |
1. Product and Offer: the merchant listing core
This is the base type. Product carries the name, image, description, brand, SKU, GTIN, and MPN, while a nested Offer carries the price, currency, and stock status. Google requires a name, at least one image, and an offers property holding an Offer. Inside that Offer, the price must be greater than zero, and priceCurrency must use a three letter ISO 4217 code such as USD. Availability, brand, description, SKU, GTIN, shipping details, and return information are recommended on top.
2. AggregateRating and Review: the stars shoppers trust
AggregateRating rolls your reviews into one average score and one review count, and that powers the star rating in search results. A single Review adds a named reviewer, a rating, and a short quote. The rule is strict: the rating and review count in your markup must match the reviews shoppers can see on the same page. Never invent a score, import reviews from another site, or add stars to a page with no visible reviews.
3. ProductGroup: one product, many variants
Many products come in sizes, colors, materials, or patterns. ProductGroup groups those variants under one parent product, using variesBy, hasVariant, and productGroupID. Shared facts such as the brand and the review information sit on the group, so you do not repeat them on every variant. Each variant then carries its own price, stock, and option values. Do not use AggregateOffer for variants: Google says merchant listings require an Offer, because the merchant has to be the seller.
4. Shipping details and return policy: the total cost
Shoppers judge the total cost, not the price alone. OfferShippingDetails states the shipping cost and delivery area, and MerchantReturnPolicy states the return window, any fees, and the return deadline. Google can show shipping costs, especially free shipping, and return information. You do not have to repeat these policies on every product: Google accepts one site wide policy in your Organization markup.
5. Product snippet markup: for pages where shoppers cannot buy
An editorial review, a comparison, or a roundup talks about a product without a buy button. Google calls this a product snippet, with lighter rules: the product name plus at least one of a review, an aggregateRating, or an offer. This type also has more room for review detail, such as pros and cons. Only pages where a shopper can buy are eligible for merchant listing experiences, not pages with links to other sites that sell the product.
What Does Google Require for a Merchant Listing?
The image must be crawlable and indexable, must show the marked up product, and should be high resolution. A single product page must also focus on one product, or variants of the same product. Google recommends marking up product pages instead of category pages or search results pages.
Prices need care, too. Google recognizes the active price, the strikethrough price shown during a sale, and the member price for a loyalty program. Mark a sale with a priceType of StrikethroughPrice on the old price, never on the active price. Add a start and an end date with validFrom and either validThrough or priceValidUntil, and never leave a priceValidUntil date in the past, or your listing may not display. Put the markup in the server HTML where you can, not only in JavaScript.
What Are the Rules for Reviews and Ratings in Product Schema Markup?
Product schema markup earns stars only from reviews you collected and show on the page. The aggregateRating needs a ratingValue and a reviewCount, and both must match the visible reviews. Individual reviews need a real author name and a reviewRating. Google says the reviewer name must be a valid name for a Person or a Team.
Keep three checks in mind. First, never write markup for reviews that do not exist on the page. Second, never average in reviews from a marketplace or a review site you do not host. Third, keep the score and count in sync when new reviews arrive, because a stale count is a mismatch. If a shopper cannot see it on the page, do not put it in the markup. Clear product description rules that help pages rank give shoppers real detail to judge, and that detail earns honest reviews over time.
How Do You Test Product Schema Markup Before You Publish?
Test every template on a few pages first, then roll it out. The Rich Results Test takes a URL or a code snippet and shows which rich result types were found, plus any errors or suggestions. The Schema Markup Validator checks your JSON-LD against the full schema.org vocabulary, while the Rich Results Test checks it against what Google supports. After launch, watch Search Console: its enhancement reports show valid Product markup, items with warnings, and items with errors, split into merchant listings and product snippets.
What Mistakes Kill Product Rich Results?
- Price and page do not match. The markup says one price and the page shows another.
- Stock status is stale. A product marked InStock sold out weeks ago.
- Stars with no visible reviews. An aggregateRating sits on a page with no visible reviews.
- Markup on the wrong page. Product markup sits on a category page or a post that only links to the product. Category pages need their own treatment, not Product markup.
- Variants marked up as one flat offer. A store with many sizes sends one AggregateOffer, and Google cannot tell the options apart.
- JavaScript only markup. The schema loads late or not at all, so Google never sees it.
One more mistake is easy to miss: adding markup to a page blocked by robots.txt, carrying a noindex tag, or sitting behind a login. Google cannot test or show a page it cannot crawl. Stores with large catalogs face a related trap in faceted navigation, where filter URLs create thousands of near duplicate product views. Keep the markup on the canonical product page.
What to Do Next
- Pick your ten best selling products and add Product and Offer markup to those pages first.
- Add AggregateRating only where reviews are visible, with the score and count matching exactly.
- Group variants with ProductGroup, and add shipping and return policy markup at the Organization level.
- Run each page through the Rich Results Test, fix every error, then check Search Console a week later.
- Re-check price, stock, and ratings after every sale, restock, and review.
Frequently Asked Questions
What is product schema markup?
Product schema markup is JSON-LD structured data that labels a product name, image, price, currency, stock status, and ratings in a form Google can parse. It makes a page eligible for rich results, yet Google does not guarantee that any rich result will show.
Does product schema markup improve rankings?
No, product schema markup does not improve rankings by itself, since Google has said structured data is not a generic ranking factor. It can improve how a listing looks in search, and a clearer listing may earn more clicks from shoppers who already see it.
What fields does Google require for a merchant listing?
Google requires a product name, at least one image, and an Offer with a price above zero and a three letter ISO 4217 priceCurrency such as USD. Availability, brand, description, SKU, GTIN, shipping details, and return information are recommended on top of those required fields.
Can I add star ratings if my product has no reviews?
No, you must not add star ratings to a page with no visible reviews. Google requires the ratingValue and reviewCount in your markup to match the reviews shoppers can see on the same page, so add AggregateRating only after real reviews appear on that page.
How do I mark up products sold in sizes and colors?
Use ProductGroup with variesBy, hasVariant, and productGroupID to group the variants under one parent product. Put shared facts such as brand and reviews on the group, then give each variant its own Offer with its price, stock status, and option values.
How do I test product schema markup?
Run the page URL or code snippet through Google Rich Results Test and fix every error it reports. Then check the Schema Markup Validator for vocabulary errors, and watch the merchant listings and product snippets reports in Search Console for site wide issues.
Sources
- Introduction to Product structured data, Google Search Central
- Merchant listing (Product, Offer) structured data, Google Search Central
- Rich Results Test, Google Search Console Help
- Product type definition, Schema.org
Sources checked November 2026. Rules change, so re-check the Google Search Central pages before you build on this guide. For help with the wider page, see our on-page SEO services.
Want your product schema markup and product pages checked properly? Get a free SEO audit and we will review your markup, your prices, and your stock data, then tell you what to fix first. You can also reach us through the contact page.
