Browse
Log in / Register
Share
Editor’s note: This article was updated on May 11, 2026.
There you are, clicking a link that seemed perfectly fine. Instead of content, you get a stark “404 Not Found” message. For website owners, that moment is more than a small annoyance—it’s a pain point that can cost you a sale, a reader, or a ranking. But what exactly causes a 404 error, and how do you fix it without tearing your hair out?
Let’s back up a bit. A 404 status code is a standard HTTP response that tells browsers and crawlers “the page you asked for doesn’t exist.” The message itself is simple, but the underlying reasons aren’t always obvious. It could be a mistyped URL, a deleted page, a broken internal link, or a redirect that’s gone wrong.
HTTP status codes are grouped into classes. 2xx means success, 3xx means redirect, 4xx means client error, and 5xx means server error. A 404 is in the client-error group, which sounds a bit harsh. In plain English, the server reached the request but couldn’t find the resource.
That distinction matters for SEO. Search engines like Google treat 404s as normal, provided they’re returned for pages that truly don’t exist. The problem arises when a URL that should be live returns a 404—or when a page that’s gone returns a “soft 404” instead. This can waste crawl budget and confuse the index.
Most site owners run into the same handful of situations. A page gets deleted without a redirect being set up. A URL slug is changed but no 301 is added from the old to the new address. A third-party site links to an old product page that no longer exists. Someone types the link manually and drops a letter. Any of these can trigger the error.
Another subtle cause: trailing slashes. Some servers treat /services and /services/ differently. If your content management system isn’t configured to normalize those URLs, you’ll see unnecessary 404s.
You shouldn’t wait for someone to tell you about a broken page. A few reliable tools can show you exactly where 404s are happening. Google Search Console’s “Indexing” report lists URLs that Google tried to crawl but which returned 404. That’s the best place to start, because it shows the search engine’s perspective.
For a deeper look, crawl your own site with tools like Screaming Frog, Ahrefs, or Semrush. These will flag every 404, the pages that link to it, and the response status for each URL. You can also set up real-time monitoring in a server log analyzer to catch errors as they happen.
Here’s the nuance that most blog posts never mention. A 404 isn’t inherently bad. Search engines understand that sites remove pages, and they expect a 404 for a URL that has no real replacement.
What hurts is a page that should be live but isn’t. If you changed your URL structure during a redesign and didn’t set up redirects, search engines have to discover that old URLs are dead. Then they’ll drop those URLs from the index, and the link equity you’d built over the years is gone.
Then there’s the so-called soft 404. This happens when a server returns a 200 OK status but shows a “Page not found” message. From a search engine’s perspective, that’s worse than a real 404 because it looks like a page exists when it doesn’t. Google specifically calls out soft 404s as an issue you should fix.
Your first decision is simple: does the page have a replacement? If yes, set up a 301 redirect from the old URL to the new one. A 301 is a permanent redirect, and it tells search engines “this content moved for good.” That passes most of the ranking signals to the new page.
If no replacement exists, you can let the page return a real 404. Some experts argue in favor of a soft 404 to keep visitors on the site, but that’s a misunderstanding. A genuine 404 is honest, and you can make it helpful.
A great custom 404 page does more than apologize. It acknowledges the problem, offers a search bar, lists popular pages, and includes a clear link back to your homepage. This turns a dead end into a path forward.
You’ll want to keep the page on-brand but useful. A funny message can be memorable, but only if visitors can still find what they’re looking for. A few companies playfully tell visitors they’ve drifted into “the phantom zone” or “lost in space.” That’s fine, as long as the navigation is obvious.
One common mistake is redirecting every 404 to the homepage. This is a bad idea. If a user wants a specific product and lands on a generic homepage, they’ll be confused. Worse, search engines may treat your entire site as a set of redirected pages, which wastes crawl budget.
Another mistake is leaving broken internal links untouched. Internal links are a ranking signal, and every broken one is a lost opportunity. A 15-minute crawl can reveal dozens of outdated links inside your articles, footer, or navigation.
Don’t forget external links, either. If your site is a popular reference, other websites will link to your pages using whatever URL they saw. If you change that URL, set a redirect, and those external links will continue sending traffic.
Google’s documentation is straightforward: you don’t need to proactively report a 404. When Google’s crawlers encounter one, they stop crawling that URL and eventually remove it from their index if it’s no longer in your sitemap. That’s the normal lifecycle. In fact, Google’s John Mueller has repeated this point in several office-hours sessions: a proper 404 is not something to panic about.
There’s also a small but important detail about the “Not Found” page title. Many servers default to “404 Not Found” as the page title. That’s fine for a dead page because it won’t be indexed as useful content. But if you’re creating a custom page, make it clear that the content is missing. Don’t stuff keywords there, and don’t include long paragraphs that could be indexed as a low-value page.
You can dramatically reduce 404s with a few simple habits. First, always use a spreadsheet or a note to track URL changes before you migrate. Second, set up 301 redirects immediately after changing a slug. Third, schedule a monthly crawl to catch broken links. Fourth, submit a fresh XML sitemap in Google Search Console after major changes. Fifth, keep an eye on your server logs for 404 spikes.
Maybe you’re thinking, “This all sounds like a lot of work.” It is, but the payoff is a cleaner site that both visitors and search engines trust. A 404 is not a catastrophe. It’s a signal. Once you know what it’s telling you, you can act on it.
The “Not Found” error has been around since the earliest days of the web, and it won’t disappear. What you can control is how your site handles it. A thoughtful mix of redirects, honest 404s, and a user-friendly custom page will keep your rankings intact and your visitors happy.
If you sit down today, open Google Search Console, and fix just the top five broken URLs, you’ll already be ahead of most site owners. That’s a tiny step, but search engines notice. So do users.
Now go check your links. That old product page you deleted in June? It might be waiting for you with a 404.
