Google for Jobs: how to get in (2026)
Google for Jobs is the job listing block in Google Search that aggregates job postings from websites. It is free and has been operational in the Netherlands for years. Your job listing will appear if the job page contains structured data of the type JobPosting. In this article, you will learn how it works, which fields are mandatory, and which mistakes can cost you visibility.

Google for Jobs explained
What is Google for Jobs?
Google for Jobs is the job search feature in Google Search: when someone searches for work, Google shows a separate block of vacancies that it collects from employer websites, ATSs and job boards. You don’t post anything there yourself. Google reads your vacancy pages and includes them if they contain the right structured data.
If you search for “nurse jobs utrecht”, for example, you’ll see a block above or between the regular results with job titles, employers and locations. When a job seeker clicks through, they land on the vacancy page, or on an overview where they can filter by location, employment type and date.
Many articles about Google for Jobs still discuss when it will come to the Netherlands. That question has been answered: the Netherlands is on the official list of countries where the job search feature is available. So the question in 2026 is not whether you can be included, but whether your vacancy pages are built well enough.
What does Google for Jobs cost?
Inclusion in Google for Jobs is free. You pay Google nothing per vacancy or per click. On jobs.google.com/about, Google describes two routes: adding the data to your own website yourself, or posting vacancies through a party that already supplies Google. Google mentions no paid route or registration. According to the documentation, you also don’t need to register with Search Console to appear in the results, although we do recommend it so you can see errors.
The costs lie elsewhere:
- Technology. Someone has to add the structured data to every vacancy page and keep it up to date. That’s work for a developer, or it’s built into your website or ATS.
- Maintenance. A vacancy that has been filled has to be removed from Google. If that happens manually, it takes time every week.
- Via a job board. If you pay to post on a job board that supplies Google, your vacancy can also reach the block that way. You then pay for that job board, and the click goes to them instead of to you.
How does Google for Jobs work?
Google crawls your vacancy page, reads the JobPosting data in the source code and shows the vacancy in the job block if that data is correct and meets the guidelines. You add this data to the page as JSON-LD: a snippet of code that visitors don’t see, but that tells Google exactly what the job title, employer, location and salary are.
A heavily shortened example:
json
{
"@context": "https://schema.org/",
"@type": "JobPosting",
"title": "Nurse",
"description": "<p>As a nurse on our ward ...</p>",
"datePosted": "2026-11-03",
"hiringOrganization": {
"@type": "Organization",
"name": "ExampleCare",
"sameAs": "https://www.examplecare.nl"
},
"jobLocation": {
"@type": "Place",
"address": {
"@type": "PostalAddress",
"addressLocality": "Utrecht",
"addressCountry": "NL"
}
},
"employmentType": "PART_TIME",
"baseSalary": {
"@type": "MonetaryAmount",
"currency": "EUR",
"value": {
"@type": "QuantitativeValue",
"minValue": 3200,
"maxValue": 4100,
"unitText": "MONTH"
}
}
}
Google decides where your vacancy appears in the block. You can’t pay for a higher position. What you do control: complete, correct data and a page that Google can read without problems.
Which JobPosting fields are required and which are recommended?
Five fields are required: title, description, datePosted, hiringOrganization and jobLocation. For a fully remote role, you can omit jobLocation if you fill in applicantLocationRequirements. The rest are recommended. If a recommended field is missing, your vacancy is still eligible, but it lacks information job seekers filter on. Source: Google Search Central, JobPosting.
title
- Status: Required
- What it is: Only the job title. No code, location, salary or company name.
description
- Status: Required
- What it is: The full vacancy text in HTML.
datePosted
- Status: Required
- What it is: Date the vacancy was posted (ISO 8601).
hiringOrganization
- Status: Required
- What it is: The employer, with name and preferably website (sameAs) and logo.
jobLocation
- Status: Required*
- What it is: Address of the workplace. *Not needed for fully remote roles with applicantLocationRequirements.
baseSalary
- Status: Recommended
- What it is: The employer’s actual salary, with currency and period (hour, month, year).
employmentType
- Status: Recommended
- What it is: Full-time, part-time, temporary, internship, and so on.
validThrough
- Status: Recommended
- What it is: Closing date. Only fill in if there really is one.
directApply
- Status: Recommended
- What it is: Whether you can apply directly on the page.
identifier
- Status: Recommended
- What it is: Your own vacancy number.
jobLocationType
- Status: Recommended
- What it is: TELECOMMUTE for fully remote work.
applicantLocationRequirements
- Status: Recommended
- What it is: Where a remote candidate must live.
educationRequirements
- Status: Recommended (beta)
- What it is: Required level of education.
experienceRequirements
- Status: Recommended (beta)
- What it is: Required experience in months.
Two fields deserve extra explanation, because they’re often filled in incorrectly.
validThrough. Google says explicitly: if the vacancy has no closing date or you don’t know it, leave the field out. A made-up date (“always 30 days from now”) is therefore not a good idea. If the vacancy is filled earlier, you remove it, even if the closing date hasn’t been reached yet.
directApply. Only set this to true if a candidate can apply on your site in a short, simple step. If they first have to click through to another system or create an account, it isn’t direct apply. Google itself says it is still working out how it uses this field, so don’t expect miracles. Do fill it in honestly.
Step-by-step: how to get your vacancies into Google for Jobs
It comes down to one page per vacancy with the right data, testing before you go live, and removing expired vacancies immediately. Step by step:
- Give every vacancy its own page. With its own URL that Google is allowed to index: no noindex, not blocked in robots.txt, no login. A list of ten vacancies on one page doesn’t count.
- Put the full vacancy text on that page. Everything in the structured data must also be visible to the visitor. That certainly applies to the salary.
- Add the JobPosting data as JSON-LD. Fill in at least the five required fields. If you work with an ATS or website that does this automatically, check exactly what it contains (see step 5).
- Fill in the recommended fields you can fill in honestly. Salary, employment type and location first: those are what job seekers filter on.
- Test one vacancy in the Rich Results Test. Paste the URL and see whether Google recognises the vacancy, and what errors and warnings there are.
- Make sure Google finds your vacancies. Include all vacancy pages in your XML sitemap and submit it in Search Console. Google also mentions the Indexing API: you may only use it for pages with JobPosting (or livestreams), and it makes Google pick up a new or removed vacancy faster. For most employers with a handful of vacancies, an up-to-date sitemap is enough. Job boards and ATSs with many changing vacancies benefit more from it.
- Arrange the removal of expired vacancies. Choose one of the three methods Google lists (see below) and make sure it happens automatically.
- Check Search Console after a few days. In the job postings report under rich results, check whether the number of valid vacancies matches what’s on your site.
Want to know first what such a vacancy page should look like within your site? Read what belongs on a careers page.
Which mistakes cost you visibility in Google for Jobs?
Most vacancies drop out because of data that is missing or doesn’t match the page. If the guidelines are violated, Google can issue a manual action and remove your vacancies from the job block. These are the mistakes we see most often.
No salary
baseSalary isn’t required, but job seekers filter on salary and compare vacancies side by side in the block. If you leave it out, your vacancy has less information than your competitor’s. Don’t fill in an estimate either: Google asks for the actual salary as stated by the employer. And the salary in the code must also appear on the page, otherwise it violates the guidelines.
An expired vacancy that’s still live
Google states it explicitly in its guidelines: expired vacancies are not allowed, and an expired vacancy that stays online can lead to a manual action. You have three ways to remove a vacancy:
- delete the page, so it returns a 404 or 410;
- remove the JobPosting data from the page;
- set validThrough to a date in the past.
After that, keep your sitemap up to date, and with the Indexing API you can ask Google to remove the URL.
One page for multiple vacancies
JobPosting data may only appear on a page with a single vacancy. An overview page with ten roles and ten blocks of code beneath it therefore doesn’t qualify. Every vacancy needs its own page.
A job title stuffed with keywords
“Nurse Utrecht | Full-time | €4,000 | Start now!” is not a job title. The title field should contain only the role: “Nurse”. Location, employment type and salary have their own fields. Google explicitly lists stuffing titles and descriptions with keywords as a violation.
A few more common ones
- No address or location. Without jobLocation (or a remote specification), the vacancy is invalid.
- A recruitment agency as the employer. hiringOrganization should contain the party offering the vacancy, as it also appears on the page.
- A page Google isn’t allowed to read. A noindex, a block in robots.txt or a vacancy behind a login. URL inspection in Search Console shows whether Google can fetch the page.
How do you check whether your vacancies are in Google for Jobs?
Test an individual vacancy with the Rich Results Test and monitor the whole picture in Search Console. Together they show whether your code is correct and whether Google has actually included your vacancies.
Rich Results Test
- What for: Reads one URL or piece of code and shows whether Google recognises a valid vacancy, with errors and warnings.
- When: Before going live and after every change to your vacancy pages.
URL inspection (Search Console)
- What for: Shows how Google sees the page and whether it’s indexed.
- When: When a vacancy doesn’t appear.
Job postings report (Search Console, rich results)
- What for: Overview of valid and invalid vacancies across your whole site. After a fix, you request validation here.
- When: Every few weeks, or after a change to your website or ATS.
A handy rule of thumb from practice: the number of valid vacancies in Search Console should roughly equal the number of vacancies on your site. If you see far fewer, a required field is missing. If you see far more, there are probably expired vacancies in the index.
[NEEDED: screenshot of the Google for Jobs block for a Dutch search query and of the job postings report in Search Console, without client data]
How does Recruit Website handle this?
On Recruit Website, every vacancy page automatically gets the JobPosting data, filled from the vacancy that comes from your ATS. So you don’t need to add any code. What it includes:
- job title, description, date posted, employer (with website, and the logo if you’ve set one) and the work location, or remote work if the vacancy is fully remote;
- employment type, education and experience requirements if your ATS sends them;
- salary, but only if your ATS provides both an amount and a period, so there’s never a partial or estimated salary;
- directApply set to true only if you have an application form and an application page on your site;
- no validThrough, because vacancies on our platform have no closing date. That’s also how Google prescribes it.
If a vacancy disappears from your ATS, it also disappears from your site and the old vacancy page returns a 404. If a vacancy has no location at all, we leave the data out rather than showing invalid code. How high your vacancy appears in the block is up to Google.
Still deciding between a single careers page and a complete site? Read careers page or careers site.
Frequently asked questions
Is Google for Jobs available in the Netherlands?
Yes. The Netherlands is on the list of countries where Google offers the job search feature. Anyone searching for work with a location or job title sees the job block in Dutch search results. Reports about “when it’s coming to the Netherlands” are outdated.
Does Google for Jobs cost money?
No. Google charges nothing for inclusion in the job block. You only pay for the technology: someone who adds the structured data to your vacancy pages, or a website or ATS that does it automatically.
How long does it take for my vacancy to appear in Google for Jobs?
That depends on how quickly Google crawls your page. An up-to-date sitemap in Search Console helps. With the Indexing API, which is intended only for job posting and livestream pages, you ask Google to pick up a new vacancy faster.
Do I need to register with Google for Jobs?
No, there’s no registration. Google fetches vacancies itself from pages with JobPosting data. Search Console isn’t required, but it is where you see which vacancies are valid and which contain errors.
Why isn’t my vacancy showing in Google for Jobs?
Usually a required field such as the location is missing, the page is set to noindex, or there are multiple vacancies on one page. Test the URL in the Rich Results Test and check URL inspection in Search Console. If there’s a manual action, you’ll also see it in Search Console.
What’s the difference between Google for Jobs and Google Jobs?
When it comes to vacancies in search results, people mean the same job block with both terms. Note: someone searching for “Google jobs” often means working at Google itself. If you want your vacancies in the block, the only thing that matters is the JobPosting data on your own pages.
Your vacancies in Google for Jobs automatically
With Recruit Website, your vacancies come automatically from your ATS onto your careers site, with the Google for Jobs data included. You write the content, the technology is taken care of. Want to know what’s involved in having your own site? Read having a careers site built. Or try it straight away: start your 14-day trial.