Updated 8 October 2026.
A custom 404 page should explain that the requested page is unavailable and help the visitor continue. It also needs to tell crawlers the truth. A polished design is not a reason to return a successful status for content that does not exist.
Keep the HTTP status correct
A genuinely missing page should return an appropriate error response, usually 404, while showing a useful recovery page. Returning 200 with a missing-content message can create a soft 404. Google’s HTTP status guidance explains how these responses affect crawling and indexing.
For an existing page that has moved, redirect to its actual replacement. For content you still intend to offer, restore the content at the promised URL. Do not redirect every unknown address to the homepage or fabricate an empty successful page merely to remove an error count.
Give the visitor a useful route forward
Use a clear heading, one sentence explaining the problem, and a small set of relevant options. Keep normal site navigation available. A search box can help when the site has enough content and the search itself is usable.
- Link to core services, popular categories or the main content directory.
- Offer a contact option where a person can help locate the information.
- Explain the result of each action with a descriptive label.
- Keep decorative artwork secondary to the recovery choices.
- Make the page work in the site’s supported languages.
Use suggestions carefully. A guessed destination can be more confusing than a clear category link. Avoid exposing administrative information, private content or raw error details when trying to make the recovery page helpful.
Implement it in the right layer
On WordPress, the active theme can render the recovery experience through its 404 template. The web server and application routing must still preserve the correct response status. On another platform, use the supported error-page mechanism rather than adding a catch-all route that reports success for every path.
Test a deliberately nonexistent address in a signed-out browser and with an HTTP client. Check the status, title, heading, navigation and displayed language. Repeat the check through the CDN, because cache configuration can change which response a visitor receives.
Repair broken links at their source
Collect the failing URL, referring page and final response. Distinguish a typo from a removed product, an old migration path and a link to an unpublished article. The right repair depends on that history.
Update internal links to the correct destination. Add a permanent redirect when a genuine replacement exists. Restore important missing pages with complete content where appropriate. Keep an error response for an address with no meaningful destination.
After a repair, check both the original link and the final page. Avoid redirect chains, and update navigation, canonicals and sitemaps where a public URL has changed.
Accessibility and performance checks
A recovery page should load quickly and remain usable with a keyboard. Check visible focus, search labels, contrast and the order of the recovery options. Respect reduced motion and keep decorative animation from delaying interaction.
Monitor whether visitors can reach useful content from the error page. Review recurrent failing URLs and fix the causes rather than relying on the error-page design to compensate indefinitely.
Frequently asked questions
Should a custom 404 page return 200?
No, when the requested content genuinely does not exist. Use 200 for real available content and an appropriate error response for missing content.
Should every missing URL redirect to the homepage?
No. Redirect to a meaningful replacement when one exists. Otherwise provide a helpful error page with recovery options.
What if a linked article is scheduled for the future?
Remove the premature public link until publication, or complete and publish the article if the owner wants it available now. A public link should match the availability of its promised content.
For a URL inventory and implementation review, see our website services or request a technical audit.
A visible HTML sitemap, like ours, gives every lost visitor a route back to the page they wanted.
Want this handled for you?
We build and optimise sites like this every week. Book a free 30-minute call and we will tell you exactly what we would change on yours.
Get a free site review
