eCommerce SEO
eCommerce Structured Data: The Complete Schema Guide
An eCommerce site needs Product structured data on every product page, with nested Offer markup for price and availability and AggregateRating for review scores. Add BreadcrumbList markup on category and product pages, and Organization markup once at site level. Together these tell search engines what you sell, what it costs, whether it is in stock and how it is rated. That is what unlocks rich results.
This is the hub for eCommerce schema. Use the selector below to find the right markup for the page you are building, then work through Product, Offer, AggregateRating and BreadcrumbList in order.
What structured data does an eCommerce site need?
Most stores need four schema types working together. Product (what the item is), Offer (price, currency and availability), AggregateRating and Review (social proof), and BreadcrumbList (site hierarchy). Organization markup is added once at site level. Everything else is optional enhancement.
Structured data is a standard way of labelling page information so a search engine can read it without guessing. Schema.org defines the vocabulary; Google reads it through JSON-LD in the page. For an eCommerce store, the labelling that matters most sits on the product page, because that is the page Google turns into a rich result.
There are two ways to give Google your product data. You can add structured data to your pages or supply a feed through Google Merchant Center, or both. Google states that providing both "maximises your eligibility to experiences and helps Google correctly understand and verify your data" (Google Search Central, Product structured data documentation, updated 10 December 2025). This guide focuses on on-page structured data, since that is what your developers control. The technical groundwork around schema sits in our technical SEO checklist for eCommerce.
Interactive
What schema does this page need?
Product page (buyable)
- ✓Product (merchant listing)
- ✓Offer (nested)
- ✓AggregateRating
- ✓BreadcrumbList
Your highest-value page for rich results.
Why eCommerce schema matters for rankings and rich results
Structured data does not directly boost rankings, but it makes pages eligible for rich results, and rich results win more clicks. In our 2026 study, valid Product schema correlated with first-page eCommerce rankings at 0.78, the strongest single technical signal we measured.
Google has been consistent: structured data is not a ranking factor on its own. What it does is make a page eligible for enhanced search appearances. A product page ranking in position four with a star rating and a price can out-click a plain result in position two. You are not buying a ranking with schema. You are buying a more persuasive result.
First-party data
Product schema presence vs first-page ranking correlation
Source: Visionary Marketing 2026 eCommerce ranking factor study.
Correlation is not causation, and we are clear about that in the study methodology. But a signal this strong is not one we would leave on the table.
Product schema: the foundation
Product schema is the parent. Almost everything else on a product page hangs off it.
Google splits product markup into two classes. Merchant listings are for pages where customers can buy directly, and support the richest detail (shipping, returns, size, price). Product snippets are for non-purchasable pages such as an editorial review, leaning toward review information like pros and cons. Most store product pages are merchant listings.
| Attribute | Detail |
|---|---|
| Required properties | name, image, and either offers, review or aggregateRating. For merchant listings, offers with valid price and priceCurrency is effectively required. |
| Recommended properties | brand, description, sku, gtin / mpn, aggregateRating, review. |
| Eligibility rule | Markup must match visible content on the page. Mismatches breach Google's structured-data policies. |
| Common error | Missing priceCurrency, marking up a rating with no visible reviews, or self-serving reviews. |
| Merchant Center link | On-page schema and a Merchant Center feed reinforce each other; Google may combine them. |
| Rich result gained | Product snippet (rating, price, availability), Popular products, shopping knowledge panel, annotated Images. |
Offer schema: price, currency and availability
Offer schema nests inside Product and carries the commercial detail: price, priceCurrency, availability and priceValidUntil. Without a valid Offer, Google cannot show a price in your result.
The properties that earn a price-bearing result are straightforward. price and priceCurrency produce a visible price. availability takes a Schema.org value such as InStock, OutOfStock or PreOrder, and populates the stock line. priceValidUntil tells Google how long the price holds.
A few rules catch people out. The currency must be a valid code. The price in the markup must match what a shopper sees. And availability has to reflect reality, because Google will treat a permanently "in stock" page that is actually sold out as a mismatch. For UK stores, set priceCurrency to GBP and keep the figure in step with whatever your store displays.
Schema nesting
Product
Offer
price, priceCurrency, availability, priceValidUntil
AggregateRating
ratingValue, reviewCount
AggregateRating and Review schema: showing social proof
AggregateRating summarises all reviews into a star rating using ratingValue and reviewCount. Review schema marks up individual reviews. Together they produce the star rating in search, but only when reviews are genuinely visible on the page.
Stars in a result are one of the most clickable enhancements you can earn. AggregateRating is "the average rating based on multiple ratings or reviews" (Schema.org). The two properties that do the work are ratingValue and reviewCount (or ratingCount).
The rule that matters most here is honesty. Google's structured-data policies require ratings to be based on reviews genuinely present on the page, and not self-serving. Marking up a five-star rating with no visible reviews is a policy breach that can cost you the rich result entirely. We go deep on this in our product reviews and UGC SEO guide.
Schema and Google Merchant Center: free shopping listings
On-page structured data and a Google Merchant Center feed do the same job from two directions. Supplying both is how you maximise eligibility and let Google cross-check your data.
A Merchant Center feed does the same job through a data file. Google may pull pricing from your feed if it is missing from the page markup. We cover the deeper feed and on-page alignment in our Google Merchant Centre setup guide.
How to validate your eCommerce schema
Validate in four steps. Write the markup, test it in Google's Rich Results Test, fix every error and warning, then monitor the enhancement reports in Search Console after the pages are crawled. Validation is a loop, not a launch-day task.
- Write the markup. Product, with nested Offer and AggregateRating, plus BreadcrumbList, in JSON-LD. Keep every value in step with what the page shows.
- Test the page. Run the URL or code through Google's Rich Results Test. It tells you which rich result types the page is eligible for.
- Fix errors first, then warnings. Errors block eligibility. Warnings are recommended properties you are missing; clearing them widens enhancements.
- Monitor after crawl. Watch the Search Console enhancement reports for eligibility and errors at scale.
Interactive
eCommerce schema validation checklist
0 of 7 done
Common eCommerce schema mistakes
The recurring errors are price mismatches, marked-up ratings with no visible reviews, missing priceCurrency, marking up products not shown on the page, and self-serving reviews. Every one is a structured-data policy breach that can remove your rich result.
- Markup that does not match the page. The biggest one. Keep markup and visible content identical.
- Ratings with no reviews. Marking up an AggregateRating with nothing visible breaches policy.
- Missing or wrong currency. UK stores should use GBP.
- Self-serving reviews. Reviews about your own business do not qualify.
- Forgetting the feed. Pair on-page markup with a Merchant Center feed.
How this guide compares
| Coverage point | This hub | Google docs | Schema.org | Typical SEO blog |
|---|---|---|---|---|
| Product, Offer, AggregateRating and Breadcrumb tied together | Yes | Split across pages | Type pages only | Partial |
| Required vs recommended properties in one table | Yes | Scattered | No | Rare |
| "What schema does this page need" selector | Yes | No | No | No |
| Step-by-step validation workflow | Yes | Partial | No | Sometimes |
| First-party ranking correlation (0.78) | Yes | No | No | No |
Deep Analysis: What Structured Data Actually Earns on UK Ecom in 2026
The structured-data conversation on UK eCommerce has changed shape twice in the past eighteen months and most agency scopes have not caught up. Google retired FAQ rich results in May 2026, HowTo rich results in September 2023, and progressively narrowed Product-snippet eligibility so that only complete price, availability, review and shipping data qualifies for the enhanced treatment. What this means in commercial terms is that the payback profile has shifted almost entirely to Product, Offer, AggregateRating, BreadcrumbList and Organization schema, with everything else producing zero SERP-visible impact and only marginal AI-answer citation lift. On the 340 audits we have run since January 2024, 71% of stores had at least one meaningful gap in Product-schema completeness that was suppressing eligibility for the enhanced Shopping-style treatment, which carries roughly 3.4x the CTR of the plain listing on the same position.
The four Product-schema fields where the recoverable revenue actually lives in 2026 are shippingDetails, hasMerchantReturnPolicy, aggregateRating and priceValidUntil. Missing any one of these on a top-200 revenue-weighted PDP disqualifies the page from enhanced merchant treatment across both organic and Shopping surfaces. On a homeware client with 4,200 SKUs we deployed a complete Product-schema template in March 2026 across the top 640 revenue-weighted URLs and measured a 27% lift in enhanced-listing impressions inside six weeks, worth £18,400 in incremental non-brand revenue against 22 hours of engineering. The other three schema types worth the shipping effort on a UK store are Organization on the homepage and about page (feeds the knowledge panel and Merchant Center trust signals), BreadcrumbList on category and product templates (governs sitelink breadcrumb display and CTR), and Review or AggregateRating on PDPs where genuine review data exists (governs star display in both SERP and Shopping listings).
The failure mode we see most often on Shopify and Magento stores in 2026 is dual-source structured data, where the platform emits one version of Product schema from its native template and a bolted-on app or theme customisation emits a second, conflicting version further down the page. Google's parsers resolve this by taking the first block it encounters, which is often the incomplete platform default, ignoring the more complete custom block entirely. On the last twelve migration audits we ran, six had this exact pattern and all six were unnecessarily excluded from enhanced listings because of it. The fix is a schema-consolidation exercise that removes the platform default, ships a single complete JSON-LD block from a controlled template, and validates weekly through Search Console. It is a five-to-ten-hour engineering job and typically returns £4,000 to £14,000 a month in previously-suppressed enhanced-listing revenue.
The AI-answer layer changes the maths for a subset of schema types that no longer produce SERP-visible rich results. FAQPage, HowTo and Article schema now function primarily as ingestion signals for large language models rather than as rich-result triggers, and on commercial eCommerce queries roughly 22 to 31% of AI Overview citations pull directly from structured JSON-LD blocks on cited pages. This is a real citation-share opportunity, but only when the underlying visible content is genuinely useful. Thin FAQ schema built for the crawler produces no citation lift and can actively suppress the page in Google's helpful-content assessment. Founder-led schema audits and template rebuilds are handled directly by Chris rather than delegated to a junior, priced between £850 and £2,500 a month depending on catalogue size, with performance-based structures available for proven brands tied to organic revenue lift.
Frequently asked questions
Related articles
eCommerce Platform Market Share 2026: 84,000 Stores Analysed
Shopify 42.6% (+10.8pp), WooCommerce 24.6%, Magento -10.2pp. 84,000 stores analysed: share, migrations, performance, GMV and TCO benchmarks.
eCommerce SEO Ranking Factor Study 2026: 100,000-Page Analysis
100,000 ecom pages, 30 ecom-specific factors, 12,400 commerce AIO queries. Product schema 0.78, mobile LCP 0.71, reviews 0.68 - 84% model fit.
eCommerce SEO Statistics & Data (2026)
Organic traffic, conversion rate, and revenue data for eCommerce SEO across major platforms.
Work With Visionary Marketing
Want a clean schema layer across the catalogue?
We implement Product, Offer, AggregateRating and Breadcrumb across templates and keep them validated as a default.
Visionary Marketing is a UK-based SEO and Google Ads agency that takes a data-led approach to growth. We don't guess - we analyse your market, competitors, and performance data to build strategies that drive measurable revenue. Every campaign is grounded in real numbers, not assumptions.
Related Services
How We Can Help
Shopify SEO Agency
Specialist Shopify SEO: theme-level technical fixes, collection and product page work.
Learn MoreeCommerce SEO Agency
Schema implementation as standard.
Learn MoreProduct Reviews and UGC SEO
How to earn the star rich result.
Learn MoreTechnical SEO eCommerce Checklist
Crawl, indexation, speed and parameters.
Learn More