404 or 410 for pages you removed? A decision tree
Short answer: If a removed page has a close replacement, redirect it with a 301. If it has no replacement, return a 404 or a 410. For Google Search the difference is small: Google's documentation says all 4xx errors except 429 are treated the same, and indexed URLs that return them are removed from the index over time; use 410 when you're sure the removal is permanent and 404 when you're not. What to avoid is the "soft 404": a missing page that returns 200 OK, or redirecting everything to your homepage.
Every site removes pages: discontinued products, ended services, old promotions, outdated blog posts. The question "should this be a 404 or a 410?" comes up often, sometimes with strong opinions attached. In practice the bigger decisions are whether to redirect at all and whether the server returns a real error code. Work through the tree below for each removed page or group of pages.
What the codes mean
- 404 Not Found: the server can't find the resource. It says nothing about whether it might come back.
- 410 Gone: MDN describes it as indicating the resource is no longer available at the origin server and that this is likely to be permanent. Clients shouldn't repeat requests for it, and site owners should remove or replace links to it. MDN adds that if you don't know whether the condition is temporary or permanent, use 404 instead.
- 301 Moved Permanently: the content lives at a new URL. Google's documentation says Google follows the redirect and treats it as a strong signal that the target should be processed.
- 200 OK on a missing page: the server claims success while showing an error or empty page. Google's documentation says that if the content suggests an error, an empty page or an error message, Search Console will show a soft 404 error.
The decision tree
Question 1: Is there a page that genuinely replaces it?
A newer model of the same product, a merged service page, an updated version of the article.
- Yes → 301 redirect to that page. Visitors and links reach something useful.
- No → go to Question 2.
Be strict: "replaces" means someone looking for the old page would be satisfied by the new one. A product category might qualify for a discontinued product; the homepage almost never does.
Question 2: Might it come back?
Seasonal products, a temporarily paused service, a page under rework.
- Yes → consider keeping the page live with a clear note ("Back in spring" or "Temporarily unavailable") rather than removing it. If you do remove it, use 404.
- No → go to Question 3.
Question 3: Are you sure it's gone for good?
- Yes, permanently → 410 is accurate. 404 is also fine.
- Not sure → 404.
Question 4: Does the error page help people?
Whichever code you return, the page visitors see should:
- say clearly that the page isn't available;
- offer search, main categories and contact options;
- keep your normal header and navigation.
It must still return the 404 or 410 status code, not 200.
How Google treats 404 and 410
According to Google's documentation on HTTP status codes:
- Google doesn't use content from URLs that return 4xx codes.
- All 4xx errors except 429 are treated the same: the URL is removed from the index if it was indexed, and crawling frequency gradually decreases.
- Newly encountered 404 pages aren't processed.
- 4xx codes other than 429 have no effect on crawl rate.
So for Google, choosing 410 over 404 isn't a magic switch. Choose the code that describes reality; other systems and clients may use the distinction.
Common mistakes
- Redirecting every removed page to the homepage. Visitors land somewhere irrelevant, and search engines may treat it like a missing page anyway.
- Error pages that return 200. Check with your browser's developer tools (Network tab) or an online header checker.
- Removing pages that still get valuable traffic or links without a redirect. Check analytics and Search Console before deleting.
- Leaving internal links to removed pages. Update menus, related-product blocks and old posts.
- Bulk-deleting product pages after a range change without mapping them first.
A workflow for removing pages
- List the pages to remove.
- For each, check traffic, inbound links and whether a replacement exists.
- Assign an action: 301 to a specific URL, 404, or 410.
- Implement redirects and error codes, ideally in one place (server, CMS or redirect plugin).
- Update internal links and your sitemap.
- Test a sample of URLs for the right status codes.
- Watch Search Console's page indexing report over the following weeks.
A worked example (hypothetical)
A Portland outdoor store drops a jacket line. Two jackets have direct successors, so their pages get 301 redirects to the new models. The rest have no equivalent; the store returns 410 for those, with a page linking to the current jacket category. A limited-edition collaboration that might return next winter stays live with a "sold out, back later" note.
Where to set this up
Most platforms handle it without code. Many CMSs and shop platforms have redirect managers and return 404 automatically for deleted pages; returning 410 may need a plugin or a server rule. If you manage your own server, redirect and status rules usually live in the web server configuration. Keep the list of rules in one place so they don't conflict.
FAQ
Will 404 errors hurt my site's rankings?
Pages that don't exist returning 404 is normal. Problems arise when important pages break unintentionally or links point to missing pages.
Is 410 faster than 404 for removing pages from Google?
Google's documentation says all 4xx codes except 429 are treated the same. Use 410 when it's accurate, but don't expect a big difference in Google.
Should I redirect old blog posts?
If a newer post covers the same topic, yes. If not, return 404 or 410, or keep the post with an update note if it still helps readers.
How do I check what code a page returns?
Use your browser's developer tools, a header-checking tool, or Search Console's URL Inspection.
If you're about to remove a batch of pages and want to avoid broken links, send us the list and we'll help map redirects and error codes.