404 Errors: How They Hurt SEO and How to Fix Them

A 404 error means the page a visitor asked for no longer exists at that address — and learning how to fix 404 errors starts with one honest fact: Google says a 404 on its own does not hurt your rankings. The real damage is quieter. Lost visitors, lost enquiries, and link value pointing at a page that has simply gone.

So do not panic about every 404 in your Search Console report. Just learn which ones cost you money, and which ones Google itself tells you to leave alone.

What Is a 404 Error, Really?

When someone clicks a link or types an address, your website’s server looks for that page. If it cannot find it, it answers with a status code of 404, and the visitor sees a “Page Not Found” message. The page might have been deleted, renamed, or moved without a redirect. Sometimes the link itself just has a typo in it.

There is also a sneakier cousin called a soft 404: a page that shows “not found” wording but returns a success code instead of a real 404. Google finds that confusing, and a soft 404 is actually worse than a proper one.

Here is the part most guides bury: Google treats 404s as a normal part of the web. A handful on a small site is no sign of trouble, and Google has said plainly that 404s alone do not count against your other pages. What hurts is when a page you care about — a service page, a product page, a post that ranked well — starts returning a 404. Google drops it from search results over time, and its visitors and enquiries go with it.

How to Fix 404 Errors: The 4-Step Triage

Forget fixing every 404 you can find. Sort them first, because the fix depends on what the page was and who still wants it.

Step 1: Find them. In Google Search Console, go to Indexing, then Pages, and look for the “Not found (404)” row. That is your free, official list. The free version of Screaming Frog also crawls up to 500 pages and shows every broken internal link. See also our guide to broken links and how to fix them.

Step 2: Sort them into four piles. For each 404, ask one question: did this page matter?

• The page moved. Add a 301 redirect from the old address to the new one. A 301 tells Google and visitors, permanently, where the page went.
• Something similar exists. Redirect to the closest match, not the homepage. A visitor looking for your old “emergency call-out” page wants your current emergency page.
• Gone for good. Leave the 404, or use a 410 if you are certain it will never return. Google treats both the same for indexing.
• Should still exist. Restore it. This is the urgent pile: a page with traffic, backlinks or internal links that broke by accident. Fix it first.

Step 3: Fix the links at the source. A redirect is a bandage, not a cure. If your own menu, footer or blog posts still link to the old address, update them to point straight at the new page. See our guide to internal linking for why this housekeeping matters.

Step 4: Check your work. Visit the old address yourself: you should land on the right page, not a dead end and not the homepage. Then ask Google to re-crawl the fixed page through Search Console’s URL Inspection tool. Google’s documentation on how HTTP status codes affect crawling confirms fixed pages return to the index once recrawled.

The Mistakes That Make 404s Worse

Redirecting everything to the homepage. It feels tidy, but Google may treat a homepage redirect as a soft 404 anyway, and your visitor, who wanted a specific service page, will usually hit Back and call your competitor instead.

Ignoring soft 404s. If your theme shows a “page not found” message while returning a success code, Google cannot tell the page is gone. Ask your developer to confirm missing pages genuinely return a 404 status. This quiet technical SEO issue can silently hold a site back.

Letting redirect chains grow, and forgetting mobile. Page A redirecting to page B, which redirects to page C, wastes Google’s attention and slows visitors down. Always point old redirects directly at the final page. And Google now crawls the mobile version first: a page that works on desktop but 404s on mobile is treated as gone.

Build a 404 Page That Saves the Visitor

Picture this. A customer in Leeds is looking for a bakery that does wedding cakes. She clicks an old link and lands on your 404 page. On a bad 404 page, she sees a blank screen saying “Not Found” and nothing else, and she leaves. On a good one, she sees a short apology, your normal menu, a search box, links to your most popular pages, and a big “Order a cake” button. She stays. That is the difference between a dead end and a second chance, and it costs almost nothing to build. One rule is non-negotiable: your 404 page must return a real 404 status code, or it becomes a soft 404 itself.

Your 20-Minute Monthly 404 Routine

Once a month, set a timer and work through this list. It is the simplest version of how to fix 404 errors before they pile up:

• Note any new 404s in Search Console since last month.
• Fix the urgent pile first: pages with traffic, backlinks, or internal links pointing at them.
• Redirect moved pages to their closest match, and update your own internal links to the new addresses.
• Type your own domain followed by a made-up address, and check what your 404 page looks like to a stranger.
• After any redesign, migration or big clean-up, run the whole check again immediately.

Twenty minutes a month keeps the problem small. If your 404 list suddenly jumps into the hundreds, that is a different signal: something changed on your site, probably a migration or a plugin update, and it is worth investigating before it spreads.

FAQs

Conclusion

So, do 404 errors hurt SEO? Only the ones that matter. A few stray 404s are normal, and Google says so itself. But a broken page that used to bring you customers is a leak in your business, and leaks do not fix themselves. Start this week: open Search Console, fix your urgent pile first, then build a 404 page that gives lost visitors somewhere useful to go.