You handle duplicate job postings across aggregators by preventing them at the source rather than cleaning them up after they spread. Distribute every role from a single authoritative feed (your ATS), stamp each posting with a canonical job ID and canonical URL, and monitor live distribution so filled or expired roles are pulled down immediately. Aggregators like Indeed and Google for Jobs do run their own de-duplication, but they act after budget is already spent and the candidate experience is already compromised.
- Distribute from one source of truth. Route all roles through the ATS feed instead of career sites, staffing partners, and third-party boards submitting the same job in parallel.
- Assign a canonical job ID. Populate the identifier field so platforms can tell true openings apart from copies.
- Use canonical URLs. Point every copy of a posting to one authoritative page.
- Retire expired and filled roles fast. Set validThrough in the past, or return a 404 or 410, so ghost jobs stop collecting applications.
- Monitor distribution in real time. Watch where each job appears across publishers and correct feeds the moment duplicates surface.
- Protect attribution. A clean, single-source feed lets you see which channel actually drove each quality hire.
Why Duplicate Job Postings Happen Across Aggregators
Job aggregators such as Indeed, Google for Jobs, and LinkedIn continuously scrape listings from many distribution channels at once – career sites, ATS feeds, third-party boards, and staffing agencies. When the same role flows in through more than one of those channels, each source looks like a separate job, and duplicates multiply quickly.
The problem has grown alongside the ghost-job phenomenon. Greenhouse’s 2024 State of Job Hunting report found that 18% to 22% of the jobs posted on its platform in any given quarter are classified as ghost jobs, and a MyPerfectResume survey of 753 recruiters found that 81% admit their employer posts ads for jobs that either do not exist or are already filled. Filled or fake roles that stay live behave exactly like duplicates, and many linger long after the opening is gone. The result is an inflated, noisy market where a single opening can appear many times over.
The main reasons duplicates appear
- Multi-channel submission. The same role is pushed to boards directly and also picked up from the career site and ATS.
- Staffing and agency overlap. Multiple partners post the same requisition independently.
- Missing or inconsistent identifiers. Without a canonical job ID or canonical URL, platforms cannot reliably match copies.
- Stale postings. Filled roles that are never retired linger as de facto duplicates.
The Problems Duplicate Job Postings Cause
Duplicates are not just untidy – they cost money, damage the candidate experience, and corrupt your data. The table below maps the most common causes to their impact and the fix that addresses each one at the source.
| Cause | Impact | Fix at the source |
|---|---|---|
| Same role submitted through several channels | One opening appears many times; sponsored budget is split across copies | Distribute every role from a single ATS feed |
| No canonical job ID or canonical URL | Platforms cannot match copies; duplicates slip through de-duplication | Stamp each posting with a unique identifier and a canonical URL |
| Candidate sees the same job on multiple sites | Multiple applications trigger ATS spam filters and ownership disputes | Consolidate distribution so each role has one live destination |
| Filled or expired roles left live (ghost jobs) | Wasted spend and eroded candidate trust | Set validThrough in the past or return 404 or 410 promptly |
| Duplicate postings across channels | Attribution breaks; you cannot tell which channel drove the hire | Use a unified, monitored feed that preserves source data |
How Platforms Handle Duplicate Job Postings
Aggregators do try to clean up duplicates, generally through three mechanisms. First, technical de-duplication uses algorithms such as shingling and machine-learning classifiers to spot near-identical text. Second, platforms match jobs on canonical IDs and key fields like title, location, and company. Third, monetization barriers require a sponsor for similar reposts, which discourages some duplication.
Google is explicit about the employer’s role here. Its JobPosting guidance tells sites to “use canonical URLs on each copy of the page” when the same job lives under different URLs, and to populate the identifier property with “the hiring organization’s unique identifier for the job.” For roles that are no longer open, Google requires timely removal – set validThrough in the past, return a 404 or 410, or strip the JobPosting markup – and warns that failure to take timely action on expired jobs may result in a manual action.
The catch is timing. Every one of these platform-side controls acts after distribution, once the budget is committed and a candidate may already have applied to three copies of the same role. Cleanup is necessary, but it is not prevention.
What Fixing Duplicate Job Postings at the Source Looks Like
The most reliable way to handle duplicate job postings across aggregators is to stop them from being created. That means consolidating distribution through a single authoritative source – the ATS – so every role carries one canonical job ID and flows through one controlled feed rather than being submitted from several places at once.
A programmatic job advertising platform makes this practical at scale. Joveo monitors live distribution across its full publisher network in real time and updates feeds immediately when duplicates or ghost jobs appear, so filled roles come down fast and each opening has one clean destination. Because the feed is single-source and monitored, attribution stays intact: you can see which publisher actually drove each quality hire instead of guessing across scattered copies.
A practical checklist
- Make the ATS the single source of truth for every requisition.
- Populate a canonical job ID and canonical URL on every posting.
- Enforce expiry: retire filled roles the day they close.
- Monitor live distribution across publishers and correct feeds automatically.
- Review attribution against the single-source feed, not per-channel copies.
For the broader mechanics of feed-based distribution, see Joveo’s guide to programmatic job advertising and the Google for Jobs ultimate guide. If duplicates trace back to how your careers pages are built, the ultimate guide to career sites covers structured, canonical job pages.
Frequently Asked Questions
Why do the same jobs show up multiple times on Indeed and Google for Jobs?
Because aggregators scrape listings from many channels at once. When the same role is submitted from a career site, an ATS feed, and a staffing partner in parallel, each source looks like a separate job, so one opening appears several times.
How do job aggregators de-duplicate postings?
They combine text-similarity algorithms such as shingling and machine-learning classifiers, matching on canonical IDs and key fields like title, location, and company, and monetization rules that require a sponsor for similar reposts. These controls act after a job is distributed, not before.
What is a canonical job ID and why does it matter?
A canonical job ID is a single unique identifier for a role, set in the identifier field of your job posting data. It lets platforms tell a genuine unique opening apart from copies, which is the foundation of reliable de-duplication.
How do I stop filled or expired roles from lingering as duplicates?
Retire them quickly. Google recommends setting the validThrough property to a past date, returning a 404 or 410 status code, or removing the JobPosting markup. Prompt expiry stops ghost jobs from collecting applications and inflating your live count.
How do duplicate postings affect attribution and budget?
Sponsored budget gets split across identical copies, and you lose the ability to see which channel actually drove a hire. A single-source, monitored feed keeps spend consolidated and preserves the source data attribution depends on.
