Product schema
A thing being sold, with its price, availability and the brand behind it.
Where to use it
Product and pricing pages.
A complete example
Valid as written, with every required property and the recommended ones that carry real information.
{
"@context": "https://schema.org",
"@type": "Product",
"@id": "https://www.seoforsolos.com/#product",
"name": "Acme Reference",
"image": "https://www.seoforsolos.com/opengraph-image",
"description": "A one sentence description that restates its own subject.",
"offers": {
"@type": "Offer",
"price": "249.00",
"priceCurrency": "USD",
"availability": "https://schema.org/InStock",
"url": "https://www.seoforsolos.com/pricing"
},
"brand": {
"@type": "Brand",
"name": "Acme"
},
"sku": "ACME-001",
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": 4.8,
"reviewCount": 42
},
"review": {
"@type": "Review",
"author": {
"@type": "Person",
"name": "A Real Person"
},
"reviewRating": {
"@type": "Rating",
"ratingValue": 5,
"bestRating": 5,
"worstRating": 1
},
"reviewBody": "A short review written by a real customer."
}
}Generate a Product node with your own values in the schema generator, and lint what your page actually ships with the schema validator.
Properties
| Property | Status |
|---|---|
name | Required |
image | Required |
description | Recommended |
offers | Recommended |
brand | Recommended |
sku | Recommended |
aggregateRating | Recommended |
review | Recommended |
The three mistakes this type attracts
- 01aggregateRating with no real reviews behind it, which is a policy violation.
- 02A price in schema that disagrees with the price rendered on the page.
- 03Using Product for a service, which Service describes correctly.
Related types
Where this appears in the playbook
- Structured data: what each type is for and which ones earned their place.
- The schema graph: composing types into one graph with stable identifiers.
- One JSON-LD script per page, holding one @graph
- Stable @id anchors that cross-reference rather than duplicate
- Optional fields are omitted, never emitted as empty strings
- Does schema markup work? What 42 types on one site actually did: which of these types measurably did anything in production.
Questions
What is the Product schema type for?
A thing being sold, with its price, availability and the brand behind it. Use it on: product and pricing pages.
Which Product properties are required?
Product requires 2 properties: name, image. It also recommends 6: description, offers, brand, sku, aggregateRating, review.
Does Product produce a rich result?
Product is eligible for a Google rich result when its required properties are present and valid. A validation error therefore has a visible cost in the search result itself.
What is the most common Product mistake?
The most common Product mistake is: aggregateRating with no real reviews behind it, which is a policy violation.