You’re clicking a link, maybe one you’ve bookmarked for months, and instead of the page you wanted, you get a stark message: 404 Not Found. No explanation. Just a number and a phrase that tells you almost nothing useful.
Most people shrug and hit the back button. But if you run a website, that 404 is actually a signal worth paying attention to. It can mean a broken link is sitting in your site’s navigation. It can mean Google is crawling a page that doesn’t exist anymore. It can mean a customer who was about to buy something just hit a dead end and left.
What does error 404 indicate, exactly? The short version: the server found your request, understood it, but couldn’t find the specific page you asked for. The server is alive. Your connection is fine. The page just isn’t there. That’s it mechanically. But the real story goes much deeper than that, especially when you start looking at what causes these errors at scale, how they pile up quietly over years on a real website, and what they actually cost you in rankings and revenue.
This post breaks all of that down. You’ll understand exactly what a 404 error is, where it comes from, why it matters for SEO, how Google actually handles 404 pages, and what to do about them. Whether you’re a site owner dealing with a crawl report full of red flags, or just someone who’s curious why the internet keeps showing you this number, this covers it properly.
What Does Error 404 Indicate in Simple Terms
A 404 error is an HTTP status code. When your browser requests a page, it’s sending a message to a web server asking for a specific resource at a specific address. The server responds with a three-digit code telling your browser what happened. 200 means everything is fine. 301 means the page moved permanently. 500 means something broke on the server’s end. And 404 means: the server is running, it received your request, it understood exactly what you were asking for, and it has no idea where that page is.
The full name is “404 Not Found.” The “4” at the start of a status code means it’s a client-side error, which sounds like your fault but isn’t always. It just means the problem lives in the request itself, not in the server’s ability to process it. The page you asked for doesn’t exist at that URL.
The Difference Between 404 and Other Error Codes
People confuse 404 with other errors constantly, so let’s be direct about it.
A 500 error means the server crashed or encountered an internal error. The page might exist, but the server failed trying to serve it. A 403 error means the server knows the page is there but won’t let you see it, usually because of permissions. A 301 means the page moved and the server is redirecting you to its new location. A 410 error is actually more specific than 404: it means the page is gone and it’s intentionally gone for good. Google handles 410s faster than 404s.
The thing about 404 is that it tells you almost nothing about why the page is missing. Was it deleted? Was the URL changed? Did someone type the wrong link? Did the CMS update and break a permalink? You need to investigate that separately.
Why the 404 Code Specifically
The number comes from HTTP, which stands for HyperText Transfer Protocol. HTTP was developed by Tim Berners-Lee and his team at CERN in the late 1980s and early 1990s. The status codes were part of the original spec, with 4xx codes reserved for “client errors,” meaning problems with the request rather than the server. The specific story that 404 was named after “Room 404” at CERN where the original web servers were kept is a myth that spread widely online. It’s not true. The number was just the next available in the 4xx range when the spec was written.
The Main Reasons Error 404 Indicate a Problem on Your Site
Understanding what error 404 indicates is one thing. Actually diagnosing why it’s happening on your specific site is where people get stuck. There are a handful of common causes, and they’re worth knowing because the fix depends entirely on the cause.
Deleted Pages Without Redirects
This is the most common reason 404s pile up on a website. Someone deletes a blog post, removes a product from a store, or takes down a landing page. The URL is gone. The content is gone. But the links pointing to that URL, both internal and external, are still there. Every time someone follows one of those links, they hit a 404.
On an eCommerce site, this happens constantly with seasonal products, discontinued SKUs, and limited-time offers. On a blog, it happens when writers delete old posts or editors clean up thin content. Every deletion without a redirect is a 404 waiting to happen.
The fix is simple in theory: set up a 301 redirect from the dead URL to the most relevant live page. In practice, most sites don’t have a process for this, so the 404s just accumulate over years.
URL Structure Changes
Changing your URL structure without handling the old URLs is another very fast way to generate hundreds of 404 errors in a single afternoon. This happens when a site migrates platforms, changes its permalink structure in WordPress, restructures its category hierarchy, or moves from HTTP to HTTPS without proper setup.
Say you had a blog post at yoursite.com/blog/post-name and then you restructured so all posts now live at yoursite.com/resources/post-name. If you didn’t add 301 redirects from every old URL to the new one, every single old URL is now a 404.
Google had indexed those old URLs. Other websites had linked to them. Your own internal links still point to them. All of that suddenly hits dead ends. A site migration without redirect mapping is one of the most damaging SEO events a website can go through.
Typos and Broken Links
Someone on your team links to yoursite.com/servics instead of yoursite.com/services. Someone on another website links to a URL they typed manually and got wrong. Someone shares a link on social media with a character cut off at the end. These manual errors create 404s that are harder to catch because they never existed as a real URL in the first place, so there’s no historical data to trace them from.
Tools like Screaming Frog SEO Spider can crawl your site and find every internal link pointing to a URL that returns a 404, including typos. Running this crawl monthly on any site over a few hundred pages is worth the time.
External Links Pointing to Dead Pages
When another website links to you, that link has value. It passes authority and sends traffic. If the page they’re linking to returns a 404, that value is wasted. The link still counts as an inbound link in tools like Ahrefs or Semrush, but the destination is a dead end. The equity that link was supposed to pass goes nowhere.
This is one of the most overlooked 404 problems. People focus on crawl errors and user experience, which are valid, but they forget that their best backlinks might be pointing to pages they deleted two years ago. Checking your backlink profile for links pointing to 404 pages and then setting up 301 redirects to the closest live equivalent is genuinely one of the highest-ROI technical SEO fixes you can make.
How Error 404 Affects SEO and Google’s Crawling
A lot of people read that 404 errors are “bad for SEO” without ever getting a real explanation of the mechanism. So let’s actually go through what happens.
Crawl Budget and 404 Pages
Google has a finite amount of capacity it dedicates to crawling any given website. It calls this crawl budget. For a small blog with 50 pages, crawl budget isn’t a real concern. For an eCommerce site with 50,000 product pages or a news site publishing dozens of articles a day, it matters a lot.
When Google’s crawler, Googlebot, visits a URL that returns 404, that’s a wasted crawl. The crawler spent time on a request that yielded nothing. If your site has hundreds or thousands of 404 URLs that Googlebot is still trying to crawl, because they’re in its index or because other pages link to them, it’s eating through your crawl budget on pages that will never rank for anything.
Google has said publicly that they de-prioritize crawling URLs that consistently return errors. But “de-prioritize” isn’t “stop.” Googlebot will keep trying those URLs for a while, which means every crawl of a 404 is a crawl that didn’t go to a real page you actually want indexed.
How Long Google Takes to Drop a 404 From Its Index
This is something a lot of site owners get frustrated about. You delete a page, you see it’s returning 404, but it stays in Google Search Console as an indexed page for weeks. Sometimes months. Why?
Google doesn’t immediately remove a 404 from its index. The crawler has to visit that URL, see the 404, and then decide it’s not coming back. Google typically revisits a URL several times before removing it from the index, because maybe the 404 was temporary (a server hiccup, a deployment issue). Google needs to confirm the page is consistently gone before it stops indexing it.
According to Google’s John Mueller, this process usually takes a few weeks to a few months depending on the site’s crawl rate and how often Googlebot visits those specific URLs. If you want to speed it up, use a 410 status code instead of 404. A 410 tells Google explicitly that the page is intentionally and permanently gone, and Google processes those faster.
Soft 404s: The Sneaky Version That’s Actually Worse
Here’s something that trips up a lot of sites, including some very large ones. A soft 404 is when a page returns a 200 status code (meaning “everything is fine”) but the content of the page is essentially “this page doesn’t exist.” WordPress sites do this when a URL doesn’t match any post but the theme still renders the homepage or a generic page template.
Google hates soft 404s. From Google’s perspective, a 200 status code is a promise that the page has real content. When the crawler arrives and finds a page that says “sorry, nothing here,” it’s a broken promise. Google will often flag these in Search Console, and they can quietly eat crawl budget while appearing to be fine in your analytics.
Fixing soft 404s requires making sure that requests for non-existent URLs actually return a real 404 status code, not a 200. In WordPress, this is usually handled correctly by the CMS, but custom-built sites and some poorly configured servers get this wrong.
Internal Links to 404 Pages
If your own site has internal links pointing to 404 pages, you’re spreading bad signals through your own site structure. PageRank, Google’s original measure of page authority, flows through internal links. When a link points to a 404, that flow goes nowhere. It doesn’t hurt the page it came from, but it wastes the signal.
More practically, when a user follows your internal navigation and hits a 404, that’s a failure of your site’s basic function. Google’s quality evaluators look at user experience, and a site where navigation links regularly point to dead ends is not a site that signals quality.
What Does a 404 Error Page Actually Look Like (and What Should It Look Like)
By default, most web servers return a bare, unstyled 404 page that says something like “404 Not Found” and the name of the web server software. That’s it. No guidance, no links, no help. It’s one of the worst user experiences on the web because it leaves the visitor completely stranded.
Default Server 404 Pages vs. Custom 404 Pages
The default page from Apache might look like this: a white background, “Not Found” in bold, the URL, “Apache/2.4.57 Server” in tiny text at the bottom. Nginx has its own version. IIS has its own. They’re all equally unhelpful.
A custom 404 page is something you design yourself, served at the same URL when a page isn’t found but looking like the rest of your site. It includes your site’s navigation, a search bar, links to popular pages, and maybe a friendly message. Shopify lets you customize this. WordPress has plugins and theme settings for it. On a custom-built site, you configure the server to serve your custom HTML when a 404 occurs.
The goal of a good 404 page is to turn a dead end into a redirect opportunity without using an actual HTTP redirect. The visitor hit a wall; give them a door. The best 404 pages are from brands that put actual personality into them, like GitHub’s 404 page, which shows an octocat floating in space, or Mailchimp’s, which has their mascot Freddie with a helpful search bar. They’re memorable, they keep users on the site, and they reflect the brand.
What to Put on a Custom 404 Page
Keep it simple. The user is already slightly annoyed. They don’t need a long explanation.
Start with a quick acknowledgment that the page doesn’t exist. Something like “Looks like this page moved or never existed.” Then give them useful next steps: a search bar is the highest-value element on a 404 page. Follow that with links to your most-visited or most useful pages. If you run an eCommerce store, link to your most popular categories. If you run a blog, link to your best posts.
Don’t explain HTTP status codes on the 404 page. The visitor doesn’t care. They want to get where they were going.
One thing to be careful about: don’t make your 404 page so engaging that users spend time on it instead of converting. It’s a helpful redirect, not a destination.
How to Find and Fix 404 Errors on Your Website
Knowing what 404 errors are is one thing. Actually hunting them down and fixing them is where most site owners get stuck, because the errors aren’t always obvious and the fix requires a few different tools working together.
Finding 404 Errors in Google Search Console
Google Search Console is free and it’s the first place to look. Go to the “Indexing” section, then “Pages.” You’ll see a breakdown of pages that are indexed and pages that aren’t, with reasons for each. Look for “Not Found (404)” in the list of reasons. Click through and you’ll see every URL that returned a 404 when Googlebot tried to crawl it.
The data in Search Console represents what Google has tried to crawl recently. It won’t catch 404s that Google hasn’t tried yet, and it might include some URLs that were briefly broken and are now fixed. Cross-reference with crawl data from Screaming Frog or Ahrefs for a more complete picture.
Running a Site Crawl With Screaming Frog
Screaming Frog SEO Spider is the standard tool for this. The free version crawls up to 500 URLs, which covers most small sites. The paid version (about $259 per year) crawls unlimited URLs and is worth it for any site over 500 pages.
Run a crawl of your site. When it finishes, go to “Response Codes” and filter for 404. You’ll see every URL on your site that returned a 404, along with which pages link to it. That second part is the piece most people miss. Knowing which page links to a broken URL tells you exactly where to go fix the internal link or set up the redirect.
Finding Backlinks Pointing to 404 Pages
Open Ahrefs Site Explorer or Semrush and look at your backlink profile. Filter for links pointing to URLs that return 404. In Ahrefs, you can do this in the “Broken Backlinks” report. In Semrush, look under “Backlink Audit” for broken links.
Every external link pointing to a 404 page is recoverable with a 301 redirect. Set up the redirect from the dead URL to the most relevant live page, and the link equity flows through. This is a simple fix with a real impact, especially if those links are coming from high-authority domains.
Setting Up 301 Redirects
A 301 redirect is a permanent redirect. It tells the browser and search engines: this page has moved permanently to this new URL. When Google sees a 301, it transfers the ranking signals from the old URL to the new one. It’s not instant, but it’s usually complete within a few weeks.
In WordPress, the Redirection plugin is the easiest way to set this up without touching server config files. You enter the old URL, the new URL, and it handles the rest. In Shopify, redirects are built into the admin under “Online Store > Navigation > URL Redirects.” On a server level, you can set up redirects in the .htaccess file for Apache or in the server block config for Nginx.
Redirect to the most relevant page you have. If you deleted a blog post about “email marketing for beginners” and you still have a live page on email marketing, redirect there. If there’s truly nothing relevant, redirect to the category page. If there’s no category either, redirect to the homepage, though this is the least valuable option because it sends a confusing signal about what the original page was.
Conclusion
A 404 error is simple on the surface, just a page that doesn’t exist at the URL you requested, but the downstream effects on SEO, user experience, and link equity are real and worth fixing. The most important thing to understand is what error 404 indicates in the context of your site’s health: broken links, lost authority from backlinks, and wasted crawl capacity, all of which compound quietly over time if you’re not paying attention.
The fix is straightforward. Audit your 404s with Search Console and Screaming Frog. Set up 301 redirects from deleted or moved pages to the best relevant alternatives. Build a custom 404 page that helps users find what they’re looking for. And make checking for new 404s a recurring part of your site maintenance, not a one-time cleanup. That habit alone will keep your site cleaner than most.
Frequently Asked Questions
What exactly does a 404 error mean?
A 404 error means the web server received your request for a specific URL, was able to process it, but couldn’t find the page at that address. The server is working fine. Your internet connection is fine. The page just doesn’t exist at the URL you requested. It’s an HTTP status code in the 4xx range, meaning it’s classified as a client-side error, referring to the request rather than the server.
Does a 404 error hurt SEO?
Yes, in a few specific ways. 404 pages waste crawl budget when Googlebot keeps trying to visit dead URLs. Broken internal links to 404 pages waste link equity that could have flowed to live pages. And if you have valuable backlinks from other websites pointing to a 404, you’re losing the authority those links were supposed to pass. Fixing 404s, especially with 301 redirects, is a real SEO improvement, not just housekeeping.
What is the difference between a 404 and a soft 404?
A real 404 returns an HTTP status code of 404, which tells browsers and search engines the page doesn’t exist. A soft 404 returns a 200 status code (meaning “success”) but serves content that indicates the page isn’t found, like a blank page or an error message inside the site template. Soft 404s are worse from an SEO perspective because they trick search engines into thinking content exists when it doesn’t, and Google flags them separately in Search Console.
How long does Google take to remove a 404 from its index?
It typically takes a few weeks to a few months for Google to remove a 404 page from its index. Google doesn’t drop pages immediately because transient server errors can also return 404, so it waits to confirm the page is consistently gone. If you want Google to process the removal faster, use a 410 status code instead of 404. A 410 explicitly signals that the page is intentionally and permanently deleted, and Google responds to 410s faster than 404s.
Should I redirect all 404 pages to my homepage?
Redirecting everything to the homepage is better than leaving 404s in place, but it’s not ideal. Google and other search engines recognize when a site redirects all dead URLs to a single destination, and they often treat these as “soft 404s” anyway because the destination page isn’t relevant to what was requested. The better approach is to redirect each 404 to the most topically relevant live page. Homepage redirects should be a last resort for URLs where you have no relevant live content at all.
What causes a 404 error to appear suddenly?
Sudden spikes in 404 errors usually come from one of a few things: a page was deleted or unpublished without a redirect, a URL structure was changed during a site update or migration, a plugin or CMS update broke permalink settings, or a large batch of content was moved and the old URLs weren’t redirected. If you see a sudden jump in 404s in Search Console, check your site’s change log or deployment history for the same time period.
Can users cause 404 errors themselves?
Sort of. If someone types a URL manually and makes a typo, they’ll hit a 404. If someone follows a link from a third-party site that has the wrong URL, they’ll hit a 404 on your site even though you did nothing wrong. You can’t control those situations entirely, but a good custom 404 page with a search bar and helpful links minimizes the damage by keeping the user on your site instead of sending them back to wherever they came from.
Is a 404 error the same as a broken link?
A broken link is a link that points to a URL returning an error. That error is usually a 404, but it could also be a 410, 500, or other error code. So all 404s that are linked to from somewhere are broken links, but not every broken link is necessarily a 404. In practice, most broken links you’ll encounter are 404s because that’s the most common type of “page not here” response.
What is the best HTTP status code to use when I permanently delete a page?
Use 410 Gone if the page is intentionally and permanently deleted with no replacement or redirect target. Use 301 if you have a relevant page to redirect to. In most practical cases, a 301 to the best available alternative is the right call because it recovers any link equity and keeps users on your site. Only use 410 when there’s truly nothing to redirect to and you want Google to process the removal quickly.
How do I fix a 404 error on my WordPress site?
Start by identifying the specific URL causing the error through Google Search Console or a Screaming Frog crawl. If the page was deleted and has a relevant replacement, install the Redirection plugin and set up a 301 redirect from the old URL to the new one. If it’s caused by a permalink structure issue, go to Settings > Permalinks in your WordPress admin and click “Save Changes” to flush the rewrite rules, which often fixes permalink-related 404s without any redirects needed. If the 404 is from a typo in an internal link, find and fix the link directly in the page or post editor.
Do 404 errors affect website speed or performance?
Not directly in terms of load time. A 404 response is actually served very fast because the server doesn’t have to load any real content or run complex queries. But 404s do affect Googlebot’s efficiency on your site, which indirectly affects how quickly your live pages get crawled and indexed. More practically, 404 pages that chain through JavaScript-heavy site templates can sometimes be slower than a clean server-level 404 response, so custom 404 pages should be kept lightweight.
