usdigitalmarketingindex.com SEO
How should expired job postings be removed from Google’s job-search experience?
Updated November 15, 2026
By doing one of three things to the posting’s page when the job closes, and then telling Google the page changed. Google’s documentation lists the three: make sure the validThrough property is populated and in the past, remove the page so that it returns a 404 or 410, or remove the JobPosting structured data from the page (Google’s job posting structured data documentation). Any one of them marks the job as expired. The documentation is firm that this is an obligation: “Jobs that are no longer open for applications must be expired”, and “Failure to take timely action on expired jobs may result in a manual action”. An applicant who finds a listing, prepares an application, and discovers the job closed weeks ago has been misled. Prompt removal protects them and the employer’s standing in the feature.
Expired job signals
A job is expired when applications are no longer accepted, for whatever reason.
| Event | Expired? |
|---|---|
| The closing date has passed | Yes |
| The position has been filled | Yes |
| The vacancy has been withdrawn or put on hold | Yes |
| The posting has been replaced by a revised one at a new URL | The old one, yes |
| Applications are paused temporarily | Yes, until reopened |
| The role is continuously open | No; keep the dates current and true |
The signals Google’s documentation accepts:
| Signal | What it is |
|---|---|
| validThrough in the past | The markup's own expiry date has passed |
| 404 or 410 | The page no longer exists |
| No JobPosting markup | The page remains without the structured data |
The source of truth is the recruitment system. Expiry on the website should be driven by the job’s status there, automatically, so that closing a vacancy closes its listing.
JobPosting markup and status
A simple expired-listing example. The employer and dates are fictional.
While open:
{
"@context": "https://schema.org/",
"@type": "JobPosting",
"title": "Heating Engineer",
"datePosted": "2026-09-01",
"validThrough": "2026-10-15T23:59",
"hiringOrganization": {
"@type": "Organization",
"name": "Example Heating Ltd"
},
"jobLocation": {
"@type": "Place",
"address": {
"@type": "PostalAddress",
"addressLocality": "Ashby",
"addressCountry": "GB"
}
},
"description": "Full description of the role as shown on the page."
}
After 15 October, the validThrough date is in the past. Under the first option, the posting is expired by that fact, provided the property was populated.
Requirements that follow:
| Point | Detail |
|---|---|
| Populate validThrough | A posting with no expiry date cannot expire by date |
| Use the real closing date | Do not set a far-future date to keep a listing visible |
| Filled early | If the job closes before its date, change validThrough to a past date, or use one of the other two options |
| Extended | If the deadline is extended, update validThrough and the visible page together |
| Visible page agrees | The page shows the same closing date and, after it, says the job is closed |
| No reposting tricks | Do not refresh datePosted on an unchanged job to make it look new |
What the visible page shows after expiry matters as much as the markup. Remove the apply button, state that the position is closed, and give the date.
Page retention options
Choose what happens to the URL.
| Option | Implementation | Suits |
|---|---|---|
| Remove the page | Return 404 or 410 | Postings with no lasting value; high volumes of short-lived listings |
| Keep the page, remove the markup | Page stays live, marked "This position is closed"; JobPosting structured data removed; links to current vacancies | Employers who want former listings to lead applicants to open roles |
| Keep the page and markup with a past validThrough | Markup stays; date has passed | Listings that will be reopened, or as the automatic first step before one of the others |
| Redirect | 301 to the careers page or a replacement posting | Only where a true replacement exists; a redirect to a generic page is not one of the documented expiry methods |
A reasonable sequence for an employer site:
- At closing: validThrough passes, or is set to now. The page shows “closed”.
- At the same time: JobPosting markup is removed, and the page offers links to open roles.
- After a retention period the organization sets: the page returns 410.
Considerations for kept pages:
- A site with thousands of closed listings left live accumulates pages of no use to searchers. Retire them on a schedule.
- A closed posting kept live should not look open. No apply button, no “apply now” in the title.
- Add
noindexif closed postings are kept for internal reasons and should not be found. - Job descriptions can contain personal details of hiring managers. Review what remains published.
For job boards and aggregators, expiry must follow the source. A listing copied from an employer remains the board’s responsibility to expire when the employer closes it.
Validation in Search Console
After changing the page, tell Google. The documentation says: “Keep Google informed of changes”, and for job posting URLs it recommends the Indexing API over sitemaps, “because the Indexing API prompts Googlebot to crawl your page sooner than removing the URL from the sitemap”. It still recommends submitting a sitemap for coverage of the whole site. The Indexing API can be used “to request removal of a job posting URL from the Google Search index”.
| Step | Action |
|---|---|
| 1 | Apply one of the three expiry methods |
| 2 | Notify through the Indexing API: an update notification where the page still exists, a removal notification where it returns 404 or 410 |
| 3 | Remove the URL from the sitemap |
| 4 | Verify |
Verification checks:
| Check | Method | Pass condition |
|---|---|---|
| Page state | Request the URL | 404 or 410; or 200 with no JobPosting markup; or markup with validThrough in the past |
| Markup | Rich Results Test on a kept page | No job posting item; or an item with a past date |
| Visible state | View the page | Clearly closed; no apply route |
| Sitemap | Search the sitemap for the URL | Absent |
| Indexing API | Check the response to the notification | Accepted |
| Search Console job postings report | Review after some days | No rise in errors; expired items leaving the valid count |
| Manual Actions report | Check | No action |
| The jobs experience | Search for the role and location | The closed job no longer listed |
Monitor the whole process, not single jobs.
| Measure | Target |
|---|---|
| Time between a job closing in the recruitment system and the page expiring | As near to immediate as the systems allow |
| Open listings on the site whose jobs are closed in the recruitment system | Zero |
| Postings with no validThrough | Zero |
| Postings with validThrough far in the future | Reviewed |
| Closed pages still carrying markup with a future date | Zero |
Run the second measure as a scheduled reconciliation: compare the list of URLs carrying JobPosting markup with the list of open jobs in the recruitment system.
The documentation’s warning bears repeating: failure to act in time on expired jobs “may result in a manual action”. The consequence is described there as a possibility, and the way to avoid testing it is automation.
Events with dates raise a related problem, keeping past occurrences from being presented as upcoming, covered in the guide to how recurring event pages should expose accurate dates and avoid obsolete results. The general choice between removing a page with a gone response and redirecting it is set out in the guide to when a removed URL should return HTTP 410 instead of using a 301 redirect.
The rule: when a job closes, expire it the same day by a past validThrough, a 404 or 410, or removal of the markup; notify Google; and reconcile the site against the recruitment system so no closed job stays listed.
Add your comment to this answer