HTTP 410 Gone: remove a page without misleading SEO claims

What does HTTP 410 Gone mean for a web page?

A 410 status expresses disappearance, not an outage the visitor needs to fix. The browser can display a customised page explaining that the content is no longer available. The technical signal is still carried by the HTTP response sent for the requested URL.

That separation matters: a page displaying ‘content removed’ with a 200 status still reports success. Google can classify it as a soft 404. Conversely, a helpful layout with navigation links can accompany a genuine 410 response without making the resource available again.

Here, ‘error’ describes a response to a request, not necessarily a website defect. Intentional removal can produce a completely correct 410. Investigate when that response appears on a page that should remain accessible, rather than converting every 410 to a successful response just to clear an alert.

diagnose a soft 404 error.

HTTP 410 vs 404: what actually changes for Google?

The difference in meaning does not become a promise of SEO performance. A 404 says the resource cannot be found; a 410 indicates that its disappearance is considered permanent. Google’s documentation groups 4xx responses, except 429, under the same indexing treatment.

Google does not use content received with these responses for indexing and removes previously indexed URLs once their unavailability is established. Crawling frequency for affected URLs gradually decreases. That means neither immediate removal nor a permanent end to all Googlebot visits.

Choose according to how certain your system is about the removal. An explicit 410 rule can represent an inventory of deliberately retired URLs. A 404 remains appropriate for a missing URL. Replacing a batch of 404s with 410s solely to ‘speed up Google’ is not a conclusion supported by the current documentation.

Google: HTTP status codes and network errors.

When should you choose 410, a redirect or another response?

Choose the response based on what happens to the content before looking at Search Console alerts. A page with a useful successor is not in the same situation as a page deleted without an equivalent.

During a migration, a redirect accompanies a genuine replacement. Google recommends mapping old URLs to new ones and warns against sending many pages to an unrelated destination such as the homepage. Commercial similarity alone is not enough: the destination should satisfy the visitor’s expectation.

An out-of-stock item, a temporarily unavailable API or an ongoing deployment does not establish permanent disappearance. Diagnose the problem before choosing the status. Server errors in the 5xx range temporarily slow crawling; if they persist, Google can eventually remove affected URLs. A 503 is therefore not indefinite protection against deindexing.

Google: site moves with URL changes · prepare an SEO migration.

How do you remove a batch without deleting useful pages?

Implementation starts with a list of explicit decisions, not a broad rule covering an entire directory. Before removing a batch, retain the mapping between each old URL and its intended outcome.

1. Inventory the URLs: affected content, reason for removal, possible destination and internal links still pointing to the page.
2. Approve the intended outcome: retain, relocate or remove without replacement. Do not infer a removal decision solely from a lack of traffic.
3. Configure the response at the layer actually serving the URL: application, hosting platform or server. Check for competing redirect rules.
4. Remove deleted URLs from the sitemap and update internal links. Keep useful replacement pages in appropriate visitor journeys.
5. Test retired URLs and neighbouring pages that must stay active. Catch an overbroad rule before it affects an entire page template.

An HTML tag cannot produce an HTTP 410 status on its own. The implementation depends on the hosting platform and application. Instead of copying an unsuitable configuration, define the expected behaviour first and implement it where the HTTP response is controlled. Retain the approved URL list so an accidental removal can be reversed.

How do you check that a page really returns 410?

Check the public response for the exact URL, not just the screen your browser displays. The test should distinguish the initial status, any redirect and the final destination.

curl -sS -D - -o /dev/null "$URL"

• The initial status is 410: a redirect to an error page is not the same as a 410 response on the old URL.
• The displayed content explains removal without claiming a temporary outage or returning a successful 200 status.
• The same public URL is not still being served as 200 from a cache or another hosting rule. Repeat the check after changes.
• Pages being retained still work. Also test URL variants actually present in the inventory without arbitrarily expanding the removal rule.

A local check does not prove that Google has already received the new response. Logs show when Googlebot requested the URL and which status was served. Search Console describes the state known to Google, which may predate the change. Record the actual deployment date and compare it with the last observed crawl.

analyse Googlebot logs.

How do you remove a URL from Google when it is urgent?

A 410 status implements the technical disappearance; it is not an instant removal button for search results. For a site you manage, Search Console’s Removals tool can temporarily hide a URL while the lasting solution is put in place.

Google describes a hiding period of about six months. That duration applies to temporary hiding, not to the processing time of a 410 response. The page must also be removed, protected or excluded from indexing through a method suited to what should remain accessible.

If visitors should still be able to read the content but it should disappear from Google, a noindex directive may meet the need. Google must be able to crawl the page to read it. If the resource should actually disappear for everyone, deletion with an appropriate response is more coherent. Define the access objective before choosing the tool.

Google: remove information from Search · Google: block indexing with noindex.

Which mistakes prevent a clean removal?

understand the limits of robots.txt.

The final check is about consistency: genuinely removed content, the correct response, possible crawling and cleaned-up internal journeys. When the inventory mixes rendering failures, relocated pages and deletions, start with diagnosis instead of a blanket removal rule.

have technical issues diagnosed.