Shopify Apps Creating Duplicate Conflicting Product Schema Blocks

View Source and copy all <script type="application/ld+json"> blocks. For each, identify the source: theme file, app ScriptTag, or app snippet. Check your theme code for all {% render %} calls in product templates that might output schema.

For each app generating a duplicate Product schema block: check the app's settings for a "Disable schema" or "Schema output" toggle. Many SEO apps and review apps have a setting to disable their own schema injection when you prefer to manage schema manually. Enable this setting.

For apps that inject schema via theme snippets (visible as {% render 'app-schema-snippet' %} in your product template), wrap or replace the render call to prevent schema output while preserving any other functionality the snippet provides.

{%- comment -%}
Disabled duplicate schema from [App Name] - schema managed in main-product.liquid
{% render 'app-name-product-schema' %}
{%- endcomment -%}

In your theme's Product schema block, incorporate all the data previously provided by app schema blocks - aggregateRating from your review app metafields, enhanced offer fields, etc. This single block becomes the authoritative schema for all product pages.

{%- comment -%} Single authoritative Product schema block in sections/main-product.liquid {%- endcomment -%}
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": {{ product.title | json }},
  "description": {{ product.description | strip_html | truncate: 500 | json }},
  "image": {{ product.featured_image | image_url: width: 1200 | prepend: 'https:' | json }},
  "sku": {{ product.selected_or_first_available_variant.sku | json }},
  "brand": {
    "@type": "Brand",
    "name": {{ product.vendor | json }}
  },
  "offers": {
    "@type": "Offer",
    "price": {{ product.selected_or_first_available_variant.price | divided_by: 100.0 | json }},
    "priceCurrency": {{ shop.currency | json }},
    "availability": "https://schema.org/{% if product.available %}InStock{% else %}OutOfStock{% endif %}"
  }
  {%- if product.metafields.judgeme.badge -%}
  ,"aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": {{ product.metafields.judgeme.average | json }},
    "reviewCount": {{ product.metafields.judgeme.count | json }}
  }
  {%- endif -%}
}
</script>

After disabling duplicate schema and consolidating into one block, paste the product URL into search.google.com/test/rich-results. Confirm only one Product entity appears and no "Multiple values" warnings are present.

Q: How do I know which app is injecting the duplicate schema?

View Source on a product page, copy all JSON-LD blocks, and compare their structure. Review app schema typically includes aggregateRating. SEO app schema often has more complete Offer fields. Theme schema is found in your Liquid files. Check each app's settings for a "disable schema" option and test one at a time to identify the source.

Q: Can Google merge multiple Product schema blocks intelligently?

No. Google does not merge or reconcile conflicting schema blocks. When it encounters two Product entities on the same URL with different values for single-valued properties (price, availability), it treats this as an error and typically discards the schema rather than choosing one over the other.

Q: What if I need data from an app in my schema (like review ratings)?

Disable the app's schema output, then manually add the app's data to your theme schema block using the app's Liquid metafields. For example, disable Judge.me's schema injection but add {{ product.metafields.judgeme.average }} to your theme's Product schema block. This gives you the best of both - app data, single schema block.

Q: Will disabling an app's schema affect the app's functionality?

No. Schema output is separate from the app's operational functionality. Disabling Judge.me's schema output does not affect review display, email triggers, or any other Judge.me feature. The schema toggle only controls whether the app injects a JSON-LD block - not whether the app works.

Q: Should I use a dedicated SEO app to manage all my schema?

Only if the app generates a single, complete schema block and actively prevents other apps from adding conflicting schema. Most SEO apps add another schema block rather than replacing existing ones, which worsens the problem. Managing schema directly in your theme gives you full control and is the most reliable approach for preventing conflicts.