SEO

Job Posting Result

Also called Google for Jobs listing, JobPosting rich result

The listing that appears in Google's jobs experience, built from JobPosting structured data on a careers page.

Quick facts: Job Posting Result

Category
SEO
Also called
Google for Jobs listing, JobPosting rich result
Level
Intermediate
Affects
Recruitment reach, candidate quality, careers page traffic
Where to see it
Rich Results Test, Search Console (job posting report), Schema Markup Validator
In this article4
  1. How a job posting result works
  2. Why job posting results matter
  3. Where job posting results go wrong
  4. How to act on it

How a job posting result works

A vacancy page marked up with JobPosting structured data tells Google what the role is, who is hiring, where the work happens, when the advert was posted and when it stops being valid. Google collects those pages into its jobs experience, where a candidate can search by title and location and filter by things like employment type. Salary is optional but usually worth supplying, because candidates filter on it and an advert without one looks evasive.

Each role needs its own indexable URL. A page listing every vacancy the company has cannot be marked up as a single posting, and a role hidden behind a search form or a script the crawler cannot run will never be found. Where roles change often, Google’s Indexing API exists specifically so employers can notify it of new and removed postings rather than waiting for a crawl. The jobs experience is not available in every country, so check before building around it.

Why job posting results matter

Hiring is a search problem like any other. Candidates type the job title and the city, and whatever appears at the top shapes who applies. A properly described vacancy page can put a company in front of people who have never heard of it, without paying a job board for the privilege.

It matters more in markets where recruitment advertising is informal. Where most vacancies circulate through social media groups and word of mouth — much hiring in Nepal still works this way — an employer with a clean, well-marked-up careers page competes for attention that competitors are not even contesting. It also gives recruitment agencies something durable to send candidates to.

Where job posting results go wrong

Expired adverts are the biggest problem. A filled role left live wastes applicants’ time and Google’s, and repeated over a year it makes the whole careers section untrustworthy. Set a valid-through date, and when a role closes either remove the page and return a gone status, or clearly mark it closed and drop the markup.

The other recurring faults are structural: several vacancies squeezed onto one page, a description in the markup that differs from the description a person reads, a careers section on an applicant tracking subdomain that is blocked from crawling, and postings for roles that do not exist — a permanent “we are always hiring” page collecting CVs. That last one breaches the guidelines and is the sort of thing that gets a site excluded from the jobs experience entirely.

How to act on it

Give every vacancy a page of its own with the full description visible, a posting date, a closing date, a named hiring organisation and a real location or a clear statement that the role is remote. Keep the visible text and the structured data identical, and validate before publishing.

Then make expiry part of the hiring process, not an afterthought: when the offer is accepted, the page comes down the same week. If the careers section sits on a third-party system, confirm with technical SEO checks that those pages are crawlable and indexable at all, since that is where most of these implementations quietly fail.

Do and do not

Do

  • Publish one indexable page per vacancy
  • Set a valid-through date on every posting
  • Remove or close pages the week a role is filled

Do not

  • List several vacancies on a single marked-up page
  • Advertise roles that are not genuinely open
  • Leave careers pages blocked on a recruitment subdomain

Questions people ask about this

Do I need to pay Google to list a job?

No. The jobs experience is not an advertising product for employers: Google gathers postings from careers pages and job boards that publish JobPosting structured data, and there is no fee to be included. What it costs is the work of a properly built careers page and the discipline to keep postings accurate and current.

Should I include the salary in a job posting?

It is optional in the markup but usually a good idea. Candidates filter and compare on pay, and a listing without it is often skipped in favour of one that is open about it. Some regions require pay information to be disclosed in advertised roles, so check the rules for the market you are hiring in.

What should happen when a vacancy is filled?

Take it out of circulation quickly. The cleanest approach is to remove the page and let it return a gone or not-found status, or to keep it as an archived record with the job posting markup removed and the closure stated plainly. Leaving a filled role advertised frustrates candidates and undermines the rest of your postings.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.