Context
Clients assess whether a consultancy understands their sector and can deliver quickly; candidates assess whether the roles are real, current and worth their time. The two need different content, different navigation and different conversion actions. Job listings create a second problem: they generate large numbers of URLs with short lifespans, and how expired roles are handled affects both site quality and candidate trust. Speed matters throughout: the first credible CV and the first response to an application both carry disproportionate weight.
Recruitment, from problem to plan
Recommended journey
Usually with the constraint that is capping everything else, rather than with the most visible symptom.
Named in the sector's own vocabulary, because a generic list would tell you nothing about whether we understand your business.
Mapped to a problem on the left, not offered because it is on our service list.
Answers01
Answers01
Answers02
Answers02
Answers03
Answers03
Technology
Named with the reason it is on the list. Each links to the page stating where we would use it and where we would not.
Page structure as a machine reads it
An extractable page states its answer first, uses one heading level per section, and anchors its structured data to a single organisation entity. A page that buries the answer beneath a hero cannot be extracted at all.
The opportunity
Separating the two journeys properly is unusually high-return here, because both audiences are actively searching and both currently arrive at a site designed for someone else.
Either removed with a clear message and relevant current roles, or kept only where they still serve a purpose. Leaving thousands indexed wastes crawl attention and sends candidates to dead ends.
In most cases yes: separate entry points, navigation and calls to action. They want different things, and a single blended journey serves whichever audience the homepage was written for.
Recruitment sites serve two audiences with opposite needs (clients hiring and candidates looking) and most sites are built for one while the other navigates around it.
Clients assess whether a consultancy understands their sector and can deliver quickly; candidates assess whether the roles are real, current and worth their time. The two need different content, different navigation and different conversion actions. Job listings create a second problem: they generate large numbers of URLs with short lifespans, and how expired roles are handled affects both site quality and candidate trust. Speed matters throughout: the first credible CV and the first response to an application both carry disproportionate weight.
Separating the two journeys properly is unusually high-return here, because both audiences are actively searching and both currently arrive at a site designed for someone else.
Client-facing and candidate-facing content compete in the same navigation, so both audiences read material written for the other before finding their own.
Roles are posted, filled and left. Expired listings that stay indexed waste crawl attention and disappoint candidates who arrive at a closed role.
Candidates who hear nothing assume rejection and stop applying. The reputational cost accrues quietly and shows up as a shrinking talent pool.
Connected
Other sectors
We publish a sector page only where we can name that sector's real problems in its own vocabulary. These are the rest of them.
Bring the constraint as you see it. We will tell you whether it is the one we would attack first, what we would need to look at to be sure, and whether this is work we should be doing at all.