E-Commerce Schema Markup

Schema markup (structured data, often JSON-LD) is a machine-readable restatement of what the page already shows. For e-commerce, the useful types are Product, Offer, BreadcrumbList, and FAQPage—the last only when a visible FAQ exists.

It does not replace product page SEO or technical SEO. It does not make a duplicate manufacturer description unique. Search engines may use it for rich results; they are not obligated to.

The conceptual SEO loop is How E-Commerce SEO Works. The e-commerce SEO guide is the full sequence.

When you debug JSON-LD, the JSON formatter and JSON validator catch syntax errors. Google’s Rich Results Test (or successor) checks type eligibility against current docs.

Product and Offer

A PDP should expose:

• Product: name, image, description, sku/mpn/gtin when you have them, brand.
• Offer: price, priceCurrency, availability (InStock / OutOfStock / BackOrder as appropriate), URL.

Those values must match the visible price and stock. Dynamic pricing and geo-price need the markup to follow what that user would see, or you should omit rather than lie.

Variant products: mark up the product the page represents. If the URL is the parent, do not claim a specific size’s GTIN unless that is what you sell on that URL.

Property	Must match	Common error
offers.price	On-page price	Sale price in schema, regular on page (or reverse)
availability	Add-to-cart state	Always InStock
image	Primary product image	Logo or a lifestyle shot of a different SKU
name	H1 / title	Marketing slogan that is not the product name

BreadcrumbList

If you show breadcrumbs, you may mark them up. The list must match the visible trail and the links shoppers can click. See internal linking.

Do not invent a deeper hierarchy in JSON-LD than the page shows. Do not mark breadcrumbs on a URL that has none.

FAQ — only when visible

FAQPage is for pages that display questions and answers in HTML (not in an accordion that never appears without JS, if you can avoid that). Typical: shipping FAQ on a shipping policy page, or a short PDP FAQ that is actually on the PDP.

Do not add FAQ schema to every product with the same three generic questions. That is spam. Do not hide answers and mark them up anyway.

Reviews and ratings — never fake

Do not output AggregateRating or Review markup for:

• Ratings you invented.
• Counts copied from another site.
• “4.9 stars” with no visible reviews.

If you have no reviews, omit the types. If a platform app injects fake stars, that is a merchant-quality problem, not an SEO opportunity.

Google’s review-snippet policies are strict. Follow current documentation. This article will not describe how to game them.

Implementation notes

• Generate JSON-LD from the same product object as the template (Shopify metafields, WooCommerce product object, headless API).
• One primary Product node per PDP; do not paste three conflicting blocks from three apps.
• Organization / WebSite schema on the homepage is optional housekeeping; it does not rank the catalog.
• Keep schema out of noindex pages you do not want enhanced.

Shopify and WooCommerce both accumulate leftover schema from uninstalled apps—view-source after changes.

Validation cadence

After theme or app changes: validate a sample PDP, a collection (if you mark collections at all—many stores should not force CollectionPage junk), and a guide with FAQ.

Search Console enhancement reports lag. Syntax-valid JSON that contradicts the page can still be ignored or penalized as spam.

Schema is a honesty layer. Describe the offer on the page. Stop there.

What not to mark up

Skip or be extremely conservative with:

• CollectionPage on thin grids with no unique copy. You are asserting a collection document that category SEO has not earned.
• ItemList of every product on a collection if the HTML grid is paginated or JS-only—the list will not match what a crawler sees.
• VideoObject for a file that is not on the page.
• Speakable and other experimental types you do not use.

Organization schema with a fake sameAs list of social profiles you do not operate is the same class of error as fake reviews: the graph is lying.

Variants, sales, and price validity

If the PDP shows a range (“from $40”), do not mark a single price of $40 unless that is the selected variant’s price. Either mark the variant the URL represents or omit Offer until the template has a single displayed price.

priceValidUntil should be a real date if you use it (end of a sale you will honor). An evergreen fake expiry is a policy problem.

Out of stock: OutOfStock plus a visible status. Do not keep InStock to “preserve rich results.”

Apps and duplicate JSON-LD

View-source after installing a reviews app, an SEO app, and a theme feature that also prints Product. Three Product nodes with three prices is worse than none. Keep a single generator: theme, one app, or your headless renderer.

When you uninstall an app, search the theme for leftover application/ld+json. Shopify and WooCommerce both accumulate this debris.

A practical rollout

1. PDP: Product + Offer only, matching price and availability.
2. BreadcrumbList where crumbs exist.
3. FAQ only on URLs that already show Q&A.
4. Reviews only if visible, legitimate, and policy-compliant—otherwise never.

Validate five URLs in different templates, not only the homepage. The homepage is not the catalog.