Resolve conflicting entity details
Find disagreements across plugins and templates while keeping intentional multiple values.
One identifier connects separate declarations
JSON-LD nodes using the same resolved @id describe the same entity. This can connect an Organization to a WebSite or combine details emitted by separate templates. Repeated declarations are not automatically duplicates or errors.
Compare the exact values and locations
CheckMySchema highlights differing scalar values for selected fields, including names, prices, currencies and identifiers. Each finding includes the values and their original normalized paths. These are possible conflicts, not a rule that every property must have one value. Arrays of legitimate alternatives are not flagged by this check.
Correct the source that produces the markup
If two templates disagree about the same fact, update the source template or plugin configuration. If they actually describe different entities, give them different identifiers. Do not solve a conflict by adding a third contradictory declaration. Recheck the page after publishing the change.
Go deeper with the official sources
W3C JSON-LD node identifiersThis is an original explanatory guide, not an official search-engine document. Requirements can change. Follow the linked sources for full, current details.