Product schema markup: win price and rating rich results

Product schema markup is the difference between a plain blue link and a listing that shows a price, a stock status, and a row of stars before anyone clicks. It is Schema.org structured data, written as JSON-LD, that states in machine-readable form what you sell, what it costs, and whether it is in stock. Google's own product structured data documentation splits it into two eligible experiences, and getting the fields right decides whether either one appears. This guide covers the required properties, the two rich result types, the July 2026 additions most existing guides predate, and how the same markup now feeds the AI engines that answer shopping questions directly.

What is product schema markup?

Product schema markup is structured data based on the Schema.org Product vocabulary that explicitly tells search engines a page describes a product available for purchase, rather than leaving them to guess from the visible text. Instead of Google inferring that "49.99" on the page is a price, you declare it as the price property inside an Offer. That removes ambiguity, and ambiguity is what stops rich results from showing.

It is part of the wider family of structured data and schema markup that also covers articles, organizations, and FAQs. What makes Product markup commercially important is that it is the gating requirement for price, rating, and availability features in Search, for free product listings through Google Merchant Center, and for eligibility to be surfaced by AI shopping assistants. Adoption reflects that: an analysis of ecommerce pages by Digital Chakra found that 57.5% of top-ranking ecommerce pages had implemented some form of schema markup, so on competitive queries the plain link is increasingly the exception, not the norm.

What is the difference between a product snippet and a merchant listing?

Google supports two distinct product rich result types from the same Product vocabulary, and knowing which one you are aiming for tells you which fields matter.

• Product snippets are for pages where people cannot directly buy the item, such as review articles, editorial roundups, or aggregator pages. They lean on review data and can display pros and cons.
• Merchant listings are for pages where a customer can actually purchase from you, typically your own product detail pages. They support richer commerce fields like shipping details, return policy, and apparel sizing.

The practical split, from Google's merchant listing documentation, is that merchant listings require a real Offer with a price greater than zero and a currency, and they do not accept an AggregateOffer in place of it. If you sell the product yourself, you almost always want the merchant listing path, because it is what feeds free listings and the shopping surfaces. Your own product page SEO work and your schema should target the same experience.

What are the required properties for product schema?

The minimum viable Product markup is small. To be eligible for a rich result you need a name, an image, and an offers block containing a price and a priceCurrency. Everything else is recommended, meaning it strengthens eligibility and enriches the display but will not, by itself, block a result.

Formatting is where most implementations quietly fail. Per Google's guidance, price must be a plain number string like "49.99", never "$49.99" and never "1,350" with a thousands separator. The currency is the three-letter ISO 4217 code such as USD or EUR. Availability uses the ItemAvailability enumeration, and the supported values include InStock, OutOfStock, BackOrder, PreOrder, PreSale, SoldOut, LimitedAvailability, Discontinued, InStoreOnly, and OnlineOnly. Here is a minimum block you can adapt:

• @type: Product
• name: the exact product name
• image: a full URL to a high-resolution image
• offers: an Offer with price "49.99", priceCurrency "USD", and availability "https://schema.org/InStock"

To move from a bare snippet toward a full merchant listing, Google recommends adding brand, a product identifier such as gtin or mpn, aggregateRating, and shippingDetails. Those recommended fields are also the ones that make your data reusable for your ecommerce product feed optimization, since Merchant Center reads the same attributes.

How do you earn star ratings with AggregateRating?

Star ratings come from an aggregateRating object nested inside the Product, or from individual review objects. An AggregateRating needs a ratingValue (the average, for example 4.6), a reviewCount or ratingCount, and it inherits the rating scale, which defaults to 1 to 5. Both aggregateRating and review are recommended rather than required, so they will not block a merchant listing, but they are what actually paints the stars.

The hard rule is that the rating must reflect genuine reviews collected on the page or product, and it must be visible to users, not invented in the markup. Google publishes no minimum count, but the durable convention is to wait until you have several real reviews and an average at or above roughly 4.0 before adding the object, because a thin or self-serving rating is a manual-action risk. If you also expose questions and answers on the page, pair this with FAQ schema and PAA optimization so a single page can qualify for more than one enhancement.

What changed in Google's July 2026 product structured data update?

This is the information most older guides miss. On July 9, 2026, Google updated merchant listing structured data with new and clarified properties, as reported by TechWyse. Two additions matter for anyone maintaining product pages:

• category: a property that accepts either a plain-text custom label (with a recommended limit around 750 characters) or a structured CategoryCode object using Google Product Categories. It helps Google place the item in the right taxonomy.
• Sale duration properties: Google clarified how to express when a sale price is valid using priceValidUntil, validFrom, and validThrough, so a temporary discount can be shown and then expire cleanly rather than lingering as a stale price.

The takeaway is that Product markup is a moving target, not a set-and-forget block. A page validated in 2024 can still be technically valid yet miss the newer surfaces because it never declares category or sale windows. Re-audit against the current documentation at least once a quarter.

Do product rich results actually improve click-through rate?

Yes, in the direction you would expect, though the size of the lift depends heavily on the query and how much of the competing set already shows enhancements. A listing that shows price, stars, and in-stock status simply gives a searcher more reasons to choose it over an equivalent plain link. Industry analysis from Digital Applied reports click-through improvements commonly in the range of 20% to 35% for pages that earn product rich results, with review-driven snippets sometimes higher.

Treat those figures as directional rather than a promise. Rich results are a visibility multiplier, not a ranking factor: Google is explicit that structured data does not directly boost position, it makes an already-ranking page eligible for a richer display. The compounding effect matters most in categories where most competitors are still a wall of blue links, which is exactly where being one of the few price-and-stars listings stands out.

How does product schema help you show up in AI answers?

The same structured data that earns a rich result now doubles as a clean, machine-readable summary of your product for the AI engines that answer shopping questions inside chat interfaces. When an assistant is asked to compare options or recommend something in a price band, explicit name, price, availability, brand, and rating fields are far easier to parse and trust than a paragraph of marketing copy. Well-formed markup is not a guaranteed ticket into an AI answer, but it removes friction and reduces the chance the model misreads a price or stock status.

This is why product markup increasingly sits at the center of both classic rich results and newer surfaces like ChatGPT shopping optimization. The information-gain move here, which most ranking guides still skip, is to treat one Product JSON-LD block as a single source of truth that feeds Search rich results, the Merchant Center feed, and AI shopping answers at once, rather than maintaining three inconsistent versions of the same facts.

How do you validate and troubleshoot product schema?

Use two validators, because they answer different questions. Google's Rich Results Test tells you whether your markup is eligible for a specific Google rich result and shows warnings for missing recommended fields. The Schema.org validator checks generic Schema.org correctness without Google's eligibility rules. Passing both is the goal: valid vocabulary and eligible for the feature you want.

The most common failures are predictable. A price with a currency symbol or a comma, an availability value that is not a real ItemAvailability enum, an image URL that is relative rather than absolute, or an aggregateRating that does not match any reviews visible on the page. After you fix markup, confirm the outcome in Search Console's enhancement reports over the following weeks, since eligibility does not equal guaranteed display. For category and collection templates, the same discipline applies across your category page SEO, where a single broken template can suppress rich results at scale. Disclosure: this guide is written by the team behind Sorank, which is one of the tools we use to keep structured data consistent across large catalogs.

Frequently asked questions

Related guides