You open Search Console and find a growing list of “Not found (404)” URLs. Your first instinct is to get that number back to zero.

Before you create redirects for the whole list, ask one question: should a useful page exist at each address?

A missing service page and an old, deliberately removed download can both return a 404. They need different decisions. This guide helps you sort the list into three actions: restore, redirect, or leave the missing page alone.

What does a 404 actually mean?

A 404 is the website's response saying it cannot find a page at that address. The number is an HTTP status code: a short message the server sends alongside the page.

It is different from the wording visitors see. A page can say “Sorry, not found” but still send a 200 response, which means success. Google may treat that mismatch as a soft 404. Google does not index pages that return a genuine 404. Google's status-code guide

That does not make every missing address an SEO emergency. Search Console explicitly allows for removed pages with no replacement. The aim is to make important pages available, not to make every URL Google has ever found appear in search. Page indexing report guidance

Use three questions to choose the right action

The examples below are illustrative, not client results.

QuestionExampleRecommended action
Should this page still exist?Your current consulting page disappeared after a website update.Restore the intended page and check its response.
Has the same useful content moved?An audit guide moved from an old address to a new one.Redirect the old address to the relevant new page.
Is it gone with no suitable replacement?A withdrawn download has no current equivalent.Keep a real 404 or 410 response; remove your own stale links.

A 410 means the resource is gone. Google's documentation groups 404 and 410 with the same indexing treatment. There is no need to promise a faster SEO recovery from changing one code to the other. Status-code guide

Restore pages that disappeared by mistake

Start with pages people still need: a service page, a booking page, a useful article or a resource linked from a current campaign.

Check what changed before editing the content. Was the file left out of a deployment? Did someone change the URL? Does the address work with one spelling but fail with another?

If the page belongs at the original address, restore it there. Then follow a real link to it from another page. A successful direct test is useful, but so is checking the route a visitor takes.

For a working page that still is not indexed, use the separate new-page indexing guide. That is a different problem from an address that genuinely returns “not found.”

Redirect when there is a relevant replacement

A redirect sends visitors from one address to another. If a move is permanent, Google recommends a permanent server-side redirect where possible, such as a 301 or 308. Google's redirect guidance

Choose the destination by the visitor's task. Someone opening an old content-audit guide should land on its updated guide, not a general page about your business.

Before adding a redirect, read both the old page's purpose and the proposed destination. If you cannot explain how the replacement answers the same need, pause. A related topic is not always a replacement.

Update links you control to point straight to the new address. This avoids making visitors take an extra step through the old URL.

Keep genuine missing pages missing

A removed page does not need a replacement just because it appears in a report.

You can give visitors a helpful error page with navigation, search or links to useful sections while keeping the correct 404 response. This helps someone recover from a broken link without pretending the original content exists.

Review the links on your own website and remove or correct those that still send people there. Keep removed addresses out of the list of pages you want people to discover. If an external link points to a working page but is absent from the Links report, check backlinks missing from Search Console; that is different from a linked URL returning 404.

Why not redirect every 404 to the homepage?

Imagine clicking “Download the audit worksheet” and arriving on a consultant's homepage. The link loads, but you still have not received the worksheet.

A blanket redirect can hide that broken journey from a simple status check. It does not solve the visitor's problem. Search Console also warns that an unsuitable redirect can be treated as a soft 404. Page indexing report guidance

Use the homepage only when it is genuinely the right destination. Do not use it as a bin for every removed address.

Turn the report into a small work list

Start with a manageable sample rather than assigning every row to a developer. For each URL, record:

  • Intended purpose: what was the visitor trying to do?
  • Current behaviour: what page appears, and what response does it send?
  • Evidence of importance: is it linked from a key page or a current campaign? Did it previously receive search clicks?
  • Decision: restore, redirect to a named destination, or retain the missing response.
  • Owner and check: who will make the change, and how will you confirm it?

Prioritise a broken page that blocks an enquiry over an obsolete URL with no useful replacement. That is a suggested work order, not a universal scoring formula. A large, sudden pattern after a release deserves investigation even before you have traffic data for every address.

For example, if five current service pages fail after an update, check the shared publishing problem first. Creating five unrelated redirects could hide the cause.

Check the fix before closing the task

Ask your developer or use a response-header checker to confirm the server response. Then open the URL yourself.

For a restored page, check that the expected content loads with a successful response. For a redirect, check both the destination address and its content. For a deliberately removed page, check that the helpful error screen still returns 404 or 410.

Use Search Console's URL Inspection for an individual address. Its stored report describes Google's previous crawl, so compare that with the current live behaviour. A fresh website fix does not mean the historical report has already changed. Page indexing report guidance

Keep the decision in your work list. “Intentionally removed; no replacement” is a useful outcome. It stops the same URL becoming a fresh emergency next month.

Need help deciding which issues deserve attention? Book a 30-minute discussion and bring a few example URLs. We can discuss what each page should do before choosing a fix.

Sources checked on 30 October 2026. Examples are illustrative; the prioritisation workflow is a recommendation, not a claim about client results.

Vishnu Sudevan

Senior SEO, AEO & GEO consultant and practitioner. I write about search strategy, the tools I build and lessons from hands-on work.

More about my work →

Need help with a wider search challenge? Explore SEO consulting.