← UCP Field Guide

Which Schema.org types does an e-commerce site need in 2026?

The non-negotiable core: Organization (identity), Product with nested Offer, AggregateRating and ShippingDetails, BreadcrumbList, FAQPage for support questions, and WebSite/WebApplication for tools. Growing in importance: MerchantReturnPolicy, Brand as its own entity, and service/booking types (Service, Reservation) for hybrid businesses. Schema is no longer decoration for rich snippets — it's the data layer agents read before transacting.

Optiqa · 4 min readUpdated September 2026

Priority map

PriorityTypeWhy agents care
1Organization (+ sameAs)Trust and entity resolution
2Product + Offer + AggregateRatingCompareable facts for recommendations
3ShippingDetails / MerchantReturnPolicyDeal-breaker filters agents apply
4BreadcrumbList + WebSiteSite understanding and navigation
5FAQPageAnswer-ready support content
6Service / ReservationNon-product transactions

Common failure patterns

  • ✦Schema present but contradicting visible content — models distrust and drop it
  • ✦Offers without price validity/availability — unusable for comparison
  • ✦Reviews in schema that no third party corroborates — treated as noise

Rule of thumb: if a value changes what an agent would say or do about your product (price, stock, rating, return window), it belongs in schema, server-rendered, and consistent everywhere.

Quick questions

JSON-LD or microdata?

JSON-LD. It's the recommended format, easiest to maintain server-side, and what agent tooling predominantly parses.

Want to know where your site actually stands on this?

cite this page, it was built for it ✦