Product schema
Product schema is the schema.org/Product structured-data type that describes a single sellable item — name, image, price, availability, ratings. Required for Google's product rich results in classic search and the Shopping tab. Implemented as JSON-LD inside the product detail page.
Long definition
Product schema is the type Google reads to surface price, stock status, review count, and star rating directly in the SERP. Without it, your listing competes only with the title and meta description. With it, the result occupies more vertical space and signals commercial intent.
The fields Google actually requires for rich-result eligibility are documented in the product structured data guide. You need name and one of image, review, aggregateRating, or offers. In practice, a competitive listing carries all of them: name, image (1:1, 4:3, and 16:9 ratios), description, brand, sku, gtin13 (or mpn), and a nested Offer with price, priceCurrency, availability (one of InStock, OutOfStock, PreOrder, BackOrder, Discontinued), and priceValidUntil.
Aggregate ratings need aggregateRating with ratingValue, reviewCount, and bestRating. Google rejects fabricated ratings — the reviews must be visible on the page and tied to the product. Cross-referencing reviews from a parent category page won't qualify.
Variant products use hasVariant (released October 2023) on a parent ProductGroup to keep all SKUs under one canonical, rather than fragmenting authority across separate pages with separate schemas. See product-variant-seo for the full pattern.
Common validation errors flagged in Search Console's Rich Results report: missing priceCurrency, priceValidUntil in the past, availability set to a string not in the allowed enum, mismatch between schema price and on-page price, and review count > 0 with no visible reviews. The last one is now a manual-action trigger after the November 2023 reviews update.
Common misconceptions
- "Product schema guarantees rich results." Eligibility, not guarantee. Google decides per-query whether to render the rich result. Markup that validates can still go unrewarded if the page itself is thin or the brand has trust issues.
- "You need Merchant Center for product rich results." No. Product rich results in classic web search work with on-page schema alone. Merchant Center is required for Shopping tab listings, Shopping ads, and the popular-products carousel.
- "More fields = better." Google ignores fields it doesn't use. Filling
nutrition,material,patternfor a t-shirt won't lift rankings — it just bloats the page payload. Stick to documented fields. - "Schema replaces the visible page content." Whatever you mark up must match what users see. Hidden prices, reviews not on the page, or stock status that contradicts the buy button — all spam-policy violations.
Continue exploring