JobPosting schema: how to get roles into Google Jobs
Job pages can appear in Google's jobs results with the right markup. Here are the fields to fill in, how the Indexing API helps, and how to retire filled roles.
Job pages are one of the few page types Google still treats as a special result. If your markup is right, a role can appear in the Google jobs experience with the title, company, location, and pay shown up front. If it is wrong, the page is just another blue link. This guide covers what to mark up, how to get changes seen quickly, and how to retire a role without leaving junk behind.
What JobPosting markup does
JobPosting is a schema.org type that describes one open role. Google reads it to decide whether a page can show in its jobs results. The markup does not guarantee a spot. It makes your page eligible.
Eligibility also depends on the page itself. Google's guidelines expect one job per page, a visible description that matches the markup, and a real way to apply. A page that lists twenty roles is a search page, not a posting. Mark up the individual job pages only.
Fields to fill in
Google requires a short set of properties. Treat the rest as the difference between a thin listing and a useful one.
- title: the job title only. Leave out the location, pay, and phrases like 'urgent hire'.
- description: the full role in HTML, matching what visitors see on the page.
- datePosted: when the role went live, in ISO 8601 format.
- hiringOrganization: the employer's name, ideally with a logo and site URL.
- jobLocation: a full postal address for on-site or hybrid roles.
Several optional fields are worth the effort. Add validThrough so Google knows when the role closes. Add baseSalary with a currency, a value or range, and a unit such as hour or year. Add employmentType, and directApply if the candidate applies on your page instead of being sent elsewhere. Some regions now require pay ranges in job ads, so check the rules where you hire.
Remote roles and common mistakes
For a fully remote role, set jobLocationType to TELECOMMUTE. Then use applicantLocationRequirements to say which countries or regions can apply. Do not put your head office in jobLocation for a remote job. That tells Google the role is on site.
These mistakes come up often:
- Markup that says one thing and the page says another, such as a different salary or location.
- Using a placeholder salary like 0 or 1 to pass a validator.
- Leaving the markup on a page after the role is filled.
- Hiding the apply path behind a login wall.
- Marking up a careers landing page that lists many jobs.
Google can take manual action against job markup that misleads people. A wrong salary is not a small error. It is the kind of thing that gets a whole site's job results removed.
Getting changes seen quickly
Jobs go stale fast, so waiting for a normal crawl is a poor fit. Google offers the Indexing API for JobPosting pages, which lets you tell it when a URL is added, updated, or deleted. It is one of the few page types the API officially supports. Using it for other page types is against Google's guidance.
Setup takes some engineering. You create a service account, add it as an owner of the property in Search Console, and send authenticated requests. If that is too much, an XML sitemap with accurate lastmod dates still works. It is just slower. Many applicant tracking systems already do this for you, so check yours before building anything.
Retiring expired jobs
A filled role should not sit in search results. People click, find nothing, and leave. Google asks site owners to remove expired postings, and you have a few options:
- Send a delete notification through the Indexing API, if you use it.
- Remove the JobPosting markup from the page, or set validThrough to a past date.
- Return a 404 or 410 status once the page has no use, or redirect to a closely related open role.
- Drop the URL from your sitemap.
A 410 is a clear signal that the page is gone on purpose. Pick the option that fits how you want to treat old links. If past postings still get visits from alumni or candidates who want to see the pay history, keep the page up with a closed notice and no markup.
How to check your markup
Run a few live job URLs through the Rich Results Test. It flags missing required fields and warns on recommended ones. Then open the Search Console enhancement report for job postings, if your site has one, and watch for errors after each template change. Compare a sample of rendered pages against their markup by hand. Validators check structure, not truth.
AI answer engines may also read this markup, but there is no public evidence about how much weight they give it. Treat that as a possible bonus, not a reason to add it.
Takeaway: audit one live job page today. Confirm it has a single role, accurate pay, a real apply path, and a validThrough date. Then write down what happens to the page the day the role closes.