Expired job still on Google? Fix the posting at its source
Remove expired jobs from Google's job search by checking the job URL, application flow, structured data, and feed that can recreate a closed vacancy.
By Crawlito · 6 min read
In short
- A vacancy that no longer accepts applications needs a matching change on its public job page.
- Google documents expiry through a past validThrough value, removal of the markup, or removal of the page.
- A recruiting platform can regenerate an expired posting after a manual CMS correction.
On this page
When an expired job still appears in Google’s jobs experience, inspect the individual vacancy, its application link, and the JobPosting data actually delivered to visitors. Close the listing in the system that publishes it and use a documented expiry method for the public page. The right response depends on whether you plan to keep the vacancy as an archive. Google’s job posting guidelines
Follow the vacancy a candidate actually saw
Start with the exact URL in the reported result. A candidate may reach a corporate careers page, an applicant tracking system on another host, or a recruitment partner's copy. Record which organization controls the first landing page and where its Apply button leads. Follow the public path up to the point where the system describes whether the job is open. You can test an expiry without submitting a candidate's details.
Record a stable identifier from the recruiting system alongside the public title. “Support engineer” can refer to several openings at the same company. A city, posting identifier, department, or requisition code can distinguish an old opening from a genuinely active position. If the public page omits those details, ask the hiring team to identify the matching record before closing anything.
Compare the public statement with the application flow. A prominent “Applications closed” alert alongside a working form creates one kind of error. A page that advertises a role as open but sends candidates to a generic list of positions creates another. A correct result should give a person the same answer about availability throughout the journey. Save the wording and the time at which you observed it.
Decide what the old URL should do
Google describes several ways to expire a job: set validThrough to a past point, remove the job posting markup, or remove the page so it returns a genuine 404 or 410. Choose according to the ongoing purpose of the URL. An HR team may keep a factual archive for former applicants. Such a page should clearly say that applications are closed, remove or disable the old application action, and implement the chosen expiry method.
A listing with no enduring use can return a missing-resource status. Check the returned HTTP status after the careers platform's rewrite rules have run. A helper that redirects every missing job to the careers homepage changes the evidence a crawler receives, even if a person can still browse other openings. The soft 404 guide explains how generic fallback pages can mask a deletion.
If the team knows the real deadline while the job is open, store it with the correct timezone and publish it consistently. A date-only field can mean different things to a hiring team and a server running in UTC. Define when applications actually close, test a deadline immediately before and after that point, and inspect the public representation. The job must also expire when the role fills ahead of its original deadline. A date months in the future does not describe an opening that ended this morning.
Find which publisher still considers the job active
Trace one record through the recruiting system, any export, the career-site database, the rendered job page, and the sitemap entry. At each step, record the identifier, active state, expiry time, and last successful update if available. This reveals whether the role was never closed upstream or whether the closing event disappeared between systems. A one-time CMS edit can seem effective until the next overnight import republishes the old state.
Inspect the delivered JSON-LD for every matching node. A theme may render the visible job details correctly while an SEO component emits structured data from a cached copy. Look inside graph arrays as well as separate scripts. Check that the entity is attached to the individual posting and that the active job listing page does not generate individual job markup for every item in a carousel. See the JSON-LD troubleshooting guide when the testing tool cannot parse a block.
| Observation | Next place to check |
|---|---|
| Archive says closed, JSON still says open | Template or structured data generator |
| Page and markup are closed, partner copy remains active | Distribution feed and partner import |
| Deleted URL returns a careers homepage with success | Router or CDN fallback |
| The same job comes back after each import | Source status mapping or update ordering |
Test the full closing cycle after release
Pick a closed vacancy, an active neighbor in the same department, and a deliberately missing test slug. Fetch all three as anonymous visitors. The closed example should match the selected policy, the active job should still allow applications, and the missing path should behave like a missing resource. A rule that disables the Apply button across the whole career site could pass a test that looks only at the closed position.
Check the public response once more after the next import or cache refresh. If the job page is being kept, inspect it with the Rich Results Test to see which entities are present. If the URL was deleted, inspect the actual status and update your job sitemap or open-roles feed accordingly. Keep a link from any useful archived page to currently available openings, with wording that makes the distinction clear to an applicant.
Google's Indexing API supports eligible job posting pages. Its notification mechanism can help communicate updates or removals for those pages. Follow the API's documented URL state for the notification you send and check the server response before doing so. The Indexing API documentation describes the difference between an update and a deletion. A successful notification does not itself close an open application or change access to the page.
Check for a race between closing and publishing
Suppose a recruiter marks a position as filled at lunchtime. A careers importer later replays a morning export that still lists the job as open. If the importer uses only the time it received the file, the stale update can reverse the closure. Compare the source record's change time or revision with the import time and the public page revision. A sequence like this explains why the role looked correct during one test and reappeared later.
Have the integration owner replay the relevant updates in a test environment, including duplicate delivery of the older export. Check that the latest authoritative job state survives both runs and that a genuinely reopened role follows the team's explicit reopening process. Inspect the affected URL after each step through the same public route that applicants follow. The guide to checking the response with GET is helpful when a quick status-only monitor sees a generic success for both open and closed jobs.
Frequently asked questions
Can the archived vacancy stay visible on the company website?
Yes. Clearly identify the position as closed and apply an expiry method Google documents for retained pages. Check both visible content and markup.
Can we reuse the URL for a different job?
A distinct address and requisition identifier make a new opening easier to share, measure, and close accurately. Reusing a URL also complicates old candidate communications and partner feeds.
What if Google shows a third party's copy?
Check which publisher owns that URL and whether your feed still distributes the vacancy as active. Provide the owner with the exact job identifier and closing status.
Inspect the careers template
Use the free page check on a public job URL to inspect its delivery and structure. For a removed listing, retain the direct response alongside the test of a still-active job.
Filed under Structure and schema. Topics: structured-data, google, indexing, troubleshooting