404 Not Found Website Fixes

Most website wide 404 problems are not accidents of the moment. They are the slow accumulation of deleted posts, renamed pages, a platform migration, or a redesign that changed every URL. This guide is about auditing an entire website for 404s, understanding what they cost in search, and building the redirect map that fixes them for good.

What a website 404 really is

A 404 is a client error status: the server received the request but could not find a page to match the URL. As MDN's HTTP reference explains, a 404 does not tell you whether the page is gone temporarily or forever. For content you have permanently removed, the more precise code is 410 Gone. On a single page this is trivial. Across a website, dozens or hundreds of 404s form a pattern that reflects how the site has changed over time.

Website wide 404s typically come from ordinary growth and change, not a server crash:

• Posts and pages deleted or unpublished without a redirect.
• URLs renamed when titles or categories changed.
• A CMS migration that altered the URL structure, for example changing the permalink pattern.
• A redesign that reorganized navigation and moved everything.
• Products discontinued and their pages removed.

Why website 404s pile up unnoticed

The danger of website level 404s is that they are invisible from the front page. Your homepage works, your new content works, and everything looks healthy while old, linked, indexed URLs quietly return errors. Visitors arriving from old bookmarks, external links, or lingering search results hit a wall, and you never see it because you never click those old links yourself.

This is why website 404s are best found with a crawl rather than by browsing. A crawler follows every link and reports every URL that errors, including the ones no human would think to test.

The SEO cost of an unmanaged website

Google states plainly how it handles 404s: indexed URLs that return 404 are removed from the index, newly discovered 404 URLs are not processed, and crawl frequency for them drops over time. Applied to a whole website, the consequences compound:

• Shrinking index coverage. Every valuable page you let 404 is one fewer page able to rank.
• Lost link equity. External sites that linked to your old URLs now point at errors, so the authority those backlinks carried is wasted unless you redirect the URL.
• Weaker internal structure. Broken internal links break the paths crawlers and users follow through your content.
• Migration losses. The most severe traffic drops usually happen when a site relaunches without a redirect map, orphaning the whole old URL set at once.

For the server side version of a sudden mass 404, see our companion guide on 404 not found across a site. For the plain single page case, read 404 Not Found: causes, SEO impact and how to fix it.

How to audit a whole website for 404s

A thorough audit combines three data sources, because each finds 404s the others miss:

1. Crawl the site. Use Screaming Frog SEO Spider (its free tier crawls up to a set number of URLs) or another crawler to follow every internal link and list each URL that returns 404. This catches broken internal links.
2. Read Search Console. The Pages report, under "Not found (404)," lists URLs Google has tried and failed to fetch. This catches URLs that external sites still link to even if you no longer do.
3. Check your server logs and analytics. Logs show which 404 URLs are still being requested by real users and bots, so you can prioritize the ones with actual traffic.

Combine the three lists, deduplicate, and you have a complete map of every broken URL on the website. Our guide to finding broken links walks through the crawl in detail.

Building the redirect map

With the full list in hand, decide the fate of each URL. Not every 404 deserves a redirect; the goal is to preserve value, not to hide errors.

• Has a clear replacement: redirect it with a 301 to the equivalent live page. This sends users and search engines to the right place and, per MDN's 301 reference, passes ranking value to the new URL.
• Content merged elsewhere: 301 to the page that now covers the topic.
• Gone with no equivalent and no value: let it return a genuine 404, or 410 to signal permanent removal. Do not force a redirect for its own sake.
• Still valuable and deleted by mistake: restore the page rather than redirect it.

Prioritize by value: redirect the URLs with backlinks, past traffic, or internal links first. Verify each redirect resolves in a single hop using our redirect checker guide, since redirect chains dilute the benefit.

Planning a migration or redesign without losing pages

The best time to prevent website 404s is before the URLs change. Follow this sequence for any relaunch:

1. Export every current URL from a full crawl and from Search Console before you change anything.
2. Map old to new for every page that has an equivalent on the new site.
3. Implement 301 redirects from old to new as part of the launch, not as an afterthought.
4. Keep a custom 404 page that helps stranded visitors find their way, with search and popular links. See our guide to the 404 page experience.
5. Recrawl after launch to catch anything the map missed, and submit an updated sitemap.

Keep the website clean over time

A website is never finished, so 404 management is ongoing, not a one time project:

• Recrawl the whole website monthly and clear any new 404s.
• Set a rule that no page is deleted without a redirect decision made at the same time.
• Monitor the Search Console Pages report for new "Not found (404)" entries.
• Use continuous status monitoring so a template or platform change that breaks many URLs is caught immediately.

Website health sits inside a bigger picture. For how broken pages, redirects, and speed fit together, see our Core Web Vitals technical guide and the broader complete guide to SEO.

Frequently asked questions

What does "404 not found website" mean?

It means pages across your website return the 404 status, indicating the server cannot find them. Unlike a one off broken link, website wide 404s usually accumulate from deleted or renamed pages, a CMS migration, or a redesign that changed the URL structure.

How do I find every 404 on my website?

Combine three sources. Crawl the whole site with a tool like Screaming Frog to catch broken internal links, read the Search Console Pages report under "Not found (404)" to catch URLs that external sites still link to, and check your server logs and analytics to see which 404 URLs real users and bots still request. Merge and deduplicate the lists.

Do website 404 errors really hurt my rankings?

Yes, especially in bulk. Google removes 404 URLs from its index, does not process newly found ones, and crawls them less over time. Across a website that means fewer pages able to rank, wasted backlink value, and, after a botched migration, large traffic losses. Redirecting valuable old URLs to their replacements recovers most of that value.

Should I redirect every removed page to my homepage?

No. Bulk redirects to the homepage are often treated as soft 404s because the destination does not match the original request, so the URL still will not rank. Redirect each page to its closest real replacement with a 301, and let pages with no equivalent return a genuine 404 or 410.

How do I avoid 404s when redesigning or migrating a site?

Export every live URL before you change anything, map each old URL to its new equivalent, and implement 301 redirects as part of the launch rather than afterward. Keep a helpful custom 404 page, recrawl after launch to catch misses, and submit an updated sitemap.