A 410 Gone is an HTTP status code that tells browsers and search engines a page has been permanently removed from the server and will not be coming back. It is a stronger, more explicit signal than a 404 error, where a 404 says the page cannot be found right now, a 410 says the page is gone for good and there is no point looking for it again.

It belongs to the 4xx class of HTTP status codes, which all indicate client errors, the request was understood but could not be fulfilled. Like a 404, the 410 means there is no content at the requested URL. Unlike a 404, it carries a definitive statement of intent: this content has been deliberately removed and will never return.

How a 410 works

When a browser or web crawler requests a URL that returns a 410, the server responds with the status code and typically an error page explaining that the content is gone. The browser displays the error page to the visitor. Search engines receive the 410 signal and begin the process of removing the URL from their index.

From a visitor’s perspective, a 410 and a 404 look identical, both result in an error page with no content. The difference is entirely in the HTTP response headers and how search engines interpret the signal behind them.

410 vs 404

The distinction between 410 and 404 is subtle but meaningful, particularly for SEO and crawl budget management.

A 404 Not Found is ambiguous. It tells search engines the page is not available at this URL right now but gives no indication of whether that is a temporary or permanent situation. Search engines treat 404s with patience, they keep the URL in their index for a period and continue crawling it occasionally in case the content returns. Google has said it may take months before a consistently 404ing URL is fully removed from the index.

A 410 Gone is unambiguous. It tells search engines the content has been deliberately and permanently removed. There is no uncertainty about whether it might come back. Search engines respond to a 410 by removing the URL from their index significantly faster than they would for a 404, often within days rather than months.

For most websites the practical difference is small enough that 404 is used for both scenarios simply because it is the default response for missing content. But for sites that regularly publish and retire content, news sites, e-commerce stores, blogs, using 410 deliberately for permanently removed pages is a meaningful technical SEO improvement that keeps the index clean and reduces crawl budget waste.

When to use a 410

A 410 is the right response when content has been intentionally and permanently removed with no replacement or equivalent page to redirect visitors to.

• Discontinued products, an e-commerce store removing a product that will never be restocked. If there is a similar product to redirect to, a 301 is better. If there is genuinely no replacement, a 410 is more accurate than a 404.

• Deleted blog posts or articles, content that has been deliberately removed because it is outdated, incorrect, or no longer relevant to the site. If there is no equivalent post to redirect to, a 410 communicates the intent clearly.

• Retired features or pages, a SaaS product removing a feature and its associated documentation or landing pages permanently. Using 410 tells search engines to remove these pages from the index promptly rather than continuing to crawl them.

• Legal removals, content removed due to a legal requirement, copyright claim, or privacy request. A 410 signals the permanent nature of the removal clearly.

• Expired time-sensitive content, event pages, limited-time offers, or seasonal content that has definitively ended with no future equivalent. If the same event or offer will return next year, a 302 to a relevant page during the off-period is a better approach.

When to use 301 instead of 410

A 410 should only be used when there is genuinely no relevant alternative to send visitors to. In many cases where a 410 might seem appropriate, a 301 redirect is actually the better choice.

If a discontinued product has a similar replacement, redirect the old product URL to the new one with a 301. If a deleted blog post covered a topic that other posts address, redirect to the most relevant alternative. If a retired page’s content has been merged into another page, redirect to the merged destination.

The reason to prefer a 301 over a 410 wherever possible is link equity. Any backlinks pointing to the removed URL represent accumulated SEO value. A 301 redirect recovers that value by transferring it to the destination. A 410 discards it entirely, all incoming link equity pointing to a 410 URL is lost with no recovery.

Only use a 410 when you are certain there is no page on your site that would serve as a meaningful destination for the redirect, and when you are comfortable losing any link equity associated with the removed URL.

410 and crawl budget

One of the most practical benefits of using 410 over 404 on large sites is the impact on crawl budget.

Search engines allocate a finite amount of crawl activity to each site. On large sites with thousands of URLs, crawl budget is a meaningful constraint, time spent crawling dead URLs is time not spent crawling live, indexable content.

A 404 URL stays in the crawl queue for an extended period because search engines are not certain the content is gone permanently. A 410 URL is removed from the crawl queue much faster because the intent is unambiguous. For sites that regularly retire large volumes of content, an e-commerce store cycling through seasonal products, a news site archiving old articles, using 410 consistently for permanently removed content keeps the crawl queue clean and focuses crawler attention on live content.

410 and duplicate content

A 410 can also be useful for managing duplicate content issues. If a page exists at multiple URLs and you want to retire all but one, using 410 on the duplicates, after setting up canonical tags or 301 redirects on the preferred version, sends a clear signal to search engines that the duplicate versions are gone permanently.

This is a more aggressive approach than canonical tags alone and is worth considering when duplicate pages have been indexed for a long time and canonical signals have not been effective at consolidating them.

Soft 410 errors

Just as there are soft 404 errors, pages that display a not found message but return a 200 status code — there are soft 410 scenarios where a page displays a removal message but does not return the correct 410 status code.

The fix is the same as for soft 404s, ensure the HTTP response actually returns a 410 status code rather than a 200. Verify this using browser developer tools, the curl command line tool, or a dedicated HTTP status checker. A page that says “this content has been removed” but returns a 200 will be indexed by search engines as normal content, defeating the purpose entirely.

Monitoring 410 responses

410 responses should be tracked as part of regular site maintenance, particularly on sites that frequently add and remove content. Google Search Console reports both 404 and 410 responses under the Coverage section, allowing you to verify that intentionally removed pages are being processed correctly.

When retiring large volumes of content at once, a major site cleanup, a product catalogue update, an archive purge, it is worth monitoring Search Console in the weeks following to confirm that 410 URLs are being removed from the index as expected and that no live pages were accidentally caught in the removal.

Server logs provide the most complete picture of 410 responses, including requests from sources that Search Console does not capture such as direct traffic, email links, and non-Google crawlers.