Both tell a client the page is not there. The difference is certainty: 404 means not found, 410 means deliberately and permanently gone. Search engines treat 410 as a stronger signal and typically drop those URLs faster.
In practice the difference is smaller than the debate around it. Both work, and choosing between them matters far less than not using a soft 404 instead.
When each is appropriate
Use 410 when you are certain
- A product line permanently discontinued with no replacement.
- Content deliberately removed and never returning.
- Pages deleted in a cleanup where the URLs should not persist.
- Expired listings that will not be reinstated.
Use 404 when you are not
- The page might return, such as a seasonal product.
- You are unsure whether it was removed intentionally.
- The URL was mistyped or never existed.
- Your platform makes 410 awkward, which is common.
404 is the safer default. Nothing is lost by using it where 410 would technically be more precise.
What actually matters more
The choice between them is a minor optimisation. These are not.
- Do not return 200 for a missing page. A page saying “not found” with a success status is a soft 404, and it keeps being crawled indefinitely.
- Do not redirect everything to the homepage. Also treated as a soft 404, and it discards the signal you were trying to preserve.
- Do redirect where a genuine equivalent exists. A 301 to a relevant replacement beats both status codes. See 301 vs 302 redirects.
- Do check what your platform actually returns, since custom error pages frequently return 200 by accident.
Whether to worry about volume
Large numbers of 404s in Search Console are usually not a problem. They are reported because they were requested, not because they are damaging. What matters is whether the URLs returning 404 are ones that should exist.
- 404s on URLs that never existed, from bad external links or bots: ignore.
- 404s on URLs you deliberately removed: correct behaviour.
- 404s on URLs that had traffic or links: fix, by redirecting to a genuine equivalent.
- 404s appearing after a deployment: investigate immediately, since that is a fault.
The reflex to redirect every 404 somewhere is misplaced. A correct 404 is the honest answer and causes no harm.
Making the page itself useful
The status code is for machines; the page is for people. A 404 page should return the correct status while helping the visitor: search, main navigation, and links to popular sections. Both are true at once, and many sites get one right and not the other.
Frequently asked questions
Do 404 errors hurt rankings?
Not in themselves. A URL that does not exist returning 404 is correct. Harm comes from 404s on pages that should exist, or from pretending missing pages exist.
Is 410 better for SEO?
Marginally, in that URLs tend to drop faster. The practical difference is small and rarely worth engineering effort where 404 is simpler to implement.
Should I redirect all my 404s?
No. Redirect where a genuine equivalent exists. Redirecting unrelated URLs to the homepage or an arbitrary page is treated as a soft 404 and helps nobody.
How long do 404 URLs keep getting crawled?
A long time, particularly where they once had value or still have external links. That is normal. Using 410 shortens it somewhat.
Consulting CTA
If your site returns 200 for missing pages, or you are unsure which removed URLs should redirect, book an SEO consultation for a status code review.