HTTP 410 Gone
The resource used to exist but was intentionally and permanently removed, with no forwarding address.
Meaning
410 is a stronger, deliberate version of 404. Search engines drop 410 URLs from their index faster than 404s. APIs use it for removed/deprecated endpoints or versions.
Common causes
- Content deliberately deleted by the site owner
- Deprecated API version or endpoint retired
- Expired one-time link (downloads, invites)
⚡ Quick fix
- If you own the site and the content moved, use a 301 redirect instead
- For APIs, migrate to the endpoint/version in the deprecation notice
- Request a new link if it was a one-time/expiring URL
Detailed fix by platform
Nginx
- Return 410 for removed paths:nginx
location = /old-page { return 410; }
Apache
Redirect gone /old-pagein .htaccess.
How to diagnose
- Intent — Was the removal intentional?
- Replacement — Is there a new URL or API version to use?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in HTTP
Where this error sits
Origin: Network. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 9 Oct 2026