JobPosting vs Occupation: the careers markup that quietly expired
Career sites confuse two types and one of them now demands a paid integration. JobPosting marks a specific open role; Occupation describes a profession generically. Critical update: as of 2024, JobPosting rich results require Google's Indexing API and a verified integration — static JobPosting markup alone no longer surfaces in the jobs experience.
— Specific open role you want in Google Jobs: JobPosting plus the required Indexing API workflow, not just markup
— Generic profession/salary-guide page: Occupation, which still works as standard structured data
— Expired roles: you must remove or update via the API, or risk policy issues
What it means for you: if you added JobPosting markup and saw nothing in the jobs widget, it's not broken — Google changed the access model to API-gated. Occupation for guide content still earns normal treatment. Watch this: the API-gating of JobPosting is the template for how Google may restrict other high-value rich results — markup-only access is shrinking.
Schema Wire
@SchemaWire
JobPosting vs Occupation: the careers markup that quietly expired
Этот пост опубликован в Telegram-канале Schema Wire. Подписаться можно по ссылке: @SchemaWire.