DevArbor
4xx Client Error

410 Gone

What it means

Unlike 404, 410 definitively states that the resource is gone and is not coming back. It's a stronger signal to search engines — they should deindex the URL more aggressively. Use 410 when you know a resource was intentionally deleted permanently.

Site Visitor

What can I do?

  • This content has been permanently removed. No archived version is available here.
  • If the problem persists after retrying, contact the site owner.
Developer

How to debug & fix

  1. Prefer 410 over 404 for intentionally deleted content to speed up search engine deindexing
  2. Create a tombstone record in your database so you can consistently return 410
  3. Consider a grace period (301 → later 410) to preserve existing links temporarily
  4. Maintain a tombstone table in your database to distinguish 404 (unknown) from 410 (known-deleted).

Code Example

Node.js / Express
app.get('/posts/:id', async (req, res) => {
  const post = await Post.findById(req.params.id, { includeDeleted: true });
  if (!post) return res.status(404).end();
  if (post.deletedAt) return res.status(410).json({ error: 'Gone' });
  res.json(post);
});

Related Status Codes

404 Not Found 301 Moved Permanently

How HTTP Status Codes Work

Every HTTP response carries a three-digit status code that tells the client — browser, API consumer, or search-engine crawler — exactly what happened. The first digit defines the class: 1xx informational (request in progress), 2xx success, 3xx redirection, 4xx client error (bad request, missing auth, not found), and 5xx server failure.

Status codes are standardised in RFC 9110 (HTTP Semantics, 2022). Extensions like WebDAV (RFC 4918) and rate-limit headers (RFC 6585) added codes beyond the core set. When a client receives an unrecognised code, the rule is to treat it as the generic x00 of its class.

Why the Right Code Matters

Semantically correct codes help search engines index accurately (301 passes link equity; 410 removes pages faster than 404), allow API clients to implement correct retry logic (429 + Retry-After, 503 + Retry-After), and let monitoring systems distinguish bugs (500) from load issues (503) from auth failures (401/403).

Looking up a different status code? The full reference covers all HTTP codes with causes, fix guides, and copyable code examples for Node.js and Python.

Browse the full HTTP Status Code reference →

Frequently Asked Questions

What does HTTP 410 Gone mean?
Unlike 404, 410 definitively states that the resource is gone and is not coming back. It's a stronger signal to search engines — they should deindex the URL more aggressively. Use 410 when you know a resource was intentionally deleted permanently.
Is HTTP 410 the visitor's fault?
HTTP 410 Gone is generally a client-side error, meaning the request itself has an issue. However, many causes — such as a broken link on the site or a misconfigured redirect — are the website owner's responsibility, not the visitor's.
How do I fix HTTP 410 Gone?
As a visitor: check the URL for typos, go to the homepage, or search for the content. As a developer: prefer 410 over 404 for intentionally deleted content to speed up search engine deindexing.