How to Publish Branch Hiring Pages Without Leaving Expired Jobs in Search

Retail, restaurant, education and healthcare chains often recruit continuously, but hiring demand changes by outlet. A central careers page may list dozens of vacancies while local pages continue showing positions that have already been filled. This creates a trust problem for candidates and unnecessary work for branch managers.

Model a vacancy as a lifecycle, not a paragraph

Use explicit states: draft, approved, published, paused, filled, withdrawn and archived. Each vacancy should have a unique requisition ID, employing entity, work location, job title, publication date, closing date where applicable, application destination and responsible recruiter. A branch page can display a vacancy only while its authoritative record is active. Do not infer that a job remains open because its URL still returns HTTP 200.

A location careers page and an individual job page serve different purposes. The location page explains the branch and links to current opportunities; a single-job page contains the complete description and application route for that requisition. Avoid adding job structured data to a page that merely lists many vacancies. Google's JobPosting guidance says markup belongs on pages for individual jobs, and expired postings should be removed or have their expiry handled according to the documentation.

The close-out sequence

When a recruiter marks a role filled, the ATS should trigger a website task. The website owner removes it from active listings, confirms the job URL's intended disposition, updates relevant sitemaps if used and checks internal links. If a job URL is retained for candidate communication, its page must not continue presenting the vacancy as open. Choose redirects or retirement based on whether a genuinely equivalent replacement exists; do not redirect every old vacancy to an unrelated careers homepage simply to preserve a URL.

Search presentation is not guaranteed

Valid structured data can make an eligible job page available for a search feature; it does not guarantee that Google will display a rich result. The visible page and markup must agree. A role should never be marked as open in structured data after recruitment has closed, and a job page should not promise an application route that no longer works.

Exception report for regional HR

Each Monday, list active vacancies older than the agreed recruitment window, job pages returning errors, closed requisitions still linked from branch pages and postings with a mismatch between ATS and website status. Regional HR owns the vacancy truth; digital owns publication mechanics; branch managers confirm the work location and hiring status. This division prevents local teams from editing technical markup directly while preserving their authority over operational facts.

Source notes

• Google Search Central — Job posting structured data — Official technical guidance for single-job pages, expiry and markup eligibility.