Shopify schema markup checklist (Organization, Product, Breadcrumb, FAQ)

A complete Shopify store needs four schema types: Organization (sitewide), Product with Offer and AggregateRating (product pages), BreadcrumbList (product and collection pages), and FAQPage (where you answer buyer questions). Shopify and your theme cover some of this automatically, but never all of it and rarely correctly. This checklist covers what each does and how to validate it.

I build and audit Shopify stores for D2C brands in India, the US, UK, and UAE, and structured data is one of the first things I check on any store I inherit — because it is almost always half-done. A theme emits Product schema but no breadcrumbs. An SEO app injects a second, conflicting Product block. Organization schema is missing, so Google has no idea the store and the brand are the same entity. This is the checklist I run through, in order.

Why schema markup matters more in 2026 than it did in 2020

Structured data — schema.org markup, almost always in JSON-LD — is a machine-readable description of what a page is about. It does not change what a human sees. It tells a machine, in plain fields, "this is a product, it costs ₹1,299, it is in stock, it has a 4.6 rating from 212 reviews."

For years the payoff was rich results: star ratings and prices in Google's blue links. That still matters. But the bigger shift is that AI systems now read this markup to decide what to say about you. Google's AI Overviews, ChatGPT shopping, and Perplexity all parse structured data to answer buyer questions. When your schema is clean, they quote your real price and rating. When it is missing or wrong, they guess from prose — and often skip you for a competitor whose data is machine-readable.

To be clear up front: schema is not a ranking factor. It will not push you up the results by itself. What it does is make you eligible for rich results and legible to AI, and that is what earns the click and the citation. I go deeper on the AI side in product schema and structured data for AI shopping and on how assistants choose stores in how AI assistants recommend stores.

What does Shopify add automatically, and where are the gaps?

This decides how much work you have. The honest answer: Shopify and modern Online Store 2.0 themes give you a partial foundation, and the gaps are predictable.

The pattern is consistent: Product schema is present but incomplete, Organization is a coin flip, and breadcrumbs and FAQ are almost always missing. So the checklist below is not "add everything from scratch" — it is "verify what exists, fill the gaps, remove the duplicates."

The store-wide schema checklist

Work through these four in order. Each section covers what it does, where it belongs, and how to validate it.

1. Organization schema — the sitewide identity block

What it does. Organization schema tells search engines and AI that your store and your brand are one entity. It carries your legal name, logo, URL, social profiles (sameAs), and contact points. This block lets Google build a knowledge panel and lets an AI assistant connect "who is this brand" to "this store." Without it, your store is just a collection of pages with no declared owner.

Where it belongs. Once, sitewide — I put it in a snippet rendered from theme.liquid so it appears on every page, or at minimum on the home page. One block per site, not per page duplicated with different data.

What to include, at minimum:

• name — your brand's exact name, matching everywhere else you use it.
• url — your canonical home URL.
• logo — an absolute URL to a square logo, ideally 112x112px or larger.
• sameAs — an array of your verified profiles: Instagram, LinkedIn, a verified marketplace, Wikipedia if you have one.
• contactPoint — support email or phone, with contactType.

Consistency is the whole game. The name in your Organization schema, your Product schema brand, your footer, and your social profiles must match exactly. Mismatches confuse entity resolution — the machine can no longer be sure it is all one brand.

How to validate. Run the home page through the Schema.org Validator and confirm the Organization block parses with no errors. Then check that logo and every sameAs URL resolve.

2. Product schema — the block AI shopping reads

What it does. Product schema is the most commercially important type on the store. It describes each product in fields AI shopping tools read directly: name, description, image, brand, sku, gtin, plus nested Offer (price, currency, availability) and AggregateRating (rating and review count). This is what makes you eligible for price and star-rating rich results, and what lets ChatGPT or Perplexity state your price without inventing one.

Where it belongs. Every product template, one block per URL. If variants have different prices, use AggregateOffer with lowPrice and highPrice, or emit per-variant Offer objects — do not emit a single price that is wrong for half your variants.

The fields that get missed:

• brand — often absent; add it and match your Organization name.
• gtin / mpn — barcodes and part numbers; strongly recommended for shopping surfaces.
• aggregateRating — only include it if you have real, visible reviews on the page. Inventing ratings is a manual-action risk.
• availability — must reflect real stock, ideally driven by Liquid so it flips to OutOfStock automatically.
• priceCurrency — set correctly per market; wrong currency is a silent, common bug on international stores.

A hard rule: every value in your Product schema must also be visible on the page. Schema describing content the user cannot see is against Google's guidelines and the fastest way to earn a manual action. The full field-by-field build is in product schema and structured data for AI shopping.

How to validate. Run a live product URL through Google's Rich Results Test. Confirm it detects "Product snippets" or "Merchant listings," the price and availability are correct, and — critically — that there is only one Product block. Two blocks (theme plus app) is the most common error I find.

3. Breadcrumb schema — the navigation path most themes skip

What it does. BreadcrumbList schema describes the path to a page — Home > Collection > Product. Google uses it to show a breadcrumb trail instead of a raw URL, and AI systems use it to understand where a product sits in your catalogue. It is low-effort and high-signal, which makes it doubly annoying that most themes omit it.

Where it belongs. Product and collection pages, matching the visible breadcrumb nav if you have one. Each ListItem needs a position, a name, and an item URL, in order from home to current page.

The common mistakes:

• Breadcrumb schema with no visible breadcrumb on the page — add the visible trail too.
• Broken or relative item URLs — use absolute URLs.
• Positions out of order or starting at 0 — start at 1.

How to validate. Run a product and a collection URL through the Rich Results Test and confirm "Breadcrumbs" is detected with the full path and no errors. Click each item URL to confirm none 404.

4. FAQ schema — the AI-citation block

What it does. FAQPage schema marks up question-and-answer pairs so machines read them as discrete Q&As. The honest 2026 reality: Google restricted FAQ rich results in 2023 to authoritative government and health sites, so a normal store will not see the accordion in blue links. But the markup is still read by AI Overviews, ChatGPT, and Perplexity — exactly where buyer questions now get answered. FAQ schema is an AI-citation play now, not a rich-result play.

Where it belongs. On pages where you genuinely answer buyer questions: product pages (sizing, shipping, ingredients, returns), collection pages (category-level buying questions), or a dedicated support/FAQ page. One FAQPage block per URL.

The rules that keep it valid:

• Every question and answer in the schema must be visible on the page.
• One FAQPage block per URL — do not duplicate the same FAQ across pages verbatim.
• Use real buyer questions, not keyword-stuffed filler.

The full implementation — metafields versus theme versus app, and the pitfalls that get FAQ schema ignored — is in FAQ schema for Shopify product and collection pages.

How to validate. Run the URL through the Schema.org Validator (the Rich Results Test may report FAQ as ineligible for rich results, which is expected — you are validating structure, not chasing the accordion).

Should you code schema into the theme or use an app?

This decision trips up most teams, so here is my honest split, with rough cost framing for the Indian market.

My default: code the core types into the theme. It renders faster, adds no third-party script to every page, and stays correct through the theme changes you control. Apps suit a non-technical team, but two things bite. First, page weight — every app script is more JavaScript, and I have watched schema and SEO apps quietly drag Core Web Vitals down; see Shopify app overhead and store performance. Second, and worse, duplicate blocks: many apps inject their own Product or Organization schema on top of your theme's, so one URL ends up with two conflicting blocks and a Search Console error. If you install a reviews or SEO app, audit the rendered HTML for duplicates. App prices and behaviour change, so verify current terms before you commit.

How to validate the whole store, not just one page

Validating one product page and calling it done is the mistake I see most. Schema lives per template, so you validate per template. Here is the pass I run:

1. Rich Results Test on the live URL, per template type. One product, one collection, one blog post, the home page. Use the live URL, not your source file, so you test what the browser renders after apps and Liquid run.
2. Schema.org Validator for structural correctness. The Rich Results Test only shows Google-supported types; the Schema.org Validator shows everything, including FAQ and Organization structure Google won't preview.
3. Check for duplicates in the rendered HTML. View source, search for application/ld+json, count the blocks. One per type per URL. Two Product blocks means an app is fighting your theme.
4. Confirm every schema value is visible on the page. Price, rating, availability, FAQ answers — if the machine can read it, the human must be able to see it.
5. Watch Search Console over the following weeks. The enhancement reports surface errors and warnings at scale across your whole catalogue — the things a single-page test never catches. This is your ongoing monitor, not a one-time check.

Run that pass once per template type, fix what breaks, and re-run after any theme update or app install. Structured data is not "set and forget" — it drifts every time the store changes.

A quick word on international and metafield-driven stores

Two edge cases. If you sell across markets with Shopify Markets, priceCurrency and availability must reflect the buyer's market — a store showing INR schema to a US buyer is a common, quiet bug. And if you drive product data from metafields (specs, ingredients, compatibility), that data should feed your schema too, so AI reads your structured attributes rather than parsing prose. I cover that in Shopify metafield structure for custom product options and AI.

The one-page summary

If you take nothing else, this is the checklist:

• Organization — sitewide, home page. Name, logo, url, sameAs, contactPoint. One block per site.
• Product — every product page. Name, brand, image, offer (price, currency, availability), aggregateRating if real. One block per URL, no duplicates.
• BreadcrumbList — product and collection pages. Absolute URLs, positions from 1, match the visible trail.
• FAQPage — where you answer real buyer questions. Visible on page, one block per URL, AI-citation play not rich-result play.
• Validate per template — Rich Results Test plus Schema.org Validator on live URLs, check for duplicates, monitor Search Console.

Get those four clean and validated, and your store is legible to both Google's rich results and the AI systems answering buyer questions before anyone reaches your site.

What's next

If your schema is half-implemented — Product present but no breadcrumbs, an app fighting your theme, FAQ missing — that is exactly the kind of surgical fix I do. Tell me your store URL and what you have installed at /start and I will tell you what is missing and what it takes to fix. The scope and fixed pricing for theme-level structured-data work is on the Shopify developer in Delhi page — a schema pass typically sits in the theme-tweak band, from ₹40,000.

Related reads

• Product schema and structured data for AI shopping — the Product type in full, field by field.
• FAQ schema for Shopify product and collection pages — the FAQPage implementation and pitfalls.
• Shopify app overhead and store performance — why schema apps can cost you speed.

Sources

• Google Search Central — Structured data general guidelines
• Schema.org — full type vocabulary
• Google — Rich Results Test