SEO glossary
What is 410 Gone?
Learn what HTTP 410 Gone means, how it differs from 404 Not Found, when to use 410 for deleted content, and how search engines process intentional permanent removals.
Definition
410 Gone is an HTTP client error status code indicating that the target resource is permanently unavailable at the origin and will not return—providing a stronger removal signal than 404 for deliberately deleted content.
410 Gone: telling crawlers the URL is dead permanently
410 Gone is an HTTP status code meaning the resource existed at this URL but has been permanently removed and will not be restored. Clients should not expect content to reappear at the same address.
For SEO, 410 is the precision tool when you know a URL is obsolete forever—delisted SKUs, expired legal notices, spam pages removed after cleanup, or CMS records deleted with no successor. It is stronger than "maybe missing" (404 Error) and more honest than 200 OK soft 404 templates.
410 response example
GET /listings/vacation-rental-8821 HTTP/1.1
Host: stays.example.com
HTTP/1.1 410 Gone
Content-Type: text/html; charset=utf-8
Cache-Control: no-store
<!DOCTYPE html>
<html>
<head><title>Listing removed</title></head>
<body>
<h1>This listing has been permanently removed</h1>
<p>Browse <a href="/search">available stays</a>.</p>
</body>
</html>
The status line matters most. Optional HTML helps humans; crawlers key off 410.
410 vs 404: semantic and SEO differences
| Aspect | 404 Not Found | 410 Gone |
|---|---|---|
| Meaning | Not found (may never have existed) | Was here; permanently removed |
| Temporariness | Ambiguous | Explicit permanent absence |
| Google indexing | Deindexes over time | Deindexes over time |
| Recrawl behavior | May retry longer on important URLs | May drop faster from crawl queue |
| Typical use | Typos, unknown paths | Deliberate retirements |
Google's documentation groups 4xx not-found codes for indexing exclusion. Operationally, 410 documents admin intent in server configs and helps analytics separate "broken" from "retired."
When to choose 410 Gone
Delisted marketplace and classified listings
Short-term rentals, auction lots, and job posts that expire permanently—410 prevents infinite recrawl of dead inventory URLs discovered via old sitemaps and backlinks.
Regulatory or legal content retraction
Pages ordered removed where republication is unlikely. 410 plus cache purge reduces stale snippet risk after deindexing.
Spam and policy violation cleanup
Mass removal after hack cleanup—410 on junk paths clarifies they should not return—pair with security review.
API-driven deletion
Headless CMS hard-deletes records; origin returns 410 for former slugs instead of empty 200 OK shells.
When 410 is wrong
| Scenario | Better choice |
|---|---|
| Content moved to new URL | 301 Redirect or 308 Redirect |
| Temporary stockout | 200 with availability schema or noindex |
| Scheduled maintenance | 503 Service Unavailable |
| URL typo in internal link | Fix link; target may be 404 Error |
| Content might return | 404 or 503—not 410 |
Using 410 for "maybe we'll restock" forces a new URL if the product returns—breaking bookmarked links and external references.
SEO implications
Deindexing speed
Neither 404 nor 410 guarantees instant SERP removal. Both require recrawl. 410 signals permanence—on high-churn templates, crawl systems may deprioritize revisiting dead URLs, improving crawl budget for live inventory.
Link equity
External links to 410 URLs do not pass ranking signals to other pages automatically. If a replacement exists—a newer model, related category—301 Redirect captures equity. Use 410 only when no relevant target exists.
Sitemap hygiene
Remove 410 URLs from XML sitemaps immediately. Continuing to submit gone URLs generates crawl errors and masks real issues.
Internal links
Update navigation and related modules still pointing at 410 targets. Crawlers follow internal links faster than they forget old URLs.
410 vs noindex vs robots.txt
| Method | Resource exists? | Index intent | HTTP honest? |
|---|---|---|---|
| 410 Gone | No | Exclude | Yes |
| noindex on 200 | Yes | Exclude | Partial |
| robots.txt disallow | Maybe | Block crawl | N/A for status |
For deleted resources, 410 (or 404) is cleaner than noindex on placeholder pages.
Implementation examples
Nginx
location = /retired-whitepaper.pdf {
return 410;
}
Apache
RewriteRule ^archive/2012/ - [R=410,L]
Express
app.get('/listings/:id', (req, res, next) => {
if (listingPermanentlyRemoved(req.params.id)) {
res.status(410).send('This listing is gone.');
} else next();
});
CDN edge (conceptual)
Return 410 for known deleted object keys without hitting origin—faster and cheaper at scale.
Verify caches honor 410—stale 200 OK CDN objects undermine the signal.
410 and soft 404 cleanup
Many sites return 200 with "This item is no longer available"—soft 404. Migrating templates to 410 (or 404) aligns HTTP semantics with indexing behavior:
Before: GET /sku/old → 200 "removed" → Soft 404 exclusion
After: GET /sku/old → 410 → Clear gone signal
Batch migrations: export delisted IDs, deploy 410 rules, purge sitemap entries, monitor Search Console exclusions trending down.
Example: classifieds platform delisting
autos.example/vehicle/VIN123 sold and listing deleted. CMS returned 200 with boilerplate removal text.
Problems:
- 2.1M URLs classified soft 404
- Crawl quota spent re-fetching sold vehicles
- New listings indexed slower
Remediation:
- 410 for sold listings older than 30 days
- 301 to similar active listings when match score high
- Sitemap only active inventory
- Related links module stopped referencing sold VIN URLs
Within eight weeks, soft 404 count fell 76%; active listing indexation rate improved.
How Crawlox helps with 410 Gone
Crawlox distinguishes 410 from 404 and 200 OK soft removals across site crawls. Identify templates still returning misleading success statuses, batch-export URLs eligible for 410 after delisting rules, and verify internal links no longer target permanently gone paths—so crawl budget shifts toward live URLs that should earn rankings.
Related terms
Frequently asked questions
Is 410 better than 404 for SEO?
For content you permanently removed and will not restore, 410 communicates intent more clearly than 404. Google treats both as not found for indexing; 410 may reduce repeated recrawl attempts on hopeless URLs.
Should I use 410 for out-of-stock products?
Usually no for temporary stock issues—use availability markup or noindex. Use 410 when the product line is discontinued with no near substitute page.
Does 410 pass link equity?
No. Equity from external links to a 410 URL is generally lost unless you 301 to a relevant replacement before or instead of 410.
Can I return 410 with a custom HTML page?
Yes. Status must remain 410. A helpful body aids users who bookmarked the URL; indexing still treats the resource as gone.
How is 410 different from noindex?
noindex asks not to index while URL may still return 200. 410 says the resource itself is gone at this address—stronger HTTP semantics for deletion.
References
Explore authoritative guidance and frameworks related to 410 gone.
Explore every glossary definition
Return to the glossary to search by term, alias, starting letter, or category.