SEO for Ecommerce from £495/month · 3-month minimum, then month to month. No 6-month agency lock-in.
Guide

Schema Markup for Ecommerce: What Actually Matters and What Doesn't

Structured data has a genuine, measurable effect on how ecommerce pages appear in search, but it's also one of the most commonly misimplemented parts of ecommerce SEO, either skipped entirely, implemented incompletely, or used in ways that risk a manual penalty. This guide covers the schema types worth prioritising, the ones that are commonly overused, and the mistakes that cause real problems.

What Schema Markup Actually Does

Schema markup, most commonly implemented in JSON-LD format and based on the vocabulary maintained at schema.org, gives search engines and other platforms explicit, structured facts about a page rather than leaving them to infer meaning from unstructured text. For ecommerce, this means telling a search engine directly: this page is a product, it's called X, it costs £Y, it's currently in stock, and it has an average customer rating of Z from N reviews. Done correctly, this can produce rich results (price, availability, and star ratings shown directly in the search listing) and feeds Google's free Merchant Center listings when a page qualifies.

The Schema Types Worth Implementing

Product Schema

The core schema type for any product page, covering the product's name, image, description, brand, and SKU. This is the baseline; without it, none of the more specific enhancements below are possible.

Offer Schema

Nested within Product schema, Offer covers price, currency, and availability (InStock, OutOfStock, PreOrder, and similar values). Keeping availability accurate and up to date matters more than most sites treat it: an out-of-date InStock value on a page that's actually sold out damages user trust and, if Google notices the mismatch between what's marked up and what a user actually finds, can affect how much the site's structured data is trusted going forward.

AggregateRating and Review Schema

These enable the star rating that appears in search results, and they matter for click-through rate more than almost any other on-page element, since a five-star rating with a visible review count is one of the most eye-catching things in a search results page. The critical rule: these must reflect genuine, visible on-page reviews. Google's structured data guidelines are explicit that review markup must correspond to actual reviews on the page itself, not manufacturer ratings, aggregated third-party scores, or fabricated content, and violating this is treated as a policy issue that can result in a manual action against the whole site, not just the offending page.

BreadcrumbList Schema

Marks up the site's breadcrumb trail so it can display in search results in place of a raw URL, which makes listings easier to read and gives a clearer sense of where a page sits in the site structure.

Organization Schema

Placed sitewide, this covers business details like name, logo, and social profiles, and supports how the brand as a whole is represented in search, including in the knowledge panel that can appear for well-known brand searches.

Schema That's Commonly Overused or Misapplied

FAQPage Schema

FAQ schema was widely recommended for years as an easy way to gain extra space in search results. In August 2023, Google significantly restricted how often FAQ rich results appear, limiting them mostly to well-known, authoritative government and health sites, which means the practical SEO benefit for most ecommerce product and category pages has largely disappeared, even though a genuine, well-written FAQ section can still help customers and support content depth.

Fake or Aggregated Review Markup

The single most common schema misstep on ecommerce sites is applying AggregateRating schema pulled from a third-party review aggregator or a manufacturer's global rating, without those specific reviews existing on the page itself. This is against Google's guidelines and is one of the more common causes of structured-data-related manual actions on ecommerce sites.

How to Check Your Current Implementation

Google's Rich Results Test and Search Console's Enhancements reports (which show Product, Merchant Listings, and other structured data types Google has detected across the site) are the two most reliable ways to check what's currently implemented and whether it's valid, rather than assuming a platform's default schema output is correct. It's worth running this check after any platform update or theme change, since these frequently break structured data without any visible symptom on the page itself.

Update, 9 October 2026: Google changed several structured data rules in 2026, including the end of FAQ rich results, a new rule on fake reviews, and new category and sale date guidance. We cover them in Google's 2026 structured data changes.

FAQs

Not directly. Schema doesn't function as a ranking factor in the way content and links do. What it does is make pages eligible for rich results, which improves click-through rate, and it helps search engines and AI tools understand page content more precisely, which supports how well that content is used elsewhere.

No. Review and rating schema must reflect genuine reviews present on that specific page. Using manufacturer or aggregated third-party scores violates Google's structured data guidelines.

BreadcrumbList and, where relevant, ItemList schema are useful on category pages. Product-specific schema (Offer, AggregateRating) belongs on the individual product page, not the category listing.

After any theme, platform, or major template change, and periodically (quarterly is reasonable) as part of ongoing technical audits, since schema errors often go unnoticed without deliberate checking.

Want a clear picture of where your own visibility currently stands? Get a free visibility audit, or head back to the full SEO guide for ecommerce.