410 Gone is an HTTP response status for a known resource intentionally removed from its origin server and unlikely to return at that URL.
What 410 Gone means
410 Gone is an HTTP response for a resource the origin server knows has been intentionally removed and is unlikely to return. RFC 9110 distinguishes it from 404: a 404 does not say whether absence is temporary or permanent, while 410 is appropriate when the origin knows the condition is likely permanent. It is a delivery decision, not a way to force a ranking change or erase copies held by other systems.
For search, the practical question is whether there is still a page that fulfils the visitor’s original need. Google says that a removed page with no similar replacement may return either 404 or 410. Its crawl documentation also says that URLs returning 4xx are not indexed; already indexed URLs are removed as Google processes the response. That describes a crawl-and-indexing process, not a guaranteed timetable.
Choose 410, 404 or 301
| Situation | Useful response | Why |
|---|---|---|
| A relevant replacement exists | 301 to that replacement | It sends people and crawlers to content that answers the same need. |
| No close replacement | 410 or 404 | Both make the URL ineligible for indexing; 410 makes intentional permanence explicit. |
| Temporary outage | 503 with an appropriate retry policy | A permanent removal response would misrepresent the state. |
| Only an unrelated destination exists | 410 or 404 | A homepage redirect does not satisfy the original request. |
A 301 is not a preservation device for every retired URL. Use it when the destination is genuinely useful for the request that brought a visitor to the old one. A 410 is honest when there is no equivalent. A temporary hide should be treated separately from permanent retirement: decide the content state first, then choose the HTTP response.
Implement and check the response
Keep a small retirement record before changing routes: the old path, its previous purpose, the decision (replacement, 410, or 404), the owner, and the date. Remove a permanently retired URL from XML sitemaps and replace or remove internal links that still point to it. Those actions keep the public inventory consistent with the response.
- Test the exact URL and one representative variation without following redirects automatically.
- Confirm that the final response is 410, not a branded page that accidentally returns 200.
- Check that the URL is absent from the current sitemap and that internal navigation no longer promotes it.
- If the URL had meaningful external links, decide whether a genuinely relevant replacement exists; document why a 301 or 410 was chosen.
- Use Search Console URL Inspection or the Page Indexing report as a later observation of Google’s handling, not as the configuration test itself.
curl -sS -o /dev/null -D - https://example.com/retired-page | head
# Inspect the status line. Expected: HTTP/... 410Avoid false removals
The common failure is making a polished ‘page removed’ template return 200. Users see an error message, but crawlers receive success; Google documents this pattern as a soft 404. Another failure is returning 410 for inventory that is merely unavailable today, or keeping the deleted URL in a sitemap. Both make the site’s signals disagree.