What exactly does a 404 error mean?
An HTTP 404 Not Found server response means that the requested resource cannot be found at that web address. Perhaps the page URL has changed, a product has been discontinued, a menu link is wrong or someone simply mistyped the address. A 404 refers to that particular URL ; it doesn't mean the entire business website has disappeared.
What you see on screen isn't necessarily the HTTP status code
A visitor may see an attractive, branded “Page not found” screen with navigation, while the server actually returns a 200 OK response. This can confuse search engines: the content says the page is missing, but the status code says it succeeded. A proper custom 404 page returns a 404 status code while helping the visitor find another route.
Not every 404 needs fixing. If an old promotional page has genuinely been withdrawn with no meaningful replacement, a 404 or 410 can be appropriate. But if an active service page linked from your menu returns 404, that is an urgent issue.
Three decisions that protect the customer journey
Missing but still needed
Important service content may need to be restored.
Moved to another page
Redirect to a genuinely suitable new page.
Permanently removed
If there is no replacement, a genuine 404/410 response may be the right answer.
Does Google penalise your website for 404 errors?
According to Google's own guidance, 404 responses generally do not, on their own, harm the indexing or ranking of your entire website. Individual URLs, however, fail to deliver the expected content, and losing an important old page may cost visitors and enquiries. That's why the raw number of errors isn't the deciding factor. What matters is whether the URL should exist, whether other pages link to it, and whether visitors have a genuinely suitable alternative.
A “Not found (404)” notice in Search Console doesn't mean you must create a new page for every URL listed. Search engines may still know about URLs removed long ago, and the report may not reflect the latest server state. If you expect a real page at that address, start by checking the live response and internal links.
You'll find more about indexing reports in the Google indexing troubleshooting guide. For an explanation of the specific HTTP status code, continue with this article.
Three questions: restore, redirect or return a proper 404?
- Should this content still exist at this address? If so, check the exact path, CMS settings, website menu and server. A simple typo or accidental deletion may be responsible. Restore the page or correct the broken link.
- Has the content permanently moved to another URL? If the new page provides the same or substantially equivalent answer, configure a server-side
301or308redirect to the specific new URL. Also update your menu, other internal links, sitemap and the new page's canonical URL. - Has it been removed permanently with no relevant replacement? You can keep the
404response or, where appropriate, return410. Remove the dead URL from the current sitemap and active internal links. Don't send readers to an irrelevant homepage.
This is a decision framework, not an instruction to preserve every historical URL or erase every error. The right solution depends on what the person clicking the original link was hoping to find.
Ten common situations and the right first step
These are illustrative examples; every setting needs checking on the actual website. On mobile, swipe sideways to view the table.
| Situation | Check | Sensible solution | Avoid |
|---|---|---|---|
| 1. Mistyped menu link | Menu href and working destination. | Correct the link, with a relevant redirect if needed. | Leaving an important service page on a permanent 404. |
| 2. Deleted article with no replacement | Is there genuinely no appropriate alternative? | Return 404/410; clean up internal links and the sitemap. | Automatically redirecting everything to the homepage. |
| 3. Renamed service URL | Does the new page meet the same search need? | Old 301/308 → relevant new URL; update internal links. | Leaving a 302 in place for a permanent move. |
| 4. Temporarily paused campaign | Will the page return, and what information is currently available? | Keep useful, accurate information live or use a justified temporary redirect. | An automatic permanent 301 without considering the circumstances. |
| 5. Temporarily out-of-stock product | Is the page still useful today? | It can remain a 200 page with genuine stock information and alternatives. | An empty 200 page saying “not found”. |
| 6. Permanently discontinued product | Is there a genuinely suitable successor? | Consider a 301 to a relevant successor; otherwise use 404/410. | Redirecting to a completely different product. |
| 7. Custom 404 design, but HTTP 200 | Actual server response. | Configure the correct 404 response. | Changing only the visible message. |
| 8. Search Console shows an old 404 | Live URL and last crawl date. | Compare with the current server response and monitor recrawling. | Assuming an old report reflects an immediate, current fault. |
| 9. Random URLs that never existed | Is there a real internal link pointing to them? | Usually return a proper 404; investigate security separately if there is heavy bot traffic. | Redirecting large numbers indiscriminately. |
| 10. An actual 500/503 outage | HTTP status and server logs. | Involve your hosting provider/developer and resolve the temporary fault. | Marking a working page as deleted by changing it to 404. |
When it affects your own business
A link to the wrong place can cost you customers
Not every 404 is a malfunction, but an important service page or enquiry route that no longer works deserves a targeted fix. Have the technical details assessed professionally.
404, 410, 301, 308, 302, 307, 200 and 503: a quick guide
| Code | What does it indicate? | When is it appropriate? |
|---|---|---|
| 200 | The URL returns a successful response. | When the page is real, useful and accessible. |
| 301 / 308 | Permanent redirect. | When suitable content has moved permanently to a new address. |
| 302 / 307 | Temporary redirect. | For a genuinely temporary situation. |
| 404 | The requested URL was not found. | When a page no longer exists or is unavailable without a replacement. |
| 410 | The resource is gone. | When content has deliberately been removed permanently. |
| 503 | The service is temporarily unavailable. | During genuine temporary server issues or maintenance, with appropriate handling. |
A 410 does not automatically carry extra SEO value, and Google does not promise immediate removal from its index. Choose the redirect type based not simply on the code, but on whether the move is permanent and whether the target page is genuinely equivalent .
What is a soft 404, and why is redirecting every broken URL to the homepage a mistake?
A soft 404 can occur when a search engine concludes from the content that a page contains no meaningful accessible information, yet still receives a successful 200 response. Typical examples include an empty search results page or a missing article that returns 200 with a generic “nothing here” message.
Another bad pattern is redirecting every old, unrelated URL to the homepage. That confuses visitors looking for a particular service or product, and Google may interpret the irrelevant redirect as a soft 404. The goal isn't to have zero 404s in your reports; it's to ensure that working pages take visitors to the right place.
If your developer suggests that “all 404s should go to the homepage for SEO”, ask for a URL-by-URL mapping. An old page without a suitable replacement does not need to be redirected at all costs.
How can you check the response your server returns?
A simple fictional redirect example
The following pelda.test addresses are examples, not a real client project or the configuration of kaluzsakrisztian.hu:
GET https://pelda.test/regi-szolgaltatas/
HTTP/1.1 301 Moved Permanently
Location: https://pelda.test/uj-szolgaltatas/
GET https://pelda.test/uj-szolgaltatas/
HTTP/1.1 200 OKThe first request redirects, while the second returns the real content. Ideally, internal menus should point straight to the new URL rather than needlessly passing through the old one.
Developer tools, Search Console and the actual HTTP response
You can check responses in your browser's Developer Tools → Network panel, or with a suitable HTTP testing tool. Advanced example: curl -I https://pelda.test/regi-szolgaltatas/. The -I option sends a HEAD request; some systems respond differently to these, so also check a normal GET request if the results differ. Search Console's URL Inspection tool is useful, but its reports and the live server state may refer to different points in time.
What makes a custom 404 page useful?
It should clearly explain in English that the requested page is missing, retain the site's branding and navigation, offer a meaningful way forward to the homepage or a relevant service and, if needed, provide a way to report the problem. It must also return a genuine HTTP 404 status code. An attractive 404 graphic does not fix a broken menu link.
Which errors should you fix first?
- Urgent: a broken main-menu or quote-request button destination; an important service page that previously brought in search traffic; widespread redirect problems; numerous pages returning 5xx errors.
- Investigate: old backlinks from other websites, incorrect sitemap entries, moved URLs and soft 404 warnings.
- Often fine: a mistyped path that never existed, or a 404/410 for a page genuinely removed without a successor.
Example of a useful bug report: “The /ajanlatkeres/ URL returns 404 although it's still in the menu; the new working page is at /ajanlatkeres-uj/. Please check the old URL's status, the relevant redirect and the menu link.” This gives a developer far more useful information than “Google says my website is broken.” If the missing URL came from another website, first check whether it refers to a former page that really belonged to you. One mistyped external link alone isn't a reason to create new content.
If many URLs have changed during a redesign or domain move, follow the domain migration checklist instead. If traffic has also fallen, start with the traffic diagnosis guide to identify exactly which pages are affected.
Frequently asked questions about 404 errors
Does Google penalise you for a few 404 errors?
Generally not. A 404 response is normal for genuinely removed pages. However, business-critical URLs that have stopped working by mistake should be restored or redirected to a suitable destination.
Which is better, 404 or 410?
Both indicate that the requested page is unavailable. A 410 explicitly signals permanent removal; it doesn't guarantee faster indexing changes or better rankings.
Why does Search Console still show a 404 after I fixed it?
The report may be based on an earlier crawl. Check the live URL and monitor subsequent processing.
Is a WordPress redirect plugin enough?
It only helps if the right URLs redirect to genuinely appropriate new pages, there are no broken redirect chains and the server returns the correct code. It does not replace a full migration audit.
Sources and professional references
Related guides
Next step · Kaluzsa
Don't let your next prospect land on a broken page
If an important page or internal link fails, let's discuss the targeted repair or website redesign it needs.