Schema markup on Shopify is a block of code, usually JSON-LD, that tells search engines exactly what's on a page: this is a product, it costs AED 240, it's in stock, it has 38 reviews. Most Shopify themes already output Product and Article markup for you. Your job is to check it's accurate, fill the gaps (Organization, breadcrumbs, return policy), and avoid apps that add duplicate data.
You don't need to write code to get this right. You need to know what's there and what good looks like.
What is schema markup, in plain English?
Schema markup (also called structured data) is a standard vocabulary, maintained at schema.org, for labelling things on a web page so machines can read them without guessing. Instead of Google working out that "AED 240" near a "Add to cart" button is probably a price, the markup says "price": "240" and "priceCurrency": "AED".
Google recommends JSON-LD, a small script block in the page's HTML that shoppers never see. It's the format Shopify themes use.
What schema can do for a store:
Make pages eligible for rich results, such as price, availability, shipping and review stars in Google's results.
Help Google understand your business: name, logo, social profiles, contact details, return policy.
Reduce ambiguity for any system that reads your pages, including AI search.
What it can't do: force Google to show anything. Google says clearly that valid markup makes you eligible, not guaranteed.
What schema does my Shopify theme already output?
Probably more than you think. Shopify provides a Liquid filter called structured_data that turns a product or article into JSON-LD. According to Shopify's developer docs:
A product with no variants becomes a schema.org Product.
A product with variants becomes a ProductGroup (the parent, with each variant described inside).
A blog article becomes an Article.
Most current themes, including Shopify's free ones, use this or their own equivalent. Older or heavily customised themes might not.
Look at "Detected items". You want to see something like "Merchant listings" and "Product snippets", with no red errors.
Expand each item and check the values match the page: right price, right currency, right availability.
Repeat for a blog post, your home page and a collection page.
In Google Search Console, check the Shopping and enhancement reports once your store has some traffic. They show errors across all pages, not just the one you tested.
Two things to look for specifically:
Duplicates. If you see two separate Product items on one page, your theme and an app (often an SEO or review app) are both outputting markup. Google may cope, but conflicting prices or ratings are a problem. Pick one source.
Mismatches. Markup that says "InStock" on a sold-out product, or a price that doesn't include your current sale. Google's guidelines require markup to match what's visible.
Merchant listings are for pages where people can buy the product from you. That's every Shopify product page.
Product snippets are for pages about a product where you can't buy it directly, like a review article.
For merchant listings, Google's requirements are short: the product needs a name, an image, and an offers block with a price (above zero) and a three-letter priceCurrency. Your theme almost certainly covers these.
The recommended extras are where most stores have gaps:
shippingDetails: shipping cost, destination and delivery time.
hasMerchantReturnPolicy: return window and which country it applies to.
gtin (barcode), brand, color, size where they apply.
aggregateRating and review from a real review app.
Google suggests defining return and shipping policies once at the Organization level, and only adding them to individual offers when a product is an exception. That's much easier to maintain than editing every product.
If you also manage a Google Merchant Center feed, Google can take shipping and returns from there too. Pick whichever is easier to keep accurate.
What about review stars?
Review stars come from AggregateRating and Review markup, which your review app normally outputs, not your theme. Whether stars actually appear is Google's decision. I've written a full explainer on product review schema and search stars, so I won't repeat it here. One extra tip: if your products have variants, make sure reviews are attached to the right product, which I cover in keeping review context clear across variants.
Organization markup: tell Google who you are
Organization markup has no required properties, but the recommended ones are useful for any store:
name and url
logo (at least 112×112 pixels, looks right on white)
sameAs: links to your Instagram, Facebook, TikTok, YouTube, marketplace profiles
contactPoint: customer service email and phone
address
hasMerchantReturnPolicy: your store-wide return policy
Put it on the home page. Many themes output a basic version with name, logo and social links taken from theme settings, so fill in those settings first. If the theme doesn't output it at all, a developer can add a small JSON-LD block to theme.liquid in under an hour, or you can use an app that does only this.
One thing Organization markup won't do: earn stars for your store as a whole. Google's review snippet guidelines treat reviews of a business shown on that business's own site, including through an embedded widget, as self-serving, so Organization and LocalBusiness pages aren't eligible for star results. Product review stars are a separate matter.
Breadcrumb markup describes where a page sits: Home > Dresses > Linen Dresses > Sage Wrap Dress. Google can use it to show a cleaner path in results instead of a raw URL. Google's documentation notes the feature is available on desktop.
If your theme shows visible breadcrumbs, it often outputs the markup too. If it doesn't, adding visible breadcrumbs is worth doing for shoppers anyway, especially on deep collection structures. It also strengthens internal links back up to your collections, which I talk about in Shopify collection pages that rank.
FAQ schema: what changed in 2026
This one has changed for good. According to the Search Central changelog, Google stopped showing FAQ rich results in Search from May 7, 2026, and removed the FAQPage documentation in June 2026. They're gone for every site.
So for a Shopify store, as of November 2026:
FAQPage markup won't earn an expanded FAQ result in Google. Don't buy an app for it.
Visible FAQs on product and collection pages are still worth having. They answer buying questions, reduce support messages and give search engines and AI tools clear text to read. Here's how to write product FAQs that answer real buying questions.
Existing FAQPage markup is harmless. You don't need to rip it out, but don't spend time adding more.
A good source for those questions, by the way, is your support inbox. In WhatFlow, for example, the questions customers send on WhatsApp sit in one shared inbox, so it's easy to spot the ones that come up every week and put the answer on the page instead.
Article markup for your blog
Article markup has no required properties. Google recommends headline, image, datePublished, dateModified and author with a name and URL. Shopify's structured_data filter covers the basics for blog posts.
Two easy wins: make sure each post shows a real author name, and update dateModified honestly by actually updating the post, not by changing the date.
Should I use a Shopify schema app?
My rule: check first, then fill specific gaps.
Situation
What I'd do
Theme outputs clean Product and Article markup, no errors
Leave it. Add Organization if missing.
Theme is old and outputs nothing or broken markup
Update the theme, or use one schema app as the only source
Review app and theme both output Product markup
Turn off one source so there's one Product per page
You want return policy and shipping markup
Add at Organization level, or via Merchant Center
An app promises "FAQ rich snippets"
Skip it
Every app you add loads code and costs money. Schema is a case where one careful fix beats three overlapping apps.
Free plan available
Run WhatsApp for your Shopify store with WhatFlow
Templates, COD confirmation, Shopify Flow automations and a shared team inbox with no seat fees. Every feature is included on every plan, including Free.
Run one product, one collection, one blog post and your home page through the Rich Results Test. Fix duplicates and wrong prices first, add Organization markup if it's missing, and forget about FAQ rich results. Then get back to the work that actually moves rankings, which is in my Shopify SEO checklist.
Frequently asked questions
Does Shopify add schema markup automatically?
Most current Shopify themes output Product structured data on product pages and Article structured data on blog posts, usually through Liquid's structured_data filter. Organization, breadcrumb and return-policy markup vary by theme, so check your own pages with Google's Rich Results Test.
Do FAQ rich results still work in Google?
No. Google stopped showing FAQ rich results in Search from May 7, 2026, and removed the documentation in June 2026. Visible FAQs on your pages are still useful for shoppers, but FAQPage markup no longer earns an expanded result in Google.
Will schema markup improve my Shopify rankings?
Not directly. Structured data helps Google understand a page and can make it eligible for rich results like price, availability and review stars, which can improve how your listing looks. Google decides whether to show those enhancements.
Should I install a schema app on Shopify?
Only if your theme is missing something you need, such as Organization or return-policy markup, and you can't add it another way. Check first, because a schema app on top of a theme that already outputs Product markup can create duplicate, conflicting data.
