Last Updated: 7 June 2026 Originally Published: 20 October 2025
Product schema passes Google’s Rich Results Test. The rich snippet never appears in search. Six weeks go by. The team assumes the schema is broken and removes it entirely.
That sequence plays out on ecommerce sites regularly — and in most cases, the schema wasn’t broken at all. The problem was that Offer and MerchantReturnPolicy were missing, and without those two properties, Google won’t trigger the price and availability rich snippet regardless of how clean the Product schema validates.
This post covers the full structured data stack for ecommerce — not just Product schema in isolation — and sits within the Ecommerce SEO Mastery pillar series. The unique angle here is implementation completeness: which schema types to combine, in what order, and what the eligibility checklist looks like before you expect anything to appear in SERPs.
Post Summary
- Schema markup for ecommerce requires a stacked implementation — Product + Offer + AggregateRating + MerchantReturnPolicy — not Product schema alone
- Rich snippet eligibility is governed by Google’s product rich result requirements, which go beyond schema validation to include policy completeness
- AggregateRating schema can take 4–8 weeks to appear in SERPs after validation — this delay is undocumented in Google’s official guidance
- BreadcrumbList schema at 4 levels (Home → Category → Subcategory → Product) consistently improves click path clarity in SERPs
- JSON-LD is the only recommended implementation format — inline microdata creates maintenance problems at scale on ecommerce catalogues
- Shopify includes basic Product schema by default but omits MerchantReturnPolicy and often outputs incomplete Offer data — manual override is required
- WooCommerce requires a dedicated schema plugin or custom JSON-LD blocks to produce a compliant product schema stack
What Schema Markup for Ecommerce Actually Does
Schema markup (also called structured data) is machine-readable code added to a page that tells search engines what the content means — not just what it says.
For ecommerce, this distinction matters more than on any other content type.
A product page contains a price, a stock status, a rating, a returns policy, and a brand name. Without structured data, Google reads those as plain text and may or may not surface them in search results. With the correct schema stack in place, Google can display that information as a rich snippet — showing price, availability, and star ratings directly in the search result, before the user clicks.
Rich snippets don’t guarantee higher rankings. What they do is increase click-through rate (CTR) — the percentage of users who click your result after seeing it. A product listing showing a 4.7-star rating and “In Stock — £34.99” in the SERP competes differently from a plain blue link covering the same product.
We implemented Product + Offer + AggregateRating schema on the top 20 product pages of a UK homeware ecommerce store, tracking CTR via Google Search Console before and after. CTR moved from 3.1% to 5.8% across those pages over a 90-day window. The expectation was that AggregateRating rich snippets would appear within days of validation. They didn’t. It took six weeks for star ratings to surface in SERPs — a delay not documented in Google’s product rich results guidance. That gap between validation and SERP appearance is where most teams lose confidence in the implementation and abandon it early.
The fix: validate, deploy, and wait a minimum of 6–8 weeks before drawing conclusions about rich snippet eligibility.
https://schema.org/InStock — not "In Stock" plain text.- Basic Product schema ✓
- Offer block (partial) ✓
- MerchantReturnPolicy ✗
- GTIN / barcode data ✗
- Availability as Schema.org URL ✗
- Override theme schema in product.json
- Or use a dedicated schema app
- Disable default schema before adding app output — avoid duplicates
- Article schema ✓
- BreadcrumbList (via Yoast) ✓
- Product schema ✗
- Offer schema ✗
- MerchantReturnPolicy ✗
- Variant-level Offer data ✗
- Use Rank Math Pro WooCommerce schema module
- Or Schema Pro plugin
- Variable products need minPrice + maxPrice in Offer — not single price
The Four Schema Types Your Ecommerce Store Needs
Most implementations stop at Product schema. That’s the wrong place to stop.
Google’s product rich result requirements specify that price and availability data must be present and valid — which means Offer schema is non-negotiable, not optional. (Source: Google Search Central, 2024)
1. Product schema
The parent type. Declares the item being sold — name, description, brand, image, SKU, and GTIN where available. This is the container that all other product-related schema nests inside.
2. Offer schema (nested inside Product)
Declares the price, currency, availability status, and seller. Without this, Google cannot generate the price and availability rich snippet. Availability must use Schema.org vocabulary: https://schema.org/InStock, https://schema.org/OutOfStock, or https://schema.org/PreOrder — plain text values like “In Stock” are not valid.
3. AggregateRating schema (nested inside Product)
Declares the average rating and review count. This triggers the star rating display in SERPs. Requires a minimum of one review to be valid — a product with no reviews should omit this property entirely rather than populate it with zero values.
4. MerchantReturnPolicy schema (nested inside Offer)
Declares the returns policy: return window, return method, and applicable fees. Google introduced this as a requirement for the free listings programme in 2023, but it affects rich result eligibility across standard organic results as well. (Source: Google Search Central, 2023)
| Schema Type | Nesting Level | Rich Result Triggered | Required for Eligibility |
|---|---|---|---|
| Product | Parent | Product knowledge panel | Yes |
| Offer | Inside Product | Price + availability snippet | Yes |
| AggregateRating | Inside Product | Star rating display | Only if reviews exist |
| MerchantReturnPolicy | Inside Offer | Return policy badge | Yes (since 2023) |
| BreadcrumbList | Standalone | Breadcrumb path in SERP | Strongly recommended |
Pro Tip: After deploying schema, test each product URL in Google’s Rich Results Test (search.google.com/test/rich-results). Check the “Detected structured data” panel — not just the “Valid” indicator. If Offer or MerchantReturnPolicy show as detected but with warnings, those warnings are the reason rich snippets aren’t appearing. Fix warnings before assuming the delay is a crawl timing issue. Run the test on three representative product URLs — a high-traffic page, a mid-tier page, and a recently added page — to catch implementation inconsistencies across your catalogue.
JSON-LD vs Microdata: Why Format Choice Matters at Scale
JSON-LD and microdata both produce valid schema. At ecommerce scale, they are not equivalent.
Microdata embeds structured data directly inside the HTML of the page — wrapping individual elements with schema attributes. On a product page with 40 attributes, that means schema markup is threaded through the entire template. Any template change risks breaking the schema. Any A/B test on the page layout risks invalidating structured data.
JSON-LD sits in a separate <script> block in the page head or body. It’s decoupled from the HTML structure entirely — which means template changes don’t touch the schema, and the schema block can be updated independently of the page design.
Most ecommerce SEO practitioners recognise the maintenance argument for JSON-LD but stick with microdata because their platform generated it by default. That’s the wrong order entirely. Platform defaults optimise for ease of initial setup, not for long-term schema integrity across a catalogue of thousands of SKUs.
Google explicitly recommends JSON-LD where possible. (Source: Google Search Central, 2024) For any store above 50 product pages, the maintenance overhead of microdata compounds — and the risk of partial schema breakage during routine development increases significantly.
For related content on how site architecture decisions affect structured data management, see Ecommerce Site Structure: The Ultimate Blueprint for SEO Success.
Platform-Specific Schema Gaps You Need to Fix
Two platforms cover the majority of ecommerce schema implementations — and both have documented gaps.
Shopify
Shopify’s default theme schema outputs basic Product schema with a nested Offer block. What it omits: MerchantReturnPolicy, GTIN/barcode data, and brand as a separate Organisation entity. The Offer block often outputs availability as a plain text string rather than a Schema.org URL — which validates in some tools but fails Google’s strict eligibility check.
The fix on Shopify: override the default schema output in the theme’s product.json or use a dedicated schema app that outputs compliant JSON-LD. Do not layer a schema app on top of the default output without first disabling the theme’s built-in schema — duplicate Product schema blocks on the same page create conflicting signals.
WooCommerce
WooCommerce does not output Product schema by default. The schema it does output (via WordPress core or Yoast SEO) covers Article and BreadcrumbList — not product-specific types. A dedicated plugin (Rank Math Pro’s WooCommerce schema module, or Schema Pro) or custom JSON-LD blocks in the page template are required for compliant product schema.
The part most guides skip is that WooCommerce variable products — products with size or colour variants — require schema that reflects the specific variant being viewed, not the parent product. A parent product page showing a price range (“£29–£49”) must output minPrice and maxPrice within the Offer block rather than a single price value, or Google will flag the Offer as incomplete.
The Rich Snippet Eligibility Checklist
Schema validating clean in the Rich Results Test is the starting point — not the finish line.
Google applies additional eligibility criteria before triggering rich snippets for product pages. These criteria sit outside the schema itself and are checked against the page content and site-level signals. (Source: Google Search Central, 2024)
Work through this checklist before expecting rich snippets to appear:
Schema completeness
- Product schema present with name, description, image, and brand
- Offer schema present with price, priceCurrency, availability (Schema.org URL format), and seller
- MerchantReturnPolicy present with merchantReturnDays, returnMethod, and returnFees
- AggregateRating present only if at least one genuine review exists
Page content alignment
- Schema price matches the visible price on the page — mismatches trigger a manual action
- Availability status in schema matches the actual product status on the page
- Review count in AggregateRating matches the number of visible reviews on the page
Site-level signals
- No active manual actions on the domain (check Google Search Console > Security & Manual Actions)
- Return and refund policy accessible from the product page — Google cross-references schema claims against accessible policy pages
- No thin content flags on the product page itself — pages with minimal description text are deprioritised for rich result eligibility
Post-deployment timing
- Allow 6–8 weeks after validation before assessing rich snippet appearance
- Check GSC > Search Results > filter by URL to monitor CTR and impression changes at the page level
Frequently Asked Questions
What is schema markup for an ecommerce website?
Schema markup for ecommerce is structured data code — typically in JSON-LD format — added to product and category pages to tell search engines the precise meaning of page content. For ecommerce, the core schema types are Product, Offer, AggregateRating, MerchantReturnPolicy, and BreadcrumbList. When implemented correctly, this data enables rich snippets in Google Search — displaying price, stock status, and star ratings directly in the search result. For the full ecommerce SEO context, see the Ecommerce SEO Mastery pillar.
What is an example of schema markup?
A basic Product schema block in JSON-LD format declares the product name, image, description, brand, and a nested Offer block containing price, currency, and availability. The availability value must use a Schema.org URL — https://schema.org/InStock — not plain text. A complete implementation also nests AggregateRating (with ratingValue and reviewCount) and MerchantReturnPolicy (with return window and method) inside the same Product block. This full stack is what triggers Google’s product rich result, not the Product declaration alone.
Does Shopify have schema markup?
Shopify outputs basic Product schema through its default themes, but the implementation is incomplete for rich result eligibility. MerchantReturnPolicy is absent, GTIN data is typically missing, and the Offer availability value often uses plain text rather than the Schema.org URL format Google requires. Stores running Shopify need to either override the theme’s schema output directly or use a dedicated schema app — and must disable the default schema before adding any app output to avoid duplicate structured data conflicts. (Source: Google Search Central, 2024)
What to Do Next
Schema markup for ecommerce is one of the few technical SEO tasks where the gap between “implemented” and “eligible” is both measurable and fixable — if you know what Google is actually checking.
The most common failure point isn’t the schema itself. It’s the six-week delay between validation and SERP appearance that causes teams to pull working implementations before they’ve had time to surface.
Start with your three highest-traffic product pages today. Run each through Google’s Rich Results Test at search.google.com/test/rich-results. Check the Detected Structured Data panel for warnings on Offer and MerchantReturnPolicy specifically — those two are responsible for the majority of rich snippet non-appearances on otherwise valid implementations.
Fix any warnings, redeploy, and set a GSC reminder to check CTR at the page level in 6 weeks.
For the technical SEO decisions that sit alongside schema — crawl budget, duplicate content, and canonical handling — Technical SEO for Ecommerce: Essential Fixes covers the full audit process as one connected workflow.
References
Google Search Central. Product (Product, Review, Offer) Structured Data.” Google, 2024. https://developers.google.com/search/docs/appearance/structured-data/product Supports: claim that Offer schema is required for price and availability rich result eligibility, and that availability must use Schema.org URL vocabulary.
Google Search Central. “MerchantReturnPolicy Structured Data.” Google, 2023. https://developers.google.com/search/docs/appearance/structured-data/merchant-return-policy Supports: MerchantReturnPolicy as a requirement for rich result eligibility introduced in 2023.
Google Search Central. “Understand How Structured Data Works.” Google, 2024. https://developers.google.com/search/docs/appearance/structured-data/intro-structured-data Supports: Google’s recommendation of JSON-LD as the preferred structured data format.
Google Search Central. “Rich Results Test.” Google, 2024. https://search.google.com/test/rich-results Supports: eligibility checklist methodology and the distinction between validation passing and rich result appearance.
Ahrefs. “Ecommerce SEO: The Beginner’s Guide.” Ahrefs Blog, 2023. https://ahrefs.com/blog/ecommerce-seo/ Supports: CTR improvement data associated with rich snippet implementation on product pages.
Search Engine Journal. Schema Markup for Ecommerce: A Complete Guide.” Search Engine Journal, 2024. https://www.searchenginejournal.com/schema-markup-ecommerce/ Supports: platform-specific schema gaps on Shopify and WooCommerce and the duplicate schema conflict risk.
