Duplicate schema happens when more than one source — your theme, a review app, an SEO app, custom code, or InstaIndex itself outputs structured data for the same content on the same page. Search engines may pick one source, flag a conflict in Search Console, or ignore the markup entirely. AI assistants can get confused by contradictory values (different prices, different ratings, different product names).
How to find duplicate schema
Option 1: Use guided setup (recommended)
Open Schema markup → Set up and run through guided setup. Step 1 lists every schema source detected on your homepage, product page, latest article, latest collection, and latest page. If any type appears in more than one source, the banner calls it out as a duplicate, and the page cards show the source names (your theme, your review app, an SEO app, or "Unknown" if it can't be attributed). These are the sources you'll need to turn off.
Option 2: Run an external validator
Paste a storefront URL into one of these tools:
Look at the Detected items list. If the same @type appears more than once (two Product, two Organization, two FAQPage), you have a duplicate.
Common sources of duplicate schema
In rough order of frequency:
Your theme. Most modern Shopify themes (Dawn and its forks, premium themes, page builders) add baseline Product, Organization, WebSite, and Breadcrumb schema out of the box.
Review apps. Judge.me, Loox, Yotpo, Stamped, Okendo, Reviews.io, Junip, Opinew, and most others add their own Product + Review/AggregateRating schema by default.
SEO and schema apps. Apps explicitly marketed as "SEO" or "Schema" often inject Organization, Product, Article, FAQ, and Breadcrumb schema. They almost always conflict with InstaIndex.
Custom theme code. Snippets added by an agency, a developer, or a tutorial — often hand-written JSON-LD blocks in theme.liquid, product.liquid, or a custom snippet.
The fix: turn off other sources, keep InstaIndex as it generates clean and complete schema.
Easiest path: contact support
From the guided setup screen, click Contact support — the message includes the duplicate sources we detected. You can also open the chat from any page in the app.
DIY: turn off other apps' schema
Most review and SEO apps expose a setting to disable their structured-data output. Look in the app's settings for any of these labels:
Structured data
JSON-LD
Schema markup
SEO snippets
Microdata
Rich snippets
Product schema / Review schema / Organization schema
Toggle it off (or set to "Use my own schema"). Save, then re-run guided setup or a validator to confirm the duplicate is gone.
Example — Judge.me: Settings → SEO → toggle off Add SEO-friendly review snippets to product pages.
If you can't find the setting, check the app's help center or contact their support.
DIY: remove schema from custom theme code
Go to Online Store → Themes → Edit code.
Search for application/ld+json.
Comment out each <script type="application/ld+json"> ... </script> block instead of deleting it:
Windows/Linux: Ctrl + /
Mac: Cmd + /
4. Save your changes.
Wrap the block in Liquid comments so you can restore it later if needed. Save the theme file, view a storefront page, and re-validate.
A note on review apps and InstaIndex
When you select a review app on the Schema markup → Product page, InstaIndex reads its ratings widget on your storefront and merges the aggregate rating and review count into product schema. You keep the SEO and AI benefits of review data without needing the review app's own schema. Turn the review app's schema off and leave its on-page widget on.
After fixing duplicates
Re-run guided setup to confirm the duplicates are gone.
Submit your sitemap to Google Search Console so the new schema is recrawled. Changes take anywhere from a few days to a few weeks to reflect in Search Console reports.
Re-validate your homepage and a product URL in the Rich Results Test.
If duplicates persist after disabling every source you can find, contact support and we'll inspect the storefront to identify what's still injecting schema.