How to stop recruitment ads for closed vacancies

Stopping ads for closed vacancies requires a tested chain from the hiring decision to the advertising platform and candidate destination. Define what counts as closed, identify every place the vacancy is advertised, and verify the stop rather than assuming that an ATS status change completed it.

Key facts

• A closed vacancy, a paused vacancy and an unavailable feed are different states.
• The advertising stop and the application-page update need separate confirmation.
• Reopening a vacancy should require a deliberate rule, not an accidental reimport.
• Closure evidence should identify the vacancy and campaign, with timestamps for each step.

What exactly should trigger a campaign stop?

Begin with the recruiting team’s definitions. A role can be filled, cancelled, temporarily paused, awaiting approval or accepting expressions of interest. These states do not all mean the same thing to a candidate. Write down which ones permit advertising and which ones permit applications before configuring a technical mapping.

Use the authoritative vacancy record as the starting point, with an owner who can resolve uncertainty. If a hiring manager tells a recruiter that a role is filled but the ATS remains open, the campaign cannot reliably infer the decision. Agree how urgent closures reach the campaign operator while the source record is being corrected.

Avoid treating missing records as automatically closed without understanding the feed. Some exports are complete snapshots; others contain only changes. A vacancy absent from a change file can still be open. The integration owner should explain the export’s meaning and demonstrate its behaviour with an example.

Which parts of the journey must stop together?

A closure has several surfaces: paid delivery, scheduled creative, job listings, landing pages and forms. Inventory the surfaces your organisation actually controls. Include agency-managed campaigns and branch accounts, because a central dashboard may not show everything a local team launched.

Surface	Closure check	Evidence to keep
Vacancy source	Correct final status and identifier	Status history or approved record
Campaign system	Matching campaign no longer eligible	Campaign identifier and state
Advertising destination	Paid delivery has been stopped	Platform confirmation and check time
Job page	Closed status is clear	Candidate-view screenshot or saved response
Application route	No misleading open application journey	Completed walkthrough of the closed state
Reopening control	Old input cannot silently restart delivery	Controlled reimport test

Do not promise that a stop request removes every historical impression or cached preview. Record the platform’s actual behaviour and the time you checked it. The practical goal is to stop further controlled promotion and give anyone arriving through an old link an accurate explanation.

What should candidates see after a role closes?

Choose a useful closed-vacancy page rather than sending the candidate to an unexplained error. State that the specific role is no longer accepting applications. Where relevant, offer a clearly labelled route to other openings, making it obvious that those are different opportunities.

Do not silently replace the original vacancy with another job while retaining the old title in the ad. That hides the reason the candidate arrived and makes subsequent reporting difficult to interpret. If you offer a talent-community option, distinguish it from applying for the closed role and have the relevant team review its information and permissions.

Check both the page and the form. A banner saying “closed” is incomplete if the embedded form still presents an application for that vacancy. Conversely, disabling the form without explaining the change leaves candidates uncertain about whether they have encountered a technical failure.

How do you test closure and reopening safely?

Use an invented vacancy in an approved test environment or controlled preview. Start with an open record, verify its mapped campaign, then close it at the source. Record when the change is exported, when the campaign system receives it and when the advertising state changes. These observations establish your configuration’s behaviour; they are not universal service levels.

Next replay an older open record. The test should reveal whether stale information can override a newer closure. Ask the implementation team how it handles update ordering and which timestamp or version governs the decision. If no reliable ordering exists, use an explicit operational hold until the source is reconciled.

Then reopen the role deliberately. Decide whether the reopened vacancy uses the existing campaign or a new one, and how reporting distinguishes the periods. Check the job facts again, because a reopened role can have changed shifts, location or requirements.

For a broader set of input checks, use the job-feed quality checklist. It covers invalid fields and duplicate records before advertising begins.

What should happen when the feed fails?

Prepare a different response for a failed download, an invalid file and a valid empty export. Those conditions provide different evidence. A failed download tells you that the latest source is unknown; it does not prove that every advertised vacancy is still open or that every role has closed.

Give the incident an owner and a review deadline. The recruiting team should identify any urgent closures through an alternative approved channel while the integration is unavailable. The campaign operator should record any manual stops so that a later recovery does not undo them accidentally.

In a hypothetical incident, two filled vacancies need immediate stopping while the rest of the feed remains uncertain. The operator stops those two identified campaigns, logs the vacancy identifiers and checks the destinations. Once the feed returns, the team reconciles those exceptions before allowing normal updates. This example illustrates a control process, not a measured Adway outcome.

Who should own the closure receipt?

Assign one person to close the operational loop, even when several teams perform the steps. A useful receipt contains the vacancy identifier, closure reason, source update time, campaign identifiers, stop confirmations, destination check and any unresolved surfaces. Mark unverified steps as unverified rather than treating a request as proof of completion.

Review recurring exceptions. A branch repeatedly advertising from a spreadsheet may need inclusion in the inventory. A feed repeatedly reopening filled roles needs a mapping or update-order fix. A landing page that stays open after campaigns stop needs a separate website owner.

Adway describes Always-On Job Ads as turning vacancy information into social recruitment campaigns. Ask to see how closure and reopening operate in your proposed setup, including any manual responsibilities. If several branches advertise related openings, the duplicate-job controls provide a complementary identity check. To walk through a vacancy lifecycle with Adway, Book a demo.

Sources

• Adway Always-On Job Ads, product description checked 2 November 2026.
• The closure receipt, test sequence and incident example are original operational recommendations, not supplier guarantees.

A vacancy is closed only when the candidate journey tells the same story.