What Is a 404 Error? Page Not Found Management Explained
A 404 error is the HTTP status code a server returns when it has nothing at the requested URL: “Not Found.” It is a normal part of how the web works, not a sign that a site is broken. Managing 404s well means returning the right status for pages that are gone, fixing the ones that waste links or traffic you earned, and catching pages that look like errors but tell crawlers everything is fine.
What the Status Code Means
Status codes in the 400 range describe a request that cannot be fulfilled as made; 404 means the server found nothing at that path. That is different from the 500 range, where something failed on the server. A custom error page should still send the 404 status in the HTTP response, even while it shows visitors a friendly message. Crawlers and monitoring tools read the status; people read the page.
How Google Treats 404s
Google’s documentation on HTTP status codes is direct: “Google doesn’t index URLs that return a 4xx status code, and URLs that are already indexed and return a 4xx status code are removed from the index.” It also states: “The 4xx status codes, except 429, have no effect on crawl rate.” A 404 removes that page from Google’s index, and by Google’s statement it does not slow the crawling of the rest of the site.
404, 410, and Soft 404
| Type | What it is | When it applies |
|---|---|---|
| 404 Not Found | Nothing exists at the URL | The default for missing content |
| 410 Gone | The resource existed and was removed on purpose | When you deliberately deleted content |
| Soft 404 | A page that tells the visitor it does not exist but returns <!–INLINECODE0–> (success) | A misconfiguration to fix |
The choice between 404 and 410 matters little for search. Google’s John Mueller said the difference “is so minimal that I can’t think of any time I’d prefer one over the other for SEO purposes,” as Search Engine Journal reported.
Soft 404s are the case to fix. Google’s guide to troubleshooting crawling errors describes a soft 404 as “a URL that returns a page telling the user that the page does not exist and also a 200 (success) status code,” and notes that Search Console shows a soft 404 error when Google’s algorithms detect from the content that the page is an error page. Empty search result pages, discontinued products with no content, and JavaScript pages that fail to load their content while returning success are examples.
When 404s Cost You Something
Routine 404s come from ordinary change: an old post deleted, a product discontinued, a mistyped URL. Two situations deserve action:
- A page that other sites link to now returns 404. The link, the referral traffic, and the visitor’s path are lost. If there is a relevant replacement, a permanent redirect to it keeps them.
- Many working URLs start returning 404 at once after a migration, a broken template, or a CMS update. Visitors following bookmarks and old results hit dead ends, and pages you wanted indexed drop out of the index.
The goal is not zero 404s. It is finding the ones that represent lost value.
Finding Them
- The Page indexing report in Search Console lists URLs Google found as “Not found (404)” and, separately, soft 404s.
- Server logs record every request with its status code and source, including requests from other search engines’ crawlers.
- A site crawler finds broken internal links, which are 404s you created yourself.
- The URL Inspection tool checks a single URL as Google sees it, including a live test.
- Google Analytics does not record status codes on its own. To see 404 visits there, give the error template a distinct page title you can filter on or send a custom event from it.
Handling Each One
- Redirect permanently when the old URL has links or traffic and a relevant page now covers the same thing. Do not send unrelated URLs to the homepage; that leaves visitors without what they were looking for.
- Leave it as a 404, or switch to 410, when the content is gone and has no replacement, then remove the URL from the sitemap and update the internal links that still point to it.
- Fix soft 404s by making the server return a real 404 or 410 status for missing content.
Make the error page useful: say clearly that the page was not found, keep the site’s navigation, and offer search or links to main sections. Then watch the Page indexing report and logs for sudden increases, which point to a migration problem, a broken plugin update, or a bad redirect rule.
Single-Page Applications
Client-side routed applications can return 200 for every route, including ones that do not exist, because the routing happens in the browser after the JavaScript loads. A crawler then sees a success status for what is really an error page. Where the framework and server allow it, have the server return a real 404 for unknown routes. Where it does not, Google’s JavaScript SEO guidance gives two options: redirect with JavaScript to a URL for which the server responds with a 404 status, or add a noindex robots meta tag to the error view. A friendly “not found” message alone still leaves a 200 status. Check the result with the URL Inspection live test.