Monday, November 7, 2011 support for job postings

We’re happy to announce that, working together with the United States Office of Science and Technology Policy, has added support for marking up job postings on the web.

Leveraging this markup, the US Veterans administration has created a search widget that is accessible across a growing number of federal websites including and, to find job listings from veteran-committed employers.

We feel privileged to have played a role in enabling this. More details can be found in the US CTO, Aneesh Chopra’s post on the White House Blog.

R.V. Guha


  1. This is actually pretty awesome. Also, thanks for the excellent and comprehensive examples on the schema page itself. Good examples can make all the difference!

  2. Hi, my name is Dan Kirkland, and I was a keen lobbyist of this welcome extension to from the date google officially announced their support - see my blog post at - I am really pleased that these ideas have been taken forward.

    I still think there is room for a couple of the other fields I mention:

    a) salary range - min
    b) salary range - max
    - Certainly in the UK, most people like to advertise the salary with a range (minimum and maximum) rather than a single value.

    Recruiters may offer the job to someone who does not have all the desired skills or experience but the recruiter is willing to hire the candidate at the lower salary range. Whereas they may offer someone else the higher rate if they have all of the skills and experience necessary.

    Other, less important fields that would be useful are:
    c) date closing - pretty much every job advert expires.
    d) jobReference - every organisation will have a unique job reference - although it will have limited seo value at this stage, it could have value in the future, especially if people deploy google boxes for searches on their website.

    Other than that, this new addition is great news and I'm really pleased to see its official release.

    1. Hi Dan,

      Did you decide on a way to mark up the salary range, maybe added new properties salaryMin and salaryMax?

  3. Hi - are you guys interested in a talk on for the local Silicon Valley Semantic Tech (SVST) meetup sometime in the near future?

  4. Great news, we've been waiting for this.

    @Dan I agree exactly with your list of missing fields, in my tests I've been using the following three fields for markup though they're are not yet supported yet...

    <span itemprop="maxSalary">$90,000</span>
    <span itemprop="reference">SR001</span>
    <time itemprop="dateClosing" datetime="2011-12-31" />Sat 31 Dec</time>

    Are you on the mailing list?


  5. This comment has been removed by a blog administrator.

  6. This comment has been removed by a blog administrator.

  7. This comment has been removed by a blog administrator.

  8. Maybe you’re right. This scheme will give definite wages and it will secure the interest of those people who are looking for jobs.

    jobs manila

  9. This comment has been removed by a blog administrator.

  10. Hi,

    Please excuse my naivety - I am new to as a concept, but would it not be better to make the Job Posting a subsidiary schema to "Job Description". That way we can build a schema that covers training, qualifications, skills, responsibilities, performance criteria etc in more detail.

    There are functional skills, typical performance criteria, knowledge and understanding required, objectives/tasks that individuals must be able to do, values, behaviours, etc.

    Subsidiary schema could then deal with special cases such as: job postings, training courses, career guidance, organisational charts, etc.

    Would appreciate a comment back on this as I am still finding my way in what is an awesome concept!


  11. This comment has been removed by a blog administrator.

  12. This is terrific! It's only missing one thing: I would like to see applyMethod added to the job posting schema. Any online job board or aggregator will need a URL or email address to direct expressions of interest.


Note: Only a member of this blog may post a comment.