Client Error

HTTP 410 Gone

The resource has been permanently removed and will not return — the explicit "deleted forever" status code, processed by search engines faster than 404.

Check a URL for HTTP 410

Paste any URL to see whether it currently returns 410. Runs a live HTTP probe and follows redirects.

TL;DR

A 410 means "permanently deleted, never coming back" — the explicit version of 404. Google deindexes 410 pages faster than 404s, which is what you usually want when removing content. Use 410 for retired products, deleted blog posts, and discontinued campaign URLs. Use 301 instead if the content moved to a new URL.

What does HTTP 410 mean?

HTTP 410 Gone is the deliberate, explicit version of 404. Where 404 means "I can't find this right now," 410 means "this used to exist and is gone forever — stop asking." Search engines treat the distinction seriously: Google deindexes 410 pages within days, while 404 pages can linger in the index for weeks as Google verifies the absence is permanent. Use 410 for content you have deliberately deleted with no replacement: discontinued products, retired API endpoints, deleted blog posts, expired campaign pages. Use 404 only when you genuinely don't know if the URL will be valid in the future.

Common Causes

•Blog post or page deliberately deleted with no replacement
•Discontinued product on an e-commerce site
•Retired API endpoint after a deprecation period
•Expired marketing campaign or seasonal landing page
•User profile or post deleted by GDPR erasure request
•Sensitive content removed for legal/compliance reasons (use 451 if specifically legal)

How to Fix It

1.If the content moved to a new URL, return 301 to the new URL instead — preserves link equity
2.If the content is genuinely gone, return 410 explicitly — Google deindexes faster than 404
3.Serve a useful HTML body explaining what was there and pointing to related content — don't serve a blank 410
4.Submit the deleted URLs to Google Search Console's URL removal tool for instant deindexing if speed matters
5.Update internal links to remove references to the gone URLs
6.Don't use 410 for temporary removals — if the content might come back, return 503 with Retry-After instead

SEO Impact

Highly positive when used correctly. Google deindexes 410 pages faster than 404s (days versus weeks), freeing crawl budget for pages that matter and cleaning your search appearance faster after content deletion. Using 410 for content that should not exist in the index is one of the cheapest SEO wins available. Misusing it (returning 410 for content that exists, or 410 for content that should have been redirected) is harmful — affected URLs lose link equity that 301 would have preserved.

Monitor HTTP 410 with LemWatch

LemWatch tracks 410 responses and alerts if a page you didn't intend to delete starts returning 410 — often the sign of a botched migration or a CMS misconfiguration.

History & Context

HTTP 410 was defined in HTTP/1.1 (RFC 2616, 1999) specifically to give servers a way to say "this is gone forever" without ambiguity. Google's John Mueller has publicly confirmed multiple times that 410 deindexes faster than 404 — typically days versus weeks. The code is underused in practice: most CMSes default to 404 for deleted content because few content editors know the distinction exists.

Real-World Examples

Twitter deleted tweets

When a tweet is deleted, the tweet URL returns 404. Twitter could return 410 to deindex faster but doesn't — a common debate in SEO circles.

E-commerce product pruning

Shopify stores that delete discontinued products often serve generic 404s. Switching to 410 for genuinely gone products speeds deindexing and improves crawl efficiency on the remaining catalog.

API deprecation

Stripe and GitHub return 410 (with a JSON body explaining the deprecation and pointing to the replacement endpoint) when retired API versions are called. This is a textbook use of 410.

Return 410 for genuinely deleted URLs

nginx

# Specific URLs that have been deliberately deleted
location = /products/discontinued-widget    { return 410; }
location = /blog/2021-removed-post           { return 410; }
location = /campaign/expired-promotion       { return 410; }

# Pattern-based: anything under /seasonal/2022/ is gone
location ~ ^/seasonal/2022/ { return 410; }

# Custom 410 page with a useful body (recommended)
error_page 410 /410.html;
location = /410.html {
    root /var/www/html;
    internal;
}

Frequently Asked Questions about HTTP 410

What does HTTP 410 mean?

HTTP 410 Gone means the resource was deliberately deleted and will not return. It's the explicit, permanent version of 404 ("not found"). Search engines process 410 faster — Google typically deindexes 410 pages within days, versus weeks for 404s.

When should I use 410 instead of 404?

Use 410 when you have deliberately deleted content with no replacement: retired products, deleted blog posts, expired campaigns, deprecated API endpoints. Use 404 only when you genuinely don't know if the URL might be valid in the future (typos, broken links, scraper noise).

Is 410 better than 404 for SEO?

For deliberately deleted content, yes — Google deindexes 410 faster, freeing crawl budget and cleaning your search appearance sooner. For all other "not found" cases, 404 is correct. The key signal Google reads from 410 is "stop asking, this is final."

What is the difference between 410 and 301?

410 says "permanently gone, no replacement." 301 says "permanently moved to this new URL." Use 301 if the content moved (preserves link equity); use 410 if the content is genuinely gone (frees crawl budget). The worst choice is 404 for either case — both lose efficiency.

How do I return a 410 status code?

Apache: Redirect gone /old-url in .htaccess. Nginx: location = /old-url { return 410; }. Express.js: res.sendStatus(410). WordPress: most SEO plugins (Yoast, Rank Math) can set per-URL 410 responses. Always test with curl -I before deploying.

Does 410 require any special handling?

No special handling needed beyond returning the status code. Best practice is to serve a useful HTML body explaining what was there and linking to related content, rather than a blank or generic page — better user experience and clearer signal to Google about the intent.

Will 410 errors hurt my website?

Used correctly (on genuinely deleted content), no — they help by deindexing faster and freeing crawl budget. Used incorrectly (on content that still exists, or on content that should have been redirected), yes — you lose the link equity that a 301 would have preserved.