> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.adnabu.com/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Do other schema apps interfere with Nabu Schema Pro? Should a store have only one schema app?

### Yes, running more than one schema app on the same store almost always causes problems.

We strongly recommend keeping **only one schema source** active at a time, and Nabu Schema Pro is designed to be that single source.
This article explains why duplicate schema is a problem, how to spot it on your store, and what to do if you find a conflict.

## Why multiple schema apps cause problems

Schema markup (also called structured data or JSON-LD) is the hidden code that tells Google what your page is about — the product, price, availability, brand, reviews, breadcrumbs, article author, and so on.
When two apps add schema to the same page, you end up with **two competing blocks of structured data** describing the same thing. This creates three real issues:
1. **Conflicting values.** App A might say a product is "In Stock" while App B says "Out of Stock." Google sees both and has to pick one — or it ignores both.
2. **Duplicate entities.** Two `Product` or `BreadcrumbList` blocks on the same URL look like an attempt to game search results. Google's documentation explicitly warns against duplicate structured data.
3. **Validation errors in Google Search Console.** You'll start seeing "Duplicate field," "Conflicting values," or "Invalid object" warnings — and rich snippets may stop showing entirely.
The result: instead of helping your rankings, the schema markup actively works against them.