Why the same job appears once
A role carried by several boards collapses into one row marked with how many others had it, and the employer's own link wins where there is one.
The same role posted to several boards is matched on job title, company and location, with accents, punctuation and company legal suffixes normalised, so "AGS Ltd" and "AGS" are one company. You see one row, marked "Also on N more", so you do not read the same job four times.
- The first copy wins and the order is untouched, so collapsing duplicates never disturbs the relevance ranking.
- The employer’s own posting is preferred. When a company careers page and an aggregator both carry a role, the employer’s link is the one you get and the aggregator becomes one of the others, because that link goes to the source.
- The same city written differently is merged. "Villeneuve-d’Ascq, Lille" and "Villeneuve-d’Ascq, HDF, FR" are one place. Genuinely different places are not merged.
Where it stops: Matching is textual, so "London" and "London, England" are still two identities and both can appear. Doing better needs a gazetteer we do not have, and merging two places that only look alike would be a worse error than showing a job twice.
Related
- Reading a listingThe full description, the skills we pulled out of it, where it came from, and a direct link to the employer's own posting.
- Where results come from29 named job boards and aggregators, plus openings pulled straight from companies' own careers pages.
- Sorting resultsFour orders: best match, newest, salary and CV match. Sorting only reorders, it never removes a row.
Did this answer your question?
Still stuck? Ask us directly, and mention this article so we know where to start.