LandOfferJob search
The Same Job Appears on Several Sites: Which Listing Should You Use?
Use the verified employer-selected destination for the exact role; group duplicate surfaces by requisition while keeping same-title different-role listings separate.
When the same job appears on several sites, identify the employer's actual opportunity and use the application destination the employer currently selects for it. Compare requisition, location and duties before treating listings as duplicates. Several discovery pages may lead to one opportunity. Identical titles may also describe different roles.
LandOffer publishes this guide and offers job-search tools. Official public publishing and job-data documentation was checked on October 8, 2026. Miles and WrenCircuit below are fictional teaching data, with no real application submitted. Keeping one clear record in your current tracker is sufficient. For other roles to compare, browse jobs posted within the last 24 hours, then follow the employer's current instructions.
Discovery page, job identity and application destination
A discovery page helps you find an opportunity. It might be a general job board, search result, recruiter post or the employer's careers page. The underlying opportunity has its own identity: employer, requisition where visible, location, team and responsibilities. The application destination is where the employer directs candidates to submit for that identity.
These layers do not always share a domain or URL number. An employer may link to an external applicant system. Several public posts can advertise one underlying job. Google’s job-posting guidance distinguishes role data and application paths, while Greenhouse documents multiple posts for one job, including different locations, titles and languages.
That means a different board URL is not enough to identify a different opening. Nor does an identical title prove a duplicate. Map each saved page to the employer's role and selected destination, then choose the correct route once.
What to compare before choosing
Start with the employer's current careers page when it is available. Find the exact role or search the visible requisition. Compare the material details rather than relying on the board's company name and headline.
| Field | Stronger comparison | Common mistake |
|---|---|---|
| Employer | Actual hiring organization and any stated recruiting partner | Assuming a similarly named company is the same employer |
| Requisition | Employer-visible identifier in context | Treating every numeric URL path as the employer requisition |
| Location | City, country and work arrangement | Merging remote and location-bound roles from the title alone |
| Team and duties | Substantive work and required background | Ignoring a backend versus infrastructure distinction |
| Apply path | Current link selected by the employer | Choosing a stale redirect because it appears first |
| Special instructions | Referral, recruiter or board-specific route explicitly required | Removing an instructed referral route or applying twice to preserve it |
If the employer does not publish a requisition, record the remaining fields and acknowledge the identity uncertainty. You can still assess title, team, location and duties. A blank identifier does not justify inventing one from a URL.
Greenhouse's Job Board API documentation distinguishes a public post identifier from an internal job identity and provides the public destination. Candidates do not need to query an API to apply. The relevant lesson is that different identifiers can refer to different layers; use the employer's visible instructions rather than assuming every number means the same thing.
Miles maps four surfaces to two opportunities
Miles finds four WrenCircuit listings. A general board and a search result show Software Engineer in Austin. A professional-network listing uses the same title in Boston. The employer careers page lists both opportunities. His initial tracker contains four saved entries because he collected each discovery surface separately.
He opens the employer pages before selecting an application route. The Austin role is WC-301, focused on backend API development. The Boston role is WC-318, focused on infrastructure operations. Their titles overlap, but the requisitions, locations and duties differ. He now has two opportunities, not four and not one.
His completed surface map is below. It is authored teaching material, not observed data from a real employer. No route acceptance, duplicate-handling behavior or candidate outcome was tested.
| Saved surface | Compared employer identity | Destination decision |
|---|---|---|
| General board's Austin listing | WC-301 / Austin / backend APIs | Store as a discovery source for WC-301 |
| Search result's Austin listing | WC-301 / Austin / backend APIs | Same opportunity; do not create a second application |
| Network listing's Boston role | WC-318 / Boston / infrastructure operations | Keep as a distinct opportunity |
| Employer careers page | Separate WC-301 and WC-318 role pages | Follow the chosen role's current Apply link |
Miles wants the Austin backend role. His chosen route is specific: WrenCircuit careers, then the Austin Backend Software Engineer page displaying WC-301, then that page's current employer-selected application form. He checks that the form still names the Austin role before selecting his attachment. The Boston WC-318 form is not an interchangeable destination.
He retains one WC-301 tracker record, with the employer source as the current role reference and the board/search links as discovery history. The saved source descriptions and useful notes from the two WC-301 entries are copied into its retained record before cleanup. WC-318 remains separate with its own fit assessment and status. No Applied event is copied between them.
This is a completed destination choice, not a generic instruction to prefer company websites. If the employer's Austin page deliberately routes applicants to a board-hosted form, that selected route is the one to inspect. Employer-selected does not mean employer-domain only.
Follow the employer's route without losing context
An employer's Apply link can lead to Greenhouse, Lever, another applicant system or an explicitly selected board flow. Compare the destination's employer, title and location with the source. The external hostname alone is not evidence of a problem when the chain originates from the verified employer page.
If the board route and employer route reach the same identified form, Miles does not need to submit through both. He can choose the current employer-selected path and preserve where he discovered the role in his tracker. If the paths differ, he checks whether the employer gives an instruction that explains the difference.
An employer may ask candidates to use a recruiter, referral link or particular campaign route. Those instructions can matter even when another public form is accessible. Follow the legitimate current instruction rather than stripping parameters or replacing the route merely because a shorter URL looks cleaner. The goal is the correct opportunity and process, not a universally preferred hostname.
Miles has no special route instruction for WC-301 in the fictional case, so he uses the current Austin page's Apply link. If he later receives a legitimate referral instruction for that same requisition, he clarifies how to associate it with his existing application rather than sending another application simply to obtain a referral source label.
A completed pre-application record
Miles's WC-301 note reads: “Chosen opportunity: WrenCircuit WC-301, Austin, backend APIs. Board and search surfaces matched to this role. Current employer page's Apply link selected; destination title and location checked. Intended material: Miles-WrenCircuit-WC301.pdf. No submission yet. WC-318 Boston infrastructure remains a separate role.”
This record preserves the answer to “which listing should I use?” without pretending that all public surfaces disappeared. If he opens the search result again, he can see that it already maps to WC-301. If someone sends the Boston listing, he can assess it without confusing its stage with the Austin role.
His cleanup asset is equally concrete. One WC-301 record owns the role identity, current source, selected destination, materials and actual events. The two duplicate discovery entries become source notes rather than extra application tasks. Before removing entries, save a copy of the working history and check the retained record's source links and notes. WC-318 retains its own record. Four saved surfaces become two identified roles, with one selected application route for the role he currently wants.
The intended resume is reopened before attachment. Miles checks that its project emphasis is backend APIs and that he has not selected an infrastructure-focused file simply because both filenames start with WrenCircuit. Destination identity and document identity must agree; resolving duplicate listings does not solve attachment selection automatically. The final filename makes Miles's Austin choice recoverable when he returns to the record later.
After an actual submission, he would record the confirmation event and any useful acknowledgment reference in WC-301. A tracker label or a clicked Apply button is not that event. This article's example ends before submission, so the record remains a preparation record.
What if the listings disagree?
A board may show an older description, salary range, location or date than the employer page. Preserve the difference and use the current employer instructions to decide how to proceed. Do not silently combine incompatible details into a new description that neither source publishes.
For Miles, a board describing WC-301 as fully remote while the employer page names Austin would create a fit question. He would check the employer's wording and seek clarification if the distinction changes his decision. A board's convenient filter is not permission to assume a different work arrangement.
If the employer source says the role is unavailable, another board's active-looking entry does not establish that the employer is accepting applications. Google instructs publishers to manage expired job information, but an index or copied listing can lag. Look for an employer-selected current route rather than treating search visibility as acceptance.
If the employer destination cannot be reached publicly because of login, a temporary error or regional access, record the obstacle. You may be unable to settle availability from a public read. That result preserves the specific obstacle without guessing whether the role is fake or open. An unresolved route can stay unresolved while you assess other opportunities.
If a staffing firm is the named recruiter, the route may legitimately differ from the end employer's careers page. Read who is recruiting and what process is specified. This guide does not establish that every recruiter listing is authorized; it gives you a way to compare the stated organization and role before sharing materials.
Check earlier applications before starting another
Duplicate discovery can conceal a prior submission. Search your tracker or legitimate employer account for the role identity before beginning again. A previous application to WC-301 is different from a previous application to WC-318. The distinction depends on the opportunity, not the broad company name.
If you already submitted for the same role, use the employer's update or contact instructions if you need to add materials. Applying through a different board does not establish a new benefit or a clean restart. Duplicate handling differs across employers and systems; no universal rule about repeated applications is supported by the public publishing documentation.
If you applied to a distinct requisition, evaluate the new one on its own merits. Do not transfer an Applied status from the old record. Likewise, if your first attempt never reached confirmation, check whether it was incomplete before describing the next attempt as reapplication. Preserve what actually happened.
Miles finishes with a clear answer: WC-301's current employer-selected Austin application destination is the route for his chosen backend opportunity. WC-318 remains separate. The board and search pages remain useful discovery evidence, not separate reasons to submit. Keep the tracker that can preserve this map. For other opportunities, browse jobs posted within the last 24 hours and identify the employer's role before choosing its application route.