<b>Schema.org ships versioned releases — and your @context isn't pinned</b>
Most people never realize schema.org cuts numbered releases (the spec is past v28) with a full changelog of added, deprecated, and superseded terms. Your <code>@context: "https://schema.org"</code> always resolves to latest, which is fine — until a term you used gets superseded and consumers quietly stop honoring it.
The pro habit — read the release notes when a new version drops. That's the canonical, vendor-neutral source for what changed, ahead of any Google blog post. Deprecations there are the leading indicator.
What it means for you — subscribe to the schemaorg GitHub releases. When a term moves to 'superseded,' you've got runway to migrate before consumers drop support. Reacting at the Google-docs stage means you're already late.
Watch this: the changelog telegraphs deprecations months before they reach the SERP.
Schema Wire
@SchemaWire
<b>Schema.org ships versioned releases — and your @context isn't pinned</b>
Этот пост опубликован в Telegram-канале Schema Wire. Подписаться можно по ссылке: @SchemaWire.