404 Not Found: Causes, Impact and Fixes

A "404 Not Found" message means a browser reached your server, but the server could not find the page that was requested. It is one of the most common errors on the web, and while a single 404 is harmless, a pile of them quietly erodes user trust, wastes crawl effort, and buries pages that used to rank. This guide explains exactly why 404s happen, what they cost you in SEO and user experience, and how to fix each type the right way.

What "404 Not Found" actually means

Every time a browser asks a server for a page, the server answers with a status code. Codes in the 200 range mean success, codes in the 300 range mean a redirect, and codes in the 400 range mean the client made a request the server could not fulfil. According to MDN's HTTP reference, the 404 Not Found status code "indicates that the server cannot find the requested resource." The important nuance is that a 404 does not say whether the page is gone forever or only missing for now. It simply reports that this exact URL has nothing behind it.

That distinction matters because it changes the correct fix. If a page moved, the fix is a redirect. If a page never existed and someone linked to it by mistake, the fix is to correct the link. If a page was deliberately deleted and will never return, the honest signal is a 404 (or a 410 Gone), not a redirect that pretends the content still exists somewhere.

Common causes of 404 errors

Almost every 404 traces back to one of a handful of causes. Identifying which one you are dealing with tells you how to fix it.

• A deleted or unpublished page. Someone removed a product, an old blog post, or a landing page, but links to it still exist across the web and inside your own site.
• A changed URL or slug. You edited a permalink, migrated a CMS, or restructured folders, and the old address no longer maps to anything.
• A mistyped or malformed link. A missing letter, a stray space, or a wrong file extension in an internal link or a link on someone else's site.
• Case sensitivity and trailing slashes. On many servers "/Page" and "/page" are different URLs, and inconsistent linking creates dead ends.
• Broken media and asset paths. Images, scripts, or downloads that were renamed or moved, which show up as 404s in server logs even when the visible page loads.

Broken internal links deserve special attention because you control both ends. When you understand the wider family of broken links and how they hurt a site, the 404 stops looking like a mystery and starts looking like a maintenance task.

The real SEO impact of 404s

There is a lot of folklore about 404s destroying rankings. The reality, straight from Google, is more measured. Google's documentation on HTTP and network errors states that 4xx status codes, except 429, have no effect on crawl rate. In other words, a normal number of 404s will not make Google crawl your site less often.

What 404s do affect is indexing. When a previously indexed URL starts returning 404, Google's indexing pipeline removes that URL from the index. Newly discovered 404 pages are simply not processed. So the SEO cost is not a penalty. It is lost visibility: pages that once earned traffic disappear from search results, and any ranking signals and backlinks pointing at them are wasted unless you redirect them.

How 404s hurt user experience

Search engines aside, a 404 is a broken promise to a real person. Someone clicked a link expecting content and got a dead end. If your error page is generic and offers no way forward, most visitors leave immediately. That lost visit can mean a lost sale, a lost subscriber, or a lost first impression that never comes back.

The links that generate these bad experiences also drag on your reputation with people who never even see the error, because a site riddled with dead links feels neglected. A tidy site with almost no broken links signals care, and that perception feeds into the trust that both users and search engines place in you.

How to find your 404 errors

You cannot fix what you cannot see, so start by gathering a complete list of broken URLs from several angles.

1. Google Search Console. The Pages report under Indexing lists URLs returning "Not found (404)" that Google has tried to crawl. This is the most authoritative view of what Google is actually hitting.
2. A site crawler. A desktop crawler such as the free tier of Screaming Frog SEO Spider walks your internal links and reports every 404 it encounters, along with the pages that link to them.
3. Server logs and analytics. Your access logs record every 404 request, including ones triggered by external links and bots that a crawler might miss.

To go deeper on the workflow of surfacing dead links across a whole site, our guide to a broken link checker and how to read its output walks through interpreting a crawl report line by line.

How to fix 404s the right way

Once you have your list, sort each URL into one of three buckets and apply the matching fix.

1. The page moved or has a close replacement. Set up a 301 redirect from the old URL to the best live equivalent. A 301 tells search engines the move is permanent and passes ranking signals to the new address. Google explicitly recommends a permanent server-side redirect whenever possible in its guidance on redirects and Google Search. Redirect to the most relevant page, not a generic catch-all, so the visitor still gets what they came for.

2. The link is simply wrong. If the destination page exists but the link has a typo, fix the link at its source rather than adding a redirect. Redirects are a cost you pay on every request, so do not use them to paper over a fixable typo in your own navigation or content.

3. The page is genuinely gone for good. Let it return a 404, or a 410 Gone if you want to signal permanence more strongly. Then make sure your custom 404 page is genuinely helpful: keep your header and search box, link to popular sections, and use a friendly tone. A good error page turns a dead end into a new starting point.

Preventing 404s before they happen

Fixing 404s is reactive. The bigger win is preventing them.

• Redirect before you delete or rename. Make the 301 part of the same task, never an afterthought.
• Keep URLs stable. Resist the urge to reorganize permalinks. If you must, map every old URL to a new one first.
• Audit on a schedule. A monthly crawl catches new broken links from edits, expired campaigns, and dropped external resources before visitors do.
• Fix broken outbound links too. Pages you link to can disappear. Periodically re-check external links and swap dead ones for live sources.

Because dead links interact with page speed and stability, it is worth pairing your link maintenance with a review of your Core Web Vitals and overall site health so small technical problems do not compound. For dedicated 404 handling patterns, our deep dive on designing effective 404 pages covers the custom error page in detail, and a redirect checker confirms your fixes actually return the codes you intended.

Frequently asked questions

Do 404 errors hurt my Google rankings?

Not directly. Google states that 4xx errors other than 429 have no effect on crawl rate, so a normal number of 404s will not trigger a penalty or slow crawling. The real cost is lost visibility: a URL that returns 404 is removed from Google's index, so any traffic and ranking signals it earned disappear unless you redirect it to a live page.

Should I redirect every 404 to my homepage?

No. Redirecting unrelated dead URLs to the homepage creates soft 404s, which Google treats as low quality, and it frustrates visitors who wanted specific content. Redirect a missing page only to a genuinely relevant replacement. If nothing relevant exists, let the URL return a real 404 and show a helpful custom error page.

What is the difference between a 404 and a soft 404?

A real 404 returns the 404 status code, honestly telling browsers and crawlers the page is missing. A soft 404 shows a "not found" message to the user but returns a 200 success code, or redirects a dead URL to an irrelevant page. Soft 404s confuse search engines and should be replaced with genuine 404 responses.

How do I find all the 404 errors on my site?

Combine three sources: the Pages report in Google Search Console for URLs Google is crawling, a site crawler such as the free tier of Screaming Frog for internal broken links, and your server access logs for requests that other methods miss. Together they give a complete list of dead URLs and the pages linking to them.

Is 301 or 302 the right redirect for a page that moved permanently?

Use a 301 Moved Permanently. It signals that the change is permanent and transfers ranking signals to the new URL, which is what Google recommends for permanent moves. A 302 is a temporary redirect that keeps the original URL as canonical, so it is the wrong choice for a page that has moved for good.