Designing a useful 404 page: help visitors find their way
Someone opens a link in an old proposal and reaches an empty screen instead of the service they expected. A useful 404 page explains the problem and offers a sensible next step. This guide focuses on recovery from a missing URL, rather than the wider process of redesigning a website.
Distinguish missing content from moved content
Give your agency two sample URLs: one that never existed and one for a service that has moved. They should not automatically receive the same treatment. Where a genuinely equivalent page exists, a redirect may be appropriate. Otherwise, provide a helpful error page. Sending every old address to the homepage obscures what the visitor originally wanted.
Google may classify an error page returned with a success response as a soft 404. A visible “not found” message does not prove that the server sends the correct HTTP status. Ask the technical team to verify both the page and its response.
Make the message more useful than the code
An illustrative message is: “We could not find this page. The address may have changed or the link may be incomplete.” Follow it with usable choices. This is a suggested wording exercise, not a reported client result. Avoid blaming the visitor or letting a joke make the problem harder to understand.
Your brand can still sound welcoming. However, someone seeking help should not need to wait for an animation to finish. Begin with a short explanation and links whose labels identify their destinations.
Choose recovery routes from real content
For a service business, “Explore services”, “View projects” and “Contact us” can be useful starting points. Adapt them to your content rather than treating three buttons as a universal formula. A large catalogue may benefit from search; a small website does not need an empty search box added just for appearance.
If search is available, design its no-results state too. Do not offer a way out that leads to another unexplained dead end. Make the behaviour of telephone and messaging links clear before visitors activate them.
Try the return journey on a phone
Open a deliberately broken address in the preview, choose a recovery link and use the browser’s Back control. Can you read the menu, explanation and actions together? Does a decorative illustration push the useful options too far down a small screen? Also follow the links using a keyboard.
Attach a short record to design approval: tested address, message shown, selected link and destination reached. This gives the team evidence of a working recovery route instead of approval based only on an attractive screenshot.
Turn recurring errors into maintenance work
Keep a list of repeatedly requested missing addresses after launch. Fix links in your own navigation, or alert the team responsible for an older campaign. Assign an owner and resolution status to each issue. When publishing new content, also check links to pages that have been removed so the same fault is not recreated.
For wider migration planning, read our guide to preserving existing URLs or explore our web design service. A helpful error page supports the experience; it does not independently guarantee search rankings or increased sales.
Frequently asked questions
Should every 404 automatically redirect to the homepage?
No. Consider a redirect where equivalent content exists. Otherwise, explain the missing page and let visitors choose a relevant destination.
Can I approve a 404 page from its design file alone?
A design file can show readability, but test the status code, links, mobile layout and return journey on the running website.