Does 410 remove a page from Google faster than 404?
Google has said both lead to removal, with 410 treated as a slightly stronger signal. In practice the difference is small, so choose whichever is accurate.
Removed on purpose and not coming back. Search engines drop it faster than a 404. 410 belongs to the 4xx client error class and is defined in RFC 9110.
Loading the workbench.
Removed on purpose and not coming back. Search engines drop it faster than a 404. The code is registered with IANA and defined in RFC 9110.
Client error: the request has a problem, so it cannot be fulfilled as sent. Every code from 400 to 499 shares that general meaning, so a client that does not recognise 410 must treat it like 400.
410 Gone says the resource existed, was removed on purpose, and will not return, with no forwarding address. Typical uses are expired promotions, deleted user content, retired API versions, and products that are discontinued for good. Compared with 404, it carries intent: the server knows the URL is dead rather than merely unknown. Search engines may drop a 410 URL from the index a little faster than a 404.
Use 410 only when the removal is permanent and deliberate; if there is a replacement, redirect with 301 or 308 instead. Clients and link checkers should delete stored references to the URL. A 410 is cacheable by default, so caches may keep it for a while. Serving a short explanatory page with the 410 helps humans who follow old links understand what happened.
HTTP/1.1 410 Gone
Content-Type: text/html; charset=utf-8
Cache-Control: max-age=86400410 is cacheable by default under RFC 9110: a browser or CDN may store it and reuse it even without explicit freshness headers, using a heuristic lifetime. Send Cache-Control to say exactly how long.
To inspect a real one without sending it anywhere:
curl -i.Browse every code on the HTTP status codes page.
Elsewhere in 2http: Header decoder, Cookie decoder, Cache-Control decoder, CORS checker, User-agent parser, and all eleven lanes on the 2http home page. Part of the 2suite.io privacy-first ecosystem.
Google has said both lead to removal, with 410 treated as a slightly stronger signal. In practice the difference is small, so choose whichever is accurate.
Technically yes, but 410 promises the removal is permanent, and caches may keep the 410. If you might bring the page back, use 404.
Yes. 410 is a client error response: the problem is in the request, so repeating it unchanged will usually fail again.
Yes. RFC 9110 lists 410 as heuristically cacheable, so caches may store it without explicit headers. Use Cache-Control to control how long.
You do not have to take our word that your headers stay here. Developer tools show every request a page makes, so you can watch this page work and confirm that nothing is sent. The check takes under a minute.
F12, or Cmd+Option+I on a Mac, and select the Network tab.Only two things can add a line to that log, and neither carries your headers. Submitting the feedback form sends the vote and comment you typed. Typing characters in a script the page has not displayed yet, such as Cyrillic or Greek, can make the browser fetch the matching font file, and that request names only the font.
2http never sends a request on your behalf: the request builder writes code for you to run, and the meta inspector reads source you paste instead of fetching a URL. The production site also sends a Content-Security-Policy header that tells your browser to refuse connections to anywhere except this site and the anonymous analytics endpoint.