Google Announces Two New Optional Structured Data Properties to Occupation Schema Markup

August 6, 2020 in Articles

Google Announces Two New Optional Structured Data Properties to Occupation Schema Markup

Google has recently updated its structured data development page to reflect new changes to two structured data types: Occupation and OccupationAggregrationByEmployer. 

Those who utilize these structured data now have the option to include “jobBenefits” and “industry” properties. 

According to Google, the Occupation structured data.

“…allows salary estimate providers to define salary ranges and region-based salary averages for job types, details about the occupation such as typical benefits, qualifications, and educational requirements.”

While the OccupationAggregrationByEmployer lets salary estimate providers…

“…aggregate occupations by factors such as experience levels or hiring organization.”

Here is a code snippet that Google provides as an example of the “jobBenefits” and “industry” properties:

“industry”: “Technology”,
“jobBenefits”: “6 weeks paid vacation every year”,
“yearsExperienceMin”: 3,
“yearsExperienceMax”: 7

Although these properties are optional, they can generate rich results within the SERP.

Do note that for information related to salary, Google recommends you add the JobPosting structured data instead of the Estimated salary if your website posts job listings with actual salary information 

Estimated salaries are eligible to appear in the job experience view on Google search and as a rich result on the search engine results pages for an occupation’s estimated salary.

An example of this would be the search query “salary of a teacher.” Try it yourself to see what the rich result looks like on the SERP.  

Here’s the view that Google offers of the estimated salary structured data:

Technical Guidelines for the Structured Data Types

If you find that these new structured data types can benefit you, there are a few guidelines Google shares so that the structured data are eligible for rich results. 

  1. Occupation is standalone data, so it does not need to be associated with other structured data types. 
  2. Add only one Occupation or OccupationAggregationByEmployer to an individual webpage. 
  3. Have the structured data information directly match the information presented on the webpage. If the salary differs by region, have a new webpage for each region with the respective information. 
  4. If there is a webpage that has a list of different occupations, this page should not include estimated salary structured data.  

These 2 new “jobBenefits” and “industry” optional properties will be very useful to publishers who wants to post this information within Google search experience.

Leave a Reply