Skip to main content

Product structured data for Merchant Center: GTIN, brand, and price consistency

When the page, the markup and the feed disagree on GTIN, brand, price or stock, that is a mess. Use this JSON-LD template and checklist, then scan the live store.

Major11 min read
On this page

A shopper sees one price on the page. The structured data in the HTML says another. The Merchant Center feed says a third. That is a mess. Google treats it as a mess too.

The same headache shows up with identifiers and stock. A GTIN on the page that never made it into the feed. An “In stock” badge next to an out_of_stock attribute. A sale price in JSON-LD that checkout does not honour.

Google’s rules on this are rigid. The cold fact is simple: the visible product page, the Product structured data, and the product data you submit to Merchant Center have to agree.

This guide is a practical template and checklist, not a rewrite of the existing how-to articles. Use it alongside:

1. Copy-paste JSON-LD: Product, GTIN, MPN, brand and offer

Google Merchant Center Help (“Set up structured data for Merchant Center”) recommends adding Product markup as JSON-LD in the HTML the web server returns. The same article says:

  • There should be a Product object with a nested Offer in offers.
  • Structured data must be present in the initial HTML. It must not be generated with JavaScript after the page has loaded.
  • Landing-page content, including pricing, must not change dynamically based on user information such as IP address or browser type.
  • Structured data must match the values shown to the user. Providing incorrect data on product landing pages is described as a violation of Google’s web developer guidelines.
  • If there are multiple offers on the page (for example variants), each offer should be annotated with a SKU or a GTIN that matches the same SKU (id) or GTIN in your Merchant Center product data.
  • The price in structured data must use a period as the decimal separator, not a comma. If you show a sales price that is what the user would actually pay at that time, that sales price belongs in the structured data.
  • For automatic item updates, specifying schema.org price, priceCurrency, availability and condition is required.

Fussy? Yes. Still the rule.

The Merchant Center GTIN attribute help maps GTINs to schema.org properties Product.gtin8, Product.gtin12, Product.gtin13, Product.gtin14 (and Product.isbn for books). Use the property that matches the identifier’s length. Do not invent a number. Google’s GTIN and unique-identifier help pages say to provide a GTIN only when you are sure it is correct; when in doubt, do not submit one.

Copy the block below into the product page’s HTML (typically inside <head> or just before </body>). Replace every placeholder with the same values a signed-out shopper can see, and with the same values you submit in the feed.

<script type="application/ld+json">
{
  "@context": "https://schema.org/",
  "@type": "Product",
  "name": "[PRODUCT NAME AS SHOWN ON THE PAGE]",
  "image": [
    "https://www.example.com/[IMAGE-PATH].jpg"
  ],
  "description": "[SHORT DESCRIPTION AS SHOWN ON THE PAGE]",
  "sku": "[SKU OR MERCHANT CENTER ID]",
  "gtin13": "[13-DIGIT EAN, IF THE PRODUCT HAS ONE]",
  "mpn": "[MANUFACTURER PART NUMBER, IF YOU HAVE ONE]",
  "brand": {
    "@type": "Brand",
    "name": "[BRAND NAME SHOPPERS WILL RECOGNISE]"
  },
  "offers": {
    "@type": "Offer",
    "url": "https://www.example.com/[PRODUCT-PATH]",
    "priceCurrency": "[ISO 4217 CODE, FOR EXAMPLE EUR]",
    "price": "[AMOUNT WITH A PERIOD DECIMAL, FOR EXAMPLE 39.99]",
    "itemCondition": "https://schema.org/NewCondition",
    "availability": "https://schema.org/InStock"
  }
}
</script>

Notes when you fill it in:

  • If the identifier is a 12-digit UPC, use gtin12 instead of gtin13. For a 14-digit ITF-14, use gtin14. For an 8-digit GTIN, use gtin8. You can also use the generic gtin property, as in Google’s Merchant Center structured-data example.
  • If the product is a book with an ISBN, use isbn (and convert ISBN-10 to ISBN-13, as the GTIN help page describes).
  • Leave gtin13 (or gtin) out entirely when the product has no manufacturer-assigned GTIN. Do not pad zeros or reuse a similar product’s code. See section 3 on identifier_exists.
  • brand.name should be the brand shoppers recognise on the packaging or label. Google’s brand attribute help says to use your own store name as the brand only when you manufacture the product or it is a private-label or generic-brand case; do not submit values such as “N/A”, “Generic” or “No brand”.
  • offers.availability should follow the mapping in Google’s availability attribute help, for example InStock / LimitedAvailability / OnlineOnly → in_stock; OutOfStock / SoldOut / Discontinued / InStoreOnly → out_of_stock; PreOrder / PreSale → preorder; BackOrder → backorder.
  • itemCondition should match the condition you submit in the feed (new, refurbished or used) and the condition stated on the page.
  • Check the markup with Google’s Rich Results Test and with the steps in How to validate your product structured data.

A fuller “Merchant listing” property list lives in Google Search Central: How to add merchant listing structured data. Use that article for optional properties. Do not add review or rating markup unless the reviews are real and visible on the page.

2. Price and availability must match the page, the markup and the feed

Google’s price [price] attribute help says the amount and currency in your product data must match the price on the landing page and the checkout pages, in the currency of the target country, shown prominently. It also says:

  • Do not use “View price in cart”.
  • Do not change the price on the landing page based on the user’s location. IP detection is against the guidelines and may interfere with crawler behaviour. If price varies by region, use the regional pricing program where it is available.
  • Discount or coupon prices may be submitted in price only if they are freely available to every user and the price after the discount is displayed clearly on the landing page. Do not submit a member price in price or sale_price; use the loyalty program attribute where it is available.

The same consistency rule applies to stock. Google’s help article “How to fix: Inaccurate availability status due to inconsistency between feed and landing page” is about the availability in your product data not matching the landing page. The availability [availability] attribute help says the availability date for preorder and backorder items should be visible on the landing page, and that structured data markup for availability is a machine-readable representation of the same product data.

Walk this list on a signed-out browser, for every variant you advertise:

If the feed is synced automatically from Shopify, WooCommerce, BigCommerce or Wix, a storefront typo still becomes Merchant Center data. Fix the live page and the catalogue field that the sync reads. Then confirm the structured data was rebuilt from the same values. Patching only the feed leaves the hassle in place.

3. When to use identifier_exists = no (and when not to)

This flag is easy to misuse. Merchants flip it to “no” because a barcode field is empty, then wonder why Merchant Center warns them.

Google’s identifier exists [identifier_exists] help says to use the attribute when unique product identifiers are not available. Those identifiers are submitted with the GTIN [gtin], MPN [mpn], and brand [brand] attributes. For a new product (submitted with the condition [condition] attribute) that does not have assigned identifiers, submit identifier_exists with the value no or false. That value must be submitted in English.

Products that might not have unique product identifiers, according to that same help page, include:

  • Custom goods or one-of-a-kind products, such as custom T-shirts, art, or handmade goods
  • Products produced before GTINs were introduced, such as vintage products, antiques, books published before 1970, and other special products

The minimum requirement is cold and clear. Only set the value to no or false if you are certain the product does not have any assigned unique product identifiers. If you set it to no or false and there is evidence that a unique product identifier exists, the product will receive a warning.

Google’s own examples leave GTIN and MPN blank for a custom dress and a hand-knitted scarf, and set identifier_exists to no. Do the same only when that is actually true.

One more nuance from the brand [brand] help page: if you manufacture the product, you are the only seller, and it has no official brand, use your store name as the brand and include an mpn of your choice. Do not reach for identifier_exists = false in that case.

Leave the flag alone when the product has a real GTIN, MPN or brand. Inventing a number to fill the box is worse than leaving it empty.

Read: When to use identifier_exists and About unique product identifiers.

4. Variants

This is where catalogues go wrong. One parent product. Four sizes. One GTIN copied onto all of them. Or one price in the markup while checkout changes when the customer picks “Large”.

Google’s GTIN help says to use the correct GTIN for each product, including variants. Each variant (different colours or sizes) has its own GTIN. Do not guess. Do not make one up. If you are unsure of a GTIN, do not submit one.

The structured-data help article says that if there are multiple offers on the page, each offer should be annotated with a SKU or a GTIN, and the matching offer in your Merchant Center product data should use the same SKU (id) or the same GTIN.

Practical fix:

  • Give each purchasable variant its own SKU in the catalogue and in the markup.
  • Give each variant its own GTIN when the manufacturer assigned one.
  • Make sure the price and availability in the offer the shopper is looking at match the feed row for that variant.
  • If the page updates the price when a variant is selected, the structured data for that offer has to update with it, in the initial HTML Google can fetch, not only after a click.

See variant status alignment and variant pricing consistency.

5. How to validate the markup and the feed

Do not trust a theme just because it “has structured data.” Open the live product page signed out. View source. Confirm the JSON-LD is in the first HTML response, with the same name, GTIN, brand, price, currency and availability a shopper can see.

Then:

  1. Run the page through Google’s Rich Results Test. Fix critical errors. The Merchant Center structured-data article also points at Search Console for markup issues.
  2. Compare the markup to the Merchant Center product data for the same item or variant: id or GTIN, price, currency, availability, condition, brand, MPN.
  3. Walk checkout and confirm the payable price still matches.
  4. Follow How to validate your product structured data for the longer storefront walkthrough.

If the test fails because a GTIN is missing, do not invent one to make the tool go green. Fix the real catalogue data, or use identifier_exists only when it applies.

6. Shopify, WooCommerce, BigCommerce and Wix

The principle is the same on every platform. Put GTIN, MPN, brand, price and stock in the catalogue fields your Google channel or feed actually reads. Then open the live product page signed out and confirm the visible text and the JSON-LD show those same values.

A typo in the catalogue still lands in Merchant Center if the channel syncs automatically. Fix the source field, let the sync run, and check the page again. Do not patch only the feed file and leave the storefront wrong.

Official admin labels for barcode or GTIN fields were not re-fetched for every platform in this draft, so this section does not invent menu paths. If your theme injects Product markup, confirm it is in the initial HTML and that it is not still showing yesterday’s price.

Questions merchants ask

Do I have to submit a GTIN for every product?

No. Google’s GTIN help says to provide one when the manufacturer assigned it and you are sure it is correct. If you are not sure, do not submit one. For products that truly have no unique identifiers, use identifier_exists as described in section 3.

Can I reuse one GTIN for every size of the same shirt?

No. Each variant needs its own correct GTIN when one was assigned. Copying a parent code across sizes is a classic mess.

The price in the feed matches the page, but checkout is different. Is that a problem?

Yes. Google’s price attribute help says the amount and currency must match the landing page and the checkout pages. “View price in cart” is not allowed.

Does JavaScript-injected structured data count?

Not for Merchant Center matching, according to “Set up structured data for Merchant Center.” The markup has to be in the HTML the server returns, not generated after the page has loaded.

Will fixing the markup get a suspended account back?

Nobody honest will tell you that. Fix the contradictions on the live store and in the feed. Then decide, with a clear record of what changed, whether to request a review. This scan does not connect to Merchant Center and does not file that request for you.

Sources

Check the live storefront

If the page, the markup and the feed disagree, you already have a problem. Paste your store URL into the free StoreVerifier scan. You get the published mismatches, with evidence on the page, so you can fix them before you spend another review request.

Scan your store for free

Similar cases

That is one issue. The library documents 140.

The free scan shows the verdict, the counts and up to 3 findings in full. The paid report opens every finding, with the affected pages, captured evidence and step-by-step fixes. Start free, with no account needed.