- Start with Product + Breadcrumb: they’re the most valuable for ecommerce.
- Schema must match what users see (price, availability, reviews) or you’ll trigger errors.
- Validate regularly with Rich Results and Search Console after theme/app changes.
Schema guide · Updated March 20, 2026 · ~7–10 min read
Shopify structured data (2026)
Structured data (schema.org) helps Google understand your pages and can unlock rich results. For ecommerce, keep it simple: Product + Breadcrumb first, then expand.
1) Priorities (recommended order)
- Product (product pages): price, availability, reviews.
- Breadcrumb: reinforces hierarchy (home → collection → product).
- Organization / WebSite: trust baseline.
- Article (guides): editorial content type.
- FAQPage: only if the FAQ is visible and useful.
Avoid “schema everywhere”: it creates errors and rarely improves SEO by itself.
2) Product schema: what to watch
Keep aligned with the UI:
- price (including sale), currency,
- availability,
- variants (avoid inconsistencies),
- ratings/reviews (only if displayed).
If you use review apps, confirm they don’t add a second Product markup on top of the theme.
3) Breadcrumb: stable structure
Breadcrumb should reflect a logical hierarchy, ideally:
- Home → Collection → Product
Stable hierarchy makes crawl and maintenance easier.
4) FAQ/Article: useful when contextual
FAQ: add it where it resolves objections (shipping, returns, compatibility, care). Keep 3–6 questions and avoid generic copy/paste blocks.
Article: helps clarify guide pages as editorial content.
5) Validation and common errors
Routine:
- test URLs in Rich Results,
- monitor Search Console (Products, Breadcrumb),
- re‑test after theme/app updates.
Common issues:
- duplicate markup (theme + app),
- schema price not matching UI,
- incorrect availability,
- FAQ markup without visible FAQ.
Fast theme + minimal app stack + clean schema = solid base for SEO and conversion.
Try Shopify for freeFAQ
Do I need a schema app?
Not always. Many themes already include Product/Breadcrumb. Apps can help, but watch out for duplicate markup.
Should I add FAQ everywhere?
Only where it answers real questions and is visible on-page. Keep it tight and contextual.
Why does Search Console show price errors?
Usually schema doesn’t match the UI (sale price, currency, variants) or there is duplicate markup.