Build a 404 page that guides visitors forward

A custom 404 page that keeps visitors on your site starts with a clear recovery path, not a deceptive trick. When a URL fails, the server must still return a genuine HTTP 404 response, while the page itself helps people continue.

The page should explain what happened, reduce uncertainty and point visitors towards relevant content. It cannot repair a broken link, but it can stop a temporary dead end from ending the entire customer journey.

For Australian small and medium-sized businesses, the same error page may serve national campaigns and location pages for Sydney, Melbourne and Brisbane. It must remain useful on small screens, across devices and for visitors with different browsing needs.

Diagnose the source of 404 errors

Begin with server logs, analytics and Google Search Console. Group errors by requested URL, referring page and date instead of treating every visit alike. Frequent causes include deleted pages, CMS migrations, mistyped links, renamed categories and URLs shared in outdated email campaigns.

Check whether internal navigation or location templates are creating malformed URLs. For a deeper audit, Cosmin Kz’s technical SEO guidance can help distinguish crawl errors from index-coverage problems.

Add recovery choices and reassurance

Start with routes that help visitors continue their task:

Then provide enough context to reassure visitors:

Keep the choices focused. A location finder, help centre or contact form can be more useful than a large collection of unrelated links. The recovery path should reflect the sections customers use most often.

Write clear, calm error copy

Use plain Australian English and put the next action near the beginning of the message. For example: We couldn’t find that page. Try a search or choose one of the links below. This is more helpful than a technical message about an invalid request.

Match the wording to the page’s purpose, and avoid blaming visitors for clicking an outdated link. A temporarily unavailable page may require a maintenance response rather than a 404, while a page scheduled to return later should not be described as permanently removed.

Design for phones and accessibility

Design the page for small screens first. A visitor checking a service while travelling on public transport in Melbourne or Sydney may have limited time and a slow connection. Large touch targets, concise text and a simple layout make the recovery options easier to use one-handed.

Provide descriptive link labels, logical heading order, visible keyboard focus and strong colour contrast. Avoid image-only buttons and text embedded in graphics. Accessibility also supports a business’s obligations under the Disability Discrimination Act 1992 where applicable and helps more customers complete the same journey independently.

Keep the page fast and on brand

Carry the logo, colours, typography and tone of voice from the main website, but avoid distracting animation or an oversized background image. Visitors have already encountered a problem; the page should feel calm, familiar and easy to navigate.

Connection speeds can vary outside major metropolitan areas, including regional Australia. Compress images, remove unnecessary scripts and avoid autoplay video. A lightweight page loads quickly on both mobile devices and slower networks.

Measure recovery while protecting trust

Track 404 views, search terms used within the page, recovery-link clicks, contact actions and subsequent conversions. Compare results before and after redesigning the page to see whether visitors are finding useful content instead of immediately leaving.

For campaign-level attribution, teams can work with digital marketing agency Mitora to connect error journeys with marketing campaigns and lead outcomes. A rise or fall in 404 traffic should also be compared with broken-link reports, since retention alone cannot identify the underlying cause.

Review any search terms, IP addresses or contact details collected by the page. Under the Privacy Act 1988 and the Australian Privacy Principles, where applicable, collect only necessary information, explain how it will be used and set an appropriate deletion period.

Test the page and prevent recurrence

Open a deliberately missing URL and confirm that the server returns a 404 status rather than a 200 response. Test every link, search function and contact action on desktop and mobile devices, using both a keyboard and a screen reader where possible.

Maintain the page as the website changes. Fix the internal links or content responsible for each error, and use a permanent redirect only when a genuine equivalent page has moved. Review error reports after CMS or plugin updates, new campaigns and the removal of old landing pages; a useful recovery page works alongside reliable link management rather than concealing it.