404 vs 410: Choose the Right HTTP Status
Choose 404 or 410 from the state of a page, then check the response and Google status without relying on a removal deadline.

Google's current guidance does not give 410 a faster removal path than 404. Choose a code that fits the page's actual state. Both are valid for a page that is gone with no replacement. A real move needs a redirect to the matching page. Private content needs access control. Record the goal, owner and current response before changing anything. Neither status is a permanent ban on that address.
What Is a 404 Status Code?
HTTP 404 means the server did not find a current version of the resource, or will not say that it exists. It does not say whether that state is temporary or permanent. Check the actual address and response, not just the words on screen. Is the link wrong, is the route gone, or did a needed page break? Answer that before planning removal.
Check the actual HTTP status. A 'not found' message sent with status 200 can be a soft 404. The message and the status are separate things.
Google needs to fetch and process the response. Compare the site change with the last crawl and keep a dated record. There is no fixed two-to-four-week clock in the guidance used here.
What Is a 410 Status Code?
HTTP 410 means access is gone and the loss is likely permanent. It does not say the address can never be used again. Use it where you know why the page is being retired. You do not have to mark every deleted page 410. For example, a made-up old event page with no replacement could be marked gone if the team has decided to end it.
Google handles 404 and 410 alike. It gives no 410 speed guarantee. Choose the code for the actual state, then check what the server sends.
Google can fetch the address again. For these errors, its guide says crawl frequency gradually decreases. This does not mean checks stop forever. Keep the intended response in place and test it.
When to Use a 404 Status Code
Use 404 for a page that is gone with no equivalent, including a permanent deletion. It does not promise a later return. If an error made a needed page disappear, fix the page. Check the links, catalog entry and any file people still need before you change its response. Do not send every old address to the home page.
Test the intended address, case, slash, query string and redirect path. Check what the app or CDN sends back too. Record the exact request tested and its result.
Do not switch a working 404 to 410 just for speed. Choose the meaning that fits the state. Keep the reason, owner and review date with the change record.
When to Use a 410 Status Code
Use 410 for a known retirement likely to be permanent. Start with a list of intended paths and a list of pages that should stay live. Save the current rules and agree who owns the change. Test a small scope before applying it more widely. This is our suggested workflow, not a special Google process. Low traffic alone is not a reason to erase useful content.
Google handles 404 and 410 alike. Its rule for 4xx codes has an exception for 429. This does not make 410 a faster option.
A new page at the same address can be indexed. Neither error code bans it forever. Check the new response and Google status. Do not assume it will be in search.
How to Implement a 410 Status Code
Find what sends the page response. It may be the server, app, CMS or host. A site need not use .htaccess. Apache's ErrorDocument is for an error that has already occurred. It changes the response shown for that error. It does not make a live path send 410. Use the right route rule for that task. Then test the real GET response.
On Apache 2.4 with mod_alias, an example is: Redirect gone "/retired". Leave out a new destination URL. This rule covers that path and its child paths, so check what it would match. Check FileInfo override rules if you use .htaccess. Test your own setup.
For Nginx, one example in the right server block is: location = /retired { return 410; }. The equals sign marks an exact URI match. It still matches a normalized URI. Test encoded paths, query strings, slashes and nearby live pages. Run your host's config check before a reload. Check the real response too.
Monitoring Your Deindexing Progress
Check the HTTP status and scope first. URL Inspection separates indexed data from a live test. The indexed record can be older than the site change, and a live test is not proof of the current index state. A Removals request is a separate, short-term Google Search action. If you make one, check its state too. It does not delete the page from the web or other search engines.
Log the change, current GET response, date and last crawl. Add a request state only if you made a removal request. Check that pages meant to stay live still work.
An intended 404 is not always a fault. Do not build dummy content just to clear a report. Trace the exact address of a result that still shows. Check other forms of that address, rather than swap codes to chase a clock.
Frequently Asked Questions
Q: How long does it take for Google to remove a 410 page?
Google gives no fixed one-to-two-week deadline for a 410 page. It handles 404 and 410 alike for this purpose. Check the current response, last crawl and whether the result points to another address. Keep the change date, scope, owner and evidence together. A slower update is not proof you chose the wrong code, and swapping codes is not a documented shortcut.
Q: Can I use a 410 status code for pages I plan to bring back later?
If you plan to bring it back, do not call the state a known retirement. Work out why it is down. Fix a fault if the page should be live. A planned outage needs its own host-specific approach. A redirect needs a real matching page. It is not a cure for any short outage. Keep private content locked. Save the plan, test result and review date. Content that returns can be indexed again. That is not a promise that it will be. For other page states, use our noindex and removal method comparison. For a result that persists, read our deleted-page checks.
Need help with deindexing?
Our team can assess your site and guide you through the process.








