Product schema is a type of structured data from the shared Schema.org vocabulary, used to explicitly describe a product’s characteristics within a web page’s code. With this annotation, search engines can unambiguously understand information such as the item’s name, price, availability, brand, reviews, and ratings, without having to infer it from the visible text alone. It is a core element of so-called semantic search, because it lets automated systems connect content to concrete entities rather than just keyword strings.
In search engine optimization practice, Product schema is one of the structured data types that can generate rich results, meaning results enriched with additional information shown directly on the search results page. For e-commerce sites and online storefronts it is a fundamental tool, because it improves the visibility of the product page and can increase the click-through rate. Correct implementation requires attention to accepted formats, required fields, and consistency between the declared data and what is actually shown to the user.
How Product markup works
Product schema is a type of semantic markup that lets you label the properties of a good or service for sale. The most common properties include name, description, image, identifier, brand, item condition, and commercial offers. The latter are described through a linked entity, often of type Offer, which collects price, currency, validity period, and availability status.
The goal is to make machine-readable what is already understandable to a human looking at the page. A search engine that receives this information can compare similar products, show the price next to the link, and flag the presence of verified reviews. The reference vocabulary is maintained by the Schema.org community and adopted by major search engines as a shared standard.
Required and recommended properties
Product schema properties are divided into required and recommended. The former are necessary to access rich results; the latter improve the quality of the representation but do not affect eligibility. The choice of fields depends on the product type and the commercial context in which it is offered.
Required fields
Essential fields include the product name and at least one meaningful image. If the product is for sale, you must include an offer with price and currency, plus availability. For aggregate reviews, you must specify the average rating value and the number of ratings collected, when present.
Recommended fields
Recommended properties include description, a unique identifier such as GTIN or the manufacturer’s part number, brand, and item condition, which can be new, used, or refurbished. Adding these details helps search engines distinguish the product from similar ones and show more relevant information.
JSON-LD, microdata, and RDFa: the differences
There are three main formats for adding structured data to a page: JSON-LD, microdata, and RDFa. The first is a data block separate from the visible content, usually placed in the document’s head section. The other two integrate annotations directly into the content’s markup code. Search engines recommend JSON-LD for its ease of maintenance and the clear separation between presentation and metadata.
| Format | Location | Maintenance | Compatibility |
|---|---|---|---|
| JSON-LD | Separate block in the head | Easy to update | Supported by major search engines |
| Microdata | Integrated into the content code | More laborious to modify | Widely supported |
| RDFa | Integrated into content attributes | Requires specific skills | Supported but less common |
| Dynamic data | Automatically generated by the system | Depends on the platform | Varies by implementation |
Why adopt it and how to do it well
Adopting Product schema offers benefits for both site owners and users. The former gain greater visibility and potentially a higher click-through rate; the latter receive clear information right on the search results page. To fully exploit these benefits, it is advisable to follow some basic rules.
- Keep consistency between declared data and what is visible on the page, avoiding discrepancies in price and availability.
- Update dynamic values such as price and stock status whenever they change.
- Include high-quality images with appropriate proportions, linked directly to the product.
- Use unique identifiers such as GTIN codes, when available, to reduce ambiguity.
- Correctly annotate aggregate reviews, indicating average value and number of ratings.
- Validate the markup with the tools provided by search engines.
- Avoid marking as a product something that is not actually for sale or available.
- Periodically monitor error reports to correct any anomalies.
Frequently asked questions
Is Product schema mandatory for an e-commerce site?
It is not mandatory, but it is strongly recommended because it gives access to rich results and improves search engines’ understanding of the content. Its absence does not prevent indexing, but it limits visibility opportunities.
Which format is preferable between JSON-LD and microdata?
Search engines generally recommend JSON-LD because it separates metadata from visible content and is simpler to update. Microdata remains valid and widely supported, but requires more complex changes to the markup.
Can I indicate a price different from the one shown to the user?
No, declared data must match what is visible on the page. A discrepancy in price, currency, or availability can lead to loss of rich results and, in more serious cases, manual actions by search engines.
Does Product schema also apply to services?
The vocabulary provides specific types for services, such as Service, but in some contexts you can use Product to describe a commercial offer. The choice depends on the nature of the item and the guidelines of the reference search engine.
How do you handle variants of the same product?
Variants can be represented as distinct products, each with its own characteristics and offers, or linked to a main product. The most correct solution depends on the catalog structure and the need to show different prices for each variant.
Which errors compromise rich results?
Common errors include missing required fields, invalid values, missing images, and inconsistency between declared data and visible content. Improper use of aggregate reviews can also lead to suspension of the feature.
From glossary to projectDo search engines understand what your site is about?Implementing structured data and Schema markup helps search engines and AI systems interpret content.Discover structured data
Related entries:
Product structured data Schema.org Offer schema Schema markup FAQ schema