4xx Client error
HTTP 404 Not Found
The server can't find the requested resource.
A 404 Not Found means the server is reachable but can't find anything at the requested URL. It's the most familiar error on the web, and it says nothing about whether the page existed before.
Common causes of a 404 error
- The URL has a typo, a wrong path, or the wrong letter case on a case-sensitive server.
- The page was deleted, renamed, or moved without a redirect.
- The file or route wasn't included in the deploy or build.
- A missing rewrite rule, for example a single-page app without a fallback to index.html.
- An API deliberately returns 404 to hide resources you aren't allowed to see.
How to fix a 404 error
- Check the URL carefully for typos, extra slashes, and case.
- Confirm the file or route exists in the deployed build, not only on your machine.
- If the page moved, add a 301 redirect from the old URL to the new one.
- For a single-page app, configure the server to serve index.html for unknown routes.
- If the page is gone for good, return 410 Gone so search engines drop it faster.
Frequently asked questions
Do 404 errors hurt SEO?
A few 404s on pages that no longer exist are normal and don't hurt a site's ranking. It becomes a problem when important pages or pages with backlinks return 404; redirect those with a 301 to the closest matching page.
What's the difference between 404 and 410?
404 says the resource wasn't found and might return. 410 says it's permanently gone on purpose. Search engines usually remove 410 pages from the index faster.
What is a soft 404?
A soft 404 is a page that displays a "not found" message but returns a 200 status. Search engines treat it as a mistake, so return a real 404 status for missing pages.
Other common status codes
See 404 in the full searchable list, or use the HTTP Header Checker to see the status code any URL returns.