The HTTP 410 Gone status code indicates that the target resource has been permanently removed and will not be available again. Unlike 404 Not Found, 410 explicitly tells crawlers the page is intentionally gone. This guide explains when to use 410 vs 404 vs 301, SEO implications, and implementation patterns.
HTTP 410 Gone is the response code a server returns when a resource has been permanently and intentionally removed. Per RFC 9110, the 410 response indicates that the origin server requires this condition to be communicated to the client, and the resource is not expected to be available again. The response is similar to 404 Not Found but conveys a stronger signal: 404 means 'I cannot find this' (which could be temporary or due to a typo); 410 means 'this used to exist, I deliberately removed it, do not expect it to return.' For search engines and API consumers, this distinction matters significantly. We track what http 410 gone performance weekly across our portfolio.
Use 410 when: the resource definitely existed, you intentionally removed it, and you want to signal that it won't return. Examples: a discontinued product page, an archived blog post you've deliberately deleted, a deprecated API endpoint, a user account that was permanently closed. Use 404 when: the resource may not have existed, the URL might be a typo, or you're not certain about the resource's history. Examples: random URL variations, mistyped paths, URLs from outdated marketing materials, or generic 'page not found' fallbacks. The default for unknown URLs should be 404; use 410 only when you have positive knowledge that a specific URL has been permanently removed. We track what http 410 gone performance weekly across our portfolio.
410 responses cause Google to deindex pages substantially faster than 404 responses — typically within days versus weeks for 404s. Internal Google guidance and observed behavior both confirm this difference. The mechanism: when Googlebot encounters a 410, it interprets the page as deliberately removed and deindexes quickly. When it encounters a 404, it assumes the absence might be temporary and retries multiple times before deindexing. For large-scale content removal (deleting thousands of expired listings, removing entire site sections), 410 is the right choice — it cleans up Google's index faster and frees crawl budget. For occasional missing pages, 404 is appropriate.
Use 301 when there's a clear equivalent replacement page that the user (and search engines) should be sent to instead. Example: you've consolidated three product pages into one — redirect the three old URLs to the new consolidated page with 301. Use 410 when there's no equivalent replacement and the content is genuinely gone. Example: you've discontinued a product line entirely and there's no replacement. Misusing 301 to redirect deleted content to your homepage or an unrelated page is a common SEO mistake — Google may treat it as a soft 404 and either ignore the redirect or penalize the destination. If there's nothing to redirect to, 410 is honest and effective. Our what http 410 gone program combines technical depth with conversion-focused design.
Server-level implementation: Apache (.htaccess): Redirect gone /old-url. Nginx: location /old-url { return 410; }. WordPress: use the Redirection plugin's '410 Gone' option, or php: status_header(410); exit; in template_redirect. Node.js/Express: res.status(410).send('Gone'); React/Next.js: throw new Response(null, {status: 410}); in a route handler. For bulk implementation across many URLs: maintain a list of permanently removed URLs in a database or config file and check incoming requests against it. Always return a meaningful response body explaining the removal — this improves the user experience even though search engines primarily care about the status code itself.
(1) E-commerce: products discontinued with no equivalent replacement. (2) Real estate: sold listings after a reasonable archive period. (3) Job boards: filled or expired postings. (4) News sites: content removed for legal reasons (defamation correction, GDPR right-to-be-forgotten requests). (5) APIs: deprecated endpoints after sunset period. (6) User-generated content: deleted forum posts, removed user accounts, reported and removed content. (7) Site migrations: content that exists on the old site but has no place in the new architecture and shouldn't be redirected. (8) Marketing campaigns: time-limited landing pages after the campaign ends and there's no evergreen replacement.
Track 410 responses in Google Search Console under Coverage → Excluded → Page removed by user or 'Page with redirect.' Both 410 and proper deindexing show up here. Watch for: (1) Unintentional 410s — your site is returning 410 for pages that should be live. This indicates a deletion bug or misconfigured redirect rules. (2) 410 traffic loss — pages with significant external traffic that you've returned to 410 may be costing you referrals. Consider 301 to a related page instead. (3) Crawl budget impact — large numbers of 410s on a small site indicate aggressive cleanup; on a large site, they're a normal part of content lifecycle management. Monitor server logs for sustained 410 volumes that exceed expectations. Our team's perspective on what http 410 gone comes from active client work, not theory.
(1) Returning 200 with 'page not found' content (soft 404 / soft 410) — Google detects and treats these as 404s but it's slower and messier than proper status codes. (2) Using 410 when 301 to an equivalent page would be better — costs you the link equity. (3) Using 404 for permanent deletions on large content removals — slows down deindexing significantly. (4) Returning 410 with no response body — hurts user experience even though it's technically valid. (5) Forgetting to remove 410 URLs from sitemaps — Google flags this as an inconsistency. (6) Returning 410 for entire URL patterns when only specific pages are gone — kills legitimate URLs in the same path. Considering what http 410 gone? Book a no-pressure strategy call to compare options.