Schema Markup for E-commerce: A Field Guide to Rich Snippets

Schema markup doesn't guarantee a rich result — Google decides whether to display one — but incorrect or incomplete schema guarantees you won't get one. For e-commerce, three schema types cover most of the opportunity: Product, Review (or AggregateRating), and FAQPage. Product schema needs, at minimum: name, image, description, and an offers object with price, priceCurrency, and availability. Missing availability is the most common reason Product rich results don't render even when everything else is correct — Google treats it as a required signal for showing price and stock status in search. AggregateRating requires ratingValue and reviewCount, nested either inside the Product schema or as its own block referencing the same product. A common mistake is hardcoding a rating that doesn't match what's visibly displayed on the page — Google's structured data guidelines explicitly require the schema to reflect real, visible content, and mismatches here are one of the more common causes of manual structured-data penalties. FAQPage schema pairs each question with its exact visible answer text on the page — not a summary, not a rewrite. Google has tightened FAQPage eligibility over the past two years and now mostly reserves the rich result for government and health sites, but the schema still contributes to how Google's systems understand and can potentially surface your content in AI-generated overviews, so it's worth keeping even where the classic rich snippet doesn't show. A quick sanity check before publishing any schema: run it through Google's Rich Results Test. It catches missing required fields immediately, and it's the fastest way to confirm your JSON-LD is both valid and eligible — syntactically valid schema that's missing a required property for its type is the single most common structured-data mistake we see in audits.