Data related to estimating salary, region-based average salary and specific job details like Qualifications, Benefits, Educational Requirements are all structured using the Occupation Schema.

PRO TIP: This schema is added in a way similar to the previous schemas mentioned in this Series.

WHAT ARE THE PROPERTIES RELATED TO THE OCCUPATION SCHEMA?

The various entities required to structure data using this schema are:

  • Occupation: The entity holds the said profession or occupation concerning whose data is structured using this schema. It holds the information of a said job.
  • EstimatedSalary: The estimated salary of the said occupation.
  • EstimatedSalary.duration: The entity holds the amount of time taken to earn the salary in ISO 8601 Format.
  • EstimatedSalary.name: The entity holds the type of value. Example: The entity is used when naming the salary like Base Salary, Bonus Salary, Commission, etc.
  • Name: the name of the said occupation. Free- form text can be used for this entity. For Example: “Media Buyer”.

The occupation name or title should be precise and readable. Other information like the salary, company names, dates must not be included. Special Characters like *, ! should not be included.

  • OccupationLocation: The location of the said occupation. The entity holds the name of the state, city or country wherein there is a job opening. The said location must state the exact location of the occupation, not the location where the salary listing is created.
  •  Description: The entity contains the job description like the job responsibilities, educational qualifications, working hours, etc. This description must be added to all the leaf pages which a user might land on and not just the top page The description should specify the job and not contain the job title only.
  • Estimatedsalary.currency: The entity contains the currency of the said salary. It is presented in the ISO 4217 3-Letter currency code.
  • EstimatedSalary.median: The median value of the salary.
  • EstimatedSalary.percentile10: The entity contains the 10th percentile value. It contains 10% of the salaries of the occupation.
  • EstimatedSalary.percentile25: The entity contains the 25th percentile value. It holds 25% of the salaries of the occupation.
  • EstimatedSalary.percentile75: The entity contains the 75th percentile value. It holds 75% of the salaries of the occupation.
  • EstimatedSalary.percentile90: The entity contains the 90th percentile value. It holds 90% of the salaries of the occupation.
  • mainEntityOfPage: The main entity which is being described on the page.
  • mainEntityOfPage.lastReviewed: The entity contains the date of the estimated salary information in ISO 8601 format.

 

OccupationAggregationByEmployer

The Structured data called the OccupationAggregationByEmployer allows all employers to group job data to make job search easy and fast. By using this structured data entity the employer can state the industry type and hiring organisation type for a group of jobs.

The following entities are required when structuring data using the said data structure.

  • EstimatedSalary: The estimated salary of the said occupation.
  • EstimatedSalary.duration: The entity holds the amount of time taken to earn the salary in ISO 8601 Format.
  • EstimatedSalary.name: The entity holds the type of value. Example: The entity is used when naming the salary like Base Salary, Bonus Salary, Commission, etc.
  • HiringOrganization: The organization hiring for the said occupation.
  • name: the name of the said occupation. The said entity can be written using the Free Form Text The occupation name or title should be precise and readable. Other information like the salary, company names, dates must not be included. Special Characters like *, ! should not be included.
  • OccupationLocation: The location of the said occupation. The entity holds the name of the state, city or country wherein there is a job opening. The said location must be specific; the occupation location is the exact location of the occupation, not the location where the salary listing is created.
  • Description: The entity contains the description of the job including job responsibilities, educational qualifications, working hours, etc. This description must be added to all the leaf pages which a user might land on and not just the top page The description should specify the job and not contain the job title only.
  • Estimatedsalary.currency: The entity contains the currency of the said salary. It is presented in the ISO 4217 3-Letter currency code.
  • EstimatedSalary.median: The median value of the salary.
  • EstimatedSalary.percentile10: The entity contains the 10th percentile value. It contains 10% of the salaries of the occupation.
  • EstimatedSalary.percentile25: The entity contains the 25th percentile value. It holds 25% of the salaries of the occupation.
  • EstimatedSalary.percentile75: The entity contains the 75th percentile value. It holds 75% of the salaries of the occupation.
  • EstimatedSalary.percentile90: The entity contains the 90th percentile value. It holds 90% of the salaries of the occupation.
  • Industry: The entity holds the name of the industry associated with the job position.
  • JobBenefits: The entity states the description of the job benefits of the said job.
  • mainEntityOfPage: The main entity which is being described on the page.
  • mainEntityOfPage.lastReviewed: The entity contains the date of the estimated salary information in ISO 8601 format.
  • SampleSize: This entity contains the total number of data points which contribute to the aggregated salary data.
  • YearsExperienceMax: The entity holds the maximum years of experience required for the said job position.
  • YearsExperienceMin: The entity holds the minimum experience required for the said job position.

Monitoring Search Results and Troubleshooting Problems:  Please refer to the previous posts of the Series to know in detail about monitoring search results and troubleshooting problems.

In The Next Post Of This Series, I will talk about how structured data is used for structuring the display of Home Activities Results on Google.

Nirlep & Dharmesh

0 Comments

You may also Like:
All About Structured Data: Review Snippet

All About Structured Data: Review Snippet

A Review Snippet is A short Section Of a much longer review or a review rating from a review website. A review is a critical appraisal of a book, movie or even a local business. Today, online reviews have a lot of power and can make or break movies, books or even...

New Open Source Robots.txt projects

New Open Source Robots.txt projects

Google created a milestone last year by making the robots.txt parser an open-source. Being a mere de- facto standard for nearly 25 years, the Robot Exclusion Protocol is now an actual internet standard and used officially by Google for crawling web pages. What does...

Google Tag Manager : To Track Visitor Interactions

Google Tag Manager : To Track Visitor Interactions

People who are in the field of digital marketing or online marketing know the advantages of Google Tag Manager. Those who are not familiar with this tool might wonder what it is. In fact, many online marketers find it easy to track code after its release at a time....