404 Status Code: What It Means and How to Fix It

What does the 404 status code mean?

A 404 status code means the server was reached, understood the request, and has nothing at the address that was asked for. The full name of the response is 404 Not Found, and it is part of the standard set of HTTP status codes that every web server uses to describe the outcome of a request.

The distinction that matters: 404 is not a failure of the server or the network. The connection worked. The server answered. The answer was that the requested address does not correspond to anything it can serve.

What is an HTTP status code?

An HTTP status code is a three-digit number the server sends back with every response, telling the browser how the request turned out. The first digit sets the family: the 200 range means success, the 300 range means the content moved, the 400 range means the request was faulty or cannot be fulfilled, and the 500 range means the server itself failed.

404 sits in the 400 range, which is why it is described as a client-side error. That wording confuses people. It does not mean your computer is broken; it means the problem is in what was asked for, not in the server's ability to answer.

How is 404 different from 403, 410, and 500?

• 403 Forbidden: the address exists, but you are not allowed to have it. Signing in may change the outcome.
• 410 Gone: the address existed and has been deliberately removed for good. It is a stronger and more permanent statement than 404.
• 500 Internal Server Error: the server broke while trying to answer. Retrying later can genuinely help, which is not true of a 404.
• 301 or 302: the content moved and the server is redirecting you. You normally never see these, because the browser follows them.
• Soft 404: a page that says "not found" in its text while sending a success code. It looks fine to a person and lies to every automated system reading it.

What should I do when I get a 404 error?

1. Check the address for typos, especially in the part after the domain name. Retyping the last section by hand fixes a large share of 404s.
2. Remove the tail of the address one section at a time, back towards the domain, and reload after each cut. This usually lands you on a working section page that links to what you wanted.
3. Use the site's own search box, if it has one, and search for the page title rather than the address.
4. Search the page title in a search engine together with the site's name.
5. Look for a cached or archived copy if the page is genuinely gone and you need what was on it.
6. If the address came from a link on another site or in an email, the link is likely stale. Go to the site yourself and navigate from the top.

Reloading repeatedly does not help. A 404 is a definite answer, not a timeout.

Why does one visitor see 404 and another sees the page?

Several ordinary causes produce this, and none of them mean the page is half-broken:

• The page requires a signed-in session, and the site returns 404 rather than 403 to avoid revealing that the address exists.
• The address is region-restricted and is only served in some countries.
• Your browser or a caching layer is holding an old copy of a page that has since been restored, or the other way round.
• The site was recently rebuilt, and the change has not finished propagating everywhere.
• The two addresses differ in a way that is easy to miss: a trailing slash, capitalization, or a tracking parameter attached to one and not the other.

How should a site owner handle 404 pages?

1. Serve a real 404 status code with your not-found page. A friendly message with a success code is a soft 404, and automated systems will treat the page as real content.
2. Make the not-found page useful: search, main navigation, and links to your major sections, not just an apology.
3. Redirect a removed page to its closest equivalent when one genuinely exists. Do not redirect everything to the home page, which frustrates people and hides the problem.
4. Use 410 for content you removed on purpose and will not bring back, so that automated systems stop asking sooner.
5. Watch your server logs and your search console reports for the addresses generating 404s, and sort them by how often they are requested.
6. Fix the source of the broken link rather than only the symptom. Internal links you control should be corrected at the source; external ones are candidates for a redirect.

Do 404 errors hurt a website?

A page that does not exist should return 404, and doing so is correct behavior rather than a defect. What causes damage is the surrounding pattern: pages that used to work and now 404 without a redirect, internal navigation pointing at addresses that no longer exist, and soft 404s that hide the problem from your own monitoring.

Judge them by request volume. A handful of 404s from ancient links matters far less than a single broken address that appears in your own menu on every page.

What to record before asking someone for help

If you need to report a 404 to a site or to a developer, write down the exact address you requested, where you got it from, the time, and whether you were signed in. Note whether it fails for another person on another network. Those five facts separate a genuinely missing page from a session, cache, or region problem, and without them the answer is always guesswork.