What are rich snippets, and what do they do for a store?
A plain search result is a title, a URL and two lines of text. A rich snippet adds facts from the page: a product’s price and whether it’s in stock, a star rating with the review count, a readable breadcrumb path instead of the URL, a recipe’s photo and cooking time.
Google builds these from structured data: a block of machine-readable facts in the page’s HTML, written in the schema.org vocabulary. Google recommends the JSON-LD format, a small <script> that sits in the page and changes nothing visitors see.
Rich snippets aren’t a ranking factor. They make the result bigger and more specific, which is what gets the click. The same markup also tells AI assistants which product a page describes, who sells it and for how much, so the work pays twice.
What does Google still show in 2026?
Google removes rich result types from time to time, and two removals matter for stores:
- FAQ rich results are gone. Google’s documentation log says the feature “will no longer appear in Google Search starting May 7, 2026” (Google Search Central updates, May 2026). This applies to every site; the 2023 exception for government and health sites ended too.
FAQPageis still part of schema.org, and other search engines and AI assistants can read the markup, so leave it in place. Just don’t expect a dropdown under your result. - HowTo rich results are gone since 2023.
What still shows, as of Google’s product documentation (last updated 10 Dec 2025):
| Rich result | Needs | Shows |
|---|---|---|
| Merchant listing | Product + Offer with price, currency, availability; optional shippingDetails, hasMerchantReturnPolicy, brand, GTIN |
Price, stock, shipping cost, returns, in Search, Images and Lens |
| Product snippet | Product with aggregateRating and review |
Stars and review count |
| Breadcrumb | BreadcrumbList |
A path like Home › Kitchen › Pans instead of the URL |
| Recipe | Recipe with image, times, rating (Easy Recipe Pages adds it per recipe) |
Photo, stars, cook time in recipe results |
| Article | Article / BlogPosting |
Headline, image and date in Top stories and Discover |
| Organization | Organization with logo, sameAs, return policy |
Brand name and logo in the knowledge panel |
Google separates two classes of product markup: merchant listings for pages where people can buy (that’s a Shopify product page) and product snippets for review-style pages. The required merchant-listing fields also make a page eligible for product snippets, so aim for merchant listings and you get both.
Does my Shopify theme already add structured data?
Partly. Shopify’s structured_data Liquid filter is in Dawn and most current themes, and it outputs Product with name, price and availability (Shero Commerce, May 2026). That’s enough for a basic price snippet.
What themes usually don’t output: aggregateRating (your review app has the data, but somebody has to pass it on), shippingDetails and hasMerchantReturnPolicy (the fields Google uses for the shipping and returns lines), brand and GTIN, BreadcrumbList, Organization, and anything on collections and blog posts.
Check before you add anything. Paste one product URL into Google’s Rich Results Test and note which items it detects and which fields are flagged as missing. Do the same for a collection, a blog post and your home page. That’s your baseline, and it stops you adding markup your theme already has.
How do I add rich snippets to Shopify?
Three ways. All of them end in the same JSON-LD in your pages; the difference is who maintains it.
1. Edit the theme yourself
The quickest manual route for products is Shopify’s own filter, in sections/main-product.liquid:
<script type="application/ld+json">
{{ product | structured_data }}
</script>For more control, write the JSON-LD by hand. A minimal merchant-listing block:
{%- assign variant = product.selected_or_first_available_variant -%}
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Product",
"name": {{ product.title | json }},
"image": {{ product.featured_image | image_url: width: 1200 | prepend: 'https:' | json }},
"description": {{ product.description | strip_html | json }},
"sku": {{ variant.sku | json }},
"brand": { "@type": "Brand", "name": {{ product.vendor | json }} },
"offers": {
"@type": "Offer",
"price": {{ variant.price | divided_by: 100.0 | json }},
"priceCurrency": {{ cart.currency.iso_code | json }},
"availability": "https://schema.org/{% if product.available %}InStock{% else %}OutOfStock{% endif %}",
"url": {{ request.origin | append: product.url | json }}
}
}
</script>Shipping and return details go inside offers as shippingDetails and hasMerchantReturnPolicy; Google’s merchant listing documentation has the exact shape. Ratings have to come from your review app’s data, which is where hand-written markup gets tedious.
It works, and you own it: every theme update, new review app or new page type means more Liquid to write and re-test.
Who it suits: one product template, a developer on hand, no review app or one that outputs its own markup. Cost: your time.
2. Hire a developer or agency
Worth it for complex catalogs, custom themes or headless stores. Ask for JSON-LD rather than microdata, markup on every template, merchant-listing fields including shipping and returns, and a plan for keeping it current when the theme changes.
Who it suits: bigger stores with a budget and a custom setup. Cost: a few hundred to a few thousand dollars, depending on the store.
3. Use an app
An app adds and maintains the markup without theme edits and reads ratings from your review app. Before you install one, check which schema types it covers, which review apps it supports, whether it handles shipping and return details, and whether it can switch off your theme’s own Product markup so the two don’t conflict.
Easy Rich Snippets for SEO is ours: 13 schema types including Product, Article, Recipe, Local and Shop, works with 15+ review apps including Judge.me, Loox, Stamped.io and Yotpo, no code. From $2.99/month with a 7-day free trial.

Two others worth a look, so you can compare: Ilana’s JSON-LD for SEO ($399/year, 4.9 from 440 reviews) is the long-standing specialist, with a flat price that suits large catalogs; Smart SEO AI & Image Optimizer (free plan, paid from $14.99/month, 5.0 from 960+) bundles schema into a full SEO suite with meta tags, ALT text and speed tools. For schema, ours is the cheapest of the three (Smart SEO’s JSON-LD starts on its Pro plan) and does schema only, which is the point of it.
Who it suits: most stores. Cost: from $2.99/month.
Step by step with Easy Rich Snippets for SEO
- Run your product page through the Rich Results Test and keep the tab open. You’ll compare against it in step 5.
- Install Easy Rich Snippets for SEO. The 7-day free trial starts on install.
- Turn on the schema types you need: Product first, then Breadcrumb, Article, Organization. Recipe and Local only if you have recipes or a physical shop.
- Fill in the shop details: name, logo, social profiles, return policy. Pick your review app from the list so ratings flow into the Product markup.
- Re-run the Rich Results Test on the same product page. You should now see Merchant listings and Product snippets as valid items, and no duplicate Product entries. If the theme’s own markup still shows, switch it off in the theme or the app.

How do I test structured data on Shopify?
- Rich Results Test: which rich results a page is eligible for, and the errors. Google’s view, so this one decides.
- Schema Markup Validator: checks all schema.org types, including the ones Google has no rich result for.
- Google Search Console → Enhancements: valid items and errors across the whole store, once Google has recrawled it. Expect days to weeks.
Test one page per template, not one product: product, collection, blog post, home page. Most errors live on the templates nobody looked at.
Mistakes to avoid
- Two Product blocks on one page. Theme and app both output Product data with different values. Keep one source per type.
- Markup that doesn’t match the page. Price, rating and stock in the JSON-LD must be what visitors see. Google can ignore the markup, or in bad cases apply a manual action.
- Incomplete offers. A Product without price, currency and availability is rarely eligible for anything.
- Ratings without real reviews. Only mark up ratings that come from customers and are visible on the page.
- Waiting for FAQ dropdowns. They won’t come back. Keep FAQ markup for AI and understanding, not for a rich result. More in Google ended FAQ rich results; building the page is in how to add an FAQ page to Shopify.
- Testing one product and stopping. Collections, articles and the home page have their own templates and their own errors.