Every website ends up with a few broken links. A page gets renamed, a product is retired or someone types an address wrong. The visitor then lands on an error page instead of what they wanted. How that page looks and behaves decides whether they stay or leave.
A good error page does two jobs at once. It tells people clearly that the page is missing and points them somewhere useful. It also sends the right technical signal to search engines. Getting both right is simple once you know what to check.
What a 404 error actually means
When a browser asks for a page, the server replies with a status code. A 404 code means the server could not find anything at that address. A 410 code means the page is gone on purpose. Visitors never see these numbers unless the page shows them. Search engines read them on every request.
Google explains in its crawling documentation on HTTP status codes that it treats most 4xx codes the same way. A previously indexed URL that returns a 404 is removed from the index. Google also gradually crawls those addresses less often. Any content on a page that returns a 4xx code is ignored.
Do broken pages hurt your rankings?
This worries many business owners, but the answer is reassuring. Google’s Search Console Help page on 404 errors says that 404 errors won’t impact your site’s search performance. A missing page simply drops out of results. The rest of the site carries on as normal.
That does not mean you can ignore every broken link. If a page has moved, the same help page says to add a redirect. It also suggests mapping common misspellings to the right page. A redirect sends visitors and search engines straight to the new address.
Pages you have removed for good are different. Google’s advice is to let them return a 404 or 410 code rather than redirecting them. Sending every dead link to the home page confuses people. They expected a specific product or article and got something else.
The problem with soft 404 errors
A soft 404 happens when a page looks like an error but the server says everything is fine. The server returns a success code while the page itself is empty or shows an error message. Search Console flags these as soft 404 errors. They hide the real status of the page from search engines.
Google’s help page warns against a few shortcuts that cause trouble. It says not to create fake content, redirect missing pages to the home page or use robots.txt to block 404s. Each of these sends a confusing signal. A plain 404 code is the honest and correct answer.
Problems often creep in after custom changes to a theme or plugin settings. It is worth testing a made up address on your own site now and then. The error page should appear and the server should return a 404 code. If it returns a success code instead, ask your developer to look at it.
What to put on your error page
The page itself should feel like part of your website. Keep your normal header, menu and footer so people do not feel lost. Use the same colours, fonts and spacing as the rest of the site. Good typography matters here too, because the message needs to be read in a second.
Write the message in plain words. Say that the page could not be found and that the link may be old or mistyped. Skip jokes that hide the meaning, and skip technical codes that mean nothing to most people. One short heading and a sentence or two is enough.
Next, give people a clear way forward. A dead end is what makes visitors leave. The options below are useful on most business sites.
- A search box so people can look for what they wanted
- Links to your main services or product categories
- A link back to the home page
- A link to your contact page
Keep the list of links short. Too many choices on an error page create the same confusion you are trying to fix. A clean layout in the style of minimalist website design often works best. A search box and three or four links usually cover what people need.
Finding broken links before visitors do
Search Console lists the URLs Google could not find. Check it every month or two and look for patterns. If many errors come from one old section, a few redirects may solve the lot. Google says errors for addresses that should not exist can be ignored.
Your own internal links deserve a check as well. Menus, buttons and old blog posts often point to pages that have since changed. Fixing the link at the source is better than relying on a redirect. It saves a step for both visitors and search engines.
A rebuild is the most common time for broken links to appear in bulk. If you are planning one, list every current URL before work starts. Map each old address to its new home and add redirects on launch day. Our guide on whether to redesign your website covers the wider planning.
Small details that make a difference
Test the error page on a phone as well as a computer. The search box and links should be easy to tap and the text easy to read. Load speed matters too, so avoid heavy images or animations. People who reach this page are already a little frustrated.
Think about how the page fits your wider design standards. Clear menus, readable text and consistent branding are among the web design practices that help every page. The error page is no exception. Treat it as a real page and not an afterthought.
Frequently asked questions
Should I redirect all broken links to my home page?
No. Google advises against redirecting missing pages to the home page. Redirect a page only when its content has moved to a new address. Otherwise let it return a proper 404 code.
Will lots of 404 errors in Search Console hurt my site?
Google says 404 errors will not affect your site’s search performance. They are a normal part of running a website. Focus on fixing pages that have moved and links you control. Errors for addresses that never existed can usually be left alone.
What is the difference between a 404 and a 410?
A 404 means the page was not found, and a 410 means it was removed on purpose. Google’s help page says it currently treats them the same. Either is fine for content you have deleted for good. Use whichever your platform makes easier.
How do I know if my error page sends the right code?
Type an address that does not exist on your site and see what loads. Your browser’s developer tools show the status code for the page in the network panel. It should read 404, not 200. If it reads 200, ask your web developer to check the site settings.
