Product schema is structured data that describes a product on a web page in a format search engines can read, including its name, images, price, availability, ratings and shipping or return details. For example, a store selling a $49 ceramic planter can use Product schema to state the exact price, that it is in stock and that it ships free in the US, so Google can show those details directly in search results.
For businesses that sell online, Product schema is one of the most practical types of structured data. It can make product pages eligible for richer listings in Google Search, Google Images and shopping experiences, which helps shoppers compare options before they click. It also gives search engines and AI shopping tools a precise, machine-readable record of what you sell and on what terms.
What is Product schema?
Product schema is schema markup based on the Product type from schema.org, usually added to a page as JSON-LD. It describes a single product, and it typically includes an Offer that states the price, currency and availability.
Google's documentation splits Product markup into two uses:
- Merchant listings: for pages where customers can buy the product from you. This supports detailed information such as apparel sizing, shipping details and return policies.
- Product snippets: for pages where people can't buy the product directly, such as editorial product reviews. This supports more review information, such as pros and cons.
Google notes that adding the required properties for merchant listings can also make a page eligible for product snippets.
Why Product schema matters
It can unlock richer search results. According to Google, Product markup can make a page eligible for merchant listing experiences, including the shopping knowledge panel, Google Images, popular product results and product snippets. These can show price, availability, ratings and shipping and return information before anyone clicks. That can improve click-through rate by helping shoppers see what they need upfront.
It reduces guesswork. Without markup, search engines have to infer the price and stock status from the page layout. With markup, those facts are stated explicitly. Google also says that using both on-page structured data and a Merchant Center feed maximizes eligibility and helps it understand and verify your data.
It supports AI shopping. AI tools increasingly help people compare and buy products, a trend covered under ChatGPT Shopping and agentic commerce. Clear, consistent product data on your pages, in your feeds and across the web makes your products easier for these systems to describe accurately. Each platform has its own data sources, so markup is one part of the picture, not a guarantee.
How Product schema works
Required properties for merchant listings
Google's merchant listing documentation lists three required properties: name (the product name), image (product photos) and offers. The offer must be a single Offer, not an AggregateOffer, because the merchant has to be the seller of the product. For product snippets, Google requires name plus at least one of review, aggregateRating or offers.
Recommended properties
Google recommends adding properties such as brand, description, aggregateRating, color and global identifiers like gtin. Within the offer, shippingDetails describes shipping rates, destinations and delivery times, and hasMerchantReturnPolicy describes returns. Google recommends setting a standard return policy in Organization schema and using product-level policies only to override it.
Reviews and pros and cons
Product snippets can show ratings and review information. Since 2022, Google has supported pros and cons markup, but only for editorial product review pages, not merchant product pages or customer reviews. Ratings in your markup should reflect reviews that are actually shown on the page.
Variants
For products that come in multiple sizes or colors, Google recommends product variant markup, which both merchant listings and product snippets support.
How to add Product schema
- Check what your platform already does. Many ecommerce platforms and themes output Product markup automatically. Test a product page before adding anything to avoid duplicate or conflicting markup.
- Include the required properties. Make sure every product page has name, image and an offer with price, currency and availability.
- Add the useful extras. Brand, GTIN, description, shipping details and return policy give search engines more to work with.
- Keep markup and page in sync. The price and stock status in your markup must match what shoppers see. Automate this through your platform where possible.
- Connect Merchant Center. Google says combining a product feed with on-page structured data gives the best eligibility. Free listings can be enabled in Merchant Center.
- Test and monitor. Use Google's Rich Results Test on sample pages and check the merchant listing and product snippet reports in Google Search Console for errors.
Common mistakes and misconceptions
- "Markup guarantees rich results." Google decides whether to show enhanced results. Valid markup makes a page eligible, not guaranteed.
- "Stale prices are fine." Markup that shows an old price or wrong stock status creates a mismatch between search results and your page, which frustrates shoppers.
- "Use AggregateOffer for our own products." For merchant listings, Google requires a single Offer because you are the seller. AggregateOffer is for pages listing offers from multiple sellers.
- "Add Product schema to category pages." Product markup is meant for pages about a specific product, not lists of many products.
- "Our app adds schema, so we're done." Plugins and themes sometimes output incomplete or duplicate markup. Test your actual pages.
Product schema vs. Merchant Center feeds
Product schema lives on each product page and describes that one product. A Merchant Center feed is a file or connection you submit to Google with data for your whole catalog. Google uses both, and some features combine them. For example, Google says product snippets may use pricing from your feed if the page doesn't include it. Schema helps Google understand the page itself. Feeds give Google complete, structured catalog data. Most online stores benefit from both.
How Butter approaches Product schema
At Butter, Product schema is a core part of our schema markup guidance for ecommerce clients and part of our broader ecommerce SEO work. We check what the client's platform already outputs, look for missing required or recommended properties and flag mismatches between markup and visible prices or availability.
We also look at how products are described across the web, since AI shopping tools draw on more than one source. We can't promise rich results or AI recommendations, but accurate, complete product data gives your products a better chance of being shown correctly.
Frequently asked questions
What are the required properties for Product schema?
For Google merchant listings, the required properties are name, image and offers, with the offer stating the price. For product snippets, Google requires name plus at least one of review, aggregateRating or offers.
Does Product schema improve rankings?
Google hasn't said it's a ranking factor. Its main benefit is making product pages eligible for richer results that show price, availability and ratings, which can help shoppers choose your listing.
Do I need Product schema if I use Google Merchant Center?
Google recommends using both. It says combining on-page structured data with a Merchant Center feed maximizes eligibility and helps Google understand and verify your product data.
Can I use Product schema on a service page?
Product schema is designed for products. For services offered by a local business, LocalBusiness or Organization schema is usually a better fit.