Structured Data & Schema Markup for Google Shopping

Why Schema Matters for GMC (Beyond SEO)

Schema markup (structured data using the Schema.org vocabulary) is typically discussed in the context of rich snippets in organic search. But for Google Merchant Center, it has an additional and often overlooked role: it's one of the signals Google's crawler uses to verify that your product data matches your product pages.

When Google reviews your GMC account — whether as part of an automated policy check or a manual review — their systems compare the data in your product feed with what they find when they crawl your product pages. If your feed says a product costs $49.99 but the schema on your product page says $59.99, that discrepancy is a misrepresentation signal. If your feed says "in stock" but your schema says OutOfStock, that's another flag.

This means implementing accurate, up-to-date schema isn't just a nice-to-have for rich results — it's active compliance infrastructure.

The Product Schema: What to Include

The core schema type for e-commerce product pages is Product from Schema.org. Here's the minimum viable implementation:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Wireless Noise-Cancelling Headphones — Black",
  "description": "Premium wireless headphones with active noise cancellation, 30-hour battery life, and foldable design.",
  "sku": "WH-BLK-001",
  "mpn": "WH2025-BLK",
  "brand": {
    "@type": "Brand",
    "name": "SoundWave"
  },
  "image": [
    "https://example.com/images/headphones-main.jpg",
    "https://example.com/images/headphones-side.jpg"
  ],
  "offers": {
    "@type": "Offer",
    "url": "https://example.com/products/wireless-headphones-black/",
    "priceCurrency": "USD",
    "price": "149.99",
    "priceValidUntil": "2026-12-31",
    "itemCondition": "https://schema.org/NewCondition",
    "availability": "https://schema.org/InStock",
    "seller": {
      "@type": "Organization",
      "name": "Your Store Name"
    }
  }
}
</script>

The fields above are the minimum. Google explicitly supports and uses these Product properties for Shopping:

Offer Schema: Price, Availability, and Currency

The Offer nested within your Product schema is the most compliance-critical piece. This is what Google's automated systems compare against your feed data to check for price and availability misrepresentation.

Price: The Exact Match Rule

The price in your schema must exactly match the price a customer sees on your product page and at checkout (before shipping). Even a $0.01 difference can trigger a mismatch flag. If you show a sale price on the page, the schema price should reflect the sale price. If you show both a regular and sale price, use price for the current selling price and optionally add priceValidUntil for time-limited sales.

Availability Values

Use the correct Schema.org availability values — not your own strings:

• https://schema.org/InStock — product is available for immediate purchase
• https://schema.org/OutOfStock — product is not available
• https://schema.org/PreOrder — product available to order but not yet shipped
• https://schema.org/BackOrder — product ordered but currently unavailable, will ship when available
• https://schema.org/Discontinued — product no longer sold

Sale Price Schema

For products with both regular and sale prices, use the full price specification:

"offers": {
  "@type": "Offer",
  "priceCurrency": "USD",
  "price": "89.99",
  "priceValidUntil": "2026-07-15",
  "itemCondition": "https://schema.org/NewCondition",
  "availability": "https://schema.org/InStock"
}

The price field should always reflect what the customer actually pays at checkout (the sale price if a sale is active).

Review & Rating Schema

Adding review schema to your Product schema unlocks star ratings in Google Shopping results — a significant conversion rate advantage.

"aggregateRating": {
  "@type": "AggregateRating",
  "ratingValue": "4.7",
  "bestRating": "5",
  "worstRating": "1",
  "ratingCount": "342"
}

Important rules for review schema:

• Don't fabricate reviews. Google manually audits review data and creating fake ratings is a policy violation that can lead to account suspension.
• Only include aggregateRating if your page visibly displays reviews — it must be based on real user reviews visible on the page
• The rating data must update dynamically as new reviews come in; static ratings that never change raise red flags

Implementation Guide by Platform

Shopify

Shopify's default themes (Dawn, Sense, etc.) include basic Product schema. To verify what your theme generates:

1. Open a product page in your browser
2. Right-click → View Page Source
3. Search for application/ld+json
4. Paste the schema into Google's Rich Results Test

If your theme's schema is missing key fields (like sku, gtin, or accurate availability), you have two options:

• Edit the theme's product.json Liquid template to add missing fields (developer required)
• Use a Shopify app like JSON-LD for SEO (paid) or Schema Plus for SEO to override the default schema

WooCommerce

WooCommerce doesn't include Product schema by default. Install one of:

• Rank Math SEO — free tier includes Product schema; excellent for WooCommerce
• Yoast SEO + WooCommerce SEO — paid WooCommerce plugin adds proper Product schema
• Schema Pro — dedicated schema plugin with WooCommerce integration

BigCommerce

BigCommerce's Stencil themes include Product schema but it's often incomplete. Use the SEO Manager app or edit the theme's schema template directly. See our BigCommerce GMC guide for the full walkthrough.

Testing and Validating Your Schema

Always validate your schema before considering it done. Use these tools:

1. Google's Rich Results Test (search.google.com/test/rich-results) — shows whether Google can parse your schema and which rich result types you qualify for
2. Schema.org Validator (validator.schema.org) — checks for schema syntax errors and warnings
3. Google Search Console → Enhancements — after deployment, GSC shows schema errors across your site over time

After validating the schema itself, cross-check it against your GMC feed:

• Price in schema = price in feed = price visible on page
• Availability in schema = availability in feed
• SKU in schema = item ID in feed

Common Schema Mistakes That Cause GMC Issues

These are the schema errors we see most commonly in stores that have GMC problems:

1. Hardcoded prices that aren't updated. Adding schema manually to a product page and then changing the price without updating the schema creates an immediate mismatch.
2. Showing "InStock" for out-of-stock items. This is one of the most common causes of misrepresentation flags — especially for stores that don't update their schema when items sell out.
3. Multiple conflicting schema blocks. Some themes output one Product schema and an SEO plugin outputs another. Conflicting data confuses Google's parser.
4. Schema only on some product pages. If 60% of your products have schema and 40% don't, the inconsistency can create questions about the whole account.
5. Price in the wrong currency. If your store displays prices in USD but your schema specifies GBP, that mismatch is flagged.

Want to check your store for schema issues and other GMC compliance problems? The GMCUnbanned free scan checks your pages for schema accuracy as part of the full compliance audit.