If you use an applicant tracking system to generate your job descriptions, chances are that you’re leaving a bunch of Google and other search traffic on the table because you’re neglecting to adhere to Schema.org.

One client of ours saw an increase in Google traffic of 45% in the very first month they began adhering to Schema.org.

Schema.org Job Description Traffic SEO

What is Schema.org?

Schema.org sounds like a weird “black-hat” type of movement, but it’s actually very legit and backed by Google, Microsoft, Yahoo and Yandex (the largest Russian search engine).

Schema.org launched in 2011 to try to get Web sites to send more structured data so that they can deliver a better experience for the user (the candidate in your case).

Note: Schema.org is one of many elements of SEO (search engine optimization) and if you want free tips on SEO for job descriptions check our Ongig SEO pageFor details of how to code your job description pages, check out Schema.org Job Descriptions.

Here’s the gist of Schema.org:

There are a number of data points in your job descriptions that Google et al consider “structured data”. They include simple things like:

  • Name of your company
  • Title of job
  • Location of job
  • Apply link
  • etc.

These are things you would find in nearly all job descriptions and Google et al want you to signal to them that you have these fields in your job descriptions.

For example, below is a Duke Energy job description below and 7 examples of data points that they should be telling Google and the other search engines about.

Schema.org for job descriptions examples of properties SEO

You Need to Tell Google that Your Job Description is Official

But when you look at the HTML of the Duke job description, as you can see below, there are no mentions of Schema.org meaning that Google will not consider this an official job description. They’ll still send some traffic to it but not as much as if Duke adhered to Schema.org in the various fields of data.

Schema.org for job descriptions example of no microdata SEO

Here are Examples of Schema.org Data Ongig Communicates to Google for Our Clients’ Job Ads

On the flip side here is the HTML of a job description by Yelp in which there are 11 Schema.org data points in the HTML that Ongig has generated for Google’s behalf:

Job description optimized for Schema.org SEO by Ongig for client Yelp

All other things equal, when a candidate searches for job opportunities then Google, Microsoft, Yahoo, Yandex and other search engines will more likely serve up the ones that adhere to Schema.org.

Get Even More Google Traffic Through Schema.org 2.0

And if you want to get even more Google Traffic to your job descriptions via Schema.org, there are a number of other fields of data that you can tell Google et al about, including the following if you have them on your job pages:

  • Social Shares
  • Join Talent Community
  • Image Object
  • Video Object

How to Get Your Job Descriptions to Adhere to Schema,org

There are a few main options to get your job descriptions to adhere to Schema.org:

  1. Ask Your Applicant Tracking System — You can ask your ATS to do it (some do it already but most don’t).
  2. Ask Your IT/Tech Team — Your internal tech team can take care of this for you.
  3. Ask an Agency — If you’ve got a digitally-savvy agency you work with then they should be able to handle this.
  4. Use Recruitment Marketing Software — You can use recruitment marketing software like DirectEmployers, PhenomPeople and Ongig to do this.

*For more SEO recruiting tips, check out this comprehensive list of free best practices on recruitment SEO.


About the Author — Rob is the Co-founder & CEO of Ongig which attracts the best talent faster through next-generation job descriptions (including through Schema.org and SEO!). Yelp, Autodesk, Verizon Digital, GoDaddy, Auction.com and BMC Software are among the early clients of the Ongig SaaS.

by in Recruitment SEO