Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

SEO › E-commerce SEO

Adding Product Structured Data

Add Product structured data to a store: product snippets and merchant listings, mapping catalogue fields, offers, reviews, variants and checks against the feed.
Tutorialintermediate7 min readUpdated

Product snippets and merchant listings

Google's Product structured data documentation describes two kinds of result. Product snippets add details such as ratings, review information, price and availability to a result for a page about a product, including review and comparison pages. Merchant listings are for pages where a shopper can buy the product, and use more specific offer data, such as price, availability, shipping and returns, in shopping experiences across Google's surfaces. The category and product pages guide lists the properties and rules in one section; the structured data guide covers JSON-LD in general (Schema Markup). This tutorial implements the markup on a store's template.

Row labelProduct snippetsMerchant listings
Pages that qualifyPages about a product, including reviews and comparisonsPages where the shopper can buy the product
What the markup centres onThe product, with a review, a rating or an offerThe product with a full offer
Where it can showEnhanced results on the results page (SERP)Shopping experiences across Google, as the documentation lists them
A store's own product pageCan qualifyCan qualify
An affiliate or review siteCan qualifyDoes not qualify

Google's introduction to structured data states that markup can make a page eligible for these features, and its general guidelines state that eligibility does not guarantee display. The markup describes; Google decides.

Before you start

  • The JSON-LD basics from the structured data guide, the prerequisite.
  • A catalogue export with every field the product template prints: name, description, images, brand, identifiers, price, sale price, currency, stock, condition, variant attributes, rating and review count.
  • The Merchant Center feed (Product Feed) if the store has one, with its attribute list. The product feeds guide explains the feed; the Merchant Center feed setup checklist checks it before it serves.
  • Access to the product template and to the code that renders it.
  • A testing route: Google's Rich Results Test, a schema validator and Search Console for the site.

The steps

  1. Map catalogue fields to properties

    Build a mapping table with four columns: the catalogue field, the Product or Offer property, the Merchant Center attribute from the product data specification, and the element on the page that shows it. Every property in the markup must trace to a catalogue field and to something visible on the page, because Google's general guidelines require markup to represent the page's visible content. Fields with no visible counterpart are either added to the page or left out of the markup.

  2. Mark up the product and its identifiers

    Write the Product node with the name, description and images, then the identifiers: the brand, the GTIN where the product has one, the manufacturer part number and the store's own SKU. Google's Product documentation lists these identifiers among the properties it uses, and the product data specification asks for the same identifiers in the feed. Use the same values as the feed, character for character. Leave an identifier out when the product has none; never invent one.

  3. Add the offer: price, currency and availability

    Nest an Offer in the Product with the price the shopper pays now, the currency and the availability value from the schema.org list that the documentation references, plus the page URL. Add the condition, shipping and returns details where the store shows them, since merchant listings use them. Take the price from the same field that prints the price on the page, so that a sale changes both at once; a separate field for the markup is how sale prices end up lagging the page.

  4. Add ratings only where reviews are real and shown

    Add the aggregate rating and individual reviews only when the page displays real customer reviews of that product, and only with the same count and score the page shows. Google's general guidelines forbid markup that describes content readers cannot see, and the structured data guide explains why site-wide or self-serving ratings are not eligible. A product with no reviews gets no rating markup, not a zero.

  5. Express variants

    Decide variants at the URL level first, using the variants table in the category and product pages guide: which attributes get their own page and which stay as a selector on the parent. Then make the markup on each URL describe what that URL shows: a page for one colour carries that colour's identifiers, images, price and stock. Google documents a dedicated pattern for grouping variants on a separate page that this site does not cite, so read Google's current documentation before implementing grouped variants, and keep to the principle that each variant's offer matches the variant the shopper sees. On the feed side, the Merchant Center product variants tutorial gives each variant its own item, a shared item group id and a link that opens that variant.

  6. Keep markup and feed in agreement

    Google's e-commerce guidance treats structured data and the Merchant Center feed as two routes for the same product data. Generate both from the catalogue, on the same schedule as price and stock change, and compare them: price, currency, availability, identifiers and the product URL should match the feed and the page. The product data specification asks for the feed's price and availability to match the landing page, so a disagreement is a problem in Merchant Center as well as in search. When an AI tool proposed the field mapping, the routine for checking AI-generated structured data runs this comparison as one of its checks.

  7. Output the markup in the HTML

    Render the JSON-LD in the HTML the server sends with the product page, from the same template data that prints the visible price and stock. Markup added later by a tag manager or a third-party widget introduces a second source and one more dependency between the catalogue and what crawlers read, which matters for values that change as often as price and stock.

  8. Test a sample per template

    Run a sample of URLs through the Rich Results Test and a schema validator: an in-stock product, an out-of-stock product, a product on sale, a product with variants, a product without reviews and a product without a GTIN. Fix every error and review the warnings: a missing recommended property is worth adding if the catalogue holds it. The SEO page checker is a quick first check that a live page carries structured data.

  9. Monitor the reports and fix drift

    After deployment, watch Search Console's reports for product snippets and merchant listings, which list valid items and items with issues by property, and Merchant Center's diagnostics for mismatches. A rise in errors after a release points to a template change; a rise in price or availability mismatches points to the update schedule. When valid markup produces no result, the rich results not showing page works through the causes.

A product page's markup mapped to catalogue fields (illustrative)

Illustrative example — not a real result

A lighting store finds sale prices lagging in its markup

Glimmerbark Lighting, an invented lighting store, sells around 2,400 products. Its product template printed the visible price from the catalogue's current price field, but a plugin built the markup from the regular price field, so during sales the markup and the page disagreed. The team built the mapping table below and moved the markup into the template.

Catalogue fieldMarkup propertyFeed attributeOn the page
titlenametitleProduct heading
brand_namebrandbrandBrand line under the heading
eangtingtinSpecifications table
skuskuidSpecifications table
current_priceoffers.pricesale_price, with price for the regular pricePrice block
currencyoffers.priceCurrencyPart of the price and sale_price valuesPrice block
stock_statusoffers.availabilityavailabilityStock line
review_avg, review_countaggregateRatingNot sent in this feedReviews section

Before the change, a sale weekend produced 640 price mismatch issues in Merchant Center and 410 product pages with markup prices different from the visible price. Four weeks after the template change, the next sale produced 12 mismatches, all on products whose feed had not refreshed, and none between markup and page.

Common mistakes

  • Markup built from a different field than the page. Sale prices and stock that lag what the shopper sees.
  • Ratings with no visible reviews, or site-wide ratings on every product.
  • Invented or placeholder identifiers. Leave an identifier out when the product has none.
  • One offer for every variant, whatever colour or size the URL shows.
  • Removing markup when stock runs out instead of changing the availability value.
  • Markup injected by a separate tool that drifts from the template's data.
  • Testing one product. Sales, variants, missing identifiers and out-of-stock products are where markup breaks.
  • Treating search and shopping as separate projects. The markup and the feed describe the same products and must agree; good product markup is part of SEO and of the e-commerce section's feed work at once.

Frequently asked questions

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

Google's Product structured data documentation describes product snippets as a richer result for product pages, such as reviews and comparisons, that can show ratings, price and availability. Merchant listings are for pages where a shopper can buy the product directly, and rely on more detailed offer data such as price, availability and shipping. A store's own product pages can qualify for both; a review site that links to retailers qualifies only for snippets.

Do I still need Product markup if I submit a Merchant Center feed?

Google's e-commerce guidance describes structured data and a Merchant Center feed as two ways of sharing product data, and the two work together: the feed drives shopping surfaces, the markup describes the page that the feed links to. Merchant Center can also read price and availability from the markup to correct small differences, as the product feeds guide explains. Keeping both, generated from the same catalogue, gives Google one consistent account of each product.

Should out-of-stock products keep their markup?

Yes. Keep the page and the markup, and change the availability in the offer to the out-of-stock value so that the markup, the page and the feed agree. Removing the markup hides the product's details without telling Google anything useful. What to do with the page itself when a product is discontinued is a separate decision, covered in the category and product pages guide.

Terms used on this page

Tools to try

Frameworks

Where this page is used

Also related

Sources

  1. Product structured data — Google Search Central
  2. General structured data guidelines — Google Search Central
  3. Introduction to structured data markup in Google Search — Google Search Central
  4. Product data specification — Google Merchant Center Help
  5. Ecommerce SEO guide — Google Search Central

Related