Job Sources & Attribution

Job listings on this site don’t originate from us — we’re a distribution and organisation layer, not the source of the vacancies themselves. This page explains exactly where listings come from, how we credit the original source, and what that means for you as a job seeker deciding whether to trust a given listing.

The three sources of job listings on this site

1. Direct employer submissions

Employers and their recruiters can submit vacancies directly to us for publication. This is the most straightforward source: the company is telling us, first-hand, about a role it wants to fill. These listings carry the company’s own description, requirements, and application link, exactly as provided, subject to our standard review (see our Job Verification & Methodology page for what that review covers).

2. Manually sourced listings

Our editorial team also adds listings we find on employer careers pages and other public job postings, where we think a role will be genuinely useful to someone using this site. When we do this, we always link through to the original posting or the employer’s own careers page — never to a copy hosted on our infrastructure pretending to be the original. Where the original source is different from the employer’s application page (for instance, we found the listing on a public job board but the actual application happens on the employer’s own site), we record both and disclose the difference on the job page itself, in a line noting where the listing was originally found.

3. Structured imports

Listings can also be added in bulk through structured data — CSV files today, and potentially live data feeds via API integrations in future. Each imported listing carries an external reference ID from its source, which we use to prevent duplicate postings and to track a listing back to where it came from if a question arises about its accuracy.

How we handle attribution on the job page itself

Every job listing page is built around two possible links, and we’re careful to keep them distinct:

• The Apply URL — this is where the “Apply on Original Website” button sends you. It is always the employer’s genuine, current application process. This is the link that matters if you want to actually apply.
• The Source URL — when a listing was originally found on a different page than the one hosting the live application (for example, an aggregator, a public job board, or a company’s general jobs page before it was migrated to a specific posting), we note where it was originally sourced, as a small attribution line near the bottom of the job page. This is about transparency, not navigation — you don’t need to visit it, but you’re entitled to know it exists.

When the source and the apply link are the same — which is the case for the majority of direct employer submissions — we don’t clutter the page with a redundant attribution line. It only appears when there’s genuinely additional context to disclose.

What we don’t do with sourced content

We think it’s worth being explicit about the boundaries here, because “job aggregation” can be done well or badly:

• We don’t rewrite an employer’s job description to obscure where it came from.
• We don’t strip out a source’s identifying detail while keeping their content.
• We don’t present a listing as exclusive to our site when it’s also posted elsewhere, unless the employer has told us it is.
• We don’t scrape and republish listings from sites whose terms of use prohibit it.

Why attribution matters for trust, not just courtesy

Knowing where a listing came from gives you a useful signal about how much to trust it. A listing submitted directly by a company you recognise, with a link straight to their own domain, carries a different level of confidence than one sourced from a public posting on a third-party board where we’re several steps removed from the original employer. We’re not asking you to distrust the second category — plenty of perfectly genuine roles are found that way — but transparency about the source lets you apply your own judgement rather than treating every listing as equally verified in the same way.

External job data feeds and future API integrations

Our import architecture is built to accept structured job data from multiple sources through a common processing pipeline — the same de-duplication, verification, and attribution logic applies regardless of whether a listing arrived as a manually uploaded CSV file or, in future, through a live API connection to a job data provider. If we do integrate a live third-party feed, this page will be updated to name the provider and describe how their data is handled, verified, and attributed, consistent with everything described above. We won’t quietly start pulling in bulk external data without disclosing it here.

How we prevent duplicate listings

Each listing carries an internal reference we use to check for duplicates — particularly relevant for imported data, where the same vacancy might otherwise be submitted more than once through different channels. When we detect that an incoming listing matches one already on the site, we update the existing listing rather than publishing a second copy, keeping the job’s original posted date intact so its “posted X days ago” indicator remains accurate rather than resetting every time the underlying data is refreshed.

Copyright and ownership of listing content

Job descriptions, requirements, and benefits text displayed on this site belong to the employer or the original source that supplied them, not to us. We display this content to help you evaluate whether a role is worth applying for; we don’t claim ownership of it. If you’re an employer and want a listing removed or corrected, or a rights holder with a concern about how content sourced from your site is being used here, contact us through our Contact page and we’ll address it promptly.

How this connects to our other policies

This page sits alongside two others that are worth reading together: our Job Verification & Methodology page explains the checks a listing passes through regardless of source, and our Expired Jobs Policy explains what happens to a listing — sourced any which way — once its closing date passes. Attribution tells you where a listing came from; verification and expiry handling tell you how much you can currently trust it.

What we look for when evaluating a new source

Before we start regularly sourcing listings from a particular public job board, careers page, or (in future) a live data feed, we look at a few things beyond the individual listing content itself: whether the source consistently provides genuine closing dates rather than leaving them blank or defaulting to a far-future placeholder, whether its listings reliably link through to real, working application processes, and whether it has a track record of hosting fraudulent or misleading postings that we’d need to filter out disproportionately. A source that fails these checks consistently isn’t one we’ll continue drawing from, regardless of how much volume it could otherwise add to the site — a smaller number of trustworthy listings is worth more to you than a larger number padded with unreliable ones.

What happens if a source stops being reliable

Sometimes a source that was reliable when we started using it degrades over time — a public job board starts hosting more spam, an employer’s careers page stops being updated promptly, a data feed starts sending stale or duplicate entries. When our periodic review process (described on our Job Verification & Methodology page) identifies this kind of pattern, we reduce or stop drawing new listings from that source, and existing listings already published from it continue to be handled under our standard rules — verified, tracked toward their closing date, and marked Expired rather than deleted once that date passes, exactly like any other listing on the site.

Frequently Asked Questions

How can I tell if a listing was submitted directly by the employer?

Direct submissions and manually sourced listings with an identical apply and source link don’t carry a separate attribution note, since there’s nothing additional to disclose. A visible “Originally listed at” line indicates the listing was found on a different page than the current application process.

Do you scrape job listings from other websites without permission?

No. Listings we source manually or in bulk are added consistent with the terms of the sites they came from, and we always link back to genuine application processes rather than hosting a copied application form ourselves.

What happens if an employer wants their listing removed?

Contact us through our Contact page with the job title and page URL, and we’ll remove or correct it promptly. Note that under our Expired Jobs Policy, a filled role is typically marked Expired rather than deleted outright, to keep the page’s URL and history intact — but we can adjust this on request where there’s a good reason to.

Will you tell me if you start using an automated job data feed?

Yes. This page will be updated to describe any live third-party data integration, including who the provider is and how their listings are verified and attributed, before or as soon as such a feed goes live.

Why does the “posted” date sometimes seem older than when I first saw a listing?

We preserve a listing’s original posted date even when the underlying data is refreshed or re-imported, so the date reflects when the role was first advertised rather than resetting every time we sync with a source.