Seeing a 404 Not Found error? Learn what causes it and how to fix it fast, whether you’re a visitor following a link or a site owner troubleshooting.
So, you have clicked a link, expecting to land on a page, and instead you get “404 Not Found.” No content, no redirect, just a message telling you the page you wanted isn’t there.
Here’s what’s actually happening: the server you reached is working fine. It received your request without any trouble. It just couldn’t find anything at that specific address. That’s different from a permissions problem or a server crash. The page you’re looking for simply doesn’t exist where you expected it.
This error shows up for everyday visitors clicking old links, and it shows up for site owners watching their search rankings slip because of broken pages.
Today, you’ll learn what causes a 404 not found error, how to fix it depending on whether you’re a visitor or a site owner, and how it’s different from similar codes like 403 and 500.
What Is a 404 Not Found Error?
A 404 not found error means the server successfully received your request but couldn’t locate the specific page, file, or resource you asked for at that address. The connection worked. The lookup failed.
This is an important distinction from other errors. A 403 means the server found the resource but refuses to hand it over. A 500 means something broke on the server itself. A 404 means neither of those happened. The server is running normally, it just has nothing to show you at that particular web address.
Visitors usually see this after clicking an outdated link, mistyping a URL, or following a bookmark to a page that’s since been moved or deleted. Site owners see it when their own internal links point to pages that no longer exist, or when a page has been renamed without updating the paths that lead to it.
What Causes a 404 Not Found Error?
There’s almost always a specific reason a page can’t be found. Here are the most common ones.
Mistyped or Incorrect URL
The simplest cause is also the most frequent: a typo in the address bar, a missing character, or an extra slash that points to a location that was never a real page.
Page Moved or Deleted Without a Redirect
When a page gets moved to a new address or removed entirely, any old links pointing to it will lead nowhere unless a redirect is set up to send visitors to the right place.
Broken or Outdated Links
Links inside a website, or links from other websites pointing in, can become broken over time as pages get renamed, restructured, or taken down. These are often called dead links.
Incorrect Permalink or CMS Settings
Content management systems like WordPress generate page addresses based on permalink settings. If those settings change or become misconfigured, previously working URLs can suddenly return a 404.
DNS or Virtual Host Misconfiguration
If a domain points to the wrong server, or if a server isn’t set up to recognize a particular domain or subdomain, every page on that address can return a 404, even though the site itself exists somewhere.
Missing or Corrupted .htaccess File
On many servers, a configuration file called .htaccess handles URL rewriting and redirects. If this file is missing, damaged, or set up incorrectly, valid pages can suddenly appear as not found.
Browser Cache Issues
Sometimes your browser holds onto an old version of a page’s address. If that page has since moved, your cached version can lead you to a dead end even though the current page exists elsewhere.
Server or Web Application Configuration Errors
Misconfigured routing rules in web server software like Nginx or Apache can cause the server to look in the wrong place for a file, returning a 404 even when the actual file exists on the server.
CDN or Caching Layer Issues
A content delivery network sometimes serves an outdated cached version of a page that no longer matches the current site structure, which can result in a 404 not found for a page that technically still exists.
Soft 404s
Occasionally, a server returns a normal looking page along with a 404 status code, or the reverse, a working looking page that’s actually empty or broken. These “soft 404s” can confuse both visitors and search engines about whether a page truly exists.
How to Fix a 404 Not Found Error
Related:
- 502 Bad Gateway: What It Means and How to Fix It
- 401 Unauthorized Error: What It Means and How to Fix It
For Website Visitors
Try these steps first, in order:
- Check the URL for typos. A single misplaced character or missing letter is one of the most common causes.
- Refresh the page. Occasionally a 404 is a brief glitch that clears up with a simple reload.
- Search for the page instead. If the content has moved, a quick search using the page’s title often leads you to its new address.
- Clear your browser cache and cookies. Outdated cached data can occasionally point you to an old, no longer valid address.
- Try a different device or browser. This helps confirm whether the problem is tied to your setup or the page itself.
- Check an archive of the page. Tools like the Wayback Machine can show you what a page looked like in the past, which is useful if you need the original content.
- Contact the website. If you believe the page should exist, letting the site owner know helps them fix a broken link they may not be aware of.
Tip: If other pages on the same site load normally, the issue is almost always tied to that specific link or URL, not the whole website.
For Website Owners
If your site is generating 404 errors for pages that should work, or that used to work, go through this list:
- Check your permalink settings. Make sure your CMS’s URL structure matches the actual paths your pages use.
- Set up redirects for moved or deleted pages. A redirect sends visitors and search engines straight to the new location instead of leaving them at a dead end.
- Audit your internal links. Use a site crawler tool to find broken links pointing to pages that no longer exist, then update or remove them.
- Review your .htaccess file. Look for missing rules, typos, or corruption that could be preventing valid pages from loading correctly.
- Verify your DNS and server configuration. Confirm your domain points to the correct server, and that the server recognizes the domain or subdomain being requested.
- Check your CDN or cache settings. Clear outdated cached versions of pages that no longer reflect your current site structure.
- Monitor 404s through Search Console. Regularly check for reported not found errors so you can catch and fix them before they affect too many visitors.
- Create a helpful custom 404 page. For cases where a 404 is expected and correct, a well designed error page with navigation options keeps visitors from leaving entirely.
Common 404 Not Found Messages
The exact wording can vary depending on the browser, server, or platform, but they all describe the same missing resource:
- 404 Not Found – the standard version of this status code.
- HTTP Error 404 – the same error, referenced by its numeric code.
- 404 Page Not Found – a more descriptive phrasing many sites use.
- The requested URL was not found on this server – a technical explanation some servers display directly.
- This page doesn’t exist – a plain language version aimed at everyday visitors.
404 vs 403 vs 401 vs 500 Errors
These codes are often mixed up, but each one points to a different kind of problem.
| Code | Meaning | Typical Cause | Who Usually Fixes It |
|---|---|---|---|
| 401 | Unauthorized | Missing or invalid authentication credentials | Visitor (login) or site owner (auth settings) |
| 403 | Forbidden | A rule or permission blocks access to a resource that exists | Site owner or server administrator |
| 404 | Not Found | The page or resource doesn’t exist at that address | Site owner or content editor |
| 500 | Internal Server Error | A general failure in the server’s own code or setup | Site owner or developer |
Frequently Asked Questions
Is a 404 Not Found error my fault? Sometimes, if you mistyped the address or followed an outdated bookmark. Just as often, it’s caused by the website moving or deleting a page without setting up a redirect.
Can I fix a 404 Not Found error? As a visitor, you can usually work around it by checking the URL, searching for the page elsewhere, or trying an archived version. If the page is genuinely gone, only the site owner can restore it or redirect you to new content.
What is the difference between 404 and 403? A 404 means the page doesn’t exist at that address. A 403 means the page does exist, but access to it is specifically blocked.
Does a 404 error mean the website is down? No. The website itself is working. Only the specific page or file you requested is missing, while the rest of the site can function normally.
Why am I getting a 404 Not Found error? It’s usually caused by a typo in the URL, a page that’s been moved or deleted, an outdated link, or a misconfigured setting like permalinks or DNS on the website’s side.
Does clearing cache fix a 404 error? Sometimes, especially if your browser was holding onto an old address for a page that has since moved. It won’t help if the page is genuinely gone.
Can a 404 error hurt SEO? Yes, if it happens on pages that should be working, or if too many broken links accumulate over time. Search engines can lower trust in a site with a high number of unresolved 404 errors.
What should website owners check first? Start by confirming whether the page was intentionally moved or deleted. If so, the fix is usually setting up a redirect rather than digging through server configuration.
Is every 404 error a problem? Not necessarily. A 404 for a page that’s genuinely gone, like an old product that’s been discontinued, is expected and correct. The concern is 404s appearing on pages that should still exist.
Final Thoughts
A 404 Not Found error looks discouraging, but it almost always comes down to one simple fact: the server is fine, and the specific page you asked for just isn’t at that address anymore.
If you’re a visitor, start with the basics. Double check the URL, try searching for the page directly, and clear your cache before assuming the content is gone for good.
If you manage the website, check your permalinks, set up redirects for anything that’s moved, and audit your internal links regularly. A 404 error is usually a quick fix once you find out whether the page was moved, deleted, or never existed at that address in the first place.