Should a deleted page return a 404 or a 410?

Should a deleted page return a 404 or a 410?

For Google Search, it barely matters. Google's own documentation says all 4xx errors except 429 are treated the same: its crawlers report that the content does not exist, and indexed URLs that return a 4xx are removed from the index. Pick whichever your platform supports cleanly. The bigger decision is whether to redirect instead.

The 404 versus 410 debate has lived in SEO forums for years. The theory goes that 410 Gone is a stronger, faster signal than 404 Not Found, so you should always use it for pages you deleted on purpose. It sounds sensible. It just is not what Google's documentation describes.

This article walks through what Google actually says, where the real decisions are when you remove a page, and how I would handle deletions on a small marketing site. If you are cleaning up a Webflow CMS collection or pruning old blog posts, this is the part worth getting right.

What do 404 and 410 status codes mean?

A 404 Not Found says the server cannot find the requested page. A 410 Gone says the page existed and has been removed on purpose, with no forwarding address. Both belong to the 4xx family of client errors. In plain terms, 404 means "not here" and 410 means "not here, and not coming back."

In HTTP terms the difference is about intent. A 404 makes no promise about the future. The page might come back. A 410 is a statement that removal was deliberate and permanent.

That distinction can still be useful for humans and for other systems that read your server responses. My point here is narrower: for Google Search indexing, the documented behavior does not reward one over the other.

How does Google treat a 404 compared with a 410?

Google treats them the same. Its HTTP status code documentation states that all 4xx errors, except 429, are treated the same, and that Google's crawlers inform the next processing system that the content does not exist. The page lists 404 and 410 together. Neither one earns special handling for indexing.

The same page explains what happens next. Google does not index URLs that return a 4xx status, and URLs already in the index that start returning a 4xx are removed. It adds that newly encountered 404 pages are not processed, and that crawling frequency for those URLs gradually decreases.

There is one more detail people often get wrong. Google says the 4xx codes, except 429, have no effect on crawl rate. So returning 410s across a site will not slow Googlebot down or speed it up. If you want to manage crawl rate, status codes in the 4xx family are the wrong tool.

Other search engines and crawlers may behave differently, and their documentation is the place to check. For Google, the documented answer is clear enough to stop worrying about it.

When should a removed page redirect instead of returning an error?

Redirect when a close replacement exists. If the old page's content now lives on another URL, or a newer page answers the same question, a 301 redirect sends visitors and search engines to it. Return a 404 or 410 only when nothing on your site genuinely replaces what the old page offered.

Google's documentation describes a 301 as a strong signal that the redirect target should be processed, and a 302 as a weak signal. It also treats 308 as equivalent to 301. For a page that has moved or merged for good, a permanent redirect is the honest choice.

The trap is redirecting everything to the homepage. If someone lands on an old pricing page and gets your homepage, they did not find what they wanted. That experience can look a lot like an error page wearing a disguise, which leads to soft 404s.

If two old pages compete for the same query and you are merging them, I covered the full process in how to consolidate two competing pages.

What is a soft 404, and why is it worse than a real one?

A soft 404 is a page that returns a 200 success code but shows error-like content, such as an empty page or a "not found" message. Google's documentation says Search Console will flag these as soft 404 errors. They are worse than real 404s because they send mixed signals and waste crawling on pages with no value.

Soft 404s often come from CMS setups. A collection item gets deleted, but a template still renders at the old URL with empty fields. Or a filter page returns zero results with a 200 status. The server says success, the page says nothing.

The fix is to make the server tell the truth. A missing page should return a real 404 or 410. A moved page should redirect. A page that exists should have real content. Search Console's page indexing report is the place to spot soft 404s on your own site.

How should you handle deleted pages on a small marketing site?

Sort every page you plan to remove into two groups: pages with a close replacement and pages without one. Redirect the first group with a 301 to the closest match. Let the second group return a plain 404 or 410. Then remove the deleted URLs from your sitemap and update any internal links that pointed to them.

The internal links step is the easiest one to skip. Old blog posts and navigation menus keep pointing at deleted pages long after the cleanup. Visitors hit errors, and crawlers keep finding those URLs through your own links. A quick crawl of your site after any cleanup will surface them.

Sitemaps drift too. If your sitemap still lists deleted URLs, you are telling search engines to check pages you know are gone. I wrote about catching that in what to do when your sitemap drifts from your real page set.

What should you check on your own platform?

Check three things: what status your platform returns for a deleted page, whether it can return a 410 at all, and how redirects are managed. Hosted site builders differ on this, so test rather than assume. If yours cannot return a 410, a clean 404 is fine for Google.

You can check status codes yourself with your browser's developer tools or any HTTP header checker. Visit a URL you know you deleted and look at the response code. If it says 200, you have a soft 404 problem to fix before anything else.

For redirect setup, follow your platform's own documentation for the current menu path and any plan requirements. If you build on Webflow, its help center lists the current steps for redirects on your plan.

Is a temporary removal any different?

Yes. If a page is down for a short time, such as during maintenance or a product pause, neither 404 nor 410 is right. Both tell search engines the content no longer exists. A temporary situation calls for a different response, so the page can come back without losing its place in the index.

The decision tree is simple once you see it. Gone for good with a replacement: redirect. Gone for good with no replacement: 404 or 410. Coming back soon: do not use a 4xx at all.

I covered the temporary case in detail in what a temporarily unavailable page should return, so I will not repeat it here. If a page must disappear from results before Google recrawls it, read when to use the Search Console Removals tool.

What should you do next?

List the pages you plan to remove and mark each one as redirect or remove. Add 301s for pages with a real replacement. Let the rest return a 404 or 410, whichever your platform supports. Then update internal links, clean the sitemap, and check Search Console for soft 404s a few weeks later.

Spend your effort on the redirect map and the internal links, not on the 404 versus 410 choice. That is where cleanups succeed or leave a trail of broken paths behind them.

If you are pruning a Webflow site or a large CMS collection and want a second opinion on the redirect plan, reach out. I am happy to look at what you are removing and help you decide what goes where.