For many recruitment agencies, this is the quiet leak in their candidate attraction. The vacancies are there, the candidates are searching for them, but the two never meet, because as far as Google, Google for Jobs and AI systems are concerned the pages simply don't register. Recruitment SEO isn't a question of more budget or more vacancies, but of technical setup, structure and how you tie your existing vacancies together.
Why recruitment agency vacancies are so hard to find on Google
The short answer: most of the organic search traffic for jobs passes you by. A jobseeker searching for "warehouse operative jobs Birmingham" is typing exactly the combination of role and place you've got sitting in your system. If your site doesn't appear for it, they click through to Indeed, to a competitor, or to a vacancy that's been built properly.
That has two consequences. You pay for candidates through paid job boards you could have won for free, organically. And you build no findability of your own: every pound that goes to Indeed or LinkedIn strengthens their position, not yours. Strong warehouse operative jobs in Birmingham pages on your own site are a lasting asset; a paid advert is gone the moment the budget runs out.
One caveat up front, because it's often missing: good recruitment SEO doesn't guarantee a flood of applications. Google for Jobs delivers mixed results in the UK, and some agencies see few direct applications from it. So don't treat it as a switch you flip for revenue, but as a foundation that structurally improves your chances, in combination with the rest of your site.
Why most recruitment websites are built on weak technical foundations
This is rarely down to unwillingness and almost always down to how recruitment websites came to exist. Most recruitment agencies run their vacancies through an ATS or a feed that populates the site. Handy for publishing, but it produces thin pages: a job title, a short description, an apply button. To Google, a page like that looks barely different from a thousand others.
The recurring problems are familiar:
- Thin vacancy pages with too little unique, relevant text.
- No local or sector-specific landing pages, so you never build ranking for "role plus region".
- Vacancy listings with no visible filters and no proper descriptions, which feel empty to search engines.
- Uncontrolled filter combinations that generate thousands of thin, duplicate pages.
- Few or no internal links between vacancies, listings and sector pages.
- Missing or incorrect JobPosting structured data, so vacancies never appear in Google for Jobs.
- Expired vacancies left sitting as dead pages.
- No XML sitemap, no Search Console and no visibility into what Google is actually indexing.
Every one of these is fixable. Below is the approach, from the page itself to the way you tell Google that it exists and keeps existing.
Building vacancy pages that rank on Google
1. Give every vacancy its own indexable page
This is the foundation everything else rests on. Every vacancy should have its own URL with a descriptive page title ("Warehouse Operative, Full-Time, Birmingham" rather than "Vacancy 48213"), a unique description and clear information on role, location and contract type. Not a stray pop-up, not a page that disappears once the role is filled, but a permanent page Google can crawl and index.
Watch one important distinction that many sites confuse: the SEO page title and the schema title are not the same thing. Your visible title and H1 can read "Warehouse Operative, Full-Time, Birmingham", but the JobPosting.title field wants only the bare job title, so "Warehouse Operative", without location, salary, date or company name. Incorrect schema titles are processed less well.
2. Build listings with visible filters, and decide which ones you index
A good listing is more than a list. Visible filters by sector, region, town, contract type and industry make searching easier for the candidate and can, provided they exist as genuine crawlable URLs, form a network of valuable landing pages. Give every listing a logical, descriptive intro of a few sentences about the regional labour market and the kinds of roles on offer, so search engines and AI systems have something to work with.
There's a trap here, though. Without rules, you'll very quickly end up with thousands of thin combinations like /vacancies/logistics/full-time/birmingham/monday/no-experience/. So keep to a clear faceted-navigation approach:
- Index only combinations with search volume and enough vacancies, for example /vacancies/logistics/birmingham/.
- Set thin or duplicate filter combinations to noindex, or point them to the main category with a canonical.
- Use fixed landing pages for your strategic combinations, rather than leaving them to chance filters.
3. Build local and sector-specific landing pages
Candidates search in combinations: role plus place, or sector plus region. "Production operative jobs Sheffield", "care jobs in Manchester", "hospitality work Brighton". Anyone who only publishes individual vacancies misses all of these listing-level searches. So create fixed landing pages by sector, region, town, contract type and industry. A page like that bundles the relevant vacancies, gives context about the local market and becomes a lasting anchor point on your site. Think of care jobs in Manchester as a permanent landing page, not a chance search filter that's gone again tomorrow.
4. Make full use of your internal link structure
Internal links are one of the most underrated levers in SEO for recruitment websites. They show Google how your site hangs together and which pages matter, and they distribute authority across your whole site, including to deeper vacancy pages that would otherwise never get any attention.
A strong structure looks roughly like this:
- From every vacancy, link to the relevant town, region and sector page.
- From listings and landing pages, link back to individual vacancies.
- Have related landing pages reference each other, for example from "logistics Birmingham" to "warehouse Birmingham".
- Give important pages more internal links than less important ones, so you show Google a clear hierarchy.
A production operative jobs in Sheffield page that links to nothing and that nothing links to sits there isolated as far as Google is concerned, however good the page is in its own right.
5. Make related vacancies genuinely related
Many sites show a "related vacancies" block at the foot of the page that's actually filled at random or only by date. That's a missed opportunity. Related vacancies should match on role, sector or region: a warehouse vacancy in Birmingham belongs alongside other logistics roles in the same area, not an admin job at the other end of the country. Good links keep candidates on your site longer, lower your bounce rate and at the same time strengthen your internal link structure, because the links make sense in context.
6. Write for coverage, not keyword density
Keyword density is widely misunderstood. The point isn't to repeat "warehouse operative Birmingham" as often as possible, because overdoing it backfires and reads unnaturally. The point is full, natural coverage: the job title, variations of it, related roles, the contract type, the region and the terms, all in a logical place across the title, headings and body text. Read your sentence back: if it sounds forced, rewrite it.
Use JobPosting structured data for Google for Jobs
If you want to make your vacancies findable in Google for Jobs, the separate jobs block at the top of the search results, then JobPosting structured data is essential. Structured data is code that tells search engines exactly what's on a page. Important: JobPosting belongs on the individual vacancy page, not on listing pages.
A good JobPosting markup for a UK vacancy should contain at least these fields, alongside recommended fields that make the vacancy more complete:
- title: the job title only, for example "Warehouse Operative".
- description: the full, unique description of the role.
- datePosted: the publication date, for example 2026-06-20.
- hiringOrganization: the name of your agency or the client.
- jobLocation: street, town, postcode and country.
- validThrough: the expiry date, for example 2026-08-01.
- employmentType: for example FULL_TIME or PART_TIME.
- baseSalary: an amount or salary range with currency (GBP) and period.
- identifier: a unique vacancy reference.
- directApply: whether candidates can apply directly on the page.
Always test your markup in Google's Rich Results Test and Schema Markup Validator, and keep the fields consistent with what's visible on the page. A platform like JobSaaS can build this correctly by sector, region, town, contract type and industry automatically, including strong listings, internal links and structured data.
What do you do with expired vacancies?
Expired vacancies left in place harm your findability and frustrate candidates. Google offers clear options for this; pick one per situation and apply it consistently:
- Set validThrough to a date in the past, so Google knows the vacancy is no longer active.
- Remove the page with a 404 or 410 status code.
- Remove the JobPosting structured data from the page.
- Or redirect the URL to a relevant category or region page, so you keep the traffic.
For fast updates and removals of vacancy URLs, Google recommends the Indexing API, alongside an XML sitemap for general coverage. That stops closed roles lingering in the search results for days on end.
Recruitment SEO beyond your site: authority and link building
Everything so far happens on your own site. But Google also weighs how many other relevant websites link to you. Those external links increase your domain's authority and with it the chance that your vacancies and landing pages rank higher. Think of mentions from local chambers of commerce, trade bodies, training providers you work with, or regional news sites during a recruitment campaign.
With a tool like Ahrefs you can map your own backlink profile and see which sites link to your competitors, so you know where the opportunities still lie for you. Link building is a long game, but for a recruitment agency that wants to become structurally more findable, it's the difference between riding on someone else's authority and building your own.
Sitemap and Search Console: help Google understand your recruitment website
A technically perfect site is of little use if Google doesn't know your pages exist. An XML sitemap is a file that lists all your important URLs and so forms a road map of your site. Submit it through Google Search Console and keep it up to date, so new vacancies and landing pages get picked up quickly.
Google Search Console is your control room here. It shows you which pages are and aren't indexed, which keywords you appear for, where your structured data is throwing errors and which pages bring in traffic. For a recruitment website, where pages come and go constantly, that's indispensable.
A vacancy that exists only as a database row does nothing for your findability. It's only when that same vacancy gets its own findable page, intelligently connected to the rest of your site, that it starts working for you.
From findable to applied: conversion counts too
Being found is only half the job. A candidate who reaches your page and then drops off still delivers nothing. Good vacancy information helps here in two ways: a salary range, a clear location and contract type make your page more appealing and at the same time populate fields like baseSalary and directApply in your structured data.
So keep an eye on the application experience itself:
- A mobile-friendly application flow, because the majority of candidates search on their phone.
- Short forms with only the genuinely necessary fields.
- A clear salary range and location, so candidates know straight away where they stand.
- A direct apply button and perhaps a text or WhatsApp option.
- Fast load times and a clear call to action.
Making vacancies findable in ChatGPT, Perplexity and Google AI Overviews
More and more candidates are putting their question to ChatGPT, Claude, Perplexity or Google AI Overviews: "Which recruitment agencies have logistics vacancies around Birmingham?" It's tempting to think this calls for special tricks. It doesn't. According to Google's own guidance, AI Overviews and AI Mode rely on the same SEO fundamentals, there are no extra technical requirements and no separate AI schema is needed. A file like llms.txt isn't needed for Google Search.
There is a nuance, though, that makes the difference between taking part and standing out. For generative AI visibility, Google advises going beyond basic SEO and creating unique, expert content that isn't readily available elsewhere. For a recruitment agency, that means: don't just write "warehouse operative wanted", but add what an AI system can't get anywhere else. Think current insight into the local labour market, realistic salary indications by region, what a role actually involves day to day and what progression is on offer.
Three things carry extra weight for AI search in recruitment:
- Entities and consistency. Name roles, places, sectors and your company name explicitly and identically everywhere, so AI systems recognise you as the source for "logistics vacancies in the Birmingham area".
- Reputation and source recognition. AI systems draw their answers from sources they trust. Mentions, reviews and consistent NAP details (name, address, phone) beyond your own site reinforce that trust.
- Clear-cut answers. Answer specific questions directly in the text: which role, which place, which salary, which contract type. That's exactly the format AI answer engines pick up.
Structured data remains useful for rich results, but it isn't the lever for AI findability. Write for people, deliver unique expertise and make sure your pages give clear-cut answers, and you'll stand strong in both classic and generative search results.
Checklist: minimum technical requirements per vacancy page
- Its own permanent, crawlable URL.
- Indexable (no accidental noindex or robots.txt block).
- A descriptive page title and H1.
- A correct canonical to the definitive URL.
- Valid JobPosting structured data with the right fields.
- Clear location and contract type.
- A salary range wherever possible.
- An expiry date (validThrough) and a way of handling things once it lapses.
- Relevant internal links to town, region and sector pages.
- A clear, mobile-friendly apply button.
How do you measure whether your recruitment SEO is working?
What you don't measure, you can't improve. Track these KPIs in Google Search Console and GA4 to see whether your findability is growing:
- The number of indexed vacancy pages.
- The number of valid JobPosting items and any errors in them.
- Impressions and clicks per vacancy cluster (role, region, sector).
- Organic traffic to your town and sector pages.
- Application conversion per page or cluster.
- Crawl errors and the number of expired vacancies.
- The leading search queries by region.
Worth knowing: traffic from AI features in Google shows up in Search Console within the normal Web performance report. So you don't need a separate dashboard for it.
What Google's own guidelines say about this
Google Search Central's documented best practices stress that a page must be crawlable and needs a clear, descriptive title to qualify for organic visibility. For a recruitment agency, that's precisely the difference between a vacancy that exists only as a database row and a vacancy that can genuinely rank: every vacancy needs its own indexable page, a specific title and supporting internal links. It isn't an advanced trick, but a foundation many recruitment websites simply skip.
Frequently asked questions
How do I make my vacancies findable in Google for Jobs?
Google for Jobs shows vacancies that sit on a crawlable, indexable page and are correctly fitted with JobPosting structured data. So first make sure every vacancy has its own page, add the right schema fields and test them with the Rich Results Test. It isn't an ad slot you buy, but an organic result you earn with good technical setup.
What goes in JobPosting.title, the job title or the SEO title?
JobPosting.title should contain the bare job title only, for example "Warehouse Operative", without location, salary, date or company name. Your visible page title and H1 can be fuller, such as "Warehouse Operative, Full-Time, Birmingham". Incorrect schema titles are processed less well by Google.
Which filter pages should and shouldn't I let index?
Index only filter combinations with search volume and enough vacancies, such as a logical role-plus-place combination. Set thin or duplicate combinations to noindex, or point them to the main category with a canonical. For strategic combinations, use fixed landing pages. That's how you avoid thousands of empty filter pages.
Do I need special tricks to make vacancies findable in AI?
No. According to Google, AI Overviews and AI Mode rely on the same SEO fundamentals, with no extra technical requirements or separate AI schema. What helps most is unique, expert content, crawlable pages, consistent entities and clear answers to specific questions. A file like llms.txt isn't needed for Google Search.
Conclusion: making vacancies findable on Google is a choice, not chance
Recruitment SEO isn't about more budget or more vacancies, but about how your existing vacancies are built, connected and handled. Their own indexable pages, listings with well-considered filters, fixed landing pages, a strong internal link structure, genuinely related vacancies, correct JobPosting structured data for Google for Jobs, tidy handling of expired vacancies, targeted link building and a well-managed sitemap in Search Console together ensure that the candidates already searching for your roles actually find your site and apply. Don't expect miracles from any single fix, but know that this foundation structurally improves your chances, in AI search engines too.
For recruitment agencies that want more control over their candidate attraction, JobSaaS offers a practical way to build and manage a recruitment website that supports SEO, AI visibility and conversion, without having to commission a bespoke project.
