Google for Jobs for Recruitment Agencies, the Complete Setup

Google for Jobs for Recruitment Agencies, the Complete Setup

Google for Jobs shows a recruitment agency's roles free in a dedicated search widget when the pages carry valid JobPosting schema, are indexable, and are kept current. Applications sourced through Google convert at roughly 2.4 times the LinkedIn rate (Huntr, 2026), so the setup is worth doing properly. This guide covers the whole thing, end to end.

Key Takeaways

• Google for Jobs is a free candidate channel, but only for roles with valid JobPosting schema on indexable pages.
• Google-sourced applications convert at roughly 2.4x the LinkedIn rate (Huntr, 2026), so the channel is high value for agencies.
• Eligibility depends on required fields, a clean URL per role, and a submitted sitemap or the Indexing API.
• Expired roles must be removed or closed, because stale listings breach Google's guidelines and risk eligibility.
• Setup is only half the job; monitoring in Search Console is what keeps the feed live and compliant.

What Google for Jobs Is and Why It Matters

Google for Jobs is the enriched jobs experience that appears in Google Search when someone looks for roles, aggregating listings from sites that mark them up correctly. It is not a job board an agency pays for; it is a free surface an agency earns by structuring its job pages properly, which is why it belongs in every recruitment website SEO plan. For agencies, the payoff is qualified candidate traffic at no media cost, and with Google-sourced applications converting at roughly 2.4 times the LinkedIn rate, the quality is as notable as the price.

Why should a recruitment agency use Google for Jobs?

Because it delivers candidate traffic free and at high quality, so it reduces reliance on paid job boards. Roles that appear in the widget reach candidates at the moment of search, and since the channel is earned through schema rather than bought, the cost per application falls as the setup matures.

Check Eligibility First

Before anything else, an agency has to meet Google's eligibility rules, because a role that breaks them never appears. Each job page needs valid JobPosting structured data, a unique indexable URL, and content that matches the markup, and the site must not block Googlebot. Getting eligibility right first avoids building a feed that silently fails, part of why strong technical SEO and UX are now non-negotiable.

What makes a job page eligible for Google for Jobs?

Valid JobPosting schema with the required fields, a unique crawlable URL, content matching the structured data, and no crawl block. If any of those fail, Google will not show the role, so eligibility is a checklist to clear before publishing, not an afterthought.

Get the JobPosting Schema Right

The core of the setup is JobPosting schema with complete, accurate fields, because Google reads the structured data to build the listing. The required fields are title, description, datePosted and hiringOrganization, with validThrough, jobLocation, baseSalary, employmentType and applicantLocationRequirements strongly recommended, and everything must mirror the visible page. Following Google's JobPosting guidance to the letter is what passes validation.

Which JobPosting fields does an agency need?

Title, description, datePosted and hiringOrganization are required; validThrough, jobLocation, baseSalary and employmentType are strongly recommended and improve the listing. Adding salary and location data also matches how candidates filter, so completing the optional fields lifts both eligibility and click-through.

Should salary be included in the schema?

Yes where possible, because salary is one of the strongest candidate filters and its transparency is rising across the market. Including baseSalary makes a listing more complete and more clickable, so omitting it usually costs applications even though Google does not strictly require it.

Connect the Feed, ATS and Indexing

Most agencies publish roles through an ATS or website platform, so the setup has to connect that feed to Google cleanly. The platform must output valid schema on each role, expose a jobs sitemap, and ideally use the Indexing API, which Google supports for JobPosting to get roles crawled fast. Where the ATS controls the templates, the schema and URL structure need checking there, since a feed that outputs broken markup fails every role at once.

How does an agency get roles indexed quickly?

By submitting a jobs sitemap and using Google's Indexing API for JobPosting, which is built for time-sensitive content. Fast indexing matters because roles are perishable, so the quicker Google discovers a live role, the more of its shelf life is spent visible to candidates.

What if the ATS controls the job pages?

Then the schema, URLs and expiry handling must be validated inside the ATS or platform, because it generates every role. A platform that outputs invalid JobPosting data or messy URLs undermines the whole feed, so the fix is at the template level, not page by page.

Handle Expiry and Compliance

Google for Jobs penalises stale data, so expiry handling is not optional. Every role needs a validThrough date, and filled or expired roles must be removed, return a 404 or 410, or be marked closed, because listings that outlive the role breach Google's guidelines and can affect the whole site's eligibility. A clear removal process keeps the feed trustworthy, which protects the channel long term.

What happens to expired Google for Jobs listings?

Left live, they breach Google's guidelines and can jeopardise eligibility across the site, so each must be removed, returned as 404 or 410, or closed on schedule. Keeping the feed accurate is a compliance requirement, not housekeeping, because Google treats stale listings as a trust failure.

Monitor, Troubleshoot and Improve

Setup is only half the work, because a job feed drifts without monitoring. Search Console's rich results and Google for Jobs reporting show which roles are valid, which have warnings and which are failing, so an agency should check it regularly and fix errors fast. Monitoring also reveals patterns, a recurring field error or a platform bug, that a one-off setup would never surface, part of the diagnostic discipline in the technical mistakes that kill recruitment websites.

How do you monitor Google for Jobs performance?

Through Google Search Console's rich results reports, which flag valid, warning and error states per role, and through the Rich Results Test for individual pages. Regular checks catch feed-wide faults early, so a broken template or missing field is fixed before it costs a month of listings.

How to Set Up Google for Jobs for a Recruitment Agency

Step 1. Confirm eligibility, valid JobPosting schema, unique indexable URLs, content matching the markup, no crawl block.

Step 2. Complete the schema fields, required plus recommended, including salary and location where possible.

Step 3. Connect the ATS or platform feed, expose a jobs sitemap, and use the Indexing API for fast crawling.

Step 4. Set validThrough dates, remove or close expired roles, and monitor Search Console to keep the feed compliant.

Frequently Asked Questions

How does a recruitment agency get roles into Google for Jobs?

By marking each role up with valid JobPosting schema on a unique indexable URL, exposing a jobs sitemap, and keeping the data current. Once eligible, Google shows the role free in the jobs widget, and using the Indexing API speeds up how fast it appears.

What schema is required for Google for Jobs?

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

Is Google for Jobs free for recruitment agencies?

Yes. It is an earned surface, not a paid job board, so an agency pays nothing for the listings themselves. The investment is in setting up valid schema and a clean feed, after which the channel delivers candidate traffic at no media cost.

Why do expired roles matter in Google for Jobs?

Because Google requires the feed to be accurate, so expired or filled roles left live breach the guidelines and can affect eligibility across the site. Each needs removing, returning a 404 or 410, or marking closed on schedule to keep the channel trustworthy.

How is Google for Jobs different from a job board?

A job board is a paid third-party platform, while Google for Jobs is a free surface an agency earns through structured data on its own site. That means the agency keeps the candidate relationship and pays no listing fee, provided the schema and feed are correct.

How long does it take roles to appear in Google for Jobs?

Once a page is eligible and discovered, roles can appear within hours to a few days, faster if the Indexing API is used. Because roles are time-sensitive, quick indexing is worth setting up so a listing is visible for as much of its life as possible.

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.

Roles not showing in Google for Jobs? Book a strategy review and we will audit your job feed, schema and eligibility end to end.