Product Schema for E-Commerce: Complete Implementation
Product schema is the highest-ROI structured data type for e-commerce sites. When implemented completely, it triggers rich results that display star ratings, price, availability, and review counts directly in search listings. Google's product search patent (US Patent 9,754,024) describes how product entities are matched to commercial queries.
The Full Product Schema Properties
Required Properties (Must Have for Rich Results)
- name — The product name exactly as displayed on the page
- image — At least one product image URL (3+ images recommended)
- offers — Price, currency, availability, and seller information
- review or aggregateRating — At least one review or a valid aggregate rating
Strongly Recommended Properties
- description — Product description (50-200 words)
- brand — Brand entity with name and optional @id
- sku — Stock keeping unit number
- gtin / gtin13 / gtin8 — Global Trade Item Number (enables product matching)
- mpn — Manufacturer Part Number
- category — Google product category taxonomy path
The Offer Object Structure
Each product must have at least one Offer:
- price — Numeric value
- priceCurrency — ISO 4217 currency code
- availability — Schema.org availability enumeration (InStock, OutOfStock, PreOrder, etc.)
- url — Link to the specific product page
- priceValidUntil — When the price expires (especially important for sales)
- seller — Organization entity selling the product
AggregateRating Requirements
- ratingValue — Average rating (e.g., 4.6)
- bestRating — Maximum possible rating (usually 5)
- ratingCount — Number of ratings
- reviewCount — Number of written reviews (can differ from ratingCount)
Search systems validate that your aggregateRating data matches visible review content on the page. Fabricated ratings will trigger a manual action.
Implementation Patterns by Platform
For Product Detail Pages
Full Product schema with all available properties. Include every variant as a separate Offer within the Product entity.
For Category/Collection Pages
Two options:
- 1ItemList schema with individual Product entities — preferred for categories with fewer than 50 products
- 2Product schema on individual cards — each product card contains its own Product schema block
For Product Comparison Pages
Use ItemList schema with Product entities. Each product should reference its canonical product page URL.
Errors That Block Rich Results
We analyze and fix these through our Structured Data Integrity dimension:
- 1Missing aggregateRating or review — No rich result without at least one
- 2Price format errors — Price must be numeric, not "starting at $29"
- 3Availability not updated — Showing InStock for out-of-stock products triggers penalties
- 4Self-hosted review schema without visible reviews — Reviews must be on the page, not generated
- 5Missing GTIN — While not strictly required, GTIN enables product identity matching that significantly improves product search visibility
The Revenue Impact
For an e-commerce client with 2,400 product pages, we deployed complete Product schema across all pages via our implementation snippet. Results within 60 days:
- Rich result eligibility increased from 23% to 94% of product pages
- Product listing click-through rate improved by 34%
- Revenue from organic product search increased 28%
Product schema is not optional for e-commerce. It is the difference between a plain blue link and a visually rich listing that displays price, rating, and availability — exactly the information that drives purchase decisions.