Product Structured Data: Markup, Mandatory Fields and Typical Errors
With Product markup Product pages can be described in machine-readable form – for example with price, availability, reviews or variants. This does not automatically improve rankings, but can support richer search representations.
How product markup works, what information is important and what errors can prevent rich results. This wiki page arranges the topic practically and shows, When priority arises, which mistakes are often and how you derive concrete measures from them.
Example: Markup and visible product price contradict each other
On the product page is 79 euros, in the offer object of the JSON-LD still 69 euros. Check price, currency, availability and assignment to the variant together. A parser can find both numbers technically valid and still not fully assess the contradiction in content.
Use actual, visible product information and traceable reviews. Category and product pages are not arbitrarily interchangeable. Even correct markup does not guarantee a certain advanced display in search results.
What Product Markup Is Good For
Product data helps search engines to understand shop pages more precisely and to classify them better in suitable interfaces.
Price, availability or reviews are classic information that users are already interested in in search results.
Price, availability or reviews are classic information that users are already interested in in search results.
Products, variants and offers are described in a machine-readable cleaner way.
Depending on the type and quality, richer search representations are more likely to come into question.
Important fields and stumbling blocks
The markup must match the visible content. Excessive or incorrect information is a common mistake.
This information should be up-to-date, clear and visible on the page.
This information should be up-to-date, clear and visible on the page.
Colors, sizes or materials should be depicted in a structured and consistent manner.
Only actually existing, cleanly integrated data belongs in the markup.
Practice in shops
In shop systems, errors are often caused by templates, feeds and variant logic – not by a lack of will.
Many themes deliver standard markup that does not fit your own data.
Many themes deliver standard markup that does not fit your own data.
Variant pages often need cleaner modeling than just a copy of the same data.
Mistakes, warnings and opportunities can be easily observed there.
FAQ
Short answers to typical practical questions about product-structured data.
For many shops it makes a lot of sense, but only with cleanly maintained product data.
Not automatically. The main benefit lies in understanding and possible rich results.
Yes. Variants often require more thoughtful modeling than simple single pages.
Additional terms
Seitenreport helps to make technical hurdles, indexing problems and untapped SEO potential visible.