Schema for ecommerce rich results: The Complete 2026 Guide

Each ecommerce rich result requires a specific combination of schema types and properties. The table below shows the minimum requirements for each feature:

All rich results in 2026 require HTTPS URLs for every property value (image, url, logo). HTTP URLs will pass schema validation but will not render in rich results.

The product snippet is the baseline ecommerce rich result. It shows a thumbnail, price, and stock status. To qualify, your Product schema must have a valid Offer with price, priceCurrency, and availability. Google also checks that the url property matches the page canonical and that the page actually displays the product (not a category or search page).

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "4K Action Camera Pro",
  "image": "https://example.com/images/camera-pro.jpg",
  "offers": {
    "@type": "Offer",
    "price": "199.99",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock",
    "url": "https://example.com/products/camera-pro"
  }
}

The product carousel rich result displays multiple products as a horizontal scrollable list. Google product carousels require:

• Minimum 3 products on the same domain with identical schema patterns.
• Images at least 1200x1200 pixels (Google's 2025 update raised this from 800px).
• Each product must have name, image, offers.price, and aggregateRating or review.

The carousel is triggered when Google determines the products share a common theme (brand, category, collection). Consistency in schema structure across all products in the carousel is critical.

Marketplace sites that aggregate products from multiple merchants need seller information on each Offer. The seller's name and URL help Google attribute the offer to the correct merchant. In 2026, Google's merchant listing rich result also uses seller to populate the "Sold by" label in search snippets.

"offers": {
  "@type": "Offer",
  "price": "199.99",
  "priceCurrency": "USD",
  "availability": "https://schema.org/InStock",
  "seller": {
    "@type": "Organization",
    "name": "Camera World",
    "url": "https://cameraworld.example.com/seller/camera-world"
  }
}

The buy-now button appears in mobile search results and takes users directly to the product page. To enable it, your Product schema must include a valid offers with url, price, and availability. The url must point to a page where the user can complete the purchase immediately (not a category page or a page requiring registration). Google validates the purchase path programmatically.

Set up a validation pipeline that runs on every deployment. The pipeline should:

1. Extract all JSON-LD from rendered pages using Google Rich Results Test API.
2. Validate against Google's schema requirements (not just Schema.org).
3. Verify price and availability consistency between schema and DOM.
4. Check image dimensions programmatically against the 1200px minimum.
5. Log warnings for missing optional but recommended properties.

Automated validation catches regressions before they reach production and lose rich result eligibility.

1. Confirm every product page has valid JSON-LD Product + Offer schema.
2. Verify images are 1200px minimum with HTTPS URLs.
3. Check that url properties match canonical page URLs.
4. Ensure AggregateRating is present on pages with reviews.
5. Validate seller information on marketplace product pages.
6. Run Google Rich Results Test on template-level representative pages.
7. Monitor Search Console for rich result impression and click data monthly.

Ecommerce rich results in 2026 reward consistency, accuracy, and completeness. A single template regression can drop thousands of product pages from rich result eligibility. Build schema validation into your deployment pipeline and audit your templates quarterly.

Audit completed on 200 product pages across 8 templates: 12 pages had image dimensions below the 1200px threshold, 5 had url mismatches between schema and canonical, and 2 were missing availability properties. All templates have been corrected and the audit pipeline updated.