A practical guide to schema markup for ecommerce: which types to add, how to implement and test Product and Offer data, and what it can and can't do.

Schema Markup for Ecommerce: What to Add and How

Schema markup is machine-readable code that tells search engines exactly what is on your page: the product, its price, its currency, whether it is in stock and how shoppers rate it. For an online store, the core job is to add Product markup with a nested Offer to every product page, then layer on Organization, BreadcrumbList, Review and VideoObject where they apply. Do that, keep it matching what shoppers see, and test it before and after launch.

This guide covers what to mark up, how to add it on Shopify or WordPress, how to test it, and what schema will and won’t do for your revenue.

Moormarketing

Build a Stronger Ecommerce Growth Strategy

Schema can improve how search engines understand product pages, while Moor Marketing helps eCommerce brands build tailored digital strategies for growth.

Explore growth strategies

TL;DR

Put Product markup with a nested Offer on every product page. Include name, image, price and currency (AUD for most Australian stores) at a minimum.
Add Organization, BreadcrumbList, Review and VideoObject markup so Google can understand the whole shopper journey, not just product pages.
Markup must match what shoppers see on the page. Mismatched prices or stock status break Google’s guidelines.
Validate with the Rich Results Test, deploy to a sample of pages, then check them with URL Inspection in Search Console.
Schema makes pages eligible for richer results. It does not guarantee rankings, rich results or sales.

What schema markup does for an online store
The schema types an Australian store should mark up
How to add schema markup to your store
The rule that catches most stores out: match what shoppers see
Test, deploy and monitor
What schema can and can’t do
Schema and AI search
Our perspective
Get the foundations right, then scale
A simple schema checklist for your store
FAQ
Sources

What schema markup does for an online store

Schema markup is standardised, machine-readable information added to a page. Google says it can improve its understanding of ecommerce content and help it display more meaningful breadcrumbs, among other features. Most stores write it as JSON-LD, a block of code in the page’s HTML that sits apart from the visible design. Shopify’s guide describes ecommerce schema as Schema.org structured data that labels details such as name, price, currency, availability, ratings and GTIN.

Think of it as a product label for machines. A shopper sees a photo, a price and a button. A crawler sees a lot of HTML and has to guess which number is the price, which is the RRP and which is the postcode in your footer. Schema removes the guesswork.

There are two practical reasons to care:

Eligibility. Product markup can make a page eligible for merchant listing experiences in Google Search. Without clean data, you simply aren’t in the running for some of those placements.
Clarity. Clean, consistent data supports how search engines and AI-driven discovery tools read your catalogue. Shopify says ecommerce schema helps search engines and LLMs understand commercial pages. Treat that as a reasonable expectation rather than a proven traffic lever.

The schema types an Australian store should mark up

Google names six types as particularly relevant to ecommerce sites: BreadcrumbList, LocalBusiness, Organization, Product/ProductGroup, Review and VideoObject. Here is how they map to a typical store.

Schema type	Where it goes	What it tells Google
Product (with nested Offer)	Every product page	What you sell, at what price, in what currency
ProductGroup	Pages with variants (size, colour)	That several variants belong to one product
BreadcrumbList	Product and collection pages	Where the page sits in your site hierarchy
Organization	Home page or About page	Business name, logo, contact details, social profiles
LocalBusiness	Pages for physical stores or showrooms	Address, opening hours, location
Review / AggregateRating	Product pages with genuine reviews	What customers say and the average score
VideoObject	Pages with product or demo video	That a video exists and what it shows

Google’s guidance implies markup should cover the whole shopper journey: hierarchy, business identity, physical locations, reviews and video, not only the product detail page. If you want a plain-language walkthrough of which ecommerce schema markup types to prioritise for merchant listings, start there, then use the sections below to build your own priority list.

Product, ProductGroup and Offer

This is the heart of it. Google’s merchant listing documentation says to use Product markup, with ProductGroup for variants and a nested Offer for the sale. At a minimum include the product name, an image, the price and the currency. Google also recommends properties such as brand, category, colour, description, GTIN, MPN, review, aggregate rating, size and SKU.

A few practical notes for Australian stores:

Currency. Set priceCurrency to AUD for Australian dollar pricing. Google requires priceCurrency when multiple currencies are represented, and it is good practice on a single-currency store too.
Price format. Google requires a period as the decimal separator, so write 49.95, not 49,95, and leave out the dollar sign and thousands separators.
GTIN. If you stock branded goods with barcodes, add the GTIN. It helps match your product to the right item in Google’s systems. Custom or handmade products may not have one, and that is fine.
Images. Google says product images must be crawlable and indexable, represent the marked-up content and use a format supported by Google Images. Don’t point schema at a lifestyle banner that doesn’t show the product.

BreadcrumbList

Breadcrumbs show the path from home to category to product. Marked up properly, they help Google understand how your catalogue is organised. They also reinforce the structure you’ve built into your collections. If your collection pages are thin or inconsistent, fix that first: our guide to collection page optimisation for Shopify stores covers the structure that makes breadcrumbs worth marking up.

Organization and LocalBusiness

Organization markup carries your business name, logo, contact details and social profiles. Put it on the home page. If you run a physical shop, warehouse pickup point or showroom, LocalBusiness markup on the relevant page adds your address and trading hours. Keep every detail identical to what appears on your Google Business Profile and in your footer.

Review and VideoObject

Only mark up reviews that real customers wrote and that shoppers can see on the page. Don’t copy third-party reviews onto your product pages purely to add stars. If you have product demo videos or short-form clips, VideoObject tells Google the video exists, what it shows and where it plays.

How to add schema markup to your store

The approach depends on your platform. Google’s Merchant Center guidance is to add JSON-LD to the store’s HTML or template, with Product and a nested Offer on landing pages. It says a landing page should contain a Product object and a nested Offer object describing how the product is sold.

Shopify

Shopify’s own perspective is that platform themes may generate basic product structured data automatically, but unsupported schema types require theme-code changes or an app. In practice:

Check what your theme already outputs. View the source of a product page and search for application/ld+json.
Compare the output to the table above. Many themes cover Product and Offer but skip Organization, richer review data or VideoObject.
Fill the gaps with a theme edit or an app, and make sure you aren’t running two sources of Product markup at once. Duplicate or conflicting blocks are one of the most common causes of errors.
Make sure variant prices and availability in the markup reflect the variant the shopper has selected.

If your theme is also dragging down conversions, a mobile-first Shopify conversion rate optimisation process is worth running alongside any schema work, since both touch the same templates.

WordPress and WooCommerce

WooCommerce outputs basic product data on its own, and SEO plugins can add more. As with Shopify, the risk is overlap: a theme, WooCommerce and an SEO plugin may each print their own Product block. Pick one source of truth and switch the others off. If your store also has checkout friction, see our 90-day WooCommerce conversion rate plan.

Custom or headless builds

Add JSON-LD to the page template and populate it from the same data source that renders the visible price and stock. That is the simplest way to stop the two drifting apart.

The rule that catches most stores out: match what shoppers see

Google says structured data must match values visible to users, and that incorrect product data violates its web-developer guidelines. The usual culprits are:

A sale price on the page but the old price in the markup.
“In stock” in the markup while the page says sold out.
A price that excludes or includes GST differently from the visible price. Australian consumers see GST-inclusive prices, so your markup should reflect what they actually pay.
A variant price shown for the cheapest size when the default selection is a pricier one.
Reviews marked up that don’t appear on the page.

Also check that pages are reachable. Pages blocked by robots.txt, set to noindex or placed behind a login can’t be read by Google, so their markup does nothing. And only pages where shoppers can actually buy qualify for merchant listing experiences. Google may verify product data before it displays it.

Test, deploy and monitor

Google’s own workflow is a good checklist. Per its merchant listing documentation, you add properties, follow the guidelines, validate with the Rich Results Test, deploy a sample of pages, inspect the URLs in Search Console, request recrawling and submit a sitemap.

Validate the code. Run representative URLs through the Rich Results Test and fix every critical error before you go wider.
Deploy to a sample. Push the change to a handful of pages across different templates: a simple product, a variant product, a product on sale, an out-of-stock item.
Inspect in Search Console. Use URL Inspection on the live pages to confirm Google can fetch them and see the markup.
Request recrawling and keep your sitemap current. This speeds up discovery of the updated pages.
Roll out and recheck. After a theme update, a new app or a price-rule change, retest. Schema often breaks quietly.

If you use Google Shopping or free product listings, your structured data and your product feed should tell the same story. Mismatches between the two cause disapprovals and wasted spend. Our walkthrough of shopping feed optimisation shows how to keep them aligned, and our piece on a feed-first Shopping ads strategy covers the margin side.

What schema can and can’t do

Be realistic. Product markup makes a page eligible for richer experiences. It is not a ranking switch. Search Engine Land’s guide says schema can enable rich snippets and support understanding across AI and other search modes, but whether it produces a significant traffic increase remains debated. Treat bold claims about big traffic gains with caution.

The sensible way to think about it: schema is hygiene. It removes ambiguity, protects eligibility and keeps your data consistent across Search, Merchant Center and AI-driven discovery. It will not rescue a weak offer, thin product copy or a slow, confusing checkout. It pays off most when the rest of the funnel is already working.

What to measure after rollout:

Valid items and errors in Search Console’s enhancement and merchant listing reports.
Impressions and click-through rate on product pages over a few months, compared with before.
Conversion rate and revenue per session on the same pages, tracked in GA4. If your ecommerce tracking isn’t reliable, start with these five item fields to verify in GA4 ecommerce tracking.

Schema and AI search

Shoppers increasingly meet products through AI-driven answers and summaries as well as classic results. Shopify says ecommerce schema helps search engines and LLMs understand commercial pages and can improve how products appear across Google and AI-driven discovery. That is a platform’s view rather than a guarantee, so the sensible response is modest: keep your product data complete, accurate and consistent everywhere it appears, because those habits help whichever system reads your pages.

Our perspective

Most stores we meet treat schema as a one-off technical tick-box. Someone installs an app, the Rich Results Test goes green and nobody looks again. Then a sale price changes, a variant goes out of stock or a theme update adds a second Product block, and the data quietly goes wrong.

We treat structured data as part of the revenue system, not a side project. It sits next to the product feed, the ad account structure and the tracking setup, and all of them need to describe the same product, the same price and the same availability. When they do, paid and organic channels work from one clean source, and you spend less time fighting disapprovals and mismatches.

That is why our senior strategists work hands-on with owners rather than handing a checklist to an outsourced team. We look at where shoppers drop off, where the data disagrees with itself, and which fixes are worth doing first for your catalogue and your margins. Schema is rarely the biggest lever in the account, but it is one of the cheapest to get right.

Liza

Get the foundations right, then scale

If your product pages carry accurate markup but traffic still isn’t turning into sales, the problem usually sits elsewhere in the funnel: the offer, the page experience, the ad structure or the follow-up. We work with eCommerce owners to find which of those is holding revenue back and fix it in order of impact.

If you want a structured plan, see our 12 Week DOUBLE Your Revenue Challenge, or look at how we help stores convert more customers. You can also explore everything we do for online stores on the Moor Marketing home page. For stores leaning on paid search, our guide to Google Ads for ecommerce explains how feed quality, measurement and budgets fit together.

A simple schema checklist for your store

Use this as a quick audit:

Every product page has one Product block with a nested Offer, and no duplicates.
Name, image, price and priceCurrency (AUD) are present and match the page.
Price uses a period as the decimal separator, with no currency symbol.
Variants use ProductGroup, and each variant’s price and availability are correct.
Brand, GTIN, MPN, SKU, colour and size are included wherever they exist.
Reviews are genuine and visible on the page before you mark them up.
BreadcrumbList matches the visible breadcrumb trail.
Organization is on the home page; LocalBusiness only where you have a physical location.
Pages are indexable and not blocked by robots.txt, noindex or a login.
You retest after theme changes, new apps and pricing changes.

FAQ

Is schema markup important for AI SEO?

It helps, but evidence of a direct effect is still thin. Shopify says ecommerce schema helps search engines and LLMs understand commercial pages. The safe approach is to keep product data accurate, complete and consistent across your site and feeds, which supports both classic search and AI-driven discovery.

How do I add schema markup to a website?

Add JSON-LD to your page’s HTML or template, with a Product and nested Offer on product pages. On Shopify or WooCommerce, check what your theme or plugin already outputs before adding anything. Then validate with the Rich Results Test and inspect deployed pages in Search Console.

What is schema in a website?

Schema is a shared vocabulary, from Schema.org, that labels the content on a page so machines can read it. A price, a product name or an opening-hours entry is tagged as such. Search engines use those labels to understand the page more accurately.

Does schema markup guarantee rich results or higher rankings?

No. Product markup can make a page eligible for merchant listing experiences, but only pages where shoppers can purchase qualify, and Google may verify the data before showing it. Search Engine Land notes that the size of any traffic gain is still debated.