Markup drift happens when page content changes but its JSON-LD does not. A product price, availability, rating, title, or event time can become inaccurate while the page still appears normal. Treat visible content as the source of truth; structured data should describe it, not add a separate version.
Use a change checklist before publishing:
• Map each field to the exact on-page element.
• Remove properties when the corresponding content disappears.
• Keep Product, Review, FAQ, and Event entities tied to the correct page.
• Verify that currency, dates, ratings, and availability use the same values everywhere.
Add a lightweight QA loop to the deployment process. Validate representative templates, not just one URL: product variants, out-of-stock pages, pages without reviews, and recurring event states. Test both the rendered HTML and the final JSON-LD after scripts run. Store validation results with the release so regressions are easy to trace.
Assign ownership for markup. Content, development, and SEO teams should know who approves schema changes and who checks failures. Never leave old markup in place “temporarily”; stale data can be worse than no markup.
Keep structured data generated from shared fields or CMS data where possible, then retest whenever a template or content model changes.
Rich Result Rx
@RichResultRx
The markup drift that breaks rich results—and a workflow that prevents it
This post was published in the Telegram channel Rich Result Rx. Subscribe here: @RichResultRx.