410 Gone 4xx

What does 410 mean?

A 410 Gone response means the requested resource used to exist but has been intentionally and permanently removed, and the server has no forwarding address. It's a stronger, more deliberate statement than 404 — where a 404 says "I can't find this" (which might be temporary, a typo, or simply unknown), a 410 says "I know exactly what you're asking for, and I'm telling you it's gone for good, on purpose."

410 is used far less often than 404 in practice — most servers default to 404 for anything missing, since explicitly tracking "this used to exist and was deliberately removed" requires more deliberate bookkeeping than simply returning 404 for "no route matches this."

How a 410 behaves

• It can carry a body — typically explaining that the resource was intentionally removed, sometimes with information about why
• It's cacheable — since the removal is permanent, caching a 410 (unlike a 404, which is often treated as needing to be checked again) is generally safe
• It's a stronger signal to search engines than 404 — search engines tend to remove 410 pages from their index more quickly and confidently than 404 pages, since 410 explicitly confirms permanence
• Retrying never helps — by definition, a 410 means the resource won't come back

Common causes

If you're building the API or website:

• You're deliberately discontinuing a product, deleting old content, or sunsetting an API endpoint, and want to communicate this more strongly than a generic 404
• A piece of user-generated content was removed for policy reasons, and you want search engines to deindex it promptly rather than potentially keeping a 404'd URL around in their index for longer
• An API version is being fully decommissioned, and 410 communicates "this isn't coming back" to integrations still pointing at it, as opposed to a 404 which might be interpreted as "currently unreachable, maybe temporary"

If you're calling an API:

• An endpoint or resource you were using has been permanently discontinued — unlike a 404 (which might warrant checking again later, or could indicate a typo), a 410 is a clear signal to update your integration immediately, as this endpoint will never return valid data again

If you're a website visitor:

• You're trying to access content the site owner has deliberately and permanently taken down — a discontinued product page, a deleted article, a closed account

How to fix it / use it correctly

As an API/website builder:

• Use 410 when you want to send a stronger "this is permanently gone, stop asking" signal than 404 — particularly useful for content you want search engines to deindex faster, or for API endpoints you're sunsetting where you want integrations to clearly understand "fix this now, it won't come back"
• Don't feel obligated to use 410 for everything that's missing — for routine "page not found" situations where you genuinely don't know if something existed or might exist later, 404 remains the appropriate default
• If content that previously returned 410 later comes back (content restored, a discontinued product relaunched), update the response accordingly — 410 implies permanence, so reversing it should be a deliberate decision

As an API consumer:

• Treat 410 as an immediate signal to update your integration — unlike 404 (where retrying later or double-checking the URL might be worthwhile), 410 confirms the endpoint won't return valid data again
• Remove references to 410'd resources from your own systems/caches, since they're confirmed permanently unavailable

As a website visitor:

• Nothing to do — the content is deliberately and permanently gone. Unlike a 404 (where checking for typos might help), a 410 confirms there's no alternative URL to find

404 vs 410

Real-world examples

Some content platforms use 410 when users delete their own content (posts, accounts, listings) specifically to signal to search engines that the removal is intentional and permanent, helping the content drop out of search results faster than it might with a generic 404. API providers occasionally use 410 for fully decommissioned API versions or endpoints — communicating more forcefully than 404 that "this isn't a temporary outage, update your integration."

SEO implications

This is 410's primary practical advantage over 404: search engines tend to treat 410 as a stronger, more confident signal that a URL should be removed from the index. For content you've deliberately and permanently removed — and specifically want out of search results as quickly as possible — 410 can achieve this faster than 404, which search engines may continue checking periodically "just in case" the content comes back.

FAQ

What's the practical difference between 404 and 410 for SEO?

Both eventually lead to a URL being removed from a search index, but 410 tends to do so more quickly and confidently, since it explicitly signals "this is permanent" rather than leaving the door open to the possibility that the content might return.

Why don't more sites use 410 instead of 404?

Tracking "this specific URL used to exist and was deliberately removed" (warranting 410) versus "this URL never existed or doesn't match any route" (404) requires more deliberate bookkeeping. Most routing systems default to 404 for anything that doesn't match, since distinguishing "deliberately removed" from "never existed" isn't always straightforward to implement.

Should I use 410 for a product that's temporarily out of stock?

No — 410 implies permanence. A temporarily unavailable product should typically still return 200 (showing "out of stock" status) or, if the page itself is genuinely unavailable, something that doesn't imply permanent removal. 410 is for products being permanently discontinued.

Can a 410'd URL ever "come back"?

Technically, yes — there's nothing stopping a server from later returning a 200 for a URL that previously returned 410. However, since 410 explicitly communicates permanence, doing this contradicts the signal you previously sent, and search engines that deindexed the page based on the 410 may take time to re-discover and re-index it if it returns.

Is 410 ever used for entire sites, like 503 sometimes is?

Much less commonly. 503 (with Retry-After) is the standard for temporary site-wide unavailability. 410 site-wide would imply the entire site is permanently gone, which is a rare and significant statement — typically reserved for sites that are genuinely shutting down for good.

Fun fact

410 is sometimes described as the status code equivalent of an obituary — while 404 simply says someone "can't be found," 410 explicitly confirms they're not coming back, which is part of why it's used so much less frequently: most situations call for the ambiguity of 404, and 410's certainty is reserved for genuinely final removals.