Should you really return a 404 or 410 for expired job postings?

Why does Google emphasize 404/410 status for expired listings?

Google treats job pages as content with a limited lifespan. Once the position is filled or removed, the page loses all relevance for the user. Leaving these pages active with a 200 status clutters the index with outdated content, degrading the user experience and the overall site quality in Google’s eyes.

The 404 (Not Found) status indicates that the resource no longer exists, either permanently or temporarily, while the 410 (Gone) explicitly specifies that the removal is definitive. Google typically de-indexes a 410 faster than a 404, as it considers the signal to be stronger — but in practice, the difference is marginal for most sites.

Does the indexing API really change the game?

The Google indexing API (initially designed for job postings and livestreams) allows you to actively notify Google that a page needs to be recrawled or removed from the index. Specifically, you send a POST request with the page status — "URL_DELETED" to signal a removal.

This is much faster than waiting for Googlebot’s natural crawling, which can take several days or even weeks on low-priority URLs. For a recruitment site with hundreds of listings expiring each day, this API is an essential index-cleaning tool. However, be careful: the API does not replace the HTTP status; it accelerates it.

What’s the practical difference between a 404 and a 410?

The 404 is the universal status for "not found." Google crawls it regularly to check if the page has been restored. The 410 indicates an intentional and permanent removal — Google crawls it less frequently, or may completely abandon it after a few visits.

For an expired job listing, the 410 is technically more accurate. But honestly? Most platforms use a 404, and it works very well. The real issue is consistency: if you choose a status, apply it uniformly and promptly after the job’s expiration.

• A 404 or 410 status prevents cluttering the index with outdated listings
• The indexing API speeds up the removal of pages from Google’s index
• The 410 is more explicit than the 404, but the treatment difference is minor
• Never leave an expired posting as 200 OK with a message "position filled"
• Don’t systematically redirect to the homepage or a listings page — it’s a soft 404

Is this directive consistent with observed practices on the ground?

Yes, and it confirms what SEO professionals have been seeing for years. Google increasingly penalizes sites that accumulate dead content in their index. On large recruitment sites, allowing thousands of expired listings to remain as 200 OK creates a dilution effect: crawl budget is wasted on unnecessary URLs, quality signals collapse, and new listings take longer to be indexed.

I’ve seen sites lose 20-30% of organic visibility simply because 70% of their indexed pages were outdated listings. After cleaning up with 410s and utilizing the indexing API, the site rebounds within weeks. The signal is clear: Google wants a clean index.

What nuances should be applied to this recommendation?

First nuance: not all expired content warrants a 410. A junior developer job posting has no archival value — 410 it without hesitation. But if you have an HR blog with articles on "how to hire a senior developer," keep them at 200 even if they’re 2 years old. The difference? One is ephemeral transactional content, while the other is enduring informational content.

Second nuance: redirecting to a similar page can work, but it must be relevant. Redirecting a "Project Manager Lyon" listing to a page listing all project manager positions in Lyon is fine. Redirecting to the general homepage, however, is a soft 404 that Google will treat as such. [To be verified]: Google does not clearly document the threshold of "acceptable similarity" to avoid a soft 404 — it's case by case.

In what cases does this rule not apply?

If you have a niche site where each listing generates long-term SEO traffic after its expiration (typically via searches like "project manager salary in Lyon" where users are looking for information, not necessarily applying), you can transform the listing into archived content. Remove the "apply" button, add a note "position filled," but keep the content visible with a 200 status.

Another exception: sites with strong seasonality. If a listing returns each year (seasonal tourism, harvest, etc.), a temporary 404 may suffice, with the URL reactivated the following year. But beware: if you leave the URL as a 404 for 6 months, Google will de-index it — you will need to actively push it back to reactivation.

What concrete steps should be taken on a recruitment site?

First step: automate the transition to 404 or 410 as soon as a listing expires. No 30-day grace period, no "position filled" page that remains as 200. The listing is closed? The page immediately changes to 404/410. Technically, it’s a flag in the database that triggers the HTTP status change on the server side.

Second step: integrate the indexing API into your workflow. When a listing expires, automatically trigger a POST request to the API with the status "URL_DELETED". This drastically speeds up index cleaning, especially if your site has a low crawl budget. That said, the API isn’t magic: if your quota is saturated, Google will prioritize according to its own algorithm.

What mistakes should you avoid at all costs?

Mistake #1: systematic redirection to the homepage. It’s a disguised soft 404. Google sees that the original URL does not match the destination content and treats the redirection as a 404. The result: you get the worst of both worlds — no clear signal for Google and a poor user experience for the visitor who lands on a generic page.

Mistake #2: leaving expired listings as 200 with a simple message "this position is filled". Google crawls, sees nearly empty or duplicated content (if you display the same message on all expired listings), and classifies it as thin content. On a large site, this could mean thousands of pages that negatively impact the overall site quality.

Mistake #3: failing to clean up the XML sitemap. Your expired listings turn to 404, great. But if they remain listed in the sitemap, you are telling Google "hey, crawl these important URLs" while they return an error. The result: wasting crawl budget. Remove expired URLs from the sitemap at the same time you change their HTTP status.

How can you check if your site is compliant?

Use Google Search Console, Coverage section. If you see a spike in 404s after implementing the recommendation, that’s normal — Google discovers that your expired listings are no longer available. What is NOT normal is to see thousands of soft 404s: this means your redirects or "position filled" pages are implemented incorrectly.

Also check the ratio of indexed URLs vs crawled URLs. On a healthy recruitment site, you should have a ratio close to 1:1 — all active listings are indexed, and expired ones are out. If you have 5,000 active listings but 20,000 indexed URLs, you have a cleaning issue. A run of Screaming Frog on your sitemap + an export from Search Console will give you a clear view.

• Automate the transition to 404 or 410 immediately upon expiration of a listing (no delay)
• Integrate the indexing API to actively notify Google of removals
• Remove expired listings from the XML sitemap in real time
• Avoid generic redirections to the homepage (soft 404)
• Monitor the Coverage section of Search Console to detect soft 404s
• Check the ratio of indexed URLs / active URLs to identify index leaks