DD DevDome Track. Protect. Grow.
Redirects & Links

410 vs 404: Which Status Code to Use for Deleted Pages

Both say the page is missing. Only one says it is not coming back. The difference matters to crawlers, and to how fast your dead URLs drop out of search.

On this page
  1. What each code says
  2. How search engines treat them
  3. The decision in three questions
  4. Look at the 404 log before deciding
  5. Serving a 410 in WordPress
  6. Bulk cleanups: the case where 410 shines
  7. After the status is set

The 410 vs 404 question has a short answer: use 404 when a page is missing, 410 when you removed it on purpose and it is not coming back, and a redirect when something equivalent exists. Browsers show the same error page for both codes. Search engines read the difference as intent, and a 410 tends to clear a dead URL from the index a little faster. Here is when each applies and how to serve a 410 from WordPress.

What each code says

404 Not Found. The server has nothing at this address. It does not say whether there ever was, or whether there will be. It is the default WordPress returns for any URL it cannot match.

410 Gone. The resource existed, it was removed deliberately, and the condition is permanent. The specification suggests clients should not retry it. In practice, browsers ignore the distinction and search engines use it as a hint.

301 Moved Permanently. Not a missing-page code at all. The content lives elsewhere now; go there. This is the one most deleted pages should actually get.

How search engines treat them

Google has stated that both 404 and 410 result in the URL being dropped from the index after it is recrawled, and that 410 is a somewhat stronger signal of intentional removal. The practical effects are small and consistent: a 410 URL may disappear a little sooner and get recrawled less often afterwards. Neither code harms the rest of your site. A site with thousands of 404s is not penalised; it just wastes crawl time.

Where 410 earns its keep is bulk cleanups. Removing an old tag archive, a retired product line or hundreds of spam pages you cleaned after a hack, and marking them all 410, tells crawlers to stop coming back. That is tidier than letting them hit 404 for a year.

The decision in three questions

Is there a page that answers the same need? Redirect with a 301. The old post about a tool you no longer cover goes to the category. The retired product goes to its replacement or its category. The merged article goes to the merged result. Readers arrive somewhere useful and the links pointing at the old URL keep their value.

Did you delete it deliberately with no equivalent? 410. Expired promotions, event pages from years ago, content removed for legal reasons, spam you cleaned up. Nothing useful to redirect to, and you want it gone from search.

Is it just missing, perhaps temporarily, or a URL that never existed? Leave it 404. Typos and bot probes for wp-login variants are 404s. Do not spend time giving them a status code.

Do not redirect everything to the homepage. Google treats an irrelevant redirect as a soft 404, so you get the worst of both: no index benefit and a confused reader.

Look at the 404 log before deciding

A 404 log shows which missing URLs are actually requested and by whom. Separate the bot probes from the human hits. The URLs humans still request are the ones that deserve a redirect, because someone is still clicking a link somewhere. The ones only crawlers request are candidates for 410. DevDome Link Monitor logs 404s with a bot versus human split and suggests redirects for the common ones, which turns this triage into a few clicks. We make it, so weigh that; any 404 log with a bot split does the job.

Serving a 410 in WordPress

WordPress cannot return 410 on its own; it 404s everything it cannot find. Three ways to add it:

A redirect manager rule. The cleanest route if your plugin supports 410 as a rule type for listed URLs or patterns. Check the rule types before assuming; some managers only do 301 and 302.

A server rule. In .htaccess on Apache, a line per URL or a regex returning 410. On Nginx, a location block. Fast and plugin-free, but easy to lose during a migration.

A small snippet. A few lines hooked early in WordPress that check the request against a list and send a 410 header. Fine for a developer, awkward for a long list.

For the redirects that are the better answer in most cases, DevDome Redirect Manager stores unlimited rules for free with 301, 302, 307 and 308 per rule and click counts, so you can see which old URLs still bring people. Its cache purging across ten cache plugins matters here too: a cached copy of a deleted page will keep serving after you remove it unless the cache is cleared.

Bulk cleanups: the case where 410 shines

The clearest use for 410 is after a large deliberate removal. Three examples come up constantly. A hacked site that was cleaned had thousands of spam pages indexed; they are gone, nothing replaces them, and you want them out of search quickly, so a pattern rule returning 410 for the spam path is right. A shop retired a whole category with no successor products; 410 the product URLs and redirect the category to its nearest sibling. A blog deleted its tag archives because they were thin; 410 the tag paths. In each case a redirect would be wrong, because nothing equivalent exists, and a 404 would be slower, because crawlers keep retrying what might merely be missing.

After the status is set

Request removal in Search Console for anything you want hidden quickly. Google hides it within a day or so and the 410 makes the removal permanent when the crawler returns. Then watch the 404 log: if a 410 URL keeps getting human hits, somebody still links to it, and a redirect was the right answer after all.

Related reading: How to Redirect an Old Domain to a New Domain Without Losing Rankings.

Disclosure: DevDome publishes this blog and makes the products it mentions. We describe what they do rather than promise results.

Key takeaways

  • 404 means not found. 410 means gone on purpose and permanently. Browsers treat them the same; search engines do not quite.
  • Google drops a 410 URL from the index somewhat faster than a 404, and recrawls it less. For a bulk cleanup of dead URLs, 410 is the tidier signal.
  • If a replacement page exists, redirect instead. A 301 to the closest live page keeps readers and link value; 410 throws both away.
  • Serve 410 for pages you deleted deliberately with no equivalent: expired offers, retired products, spam you removed.
  • Check the 404 log first. The URLs real humans still request deserve a redirect, not a tombstone.

Sources

  1. MDN: 410 Gone : the definition and intended use
  2. MDN: 404 Not Found : the definition and how it differs from 410
  3. Google Search Central: HTTP status codes and crawling : how Google handles 404 and 410

Links last checked October 17, 2026.

Frequently asked questions

Does Google treat 410 differently from 404?

Slightly. Google has said both lead to removal from the index, with 410 treated as a stronger signal that the removal is intentional, so the URL may drop a little faster and be recrawled less. Neither is a penalty. Do not expect a dramatic difference.

Should I 410 or redirect a deleted blog post?

If you have a post on the same topic, redirect to it. If you have a category page the reader would find useful, redirect there. Only if nothing relevant exists should you 410. Redirecting everything to the homepage is treated as a soft 404 anyway.

How do I return a 410 in WordPress?

WordPress returns 404 for anything it cannot find. To return 410 you need a rule: a redirect manager that supports 410 as a rule type, an .htaccess or server rule, or a small plugin that sets the status for listed URLs.

Will a 410 remove the page from Google immediately?

No. Google has to recrawl the URL to see the new status. Submitting the URL for removal in Search Console speeds up hiding it from results; the 410 then makes the removal stick when the crawler returns.

DevDome Team WordPress plugin builders

The DevDome team builds lightweight, performance-first WordPress plugins and free tools for site owners, founders and marketers. We write about the exact problems our plugins solve, in plain language for people who run real sites.