Product Rich Results Schema: Complete Guide
Product rich results are one of the most commercially valuable schema types in Google Search. They can display price, stock availability, ratings, and review counts directly in the SERP, making your product listings stand out from competitors. This guide covers the required JSON-LD markup, eligibility rules, testing methods, and how to fix the most common product schema errors.
What Are Product Rich Results?
Product rich results enhance your organic search listing by showing structured product information — price, currency, availability status, aggregate rating, and review count — beneath the standard title and description. Google also powers its Shopping tab and product knowledge panels using Product schema. For e-commerce sites, having accurate, complete product markup can improve click-through rates significantly, particularly for high-commercial-intent queries where users are actively comparing prices and reviews before deciding where to buy.
Required Schema Markup (JSON-LD)
Below is a complete Product schema example including an Offer and AggregateRating:
{
"@context": "https://schema.org",
"@type": "Product",
"name": "SitemapFixer Pro Plan",
"image": "https://sitemapfixer.com/images/pro-plan.png",
"description": "AI-powered sitemap checker and SEO fix tool for growing websites.",
"brand": {
"@type": "Brand",
"name": "SitemapFixer"
},
"sku": "SF-PRO-001",
"offers": {
"@type": "Offer",
"url": "https://sitemapfixer.com/pricing",
"priceCurrency": "USD",
"price": "29.00",
"availability": "https://schema.org/InStock",
"priceValidUntil": "2027-01-01"
},
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": "4.8",
"reviewCount": "312"
}
}Required vs Recommended Properties
Google requires at least one of: a valid Review, a valid AggregateRating, or a valid Offer. Without one of these three, the Product schema will not generate a rich result. The name property is also effectively required. Recommended properties that unlock additional rich result features include image (for product image in SERP), description, sku or gtin (needed for merchant listings), brand, and priceValidUntil in the Offer. For Google's free product listings program, GTIN is strongly recommended and in many categories required.
Offer Properties Explained
The Offer sub-type carries the pricing data. priceCurrency must be a valid ISO 4217 currency code (USD, EUR, GBP). price must be a numeric value — do not include currency symbols. availability must be one of the schema.org availability values: InStock, OutOfStock, PreOrder, Discontinued, or LimitedAvailability — always use the full URL form (https://schema.org/InStock). If you have multiple pricing tiers or regional offers, use an array of Offer objects rather than a single Offer. Keep price data current — stale pricing can lead to Google suppressing your rich result.
AggregateRating Best Practices
The AggregateRating displays star ratings in the SERP. Required sub-properties are ratingValue (numeric, typically 1–5) and either reviewCount or ratingCount. Google also wants bestRating and worstRating to understand your scale — if you omit them, Google assumes 1 and 5. Critical rule: never fake or inflate ratings. Google cross-checks ratings with third-party review signals and has been known to manually penalize sites that markup fictitious reviews. Only mark up ratings from genuine customers shown visibly on the page.
Eligibility Requirements
Product rich results are only eligible on individual product pages — not category pages, search results pages, or homepages. Each page must represent a single specific product. The page must be indexable (no noindex tag), reachable by Googlebot, and the product information in the schema must match the information visible to users on the page. Sites must comply with Google's Shopping policies. Affiliate or intermediary sites that do not sell the product directly may have reduced eligibility for merchant center-linked product features, though organic rich results can still appear.
How to Test Product Schema
Test using Google's Rich Results Test at search.google.com/test/rich-results. Paste the product page URL or the raw HTML/JSON-LD and the tool will show which rich result features are detected and flag any missing required properties. Also check Google Search Console under Enhancements > Products for site-wide coverage data, error counts, and URLs that are valid, have warnings, or have errors. For pre-deployment testing, validate against schema.org via validator.schema.org to catch spec-level issues before Google encounters the page.
Common Mistakes and How to Fix Them
Common product schema errors include: missing priceCurrency or using a currency symbol instead of the ISO code; availability set as a plain string like "In Stock" instead of the schema.org URL; fake or aggregated reviews spanning multiple products; using Product schema on category pages; price mismatches between schema and page content (Google may suppress or label your listing as misleading); and missing GTIN for physical goods (hurts merchant feed eligibility). Fix these by auditing each product page with SitemapFixer, which flags schema property errors automatically across your entire catalog.
Product Schema for Variants and Bundles
For products with variants (sizes, colors), you have two options: implement a single Product schema with multiple Offer objects representing each variant, or use separate pages for each variant each with their own Product schema. Google generally prefers one product per URL. For product bundles, use the isRelatedTo or isSimilarTo properties to signal relationships. If your variants have separate GTINs, separate pages with distinct Product schemas will yield better merchant listing coverage. Consult Google's merchant center documentation for the most current variant handling guidelines.