How to get your jobs into Google for Jobs

Google for Jobs is the common name for the job search experience in Google Search: job listings that people filter by things such as location and job title, and then click through to the site that posted them. Job pages that carry JobPosting structured data can appear in it. This post covers what that data must contain, the content rules Google applies, how to get Google to read new jobs quickly, and the common reasons jobs do not appear, with what JobClay does at each step.

Google's rules here come from its job posting documentation and its Indexing API documentation, which we read on October 27, 2026. Google changes them from time to time, so treat its pages as the final word.

First, check that it runs in your country

Google lists the regions where its job search is available. On the page we read, it covered the whole of North America, Latin America and sub-Saharan Africa, and named countries in Asia, Europe, and the Middle East and North Africa, among them India, Japan, Germany, France and the United Kingdom. No country in Oceania was on the list, so jobs in Australia or New Zealand had no Google job search to appear in, though their pages can still rank in ordinary results.

Check the region list for the country your board serves before you plan around Google's job search. Everything else in this post helps ordinary results too.

The data Google reads

Google reads a JobPosting block on each job's page, usually written as JSON-LD. For each field below, the first sentence is Google's rule and the second is what a JobClay job page sends.

Google requires five fields:

title: the job title only, without job codes, addresses, dates, salaries or company names. JobClay sends the job's title.
description: the full description of the job, in HTML. JobClay sends the job's description.
datePosted: the date the employer posted the job. JobClay sends an imported job's posting date from its source when Use the posting date from the source is on, as it is by default, and otherwise the date the job reached your board.
hiringOrganization: the company's name, not the branch that is hiring. JobClay sends the company's name, with its logo and links when it has them.
jobLocation: where the employee reports to work, with its country, unless the job is fully remote and says where applicants may live. JobClay sends each of the job's cities with region and country; a job with no city that is not fully remote gets its location text or the company's address, with your board's country.

It recommends several more, among them:

jobLocationType: TELECOMMUTE, only for jobs that are fully remote. JobClay sends it for remote jobs, and a hybrid job keeps its place.
applicantLocationRequirements: where the employees of a fully remote job may live. JobClay sends your board's country, for remote jobs.
validThrough: when the job expires, left out if it never does. JobClay sends the job's expiry on your board, which is in the past once the job has expired.
employmentType: one or more of Google's values, such as FULL_TIME, PART_TIME, CONTRACTOR or INTERN. JobClay sends the value set on the job's job type.
baseSalary: the pay the employer gives, not an estimate. JobClay sends the minimum and maximum salary in your board's currency, per month or per year, when the job has them.

Optional fields such as a salary are left out when the job has no value for them. A JobClay job page also sends the skills, qualifications and industries a job lists, when it lists any, and the experience it asks for, which is 0 months when the job sets none.

Two settings decide whether that data is complete:

Your board's country, on Region. It is the country of a job with no city, and the place where a remote job's applicants may live. If no country is set, a job with no city that is not remote names no place at all, and a remote job with no city names neither a place nor where its applicants may live, so Google finds no location for either.
Each job type's posting type, on Lists. employmentType comes from the job type. On the Job type list, each type has a menu beside it with Google's types, such as Full-time. A new board's types come with one set; a type you add starts at None and sends nothing until you choose one.

The rules beyond the data

Google's job posting content policies decide whether a marked-up job may be shown at all. Google says it may take manual action on a page that breaks them and remove its jobs from the job search. These are the ones a job board meets most often:

One job per page. The data belongs on the page of a single job, never on a page that lists jobs. JobClay sends it on job pages only.
Complete descriptions. Google does not allow job postings with incomplete descriptions. Watch sources whose jobs carry little more than a title. A JobClay job with no description at all sends a single line naming its title and company, which is unlikely to count as complete.
No expired jobs. Google would rather expired jobs were removed, and otherwise wants validThrough set in the past. On JobClay, a job that expires, for example when its time runs out or its source stops listing it, keeps its page, which says the job is closed, and sends its expiry in the past. A job you or its employer close is taken down, and its address answers 404.
A way to apply, and no login to read the job. A JobClay job page shows the whole job to anyone, signed in or not.
No payment from applicants, no fake jobs, and no ads posing as jobs. These depend on what you let onto your board. Making new employers wait for your approval, word filters on job sources and reading what comes in are how a board keeps them out.
Remote jobs that say so. Marking a job TELECOMMUTE is not enough: Google wants the description itself to say that the job is fully remote, and where applicants may live when that is limited. Occasional work from home does not count as remote.

Get Google to read new jobs sooner

Google finds job pages by crawling, and your sitemap tells it where they are. For job pages, Google recommends its Indexing API over sitemaps, because a notification prompts Googlebot to crawl the page sooner, and it still recommends a sitemap for the whole site.

What Google's documentation says about the API:

It can only be used for pages with job posting data or livestream videos.
It is free, and a Google Cloud project gets 200 notifications a day by default, counting both new or changed pages and removed ones. The day resets at midnight Pacific time.
A notification asks Google to crawl. An accepted one means Google may recrawl the page soon, not that the page is indexed.
A removal notice is for a page that answers 404 or 410, or carries a noindex tag.
The service account that sends notices must be an owner of the site in Search Console.

How JobClay uses it:

Your own key. You create a Google Cloud project, turn on the Web Search Indexing API, make a service account and upload its JSON key on SEO and Tag Manager, then add the service account as an owner in Search Console. The quota is your board's alone. The Google indexing guide walks through every step.
What it sends. A notice when a job goes live, when its address changes, and when it closes. An expired job's page still answers, so it gets an update notice, and Google reads the page again and finds the job expired. A job whose page has gone, such as one you closed, or that is now hidden from search engines, gets a removal notice.
What goes first. New jobs posted by employers or by you, then new imported jobs, then closed jobs. What the day's quota leaves waits for the next day. Untick Send imported jobs to keep the quota for posted jobs.
Jobs already live when you connect reach Google through your sitemap.
Status. The card shows whether Google is taking the notices. If it says Google refused, the service account is not yet an owner of the site in Search Console, or the API is off in the project.

The same changes go to Bing, Yandex and other engines through IndexNow, which is on for every board. Our post on job board SEO covers IndexNow, sitemaps and the rest of the groundwork.

Why jobs do not show, and what to check

When a job is not in Google's job search, work down this list.

The country is not covered. Check the region list above.
Google has not crawled the page yet. Google says it may take several days after a page is published for Google to find and crawl it. Search Console's URL Inspection tool shows whether a page is indexed; the Indexing API shortens the wait.
The data has errors. Paste the job's address into Google's Rich Results Test, which shows the job data Google reads and any problems with it. Once Google has read your jobs, Search Console's rich result reports list errors across all of them. On JobClay, a job with no location or no country in its data is a sign that the board has no country set on Region.
The title carries extras. Some sources put a job code, a city or a note such as "urgent" in the title. Edit the job's title, and tick Keep my edits on its source, so the next run does not write the old title back.
The description is thin. If a source's jobs carry little more than a title, they are unlikely to count as complete, and the source may not be worth its place on your board.
The job is hidden from search engines. Jobs from a source with Hide from search engines on carry no job data, and their pages ask search engines not to index them.
The job has closed. That is as it should be: Google does not allow expired jobs in its job search.
A manual action. When Google takes manual action against a page's structured data, it ignores that data, though the page can still appear in ordinary results. Search Console's Manual actions report is where to look.

Even with everything right, Google's documentation says it does not guarantee that structured data features appear in results. Google decides what to show; what you control is that every job is open, complete and correctly marked up.

A check to run today

Open a live job on your board and run its address through the Rich Results Test.
Check that Region names your board's country, and that no type on the Job type list in Lists is set to None.
Verify the board in Search Console and submit /sitemap.xml in its Sitemaps report.
Connect the Indexing API with a key of your own, following the Google indexing guide.
A week later, open Search Console's rich result reports, and inspect the address of a recent job.

The SEO feature page sums up what JobClay does for search, and the guide to creating a job board covers the rest of the setup.