Docs Job Posting Key concepts Job ad duplication

Job ad duplication

This content is still in draft.

As we enable hirers to advertise positions via more than one solution at once, there will be scenarios where job ads with the same content will be posted to SEEK. Duplication fragments analytics and candidates across multiple job ads, making it harder to track performance and manage candidates effectively, and provides poor return on investment, as our search and recommendation models will detect and suppress duplicate job ads.The SEEK marketplace has layered controls in place to manage duplicate job ads, with stricter deduplication rules applied to automated posting solutions such as Ad Sync.

Managing hirer duplication

Provide wayfinding for hirers to view existing job ads for a given position before posting a new one. This is especially important if they have access to an automated posting solution like Ad Sync.Your software may already support this if its job posting flow begins on a job requisition view:

Senior business analystAUD 100,000–130,000Perth, Australia

Job ads

Reference	Title	Source	Status	Created
AD-123	(Ad Sync) Señor business analyst	SEEK	Active	2048-01-01
AD-124	Experienced BA wanted	Job board X	Active	2048-01-02

If hirers can navigate to your job posting form without viewing the job ad list, provide a notice that indicates whether the given position has existing job ads, and a link that allows the hirer to jump to the list.

Post a job ad

Job requisition

You have existing job ads for this position. View and edit your job ads.

Job title

…

Managing system duplication

Requests that carry a Job Posting mutation must be idempotent . This removes the risk of unintentionally posting duplicate job ads when your software needs to retry a request due to an error.A unique idempotencyId is required when posting a job ad. We recommend that you use a generate a new v4 UUID before sending the first request, and to reuse that identifier on all subsequent retries for the same job ad. This provides a common thread across all attempts, making it easier to manage incidents and avoid manual triage of requests that initially experienced transient errors but eventually succeeded.If your software has already posted a job ad with the same idempotencyId, the SEEK API will return a PostPositionPayload_Conflict or PostPositionProfileForOpeningPayload_Conflict result in accordance with our mutation conflict convention. If your software was retrying a job posting request, you can treat the conflict result as a success as it indicates the job ad has already been posted.The SEEK API deduplicates job ads posted by your software based on their idempotencyIds. Your software should never reuse an idempotencyId when posting a different job ad; this may result in subsequent job ads being missed or other unexpected behaviour. Your identifiers are isolated and will not conflict with those generated by other recruitment software providers.Ad Sync provides similar handling to ensure a single job ad exists based on a stable identifier that your software provides for a given position, seekPartnerPositionId. Refer to Share positions for further details.

Consolidating job applications

The hirer experience on the SEEK Employer website is currently job ad centric rather than position centric. Hirers that use SEEK’s Apply Form will rely on your software to implement Optimised Apply and provide a consolidated applicant list view across multiple job ads.Include consistent references across posting sources to allow your software to associate applicants across multiple job ads with the same position.

Key concepts: Application methods

Job Posting: Ad Sync