What Is 410 Gone?

How 410 Gone Works

When a server returns a 410, it is making a stronger statement than a plain “not found.” MDN defines the code precisely: “The HTTP 410 Gone client error response status code indicates that the target resource is no longer available at the origin server and that this condition is likely to be permanent.” It is standardized in RFC 9110, the current HTTP semantics specification, alongside the other client-error codes.

The permanence is the whole point. A 404 error reports that a resource is missing but says nothing about why or for how long — it could be a typo, a temporary outage, or a page that will return. A 410 removes that ambiguity: this resource existed, it was taken down deliberately, and it is not coming back. MDN spells out the follow-on behavior it expects: “Clients should not repeat requests for resources that return a 410 response, and website owners should remove or replace links that return this code.” The response is also cacheable by default, so a client or cache can safely remember the “gone” verdict rather than re-check the URL.

MDN also gives the decision rule directly: “If server owners don’t know whether this condition is temporary or permanent, a 404 status code should be used instead.” In short — 410 requires certainty. Use it only when you actually know the page is retired for good.

410 vs 404 for Google

Here is where expectations often outrun reality. Many SEOs believe a 410 forces Google to drop a URL faster than a 404. Google’s current documentation does not support that. It states that “all 4xx errors, except 429, are treated the same: Google crawlers inform the next processing system that the content doesn’t exist.” For both codes, the outcome is identical — the indexing pipeline removes the URL if it was previously indexed, and crawl frequency for it gradually decreases. Google’s guidance even adds the nuance that “while Google treats these status codes the same way, keep in mind that they’re semantically different.”

That nuance is the real reason to choose 410: semantic honesty, not a de-indexing speed hack. A 410 communicates intent clearly to every consumer of your site — browsers, caches, third-party crawlers, and archivers — even if Google’s handling is the same as for a 404.

Example of 410 Gone

Consider a documented, real-world use of the code: retiring a product that will never be restocked. A retailer discontinues a seasonal item at /products/holiday-2024-bundle. Because the URL is being removed on purpose and permanently, the server is configured to answer future requests with HTTP/1.1 410 Gone rather than a 404.

Following the documented behavior, the effects line up with the code’s meaning. Per MDN, well-behaved clients “should not repeat requests” for that URL and any internal links to it should be removed or replaced. Per Google’s status-code guidance, Googlebot receiving the 410 informs the pipeline that the content doesn’t exist, so the previously indexed bundle page is dropped from the index and re-crawled less often over time — exactly as it would be for a 404, but now with an unambiguous “permanently gone” signal attached. The retailer has told the entire web, in one status code, that this URL is closed for good. Had there been a genuine replacement bundle, the right move would instead have been a 301 redirect to that successor — 410 is for endings, not moves.

Frequently Asked Questions

The Bottom Line

410 Gone is the definitive version of a missing-page response. Where a 404 leaves room for doubt, a 410 declares that a resource was removed on purpose and will not return, telling clients to stop asking. Google acts on it the same way it acts on a 404, so its value is clarity rather than speed: use it when you are certain a page is retired for good, and reach for a 404 whenever that certainty isn’t there.