Google for Jobs displays job listings directly in search results. For many candidate searches, such as "marketing manager jobs Bristol", it appears above the ordinary results. That makes it one of the most valuable places your vacancies can be seen, and it costs nothing to appear.
Yet many recruitment websites are missing out, often without realising.
How Google for Jobs works
Google does not read your job pages the way a candidate does. It looks for structured data, specifically JobPosting schema, embedded in the page code. This markup tells Google the job title, description, location, salary, employment type and closing date in a format it can understand reliably.
If the markup is missing, incomplete or invalid, your roles are unlikely to appear, however good the page looks.
The most common problems
- No JobPosting schema at all, usually on older or template-built sites.
- Jobs loaded by JavaScript in a way Google struggles to read.
- Missing salary, location or employment type fields.
- Closed roles left live with no expiry date, which Google treats as poor quality.
- The same job published at several URLs, creating duplicates.
- Job pages blocked from indexing by mistake.
Required and recommended fields
Google requires a title, description, date posted, hiring organisation and job location. It strongly recommends a valid-through date, base salary, employment type and an identifier. Remote roles should use the appropriate remote-working properties rather than a vague location.
Including salary is particularly important. Listings with salary information tend to attract more attention from candidates, and Google gives them more prominence in filters.
Writing job pages that convert
Appearing in Google for Jobs is only half the job. When a candidate clicks through, the page needs to load quickly on a phone, explain the role clearly and make applying simple. A good job page includes:
- A specific, searchable job title rather than internal jargon.
- Location, salary and working pattern near the top.
- A concise description of the role, the team and why it is worth applying.
- A short apply process that works on mobile, ideally under a minute.
- A link to the consultant who owns the role.
Keeping it accurate automatically
The most reliable way to keep Google for Jobs accurate is to connect your website to your ATS. When a role is approved it publishes with complete schema. When it is filled it expires. No one has to remember to update the website.
Monitoring
Google Search Console has dedicated reports for job postings, showing which pages are valid, which have warnings and which have errors. Check them regularly, and fix issues quickly, especially after any change to your site or job feed.
The checklist
- Add complete JobPosting schema to every job page.
- Include salary, location, employment type and a valid-through date.
- Expire filled roles promptly.
- Use one URL per job.
- Submit a jobs sitemap.
- Monitor job posting reports in Search Console.
Get these right and every live role becomes a free route to the candidates you are trying to reach.