Gone
4xx Client Error
Last updated:
The resource is no longer available and has been permanently removed.
Description
Stronger than 404: 'this used to exist but we deliberately deleted it'. Search engines drop 410'd URLs from the index faster than 404s.
When to use
Return 410 for URLs you've intentionally retired and never want indexed again (e.g. deleted user pages).
Specification
RFC 9110 §15.5.11
Examples
HTTP response
HTTP/1.1 410 Gone
Content-Type: application/json
{"error":"Gone"}Node.js (Express)
res.status(410).json({ error: "Gone" });Go (net/http)
w.WriteHeader(http.StatusGone)
Python (Flask)
return jsonify({"error": "Gone"}), 410Related status codes
All 4xx codes
400 Bad Request401 Unauthorized403 Forbidden404 Not Found405 Method Not Allowed406 Not Acceptable408 Request Timeout409 Conflict410 Gone411 Length Required412 Precondition Failed413 Payload Too Large414 URI Too Long415 Unsupported Media Type418 I'm a teapot422 Unprocessable Entity425 Too Early428 Precondition Required429 Too Many Requests431 Request Header Fields Too Large451 Unavailable For Legal Reasons