If your product reviews aren’t showing star ratings in Google, your FAQs aren’t appearing as expandable rich results, or your collection pages aren’t showing breadcrumbs in search, the cause is almost always structured data, the schema.org markup that tells Google what your content actually is. And the frustrating part is that Shopify stores frequently have schema issues that aren’t obvious just by looking at the page.
A schema markup audit is a specific, technical piece of a broader technical SEO review. It doesn’t look at your content or your keyword targeting, it looks at the machine-readable code that sits underneath your pages and determines whether Google is eligible to show enhanced results for them at all. Get it wrong, and you can have excellent content and reviews that still never earn a star rating, an FAQ dropdown, or a breadcrumb trail in the search results.
This post walks through exactly what a proper Shopify schema audit checks, why Shopify stores run into schema problems more often than merchants expect, and how to check your own store before you decide whether you need a deeper technical review.
Why Schema Markup Matters for a Shopify Store Specifically
Schema markup (also called structured data, most commonly written in JSON-LD format) doesn’t directly boost your rankings. What it does is make your pages eligible for rich results, the star ratings, price and availability snippets, breadcrumb trails, and FAQ dropdowns you see in Google search results. These enhanced results tend to improve click-through rate meaningfully compared to a plain blue link, because they give searchers more information before they even click.
For ecommerce specifically, the schema types that matter most are:
- Product schema, price, availability, brand, SKU, and other structured product attributes.
- Review and AggregateRating schema, the star ratings shown next to product listings.
- BreadcrumbList schema, the category trail (Home > Category > Product) shown under a search result.
- Organization schema, your business’s name, logo, and social profiles, which feed into how Google understands your brand entity.
- FAQPage schema, the expandable question-and-answer dropdowns some searches display directly in results.
- LocalBusiness schema, relevant if you also operate a physical store or showroom alongside your Shopify site.
Shopify stores have a specific quirk that makes schema audits genuinely necessary rather than a box-ticking exercise: schema can come from more than one source on the same page, and those sources frequently conflict.
How Shopify Themes Handle Schema Natively
This is where a lot of confusion starts. Shopify’s handling of structured data isn’t consistent across the platform, it depends heavily on your theme.
Online Store 2.0 themes (the current generation, including Shopify’s free themes and most modern paid themes) generally include a reasonable baseline of schema markup out of the box, typically Product, BreadcrumbList, and Organization schema on the relevant templates. This is a genuine improvement over older theme architecture, but “included” doesn’t mean “complete” or “correctly configured” for your specific store.
Older, pre-Online Store 2.0 themes are far less consistent. Some include partial schema, some include none at all, and some include outdated schema formats that no longer match Google’s current structured data guidelines. If your store is running on an older theme, or a heavily customised version of one, there’s a reasonable chance your schema coverage has real gaps.
Apps add a second layer entirely. Review apps (for star ratings), FAQ apps, currency converters, and SEO apps frequently inject their own schema via JavaScript or Liquid snippets. This is often necessary, your theme’s native Product schema usually doesn’t include review data, because that lives in a separate app. But it also means most Shopify stores end up with schema sourced from at least two, sometimes three, different places on a single page: theme code, one or more apps, and occasionally manual additions from a previous developer.
Common Shopify-Specific Schema Errors
In our experience auditing Shopify stores, the same handful of issues come up repeatedly. None of them are visible just by looking at the page, you have to look at the actual markup.
Duplicate or conflicting schema
This is the single most common issue we see. A theme includes native Product schema, and a review app or SEO app adds its own Product or Review schema on top, without checking whether one already exists. The result is two (or more) schema blocks describing the same product on the same page, sometimes with conflicting data, different prices, different availability status, or duplicate review counts. Google’s own guidance is that duplicate or conflicting structured data on a page can cause it to disregard the markup entirely rather than picking the “correct” one.
Missing required Product fields
Google’s Product structured data requirements include specific required fields, most importantly a valid price, currency, and availability status. Product schema that’s missing these fields, or that has them formatted incorrectly (a price without a currency, or an availability value that doesn’t match Google’s accepted list), won’t qualify for rich results even if the rest of the markup is technically valid.
Review schema that doesn’t match what’s visible on the page
This is a genuine policy issue, not just a technical one. Google’s structured data guidelines require that review and rating markup reflect content that’s actually visible to users on the page. If your Review or AggregateRating schema shows a rating that isn’t backed by visible reviews on that page, for example, because a review app is pulling in a store-wide average rather than product-specific reviews, that’s a guideline violation that can result in Google ignoring the markup or, in more serious cases, a manual action against structured data on the site.
Invalid or malformed JSON-LD
Schema markup has to be syntactically valid JSON-LD to be read at all. A missing comma, an unescaped quotation mark inside a product title, or a broken nested object from a theme customisation is enough to make an entire schema block unreadable by Google, even though the visible page looks completely normal to a human visitor. These errors are common after theme edits or app installs that weren’t tested against the live markup.
Orphaned schema after an app uninstall
When a review app or FAQ app is removed, its schema injection doesn’t always get cleaned up properly. This can leave stale schema, sometimes referencing an app that’s no longer installed, competing with or duplicating markup from whatever replaced it.
How to Check Your Own Schema
Before commissioning a full audit, there are two free tools that will tell you a meaningful amount about where you stand.
Google’s Rich Results Test lets you enter a specific URL (or paste raw code) and see exactly what structured data Google detects on that page, along with any errors or warnings. Run this on a product page, a collection page, and a page with an FAQ section if you have one. It’s the fastest way to spot duplicate schema, missing required fields, or invalid JSON-LD on a page-by-page basis.
Google Search Console’s Enhancements reports (found under the Enhancements section for whichever structured data type is being tracked, Products, FAQs, Breadcrumbs, and so on) show aggregated data across your whole site: how many pages have valid markup, how many have errors, and how many have warnings. This is where you’ll catch a site-wide pattern, for example, if every product page is failing on the same missing field, that points to a theme or app-level fix rather than a one-off issue.
A simple checklist for a first-pass self-check:
- Run Google’s Rich Results Test on one product page, one collection page, and your homepage.
- Check whether Product schema includes price, currency, and availability, and whether the values match what’s actually shown on the page.
- If you run a review app, confirm the ratings in your schema match ratings actually visible on that specific page, not a store-wide average.
- Check Search Console’s Enhancements reports for Products and, if applicable, FAQs and Breadcrumbs, looking for a pattern of errors across many URLs rather than an isolated case.
- Search your theme code (or ask your developer to) for more than one
application/ld+jsonscript tag of the same schema type on a single template, a strong sign of duplication between theme and app.
If any of these turn up errors, warnings, or duplication, that’s the point where a proper technical audit becomes worth the time, self-checking tells you something is wrong, but not always why, or which of several possible sources is actually the cause.
What a Proper Technical Schema Audit Actually Walks Through
A schema-specific audit, done properly as part of a broader technical SEO review, typically covers:
- A full crawl of key page templates (homepage, collection, product, blog, FAQ if applicable) to catalogue every schema type present and its source, theme, app, or manual addition.
- Validation of every schema block against current schema.org and Google structured data requirements, not just checking that it exists.
- A duplication and conflict check across theme and app-injected schema on the same templates.
- A visible-content match check for Review and AggregateRating schema, confirming the markup reflects what a user actually sees on that page.
- A Search Console Enhancements review to identify site-wide patterns rather than isolated URL issues.
- Root-cause identification, establishing whether an issue originates in the theme, a specific app, or a manual customisation, since the fix differs significantly depending on the source.
- A prioritised fix list, because not every schema issue carries equal weight, a missing price field blocking all product rich results is a different priority to a minor Organization schema warning.
This is exactly the kind of detail-level review a Shopify SEO audit is built to catch, it’s easy for schema issues to sit invisibly on a store for months, quietly blocking rich results, because nothing about them is visible on the page itself. If you’ve already noticed your reviews or FAQs aren’t showing up as rich results in Google, that’s usually a strong enough signal that it’s worth having the underlying markup properly checked rather than guessing at a fix. Our technical SEO service covers this kind of structured data review as part of a broader technical health check.
FAQ
Why aren’t my Shopify product reviews showing star ratings in Google?
The most common causes are review schema that’s missing, invalid, duplicated by a conflicting app, or that doesn’t match reviews actually visible on that specific page. Running the URL through Google’s Rich Results Test will usually show you which of these is happening, though identifying the exact source often needs a deeper look at the theme and app code.
Does installing a review app automatically fix my schema?
Not necessarily. Review apps generally add their own Review and AggregateRating schema, but if your theme already includes Product schema with review fields, you can end up with duplicate or conflicting markup rather than a clean fix. It’s worth checking after installation, not just assuming it’s handled.
Do Online Store 2.0 themes have all the schema I need already?
Online Store 2.0 themes typically include a reasonable baseline, usually Product, BreadcrumbList, and Organization schema, but this is rarely complete for every schema type you might want, such as reviews or FAQs, and it doesn’t guarantee the markup is error-free for your specific store setup.
How long does a schema markup audit take?
For a typical Shopify store, a focused schema audit as part of a technical SEO review generally takes from a few days to around two weeks, depending on the number of templates, apps involved, and how many issues turn up that need root-cause investigation before a fix list can be finalised.
Can bad schema actually hurt my SEO, or does it just miss out on rich results?
In most cases, invalid or missing schema simply means you miss out on rich results rather than being actively penalised. However, review schema that doesn’t match visible on-page content is a genuine guideline violation, and in more serious or repeated cases this can lead to Google taking manual action against structured data on the site, not just ignoring it.
Get Your Store’s Schema Properly Checked
If your rich results aren’t showing up the way they should, guessing at the fix usually wastes more time than it saves. A Shopify audit reviews your structured data alongside the rest of your technical SEO setup, so you get a clear, prioritised list of what’s actually broken and why.
