Schema Diff Checker

Four practical comparison examples

1. Product price update: Compare a Product with offers.price of 1299.00 against the same Product with 1199.00. The report should show a changed value at the nested price path. Verify the visible storefront price before using the new markup.
2. New Article author: Compare an Article without author to one containing a Person with name. This is an added property, not proof that the author is genuine or that the article meets Google's policies.
3. Removed availability: Compare two Offer objects where availability is present only in the first. Review whether the removed field reflects a deliberate content change.
4. Reordered FAQ entries: Reordering an array can produce differences even when its questions are unchanged. Array position is significant to this structural comparison; interpret it separately from semantic meaning.

Common mistakes and fixes

Do not paste JavaScript object literals with single quotes or trailing commas; both sides must be valid JSON. Keep the same entity and comparable scope on both sides, otherwise a long diff may simply mean you compared unrelated pages. A changed @id can alter entity identity, so review it carefully. This is a structural JSON comparison, not a semantic JSON-LD equivalence engine, crawler or automatic schema repair tool.

Review workflow: Save the before version, paste the proposed after version, inspect the paths and export the report. Then validate the final JSON-LD and the live page separately using the Schema Markup Validator.