410 Gone
The resource used to exist here but was deliberately removed and will not come back. There is no forwarding address.
What 410 Gone means
410 is a stronger 404. It says the removal is permanent and intended, so clients and search engines should drop the URL and links to it should be removed.
Search engines remove both 404 and 410 URLs from their index, and a 410 can speed that up a little. If the content moved somewhere else, use a 301 redirect instead.
Common causes
- A product, post or account was deleted on purpose.
- An old API version or endpoint was retired.
How to fix 410 Gone
- As a visitor, look for the content elsewhere on the site; it is not coming back at this URL.
- As a site owner, remove internal links and sitemap entries that point to the URL.
- If a replacement page exists, redirect to it with a 301 instead of returning 410.
Example response
HTTP/1.1 410 Gone
Content-Type: text/plain; charset=utf-8
410 GoneHow to check for a 410 response
cURL
# Print only the status code
curl -s -o /dev/null -w "%{http_code}\n" https://example.com/JavaScript (Node.js)
const res = await fetch("https://example.com/");
if (res.status === 410) {
console.log(res.status, res.statusText);
}Python
import requests
res = requests.get("https://example.com/")
if res.status_code == 410:
print(res.status_code, res.reason)Go
res, err := http.Get("https://example.com/")
if err != nil {
log.Fatal(err)
}
defer res.Body.Close()
if res.StatusCode == 410 {
fmt.Println(res.Status)
}Specification
410 Gone is defined in RFC 9110, section 15.5.11.
Related status codes
- 404
The server cannot find anything at this URL. The page may have moved or been deleted, or the link may have a typo.
- 301
The page has moved to a new URL for good. Browsers and search engines follow the Location header and update their links.
- 308
The resource has moved permanently to a new URL, and clients must keep the same method and body when following the redirect.