What is a job aggregator?

Aggregation describes collecting listings from several sources. A job board may accept vacancies posted directly by employers or recruiters. A service can combine those approaches, so the label alone does not tell you where its listings come from or how an application works.

Ask how your vacancy reaches the service, which version it displays and how corrections or closure reach that listing. Check the actual route before assuming the service copies updates from your career page automatically.

The service collects vacancy information from sources such as company career pages and job boards, then categorises and indexes it for search. A candidate enters criteria and sees the matching listings.

The details vary by service. Check which sources it uses, how a vacancy is updated and whether the application happens there or at the employer's own page.

Look at the regions, sectors and roles covered by a channel. Try the search as a candidate would and check whether the job title, location and company information lead to relevant results.

A large catalogue does not by itself explain whether the channel suits a particular vacancy. Review the reach alongside the relevance of the applications and the experience of using the listing.

Check the current terms and any charges before deciding how to use a service. Compare the cost with the recruitment outcome you intend to review, and keep the period and vacancy scope clear.

Check the quality of the listing and how outdated vacancies are handled. Read relevant feedback and verify what a candidate can find about the role rather than relying on a service's reputation alone.

Open the vacancy and follow the route to the application. Check that the candidate reaches the correct role and can understand the next step. Keep role information consistent between the listing and the application page.

The candidate experience guide can help you review the instructions and contact around that handover. Tell applicants how they will hear about progress once the application is submitted.

Consider a fictional fintech infrastructure company hiring an Implementation Manager. Its career page explains the role, location and working arrangements. A third-party search result introduces the vacancy, but the employer checks the route rather than assuming the listing is current.

The team compares the title and location, opens the application link on mobile and confirms that it reaches the specific vacancy. After the role closes, the responsible owner checks how the third-party listing is removed or updated. If the destination is wrong, they correct the source or contact the service responsible for that listing.

The fintech infrastructure page covers the wider hiring and employee journey. This example concerns a recruitment channel; it does not claim that Hire distributes vacancies to every aggregator or synchronises every external listing.

Treat the channel as one part of e-recruitment. Compare the effort and relevant applications with your recruitment goals, then decide whether to continue, adjust the listing or use another channel.

Compare channels over a defined period using the same vacancy scope. Keep application volume, relevance, cost and candidate feedback separate. Where the source is unknown or tracking is incomplete, record that limitation rather than assigning the application to a channel by guesswork.

Use the candidate journey to review discovery and the stages that follow. The employer still owns the application, communication and hiring decision even when a third-party listing introduces the role.