410 Gone

410 Gone is an HTTP status code that tells a browser or search engine a page has been permanently and intentionally removed. It is a deliberate signal, distinct from the more common not-found response, and its meaning is unambiguous: the resource once existed at this address, it is gone on purpose, and it is not coming back. Where a not-found response leaves open the possibility that a page might reappear or was never there at all, a 410 states plainly that the removal is final.

The mechanics are straightforward. When a server is configured to return 410 for a particular address, any request for that page receives the 410 code instead of the page content. The server is effectively announcing that the resource has been retired. Search engines treat this as a strong, clear instruction. Because the code communicates intent so directly, search engines tend to remove a 410 page from their index more quickly and confidently than they would for a page that merely returns not-found, where they might keep checking back in case the page returns. In practice, a 410 accelerates the process of clearing obsolete content out of search results.

The 410 status is part of the same Hypertext Transfer Protocol specification that defines the rest of the web's status codes. Its designers included it specifically to cover a situation that the not-found code handles only vaguely: the case where the owner of a site knows a resource is permanently gone and wants to say so. The distinction between "I cannot find this" and "this has been deliberately removed" is subtle but useful, and 410 exists to express the latter with precision. It has always been less commonly used than its not-found cousin, largely because many site owners are unaware of it or default to the more familiar code.

For a business, 410 is a tool for cleaning up decisively. When products are discontinued, campaigns end, or old sections of a site are retired for good, returning 410 for those addresses helps search engines drop them promptly, keeping search results current and steering visitors away from content that no longer serves them. This is preferable to leaving stale pages lingering in search results or letting them return a not-found code that search engines may revisit repeatedly. Used correctly, 410 keeps a site's search footprint tidy and aligned with what the business actually offers today.

The nuance, and the main risk, is that 410 is permanent by design, so it should only be used when there is genuine certainty that a page will never return. Applying it to a page that is merely temporarily offline, or that might be revived later, throws away that page's accumulated value and tells search engines to forget it. If content is moving to a new location, the right response is a redirect, not a 410, so that visitors and ranking value transfer to the new page rather than vanishing. The 410 code relates closely to the broader family of status codes, to the not-found response it refines, and to redirects, which serve the opposite purpose of preserving a page's destination rather than declaring its end. Reserved for truly retired content, 410 is a precise instrument for permanent removal.