Recruitment web design that wins clients and converts candidates

What recruitment web design actually means

The definition matters, because it explains why a general web design agency usually produces a recruitment website that looks good and performs badly.

Recruitment web design is the practice of designing and building websites for businesses whose product is people. That single fact changes almost every decision. A product company has a catalogue that it controls, a checkout it owns, and one primary buyer. A recruitment business has an inventory of live vacancies it does not fully control, a candidate audience that arrives mostly from search and social, and a client audience that arrives from referral, outbound and brand recognition, then quietly researches you before replying to a consultant's email.

Those two audiences want opposite things from the same homepage. A candidate wants to find relevant roles in as few clicks as possible, understand the salary, and apply without creating an account. A hiring client wants evidence you understand their sector, proof you have placed people like the ones they need, some sense of your process, and a low-friction way to start a conversation without committing to anything. Serve one well and you frustrate the other. Most recruitment websites resolve this by burying the client proposition beneath a job search bar, which is why so many agencies win almost no inbound client work from their own site.

Good recruitment web design resolves the tension structurally rather than cosmetically. The homepage splits early and clearly. Candidate journeys run through job search, sector pages, salary guides and career advice. Client journeys run through sector expertise, case evidence, team credibility, process transparency and a specific commercial call to action. Both journeys share the same brand, the same navigation logic and the same technical foundation, but neither is treated as an afterthought of the other.

The second defining characteristic is data. A recruitment website is a data-driven application wearing a marketing site's clothes. Vacancies are created in an ATS, syndicated to job boards, edited by consultants mid-campaign and closed without warning. The website has to present that constantly shifting dataset as fast, clean, crawlable pages, keep the search index accurate, and handle the awkward reality that job data is often incomplete, inconsistently formatted, and written by people in a hurry between calls.

That is why we treat recruitment web design as a hybrid discipline sitting between brand design, product engineering and search strategy. It needs the visual confidence of a brand project, the data architecture of a product build, and the search discipline of an SEO programme, delivered together rather than sequentially by three different suppliers.

Why most recruitment websites underperform

Patterns we see repeatedly when auditing recruitment sites before a rebuild.

When we audit an existing recruitment website, the problems are rarely exotic. The same handful of failures appear again and again, across agencies of very different sizes, because they all stem from the same root cause: the site was built as a brochure and then had a job board bolted onto it.

Designing for two audiences without compromising either

The dual-audience problem is the defining design challenge in recruitment. We solve it with a deliberate structure rather than a compromise, and we decide the split in the first week of a project based on where the commercial pressure actually sits.

For agencies whose bottleneck is candidate supply, typically volume, industrial, driving, healthcare and hospitality staffing, the site leads with job discovery. Search is immediate, filters are generous, roles are legible at a glance, and the apply flow is stripped to the minimum viable set of fields. Client content still exists and still ranks, but it lives one level down in a well-built sector architecture rather than competing for the hero.

For agencies whose bottleneck is client acquisition, typically executive search, professional services, technology, finance and specialist engineering, the site leads with authority. Sector expertise, named consultants with real credentials, market insight, retained process explanation and evidence of comparable mandates take priority. Candidate journeys are respected and well built, but the homepage speaks first to the person signing the fee agreement.

Most firms are somewhere in between, and the honest answer is that a homepage can serve both if the split happens above the fold and the navigation is unambiguous. Two clear entry points, labelled in plain language, beat any clever unified layout. We test the labelling, because industry jargon like talent solutions or workforce partners means very little to a hiring manager comparing three shortlisted agencies.

Underneath, both journeys draw on the same content system. A sector page carries client-facing proposition and market context at the top, live vacancies in that sector in the middle, and consultant contact detail at the bottom. One page, one URL, one set of accumulated authority, serving both audiences in the order that matches their intent.

Job board architecture, search and indexation

The technical heart of any recruitment website, and the part most often built wrong.

Every job on your site should have a clean, permanent, crawlable URL that describes the role and the location. That single decision determines whether your vacancies can ever compete in organic search for long-tail job title queries, which is where a large share of high-intent candidate traffic lives.

We render job pages server-side so search engines receive complete HTML rather than an empty container awaiting a client-side fetch. Filtered views need a considered indexation policy: valuable combinations such as sector plus city deserve indexable, linkable pages with genuine supporting content, while arbitrary filter permutations should be canonicalised or excluded to avoid flooding the index with near-duplicates.

Search itself has to be fast and forgiving. Candidates type job titles inconsistently, use abbreviations, misspell specialisms and search for salary ranges in different formats. A recruitment search that only does exact keyword matching against a job title field will return nothing for a large proportion of realistic queries. Synonym handling, fuzzy matching, salary normalisation and sensible location radius logic are not luxuries, they are the difference between a working job board and a decorative one.

Expired roles need a policy too. Deleting a job page that has accumulated rankings and links throws away value and produces a 404 for anyone arriving from a saved search or a shared link. Depending on the situation we either keep the page live with a clear expiry notice and prominent similar roles, or redirect it to the most relevant sector or location page. What we never do is leave hundreds of dead job URLs returning errors.

Finally, job posting structured data. Marking up vacancies correctly makes them eligible for Google's job search experience, and it forces a discipline on data quality that benefits the whole site: complete titles, real locations, honest salary information where you are permitted to publish it, and accurate posting and expiry dates.

ATS and CRM integration done properly

Your applicant tracking system is the operational core of the business, and the website is a public window onto part of it. Getting that connection right is where recruitment web design becomes genuine engineering work rather than templating.

We integrate with the systems recruitment businesses actually run: Bullhorn, Vincere, JobAdder, Recruit CRM, Loxo, Firefish, Mercury and Recruiterflow, alongside distribution and sourcing tools such as Broadbean, LogicMelon and SourceBreaker. Each has its own quirks, rate limits, field structures and authentication model, and each rewards experience. Knowing in advance how a given platform handles custom fields, multi-office data or reference numbers saves weeks of discovery.

The pattern we favour is a synchronisation layer rather than a live passthrough. The website holds its own normalised copy of vacancy data, refreshed on a schedule and on webhook events where the platform supports them. That means the site stays fast, stays online if the ATS has an outage, and can enrich job data with content the ATS has no field for, such as sector taxonomy, benefit summaries or consultant profiles.

Applications travel the other way, from the website into the ATS, with the file, the parsed fields, the source attribution and the consent record attached. Source attribution is the piece most often skipped, and it is the piece that lets you eventually answer which marketing channel produced which placement.

Every integration ships with monitoring. If a sync fails, if the job count drops by more than a defined threshold, or if an application fails to post into the ATS, we want an alert before a consultant notices. Recruitment sites lose real money to silent integration failures, and the fix is unglamorous operational discipline rather than clever code.

The SEO architecture behind a recruitment website that ranks

Recruitment is one of the most competitive verticals in organic search, and the competition comes from three directions at once: national job boards with enormous authority, aggregators that scrape your listings, and other agencies targeting the same sector and city terms. Winning is a matter of architecture and consistency rather than tricks.

We build recruitment sites around a topical hierarchy. A small number of pillar pages cover the broadest commercial themes. Beneath each pillar sit specific pages targeting a single keyword each, never two, because a page that tries to rank for both healthcare recruitment and nursing recruitment usually ranks properly for neither. Beneath those sit supporting content: guides, salary information, market commentary and case evidence that demonstrate depth rather than repeat the same claims.

Location pages are legitimate and valuable when they contain genuine local substance: the sectors that dominate that city's hiring market, the salary reality, the local competitor landscape, real clients in the region and consultants who actually cover it. They become a liability when they are one template with the city name swapped, which is both obvious to readers and increasingly obvious to search engines.

Internal linking is the mechanism that turns a collection of pages into a topic. Every page on this site links to related services, relevant insight articles, supporting case evidence and a commercial next step. That gives crawlers a clear map of which pages are important and gives readers a path that continues rather than terminates.

Technical foundations sit underneath all of it: server-rendered HTML, a sitemap that reflects live routes and published content, canonical tags that self-reference, correct handling of pagination and filtering, structured data across organisation, service, breadcrumb, FAQ and job posting types, and Core Web Vitals kept in the green on mobile rather than only on a developer's desktop.

Conversion: turning traffic into applications and enquiries

Traffic is the easier half. The harder and more valuable half is what happens once someone arrives, and in recruitment there are two separate conversion problems to solve.

Candidate conversion is largely a friction problem. Every additional required field reduces completion. Mandatory account creation before applying is one of the most damaging patterns still common in the sector. Mobile file upload has to work with the way people actually store CVs, which now includes cloud drives and email attachments rather than a tidy documents folder. Application confirmation should be immediate, human and specific about what happens next, because silence after applying is the most common complaint candidates make about agencies.

Client conversion is a confidence problem. A hiring manager comparing three agencies is looking for evidence that you have solved their exact problem before. That means specific case evidence rather than logo walls, named consultants with genuine sector track records rather than stock team photography, honest description of your model and fee structure, and a low-commitment first step. Book a call converts better than request a proposal because it asks for less.

We instrument both journeys properly. Application starts, application completions, drop-off by step, enquiry form submissions, calls booked, and where possible the downstream outcome once the ATS knows whether an application progressed. Optimisation without that measurement is decoration.

Then we test. Structured, hypothesis-led changes to the pages that carry the most commercial weight, run long enough to mean something. Recruitment sites rarely have the traffic volume for rigorous statistical testing on every page, so we prioritise the small number of pages where volume and value intersect, and use qualitative research and session review to guide everything else.

Performance, accessibility and the technical standard we build to

Speed is a candidate experience issue before it is a ranking issue. People search for jobs on phones, in transit, on unreliable connections, often in short windows between other commitments. A job search that takes four seconds to return results loses a meaningful share of those people permanently.

We build on modern rendered-on-the-server architecture with aggressive asset discipline: next-generation image formats with responsive sizing, fonts preloaded and self-hosted, critical CSS inlined, JavaScript split by route so a job page does not download the code for the entire site, and third-party scripts loaded deliberately rather than accumulated over time. The most common cause of a slow recruitment website is not the build, it is the six tracking and widget scripts added afterwards without anyone measuring the cost.

Accessibility is treated as a requirement, not an enhancement. We build to WCAG 2.2 AA: keyboard-operable search and filtering, correct labelling on every form control, visible focus states, sufficient contrast, sensible heading hierarchy and screen-reader-tested apply flows. For a business whose clients increasingly ask about inclusive hiring in tenders, an inaccessible careers journey is a commercial risk as well as an ethical one.

Security and reliability round it out. Managed hosting with automated backups, uptime monitoring, dependency patching, protected admin surfaces, sensible rate limiting on public forms and spam handling that does not punish genuine applicants. Recruitment sites hold personal data, and a recruitment business that leaks candidate CVs has a much bigger problem than a marketing one.

How we run a recruitment web design project

Six phases, run collaboratively, with working software visible early rather than a single reveal at the end.

Timelines, cost and how to compare quotes

Most recruitment website builds we run go live in six to twelve weeks. The variables that move that timeline are integration complexity, the number of distinct templates, whether content is ready or needs writing, and how quickly decisions get made on your side. Multi-brand group platforms and heavily customised candidate or employer portals run longer.

Cost varies with the same factors, and the honest guidance is that recruitment websites sit at the higher end of small business web projects because of the integration and search work involved. A templated site with a basic feed is inexpensive and will usually need replacing within two or three years. A custom, properly integrated, search-optimised platform is a larger investment that should serve for five or more, with the content programme running continuously alongside it.

We offer both a monthly plan, which spreads build and ongoing support across a term, and one-time project fees for firms who prefer to own the asset outright from day one. Full pricing detail, including what is included at each level, sits on our recruitment pricing page.

When you compare quotes, compare like for like on a specific list: who owns the code and design at the end, whether the ATS integration is bespoke or an off-the-shelf widget, whether individual job pages are server-rendered and indexable, whether SEO work is included or sold separately, what the support response commitment actually is, what happens to your site if you leave, and whether the price includes content production or assumes you supply everything. Two quotes that look a factor apart on price are often not describing the same product at all.

Who we work with

We work with recruitment businesses across the UK and the US, from founder-led boutiques winning their first retained mandates to established multi-brand groups replacing ageing platforms. The common thread is ambition and a willingness to treat the website as commercial infrastructure rather than a brochure that gets refreshed when it starts to look dated.

Sector-wise we have built for executive search, technology, finance, healthcare, life sciences, legal, construction and engineering, education, industrial and driving, hospitality, energy and public sector staffing. Each has different candidate behaviour, different compliance considerations and different client buying processes, and those differences shape the design rather than sitting in a paragraph at the end.

Our recruitment case studies set out the specific challenge, the approach we took, the design and technical decisions, and the outcome for each client. They are the most useful thing to read next if you want to judge whether we understand your part of the market.

Why work with SDM

We are an independent agency with studios in London and New York, and recruitment is one of the sectors we have chosen to specialise in rather than one we happen to have clients in. That specialisation is the reason we can start a project already knowing how Bullhorn handles custom fields, why a Vincere feed behaves the way it does, or which filter combinations are worth making indexable.

Every project is run by the people who sell it. You are not handed to a delivery team you have never met after signing. Strategy, design and engineering sit in the same studio, which is why integration questions get answered during design rather than discovered during build.

We are transparent about ownership. On our project engagements you own the design, the content and the code. On monthly plans you own your brand assets and content throughout, and we hand everything over cleanly if you ever decide to move on. Recruitment agencies have been burned by platforms that hold their site hostage, and we think the answer to that is not a clever contract clause but a straightforward one.

And we measure the work the way you measure your own business. Sessions and impressions are diagnostics. Client enquiries, qualified applications and placements are the point.