How to Optimise Recruitment Job Pages for Google Jobs

Recruitment job pages appear in Google Jobs when they carry valid JobPosting schema, clean URLs and a working sitemap. Without that structure, roles stay invisible to the feature built to surface them, so the schema is what turns a job page into a candidate channel. Here is how to set it up.

Key Takeaways

Job pages need valid JobPosting schema to be eligible for Google Jobs, so the markup is the entry ticket, not an add-on.
Each role needs a clean, unique, indexable URL and a submitted sitemap so Google discovers it fast.
Required JobPosting fields, title, description, datePosted, validThrough and hiringOrganization, must be complete and accurate.
Expired roles need removing or marking closed, because stale listings breach Google Jobs guidelines and hurt trust.
Structured job pages rank organically and in Google Jobs, so one setup wins two surfaces.

JobPosting Schema Is the Entry Ticket

A job page only enters Google Jobs if it carries valid JobPosting schema, because Google reads the structured data, not the visible layout, to understand a role. A page without it stays a normal web page, invisible to the jobs feature, so the markup is the foundation of the whole recruitment website job strategy.

How should job pages be optimised for Google Jobs?

Add valid JobPosting schema with the required fields, give each role a clean unique URL, and submit a sitemap so Google finds them fast. This makes a role eligible for the jobs feature and helps it rank organically, part of fixing the technical mistakes that kill recruitment websites.

Get the Required Fields Right

Google Jobs eligibility depends on complete, accurate fields, because missing or wrong data fails validation. Title, description, datePosted, validThrough, hiringOrganization and jobLocation must all be present and match the visible page, and adding baseSalary and employmentType strengthens the listing.

Which JobPosting fields does Google require?

Google requires title, description, datePosted and hiringOrganization at minimum, with validThrough, jobLocation, baseSalary and employmentType strongly recommended. The structured data must match the visible content, following Google's JobPosting guidance, or the role fails validation.

Manage Expiry and Stale Roles

Google Jobs penalises stale listings, so expired roles must be removed or marked closed, not left live. A validThrough date and a clear removal process keep the feed accurate, because filled or expired roles that stay indexed breach the guidelines and erode candidate trust.

What happens to expired job listings in Google Jobs?

Expired roles left live breach Google's guidelines and can affect eligibility across the site, so each needs removing, returning a 404 or 410, or marking closed on schedule. Keeping the feed clean is a technical-health issue, part of why strong technical SEO and UX are now non-negotiable.

Rank Job Pages Organically Too

A structured job page can rank in normal search as well as Google Jobs, so the setup wins two surfaces at once. Unique, indexable URLs, descriptive titles and internal links from sector and location pages help each role rank organically, not only appear in the jobs feed.

How do job pages rank in organic search?

By giving each role a unique indexable URL, a descriptive title and internal links from relevant sector and location pages, all marked up cleanly. This lets a role rank in standard results and Google Jobs together, built on the essential schema templates for AI readiness.

How to Optimise Job Pages for Google Jobs

Step 1. Add valid JobPosting schema to every role, with all required fields matching the visible page.

Step 2. Give each role a clean, unique, indexable URL and keep a submitted jobs sitemap.

Step 3. Set a validThrough date and remove or close expired roles on schedule.

Step 4. Link job pages internally from sector and location pages so they rank organically too.

Frequently Asked Questions

How should job pages be optimised for Google Jobs and organic search?

Add valid JobPosting schema with the required fields, give each role a clean unique URL, keep a submitted sitemap, and link roles from sector and location pages. This makes them eligible for Google Jobs and helps them rank in normal search too.

What schema do job pages need?

JobPosting schema, with title, description, datePosted and hiringOrganization required, and validThrough, jobLocation, baseSalary and employmentType recommended. The structured data must match the visible page content, or Google will not validate the role for the jobs feature.

Why do expired job listings hurt Google Jobs eligibility?

Because Google's guidelines require the feed to be accurate, so filled or expired roles left live breach them and can affect eligibility across the site. Each expired role should be removed, return a 404 or 410, or be marked closed.

Can job pages rank in normal search as well as Google Jobs?

Yes. A structured job page with a unique indexable URL, a descriptive title and internal links can rank in standard results and appear in Google Jobs, so one correct setup wins both surfaces at once.

About the author

Dan Jones is the founder of Kaizen SEO, a UK recruitment SEO and AEO agency. A former recruiter with more than a decade in SEO, he helps recruitment agencies win visibility in Google and AI search.

Job pages invisible in Google Jobs? Book a strategy review and we will audit your recruitment job pages and their schema against Google Jobs eligibility.

How to Optimise Recruitment Job Pages for Google Jobs