When two different sources on your site — a plugin and your theme, two plugins, or manually added code and a plugin — each output structured data for the same page, search engines and AI crawlers can receive contradictory or duplicated information about the same content, which often means neither version is trusted fully. This fixes which source wins; it doesn’t decide what your schema should claim beyond what’s already true and present on the page.
Check your raw page source for more than one schema block
View your page source (right-click, View Page Source) and search for “application/ld+json”. If more than one script block appears, or the same schema type (like Product or Article) shows up twice with different values, that confirms a genuine conflict rather than a single, clean source.
Duplicate schema conflict resolution
Two sources outputting schema for the same page, resolved to one correct one.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
This or something else?
| More than one source is outputting structured data for the same page | This fix covers it |
| A single schema source is producing invalid or malformed output | Schema validation error fixes, a different kind of problem |
| A page builder is specifically breaking otherwise-correct JSON-LD | JSON-LD broken by page builder – repair |
| Your SEO plugin and theme are the two specific sources in conflict | SEO plugin vs theme schema conflict, the more targeted version of this |
What you are seeing
- The same schema type appearing more than once in a page’s source
- Different, conflicting values for the same field across two schema blocks
- Google’s Rich Results Test flagging a duplicate or conflicting property
- The conflict possibly only affecting certain page types, not the whole site
Common causes
- An SEO plugin and a theme or page builder each independently generating schema for the same content
- Two plugins both adding structured data for overlapping purposes (reviews, products, articles)
- Manually added JSON-LD left in place after installing a plugin that now generates the same schema automatically
- A migration or theme change introducing a second schema source without removing the original
- Demo content or a starter template imported during setup, bringing example schema that was never cleaned up alongside a separately configured plugin
What we do
- Identify every source currently generating schema for the affected pages
- Determine which source has the more complete or accurate data
- Disable or suppress the redundant source, keeping the single, correct one active
- Verify the resulting page outputs exactly one, valid schema block per type
- Test against Google’s Rich Results Test to confirm no conflict remains
- Check other page types on the site for the same duplication pattern
What is included
- The duplicate or conflicting schema source identified and resolved
- A single, correct schema output verified per page
- A site-wide check for the same pattern on other page types
- The pre-fix backup, kept for 30 days
Not included
- Deciding which schema types your business should use in the first place — that’s a scope question we discuss with you, not a strategic recommendation we make unprompted
- Writing new schema types not already present on the site
- Fixing validation errors unrelated to duplication
- Ongoing monitoring as new plugins are added later
Questions about this fix
How would two schema sources both exist without me installing anything new?
Often a theme or page builder includes its own schema output by default, and a plugin you added later also generates the same type — neither one was necessarily wrong at the time it was set up, they just weren't checked against each other.
Does having duplicate schema actually hurt my rankings?
It can lead to search engines and AI crawlers being less confident about which version to trust, which works against the point of adding structured data in the first place, even if it doesn't carry an explicit penalty.
Will you tell me what new schema types I should add to improve visibility?
No — that's a strategic decision about what to prioritise, which is outside what this fix does; we resolve the conflict between sources already present, using the information already on your pages.
How do I know which of the two duplicate sources is more accurate?
We compare both against what's actually true and current on the page itself, keeping the one that reflects reality most completely rather than an arbitrary choice.
Could this happen again if I install a new SEO or schema plugin later?
Yes, that's a real risk any time a new plugin overlaps with an existing schema source — worth checking specifically after adding any new plugin that mentions structured data or rich snippets.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.