On this page
Know which kind of result you are after
Google supports two product experiences. Product snippets are for pages that show a product with reviews, such as a review or comparison page, and can show rating, price, and availability. Merchant listings are for pages where shoppers can actually buy the product, and make them eligible for richer shopping surfaces. The markup is the same Product type, with different recommended fields.
Markup is for the main product on a page. Do not apply Product to a category page of many items, or to a page that does not offer a product. Each product page gets one Product entity. For the page itself, see product page SEO.
Product pages on a marketplace you do not control have different rules from your own store. If you sell on other platforms, markup there is handled by the platform. Your job is your own site, where the markup must match your own price, stock, and shipping.
The properties to include
Required for merchant listings: name, an offers object, and for offers a price and priceCurrency. Strongly recommended: image, description, brand, sku, availability (an in-stock or out-of-stock value), and url. For reviews and ratings add aggregateRating with ratingValue and reviewCount, or individual review entries.
Price is a number without symbols, with the currency as a separate three-letter code. Availability uses the vocabulary’s defined values rather than free text. Include identifiers such as gtin or mpn when you have them, which helps products be matched. Google’s product structured data documentation lists every field and what it is for.
Brand is worth including even when it is your own name. It helps Google associate the product with a brand entity. For items without a global trade number, such as handmade goods, use a sku and leave identifiers out rather than inventing one, because false identifiers cause mismatches.
Want the articles written for you?
Researches keywords and what competitors rank for. Publishes to WordPress, Webflow, Shopify or Framer once you approve.
Write it in JSON-LD
The structure: a script block of type application/ld+json containing an object whose type is Product, with the properties above and a nested offers object of type Offer. Most ecommerce platforms and SEO plugins generate this automatically from product data, so check what yours outputs before writing any by hand. A schema generator can produce a starting point for custom sites.
Generated markup is only as good as the product data feeding it. If the platform outputs a stale price or the wrong availability, fix the source. Avoid duplicating markup from both a theme and a plugin, which creates conflicting entities.
If your platform already outputs Product markup, do not add a second copy. Open the page source, count the Product entities, and adjust the existing one through settings or a filter rather than stacking another block above it.
Rules that keep it eligible
Every value must be visible on the page. Marking up a price or rating the visitor cannot see violates Google’s guidelines. Reviews should be real reviews from your customers, not copied or self-written. Keep price and availability in sync with the page, and update the markup when they change.
If you sell through Merchant Center as well, keep the feed and the page consistent, since mismatches cause disapprovals. See Merchant Center disapprovals. Service businesses can use Service markup for clarity, but Google does not offer a dedicated rich result for it.
Variants, offers, and multiple prices
A product with several variants, such as sizes and colors, can be marked up in two ways. Use one Product with several offers, one per variant, or a product group with each variant as its own Product, which is the approach for variants that have their own URLs. Follow Google’s documentation on variants for the current guidance.
If the price varies by size, make sure the markup reflects a price the visitor can actually pay on that page. For sales, put the current price in the offer and keep any original price as visible text only if the guidelines for price drops allow it. Include priceValidUntil for time-limited offers.
For shipping and returns, merchant listings support fields for shipping details and return policy. They can show on the listing and reduce friction, and they must match the policy shown on the page. Keep them current, since a wrong shipping cost is among the things Merchant Center reviews flag.
Validate and monitor
Paste a page or the code into the Rich Results Test and fix errors, which block eligibility, and consider warnings, which flag missing recommended fields. After launch, the Merchant listings and Product snippets reports in Search Console show issues across the site. Check them after template changes.
Pair this with the checks in the technical SEO checklist. The part you can hand off: Sprites can update product titles, descriptions, and SEO fields in Shopify and fix Merchant Center product issues, with every change proposed for your approval.
Questions
What is product schema?
It is structured data, usually JSON-LD, that labels a product page’s facts such as name, price, availability, and rating so Google can read them reliably and may use them in product rich results.
Which properties does product schema need?
At minimum a name, plus offers with price and currency for merchant listings. Image, description, brand, sku, availability, and ratings are strongly recommended. Follow Google’s documentation for the current list.
Does product schema improve rankings?
Not directly. It makes pages eligible for richer displays, which can improve click-through and shopping visibility. Rankings still depend on relevance and quality.
Is there a schema for services?
Yes, a Service type exists and can describe what you offer, but Google has no dedicated rich result for it. It is useful for clarity and for non-Google systems.
How do I test product schema?
Use Google’s Rich Results Test on the live page, then check the Product snippets and Merchant listings reports in Search Console. The Schema Markup Validator checks syntax against the full vocabulary.