When I first started helping Shopify merchants recover their rich results, I was surprised how often the culprit was a tiny schema error — something a theme update or an app had quietly introduced. Rich results can lift click-through rates and visibility, so when they disappear it’s urgent to act. In this article I’ll walk you through how I audit product schema on Shopify, the frequent issues I find, and the practical fixes that actually restore rich snippets in Google Search.
Why product schema matters (and what breaks it)
Product schema (typically JSON-LD for Shopify stores) provides search engines with structured information about your products: price, availability, SKU, ratings, images, and more. When properly implemented, product schema enables rich results such as price ribbons, review stars, availability and product knowledge panels.
What commonly breaks schema on Shopify?
Step-by-step audit process I use
I follow a structured audit so nothing gets missed. You can run most of these checks yourself with free tools and a bit of detective work.
I start in Google Search Console (GSC). Under “Enhancements” look for Product reports and any warnings or errors. If you don’t see a Product report, run Google’s Rich Results Test on a product URL to confirm what Google sees.
Use GSC’s URL Inspection “View crawled page” and “Test live URL.” This helps me see whether structured data is present in the HTML Google fetched. If the schema is missing in the crawled version but present in the browser, it’s likely rendered client-side with JS and not available to Google.
I use two tools: Google’s Rich Results Test and the Schema.org Validator (or the community Structured Data Testing Tool if you prefer). Paste the exact product URL and check for errors and warnings. Note down every missing required property and any type mismatches.
If you have many products, I run Screaming Frog or Sitebulb (with JS rendering enabled if necessary) to extract structured data across pages. That reveals patterns — e.g., all variants missing priceCurrency, or duplicate Product objects.
Open Shopify’s theme editor (Online Store > Themes > Actions > Edit code). Key files to check: product.liquid (or sections/product-template.liquid), snippets that include product schema, and any app-injected snippets. I search the codebase for "application/ld+json" to find where JSON-LD is generated.
Common errors and how I fix them
Below is a quick reference table I use when diagnosing issues. It pairs the error with the likely cause and my usual fix.
| Error | Likely cause | Fix |
|---|---|---|
| Missing price or priceCurrency | Offer object not populated or JS renders price | Edit theme to output price in JSON-LD server-side; ensure currency formatting (e.g., "priceCurrency": "USD") |
| Duplicate Product objects | Theme + app both inject schema | Remove one source — prefer single canonical schema (usually theme) |
| Invalid values (e.g., “-” as price) | Empty variant or price zero handling | Set fallback logic in schema to omit or properly format values |
| Schema only visible after JS | App/theme renders JSON-LD client-side | Render JSON-LD server-side or ensure pre-rendering; avoid relying on async JS |
| Missing image or image not crawlable | Images blocked by robots.txt or 404s | Ensure image URLs are absolute, accessible and included in JSON-LD |
Typical code fixes I apply on Shopify
Here are practical implementation tips. I prefer keeping JSON-LD in the theme so it’s rendered server-side, reducing the risk Google won’t see it.
Shopify Liquid gives you product attributes directly. Example fragments I add to a product template:
// Pseudo example: ensure you adapt to your theme structure
<script type="application/ld+json">{"@context":"https://schema.org/","@type":"Product","name":"{{ product.title | escape }}","image":["{{ product.featured_image | img_url: 'master' }}"],"sku":"{{ product.variants.first.sku }}","offers":{"@type":"Offer","price":"{{ product.price | money_without_currency | replace: ',', '.' }}","priceCurrency":"{{ shop.currency }}","availability":"https://schema.org/{% if product.available %}InStock{% else %}OutOfStock{% endif %}","url":"{{ shop.url }}{{ product.url }}"} }</script>
Notes: use liquid filters to output raw values; avoid localized currency symbols in the price field; ensure arrays for images when multiple images exist.
If an app adds JSON-LD and your theme does too, pick one source. I usually keep schema in the theme for full control and disable the app’s structured data option, or remove the theme snippet if using a trusted app that handles everything well (e.g., product review apps that include review markup).
Variants can break price reporting. I include the active variant price where possible, or include an offers array containing each variant's offer if necessary for complex catalogs. Make sure SKU/GTIN are set where available.
AggregateRating must reflect actual reviews. If you display review stars via an app like Yotpo or Judge.me, ensure the schema comes from the same source and isn’t duplicated by your theme.
Monitoring and validation after fixes
Once changes are live, I re-run the Rich Results Test on multiple product URLs. Then I request indexing in GSC for a handful of fixed pages to speed up reprocessing. In GSC product reports, errors will clear over time; updates in search results can take days to weeks depending on crawl frequency.
I also set up periodic checks: a monthly crawl with Screaming Frog to ensure schema consistency and a small dashboard (Sheet or Data Studio) tracking the number of products with valid Product schema. For larger catalogs, I automate extraction of JSON-LD with APIs or headless crawlers to surface anomalies quickly.
Final practical tips I always follow
If you want, I can review a product URL from your store and point out the exact schema errors and the line in your theme where they come from. Fixing schema can feel technical, but with a consistent audit approach you can restore rich results and recapture the visibility they bring.
