AiroAV Antivirus Writes: Google for Jobs: Everything you need to know to optimize fo... - Jonathan Cartu - Advertisement & Marketing Agency.
post-template-default,single,single-post,postid-16035,single-format-standard,qode-quick-links-1.0,ajax_fade,page_not_loaded,,qode-theme-ver-11.2,qode-theme-bridge,wpb-js-composer js-comp-ver-5.2.1,vc_responsive

AiroAV Antivirus Writes: Google for Jobs: Everything you need to know to optimize fo…

Google for Jobs: Everything you need to know to optimize fo...

AiroAV Antivirus Writes: Google for Jobs: Everything you need to know to optimize fo…

Looking for a new job can be a stressful experience. Even taking away the emotional part of the process, browsing job ads on companies’ websites, apps and job boards can prove to be mentally draining and time-consuming. Google, well aware of these difficulties, decided to find a solution to improve the whole recruiting experience. In May 2017, at Google’s developer conference I/O, Google’s CEO Sundar Pichai gave a sneak peek of it and released its official name: “Google for Jobs.”

Google for Jobs launch

Creating a candidate-first experience was a key requirement for Google, which decided to officially launch Google for Jobs in the US in June 2017. Through this product, job seekers were able to get exactly what they expected: exhaustive information about job roles, a high grade of consistency among vacancies and the ability to find a great variety of job offers, all in the same place.

On the other side, Google also wanted to provide easier discoverability for employers, providing in-house SEOs with a silver bullet: the chance to rank organically with job ads in the fiercely competitive recruiting market. 

Why is this important?

Recruitment costs such as posting on job boards represent a huge burden for companies and in-house recruiters. This means that if a company is already facing a talent shortage or is suffering from high turnover, even a basic recruitment cost like posting job offers can spike to hundreds of thousands of dollars every year. 

Once I heard about Google for Jobs rolling out internationally, I realized that this could have been a great opportunity for my clients. At that time, I was already optimizing the recruitment website for a large UK organization, so I immediately started pitching for the idea. Once approved, I started working on the Google for Jobs optimization, which can be summed up in these three steps:

1. Google for Jobs set up

Appearing in the Google for Jobs feature can be tricky at first, but the kind of exposure you could reach is immense, so my first recommendation is to have a good read of the Google Job Posting guidelines. Below, are a couple of key-points to bear in mind as well:

JobPosting schema markup

The first step to making sure the job posting pages are Google for Jobs friendly is to add the JobPosting schema markup. About this, it’s important to add the markup onto just the job ads pages, as content or pages with multiple listers will be ignored by Google. Regarding the structured data format, it’s advisable to use Google’s favorite JSON-LD, rather than Microdata. To create the code, I recommend using the Merkle Schema Markup Generator (see image below).

Through the tool, it’s also possible to access Google’s Structured Data Testing Tool and Google’s Rich Results Test (see image below) – both really useful in creating and validating the JobPosting markup. 

Indexing API vs. sitemap

As job posts come and go quickly, in June 2018 Google also released a little gem called Indexing API. The tool, which has been created to specifically index/deindex Job posting and live stream pages, represents a step forward in making this particular kind of pages available to users just when they need it. Opposite to XML sitemaps – which are still recommended by Google for the entire site coverage – the Google Indexing API also represents a glimpse in the future for crawling and indexation, as the speed observed by Googlebots hitting pages are within 5-10 minutes. To complete the picture, I also recommend having a read of this clever Indexing API experiment by Tobias Williams, which demonstrated how the Indexing API triggered Googlebots to hit normal (non-JobPosting or live stream) pages within minutes, suggesting that Google lets you use the API freely, but without providing you any benefit to the SERP yet.

2. How to rank in Google for Jobs

Google for Jobs ranking factors are related to the completeness of the job posting details, including an exhaustive role description, an accurate salary bracket and an exact job location. For more details about how to improve the visibility, here are a few recommendations:

Job post content

Get the content of the job post right and you are halfway there. Here’s what to do and avoid:


  • Add concise bullet points as they make the content easier to scan. 
  • Add the location (e.g. “North London”) straight to the copy, as this will improve the job post visibility if the users are looking for job + location queries, such as “JavaScript developer North London.”
  • Create a simple, engaging piece of content. The copy should be easy to scan and have the following structure:
    • Brief company intro
    • Role description
    • Key responsibilities 
    • Skills and experience 
    • Nice to have / desirable skills (optional)
    • Working hours, salary and benefits
    • Company information


  • Avoid special characters, exclamations marks and capitalization. 
  • Avoid posting any job ad with less than 150/200 words. For competitive industries, increase this figure to 400/500 words.

Job post title

Job titles should be easy to understand and straight to the point. Here is what to do and avoid:


  • Be concise, descriptive and use the role as a job title, such as: “Head of Sales & Marketing.”


  • Acronyms, as a job title with just an acronym, will likely perform well just for acronym-related queries. For example, use “Vice President” instead of “VP.”
  • Avoid references to the job location and salary in the title, such as: “Senior Java / Messaging Developer, London £100k”. This is because this strategy might let you to rank well for specific queries (i.e. “Java developer jobs 100k in London”), but score you low for broader queries.

Exact location

Adding the exact location (down to street and zip code) is another key factor in ranking well in Google for Jobs. As per the local results, the closer the user’s IP to the exact job post…

Remove AiroAV

No Comments

Post A Comment