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.
Priority map
| Priority | Type | Why agents care |
|---|---|---|
| 1 | Organization (+ sameAs) | Trust and entity resolution |
| 2 | Product + Offer + AggregateRating | Compareable facts for recommendations |
| 3 | ShippingDetails / MerchantReturnPolicy | Deal-breaker filters agents apply |
| 4 | BreadcrumbList + WebSite | Site understanding and navigation |
| 5 | FAQPage | Answer-ready support content |
| 6 | Service / Reservation | Non-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 ✦