When to use it
Use Product when the primary entity represented by the visible page matches the Schema.org definition. Select a more specific subtype when accurate.
Minimum starting properties
- name
Recommended properties to evaluate
- @id
- image
- description
- brand
- sku
- offers
- review
- aggregateRating
JSON-LD example
{
"@context": "https://schema.org",
"@type": "Product",
"@id": "https://example.com/products/example/#product",
"name": "Example Product",
"description": "A visible description of the product.",
"brand": {
"@type": "Brand",
"name": "Example Brand"
}
}Common mistakes
- Choosing the type only because a rich result is desired.
- Adding properties not visible or supported by the site.
- Creating conflicting duplicate entities instead of using stable @id values.
- Failing to update markup when visible data changes.
Entity fit for Product
Use Product only when the page visibly represents the corresponding entity or relationship. Begin with the page purpose and the entity graph, then select the most specific supported type. Do not let the available vocabulary dictate claims the page does not make.
Visible support
Every material property should be supported by visible, current, and accurate page content.
Stable identity
Use consistent identifiers when the same organization, person, place, product, service, or webpage appears across the graph.
Consumer requirements
Treat Schema.org validity and search-consumer eligibility as related but separate checks.
Deployment record for Product
- Commercial outcomes connected to the technical and content change.
- Record the page template, generator, source fields, responsible owner, and release reference.
- Avoid allowing price, stock, review, or product structured data to diverge from visible content.
- Test representative product, category, filter, cart, and checkout journeys and compare search and revenue signals.
- Schedule review when visible content, offers, ownership, locations, products, or consumer documentation changes.
Turn product into an accountable record.
A justified type-selection decision for Product with visible-content support and validation evidence.