Structured Data

Google Structured Data for Ecommerce

A practical ecommerce guide to Product, Offer, Review, Breadcrumb, variant, shipping, and return structured data for search visibility and AI shopping readiness.

ShopGox Editorial5/23/2026en
Google Structured Data for Ecommerce: Product, Offer, Review, Breadcrumb, and Variants

Structured data helps Google and other systems understand the commercial facts on an ecommerce page: what the product is, what it costs, whether it is available, how it is rated, and how it fits into the site.

For ecommerce SEO, structured data is not decoration. It is a consistency layer between the visible product page, merchant feeds, reviews, variants, shipping promises, and return policies.

Core schema types for ecommerce

Visual summary diagram for Google Structured Data for Ecommerce: Product, Offer, Review, Breadcrumb, and Variants.

Core schema types for ecommerce

Schema typeUse it forCommon ecommerce mistake
ProductProduct identity, images, brand, description, identifiersMultiple conflicting Product entities on one product page.
OfferPrice, currency, availability, seller, URLPrice or currency differs from visible page content.
AggregateRatingSummary rating and review countRating markup exists without visible review evidence.
ReviewIndividual review contentReview app renders reviews but does not expose consistent structured data.
BreadcrumbListPage hierarchy and internal contextBreadcrumb schema does not match visible breadcrumbs.
MerchantReturnPolicyReturn termsPolicy is generic, missing, or inconsistent with the site policy.
OfferShippingDetailsShipping destination, rate, and delivery timeShipping promise is visible but not represented in offer data.

Product and Offer JSON-LD example

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Merino Travel Hoodie",
  "image": ["https://example.com/images/merino-hoodie.jpg"],
  "description": "A lightweight merino wool hoodie for travel and daily wear.",
  "brand": {
    "@type": "Brand",
    "name": "Example Brand"
  },
  "sku": "MH-001",
  "offers": {
    "@type": "Offer",
    "url": "https://example.com/products/merino-travel-hoodie",
    "priceCurrency": "USD",
    "price": "129.00",
    "availability": "https://schema.org/InStock",
    "itemCondition": "https://schema.org/NewCondition"
  }
}

Structured data must match visible content

The most important rule is consistency. If the structured data says InStock but the page says Sold out, the markup becomes less trustworthy. If schema says USD but the shopper sees EUR, your store is creating ambiguity.

Consistency checks

  1. 1Product name matches the primary product identity on the page.
  2. 2Price and currency match the shopper-facing price.
  3. 3Availability matches the visible purchase state.
  4. 4Ratings and reviews match visible review content.
  5. 5Images in schema are crawlable and representative.
  6. 6Canonical URL in schema matches the canonical page.
  7. 7Shipping and return details match policy pages.

How to think about variants

Variant handling is where ecommerce structured data often gets messy. A single product page may include size, color, material, subscription, bundle, or regional pricing differences. Your markup should avoid creating unrelated Product entities that contradict each other.

Reviews and AggregateRating

Review markup is powerful only when it reflects real, visible review content. Review apps can create duplicate or stale markup, especially when themes already output rating data. Audit both the rendered page and JSON-LD sources.

Breadcrumb schema helps explain product hierarchy. It should align with visible breadcrumbs and canonical navigation. For products in multiple collections, choose a stable primary path instead of changing breadcrumbs unpredictably.

Shipping and return data

Shipping and return structured data can help clarify commercial terms. Even when you do not mark up every detail, the visible page should make shipping, returns, and warranty information easy to find.

A practical structured data audit process

Audit flow

  1. 1Fetch the rendered HTML and extract all JSON-LD blocks.
  2. 2Identify every Product, Offer, Review, AggregateRating, and BreadcrumbList entity.
  3. 3Compare schema facts against visible page facts.
  4. 4Check theme output, SEO app output, review app output, and variant app output separately.
  5. 5Validate a representative sample across categories, variants, markets, currencies, and out-of-stock states.
  6. 6Fix contradictions before adding more markup.

FAQ

Which structured data is most important for ecommerce?keyboard_arrow_down

Product and Offer are the foundation. Review, AggregateRating, BreadcrumbList, shipping details, return policies, and variant handling become important as the product page becomes more complex.

Can ecommerce pages have multiple Product schema blocks?keyboard_arrow_down

They can, but it often creates contradictions. A product page should have one clear primary Product entity unless the page intentionally compares multiple products.

Does structured data guarantee rich results?keyboard_arrow_down

No. Structured data helps eligibility and understanding, but search engines decide whether to show rich results based on many factors, including policy compliance and page quality.

Should product schema include reviews?keyboard_arrow_down

Only if the reviews are real, visible, and consistent with the page. Review markup should not invent ratings or expose stale data that users cannot verify.

Related tools

Related posts