HTTP 404 Not Found means the origin server did not find a current representation for the requested resource, or is not willing to disclose that one exists. It does not by itself prove whether the problem is temporary or permanent.
Why a visitor sees a 404 page
- The URL was typed or copied incorrectly.
- A page was moved or deleted without a redirect.
- An internal or external link is outdated.
- Filename case differs on a case-sensitive server.
- A deployment omitted a file or route.
- Rewrite rules or application routing do not match.
- The server intentionally hides whether a protected resource exists.
What a visitor can try
- Check the address for missing characters, spaces, or punctuation.
- Return to the site's home page and navigate normally.
- Use the site's search or sitemap.
- Remove tracking parameters if the base URL is known.
- Report the broken link with the page it appeared on.
Repeated refreshing rarely fixes a genuinely missing route, and clearing browser data is not a universal 404 solution.
How a site owner should diagnose 404s
Confirm the actual response with browser developer tools or an HTTP client. Then check application routes, server rewrite rules, deployment output, filename case, permissions, and CDN behavior. Search access logs to learn which pages or websites link to the missing URL.
A styled error page can look correct while accidentally returning 200 OK. That is often called a soft 404. The HTTP response should still be 404 when the resource is missing.
Restore, redirect, or keep the 404?
Restore the page when it was removed accidentally. Use a permanent redirect when there is a genuinely equivalent replacement. Keep a real 404 when no replacement exists. Redirecting every missing URL to the home page confuses visitors and search systems.
For content intentionally and permanently removed, 410 Gone can communicate that choice explicitly, although a normal 404 is also acceptable in many workflows.
Build a useful 404 page
Keep the message plain, preserve the site's navigation, link to popular categories, and provide a way to search or report a broken link. Do not blame the visitor. Avoid auto-redirecting after a timer because it hides the failed URL and disrupts troubleshooting.
Prevent broken links
- Use stable, descriptive URL slugs.
- Update internal links during migrations.
- Maintain a redirect map for renamed pages.
- Validate generated links in builds.
- Review high-traffic 404s in server logs and search tools.
- Keep canonical and sitemap URLs consistent with live routes.
Frequently asked questions
Does a 404 mean the whole website is down?
No. A working server produced a response for one URL. Other pages may be available. DNS failures, connection timeouts, and 5xx errors describe different layers of failure.
Will changing a 404 to 301 fix SEO automatically?
Only redirect when a close replacement exists. A misleading redirect transfers visitors to an unrelated page and can be treated like a soft 404. Repair internal links and remove obsolete sitemap entries too.
Can a page look like a 404 but return 200?
Yes. That soft-404 pattern often occurs when an application renders a not-found template without setting the HTTP response. Check the Network panel or an HTTP client, not only the visible page.
Sources checked
The standards definition of HTTP 404 was checked on August 12, 2026; use the linked RFC when precise caching or response semantics matter.