Product Schema Markup Guide

Product schema is the highest-leverage markup in commerce: it's what turns a plain blue link into a listing with stars, price, and availability — the SERP treatment that lifts CTR more reliably than any position-neutral change a store can make — and it feeds every Google shopping surface besides. It's also the schema type Google polices hardest, because fake stars were inevitable. Here's the complete implementation: the required fields, the dynamic-data rule, the review-markup law, and the validation loop.

What to mark up (the fields that earn treatments)

The Product entity per page, carrying: name, image, description, brand, identifiers (GTIN/MPN where they exist — increasingly expected for product richness and feed matching), nested Offer (price, currency, availability, URL — the price-and-stock treatment's source), and AggregateRating + Review where genuine reviews exist (the stars). Optional but paying: shipping details and return policy markup (surfacing in listings increasingly), and on variant architectures, markup matched to the canonical-variant decision — one Product with offers, or ProductGroup patterns where variants have their own URLs.

The three implementation laws

1. Generate from live data, never hand-write: price and availability in markup must equal the rendered page at all times — mismatches (stale JSON-LD saying in-stock on a sold-out page) are exactly what merchant-listing enforcement checks, and drift is guaranteed the moment markup lives anywhere except the same template variables the page renders from. Platform plugins and theme-level JSON-LD do this correctly by default; verify rather than assume, per the one-emitter rule (duplicate Product blocks from theme + plugin + app is the commonest store markup bug we audit).
2. The review-markup law: stars require real, on-page, collected-by-you reviews of this product — self-serving ratings, syndicated third-party stars marked up as your own, and review markup on pages without visible reviews are all named policy violations that cost the treatment sitewide when caught. The collection engine is the prerequisite; markup just reports it.
3. Match the visible page, entirely: the general mirror rule at commerce stakes — every marked-up claim visible to a human on the page.

The validation loop

Per-template at build: Rich Results Test on a representative product page each for in-stock, out-of-stock, on-sale and variant cases (the states are where bugs hide). Ongoing: Search Console's merchant-listing/product-snippet reports — the error and warning counts by type, watched monthly, because a template change silently breaking Offer markup across 5,000 products announces itself only here, weeks before the CTR dip would make you hunt for it. And measure the payoff where it lives: CTR by search-appearance filter in the performance report — product-result appearances versus plain results on the same queries is the treatment's own receipts.

Frequently asked questions

We have schema but no stars show. Why?

The usual ladder: validation errors (test the exact URL), no eligible reviews marked up (stars need AggregateRating from real reviews), policy filters (self-serving or mismatched markup), or simply Google's discretion — treatments are granted, not guaranteed, and eligibility precedes display sometimes by weeks. Fix errors, ensure genuine reviews render, then patience before conspiracy.

Does Product schema affect rankings or just appearance?

The standard answer holds in commerce: eligibility not position — but appearance is money here: stars-and-price listings pull disproportionate CTR on commercial SERPs, and the machine-readable product data feeds the free shopping surfaces, which are a distribution channel in their own right (adjacent to the feed's paid one).

Schema markup or Merchant Center feed — do we need both?

Both, doing different jobs: on-page schema earns organic-result treatments and corroborates the feed; the feed drives Shopping surfaces directly. They cross-check each other (mismatches surface as Merchant Center warnings), so consistency across page, markup and feed is the actual deliverable — one product truth, three renderings. The clicks all this wins still land on pages competing the ordinary way: pages built right and authority earned (our aisle).