Definition
Product structured data is a machine readable description of what a product page is selling, written in the schema.org vocabulary and usually placed on the page as a script element of type application/ld+json. It states the name, identifiers, brand, images, price, currency, availability and review data in fields a search engine can read directly, rather than leaving it to infer those things from the layout.
The fields a product page usually declares
- Type
- Product, with the offer nested inside it
- name and description
- Matching the visible product title and description on the page
- image
- The same images a shopper sees, at a resolution large enough to be usable
- brand and identifiers
- Brand name plus gtin or mpn, using the same values the product feed sends
- offers.price and offers.priceCurrency
- The price actually shown on the page, in the currency the page displays
- offers.availability
- In stock or out of stock, reflecting the current state rather than a value set at build time
- aggregateRating and review
- Only where genuine reviews are collected and displayed on the page itself
- Variants
- Declared as a product group with its variants listed, so the size and colour options are described as one product
An illustrative field list rather than a complete specification. The governing rule in every case is that the markup must match what a person sees on the page, since the value of the data comes from being verifiably true.
Why it matters
Product structured data matters because it is how a store states its facts unambiguously to every system that reads the page. It is what makes product results eligible for the richer presentations in search, showing price, availability and ratings beside the listing, and it feeds the merchant listing reports that tell a store whether those facts were understood. It has grown more important as shopping questions move to assistants and answer engines, which need clean, explicit product data far more than they need well-written marketing copy. The markup does not create eligibility on its own, and without it a store is asking every system to guess.
Where it goes wrong
- Markup that disagrees with the page, most often a price that was correct when the template was built and now differs from the one displayed
- Availability hardcoded as in stock across the whole catalogue, which misrepresents sold out items and undermines trust in the rest of the data
- Ratings and review counts declared for products with no reviews on the page, which is exactly what the review snippet policies exist to prevent
- Identifiers that do not match the product feed, so the same item is described one way to Merchant Center and another way to search
- Multiple conflicting blocks on one page, added by the theme and by two apps, leaving a search engine to choose between three different prices
Questions about product structured data
Does product structured data guarantee rich results in search?
No. Valid markup makes a page eligible for the richer presentations, and search engines still decide when to show them based on the query, the device and their own assessment of the page. The realistic expectation is that correct markup removes the reason a page could not qualify, not that it produces a particular appearance on demand.
How is structured data different from the product feed?
The feed is data a store sends to Merchant Center for shopping surfaces and ads. Structured data lives on the page itself and is read by anything that crawls the site, including search engines and answer engines. They describe the same products and should agree on every field they share, which is why identifiers, price and availability are worth reconciling between the two.
Do Shopify and WooCommerce add product structured data automatically?
Most themes and plugins output something, and the quality varies. The frequent issues are stale prices, missing identifiers, availability that does not update, and duplicate blocks once a review or SEO app adds its own. Test a sample of live product pages with a structured data testing tool and check the merchant listing reporting in Search Console rather than assuming the platform has it covered.