Product structured data
Product structured data uses schema.org Product with a nested Offer and optionally aggregate-rating and review data to describe items for sale, enabling product rich results such as price, availability, and review snippets. This page covers required and recommended fields, Google's policies on review data, and how to validate the markup with the Rich Results Test and Search Console.
What this means
Product structured data marks up a page about a single product so Google can show product rich results — price, availability, and sometimes a review star snippet. The core type is schema.org Product, usually with a nested Offer for price details.
Google publishes a product feature guide with required and recommended properties. Valid markup makes a page eligible for product enhancements; it does not force them, and the data must match what the page shows.
Required and recommended fields
For a product snippet, provide name and either a review, an aggregate-rating, or offers. An Offer typically includes price, priceCurrency, and availability. Add fields like image, brand, description, and identifiers (gtin, mpn, sku) where applicable.
Price and availability must be accurate and match the visible page; misleading values violate Google's policies. The markup must describe the specific product on the page, not a category or unrelated items.
- Core type: Product, usually with a nested Offer
- Offer fields: price, priceCurrency, availability
- Recommended: image, brand, description, gtin/mpn/sku
- Values must match the visible page
Review data and validation
If you include an aggregate-rating or review, the ratings must reflect genuine, independently collected reviews of that product. Google prohibits self-serving reviews about your own organization on the same page and fabricated rating data; violations can cause loss of rich-result eligibility or manual action.
Validate with the Rich Results Test and the Schema Markup Validator, and monitor Search Console's Products / merchant listings reports for errors and warnings. Fix issues in the JSON-LD and re-test; eligibility does not guarantee display.
How it appears in analytics and logs
Product markup tells Google a page describes a purchasable item and supplies price, currency, and availability. It does not guarantee rich results, and markup that misrepresents price or availability, or includes self-serving or fabricated reviews, violates Google policy and can trigger manual action or ineligibility.
Diagnostic use case
Add and validate Product schema on product pages so they are eligible for product rich results, while staying within Google's review-snippet and accuracy policies.
What WebmasterID can help detect
WebmasterID confirms which crawlers fetch your product URLs and the responses returned. Validating the Product JSON-LD itself is done with Google's tools; WebmasterID complements that by confirming the page is crawlable and returns 200.
Common mistakes
- Listing a price or availability in markup that does not match the visible page.
- Adding fabricated or self-serving review/rating data, violating Google policy.
- Marking up a category or listing page as a single Product.
- Assuming valid Product markup guarantees a rich result.
Privacy and accuracy notes
Product structured data describes catalog items and published reviews, not individual visitors. WebmasterID records crawler fetches of product pages as bot events and never collects shopper identity.
Frequently asked questions
- What fields does a product snippet need?
- At minimum a name and one of a review, an aggregate-rating, or offers. An Offer usually includes price, priceCurrency, and availability. Add image, brand, and identifiers where they apply, and keep values matching the page.
- Can I add my own star ratings to a product page?
- Only if they reflect genuine, independently collected reviews of that product. Google prohibits fabricated ratings and self-serving reviews of your own organization, and violations can remove rich-result eligibility.
Related pages
- Review and aggregate-rating structured data
Review structured data (the schema.org review and aggregate-rating types) can produce review star snippets in search results when attached to a supported item such as a Product, Recipe, or Book. Google enforces strict policies: ratings must come from genuine reviews, self-serving reviews of your own business are not eligible, and only certain schema types support the snippet. This page explains correct usage and the rules.
- Diagnosing structured data errors
Structured data (schema.org markup, usually as JSON-LD) lets search engines understand a page and can make it eligible for rich results. Errors — missing required properties, invalid types or values, markup that does not match visible content, or policy violations — can make a page ineligible for those features. Diagnosis uses validators and Search Console's rich-result reports.
- Article structured data
Article structured data (Article, NewsArticle, BlogPosting from schema.org) marks up news, blog, and editorial pages so Google can better understand and present them, including in features like Top stories. This page covers the type choice, the properties Google recommends (headline, image, dates, author), and how to validate the markup with the Rich Results Test and Search Console.
- Website observability
Confirm crawlers reach your product URLs with a 200 response.
Sources and verification notes
- Google Search Central — Product structured dataRequired/recommended properties and review policies.
- schema.org — Product
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.