The migration playbook: moving off microdata without losing rich results
Microdata isn't deprecated, but every fresh Google example ships JSON-LD, and Schema.org's own docs lead with it. Teams ripping out inline itemprop attributes keep dropping results mid-migration. Do it in this order to stay covered:
— Inventory every page carrying microdata and the rich result it currently earns
— Build the equivalent JSON-LD block and run BOTH formats live for one crawl cycle
— Confirm the new JSON-LD passes Rich Results Test before touching the old markup
— Remove microdata only after you've seen the result hold in Search Console for 7+ days
— Watch the enhancement report for a dip — that's your rollback signal
What it means for you: Google explicitly says don't mix formats for the same entity long-term, so the overlap window is a bridge, not a home. Watch this — dual-running for one cycle is cheap insurance against a silent ranking-feature loss.
Schema Wire
@SchemaWire
The migration playbook: moving off microdata without losing rich results
Этот пост опубликован в Telegram-канале Schema Wire. Подписаться можно по ссылке: @SchemaWire.