Google for Jobs integration

Google shows job postings in a dedicated search experience, including in the Netherlands. For that, every job page needs JobPosting structured data. Appfront builds that integration for employers and recruitment sites: the job postings come from your ATS or job feed, the markup is correct automatically, and Google is quickly notified when a job is new or expires.

What Google requires

According to Google Search Central's JobPosting documentation, these properties are required:

  • title: the job title, without company name, location or salary in it;
  • description: the full job description in HTML;
  • datePosted: the date the job was posted;
  • hiringOrganization: the employer;
  • jobLocation: the work location, or for fully remote roles jobLocationType TELECOMMUTE with applicantLocationRequirements.

Recommended fields include validThrough (the end date), employmentType, baseSalary, identifier and directApply. The data must match the visible job text.

What we build

  1. Connect the source: jobs from your ATS, HR system or XML feed, via the API or feed your software provides.
  2. Generate the markup: JobPosting in JSON-LD on every job page, mapped field by field to the source.
  3. Indexing API: when a job is new, changed or expired, Google is notified. For job URLs, Google recommends the Indexing API over sitemaps, because Googlebot then visits the page sooner.
  4. Expired jobs: Google requires closed jobs to disappear, either through a validThrough in the past, a 404 or 410, or by removing the markup. Cleaning up too late can result in a manual action. We automate this.
  5. Checks: testing with the Rich Results Test and monitoring in the Search Console jobs report.

Who it's for

For employers with their own careers site, for recruitment and secondment agencies, and for job sites that publish many jobs at once. If you use an ATS, this fits in with our ATS integrations and recruitment software.

You can read more about structured data in general at implementing structured data.

Your jobs in Google for Jobs?

Tell us what's going on: which site, which platform and what is going wrong or could be better. We'll take a look and tell you honestly whether the work suits us, or is better suited to an SEO agency.

Get in touch

Frequently asked questions

Yes. The Netherlands is on the list of countries where Google's job search experience is available, according to Google Search Central's JobPosting documentation.

title, description, datePosted, hiringOrganization and jobLocation. For fully remote roles, use jobLocationType TELECOMMUTE with applicantLocationRequirements. validThrough, employmentType and baseSalary are recommended.

For job URLs, Google recommends the Indexing API over sitemaps, because Googlebot then visits new and removed jobs sooner. The Indexing API is officially intended only for JobPosting and BroadcastEvent.

They need to disappear from Google: with a validThrough date in the past, a 404 or 410, or by removing the markup, preferably with a notification via the Indexing API. We automate this from your ATS.

Want to start a project?

We'd love to hear from you.

Long story, or would you otherwise have emailed it? Choose Detailed briefing: headings and bullet lists, images in the text and attached files.

Mies

Contact Mies

Business Developer

Contact Martijn

Founder of Appfront

Martijn

Your message has been sent

Thanks for your interest! We'll get back to you as soon as possible, usually within 1 working day.

Let's get started

Together, we create smart digital solutions for your organisation's challenges. No rushed, short-lived products, but well-considered, high-quality solutions built on a foundation of UX Design and technological expertise. So your organisation is ready for tomorrow.

Edit content