Product structured data is a set of information organized in a standardized format that explicitly describes the characteristics of an item for sale or a good being offered. It is placed in the code of the product page and made readable by search engines, which can then accurately understand its name, price, availability, condition and user ratings. The most widely used format for implementing it is the Schema.org vocabulary, often expressed through JSON-LD syntax, which major search engines recommend.
The main purpose of this data is to improve automatic understanding of the content by indexing systems. When a search engine correctly interprets a product’s information, it can generate rich results, meaning visual cards that show elements such as price, average rating and availability directly on the results page. This type of presentation increases the visibility of the content and can lead to a higher click-through rate than a traditional result.
What Product structured data describes
Product structured data belongs to the family of structured data, meaning markup added to HTML code that follows a predefined hierarchy of properties and values. In this specific case, the main type is Product, defined in the Schema.org vocabulary, which groups the essential properties for describing a good or service for sale. Among the most relevant properties are name, description, image, brand, sku, gtin and offers.
The offers property, in particular, itself contains information such as price, priceCurrency, availability and priceValidUntil. This nested structure makes it possible to represent both the product and the commercial conditions associated with it in a complete way. Correct use of these properties allows search engines to distinguish a product from other types of content and to extract the data needed to create rich results.
Available formats for adding it to the page
There are several formats for adding structured data within a web page. The JSON-LD format is currently the most recommended, because it is placed in a separate block within the page’s head or body element, without interfering with the visible markup. Other historical formats are Microdata and RDFa, which integrate attributes directly into the HTML elements of the content.
The JSON-LD format
JSON-LD, short for JavaScript Object Notation for Linked Data, uses key-value pair syntax to describe entities. The block is enclosed in a dedicated tag with the type attribute set to application/ld+json. This format is preferred by search engines because it separates the markup from the visible content, reducing the risk of errors and making maintenance easier.
The Microdata format
Microdata inserts attributes directly into HTML elements, using properties such as itemscope, itemtype and itemprop. This approach ties the markup closely to the page structure, but it can be more complex to manage when the layout changes. For this reason, it has largely been superseded by the JSON-LD format in new implementations.
Which properties to fill in and why
The properties of the Product type let you describe every relevant aspect of an item. Some are required to access rich results, while others are recommended because they improve the quality of the generated card. The choice of properties to include depends on the type of product and the information actually available on the page.
| Property | Description | Requirement |
|---|---|---|
| name | The product name as shown to the user | Required |
| image | One or more representative images of the item | Required |
| offers | The sales conditions, including price and currency | Required |
| brand | The brand or manufacturer of the good | Recommended |
| aggregateRating | The average rating given by users | Recommended |
| sku | The seller’s internal identification code | Recommended |
What you can achieve and what is not guaranteed
Adopting product structured data offers concrete benefits in terms of visibility and informational clarity. However, it does not automatically guarantee the appearance of rich results, because search engines also assess the overall quality of the page and compliance with their guidelines. Incorrect or misleading use of the markup can lead to exclusion from rich results.
- They improve search engines’ understanding of the content.
- They encourage the generation of rich results with price and ratings.
- They increase the product’s visibility on results pages.
- They can increase the click-through rate compared with traditional results.
- They reduce ambiguity between similar products or variants of the same item.
- They make it easier for comparison platforms to aggregate information.
- They require constant updating to stay consistent with the actual content.
- They do not automatically guarantee the appearance of rich results.
Common mistakes and best practices
Among the most frequent mistakes is adding information that does not match the visible content of the page, such as different prices or outdated availability. Omitting required properties or using currencies that are not declared correctly can also prevent validation. It is good practice to check the markup periodically with the testing tools provided by search engines and to keep structured data and actual content aligned.
Another important aspect concerns consistency between the page and product variants. When an item is available in multiple sizes or colors, the variants must be represented correctly to avoid duplication or conflicting information. Clarity in the structure helps search engines distinguish the main product from its variations.
Frequently asked questions about product structured data
What is product structured data?
It is markup added to the code of a web page that describes the characteristics of a product in a standardized way, such as name, price, availability and ratings. It makes this information understandable to search engines.
Which format is recommended for implementing it?
The most recommended format is JSON-LD, which separates the markup from the visible content and reduces the risk of errors. Microdata and RDFa formats are still supported but are less used in new implementations.
Does structured data guarantee rich results?
No, it does not guarantee them automatically. Search engines also assess the quality of the page and compliance with their guidelines before showing rich results.
Which properties are required for a product?
The generally required properties are name, image and offers. The latter must contain information such as the price, currency and availability of the good.
Can user ratings be included?
Yes, you can use the aggregateRating property to indicate the average rating and the number of reviews. However, the data must correspond to real reviews present on the page.
Why is it important to keep them updated?
Because outdated information, such as incorrect prices or availability, can invalidate the markup and reduce search engines’ trust. Consistency between structured data and actual content is essential.
Do you have this problem?Do your products fail to show price, availability or reviews in search results?Without product structured data, Google cannot generate rich results and you lose visibility and clicks. I implement Schema.org Product professionally to get you into rich results.Discover professional implementation
Related entries:
Product schema Schema.org Offer schema Structured content for AI Rich snippet google