Designing 404 pages that keep visitors moving
A 404 error page appears when a visitor requests a web address the server cannot find. It can feel like a dead end when the visitor arrived through a search result, campaign link or bookmark. The page should turn that interruption into a clear next step with a calm, useful message.
Many missing-page designs waste attention with clip art, technical jargon or a joke that obscures the way forward. A clean informational site needs a plain explanation, familiar navigation and links that reflect what visitors were seeking.
Good error-page design accounts for why the address failed. A mistyped URL calls for search, while an outdated article link may need an archive or related topic. The requested path and referring source can shape the recovery path without treating every failure alike.
Useful 404 pages handle slow mobile connections, hurried taps, outdated links and visitors who do not know the site structure. These conditions matter across Australian cities, regional communities and busy transport networks, where local language, accessibility and transparent data practices improve inclusion.
Understand the journey behind the error
Before choosing links, identify the routes people use to reach missing content. They may have followed an external article, scanned a QR code, typed a remembered URL or explored a directory that no longer exists. Each route carries different context and needs a suitable recovery path.
The HTTP status code should remain accurate. A missing resource should return a 404 response rather than a success page that hides the problem. Sending every failed request to the home page discards intent and frustrates people seeking one resource. A related destination is usually more useful than a generic one.
Use context carefully. The requested path may reveal a category, date or topic, while referral data may show an external source. This can shape link order or suggested topics, but it should not expose sensitive queries or feel intrusive. A short explanation and predictable options work best.
Make the message plain and reassuring
A missing-page heading should say that the address could not be found. Avoid “something went wrong” when the issue is an unknown URL. Include the attempted address so visitors can spot a typo, and keep the error code secondary. The visible message and server response can both be clear without competing for attention.
Keep visuals consistent with the main site. Familiar type, restrained colour and generous spacing create hierarchy, while visible links make action obvious. Avoid animation, autoplay media and full-screen promotions. Fast loading helps people using older phones or intermittent connections.
Accessibility should cover more than contrast. Focus order should move logically through links and search, keyboard users need a clear focus indicator, and form labels should be announced correctly. The Australian Government Digital Service Standard references WCAG 2.2 Level AA. Plain Australian English reduces effort for everyone.
Account for Australian visitor behaviour
Australia's distances and multiple time zones make “business hours” a poor assumption. A visitor in Sydney may open the site late at night while someone in Perth is starting the day. Support links, dates and contact expectations should show local times rather than one narrow window for seeking help.
Mobile browsing is routine, particularly during commutes on trains, trams and buses in Melbourne, Sydney, Brisbane and Perth. Small screens, one-handed taps and patchy underground coverage argue for a lightweight page with large targets and no dependence on hover. Test shortened links and redirects as the site's addresses change.
The Australian online market rewards speed, familiar language and self-service. Use Australian spelling, local date formats and relevant contact details without cluttering the page with every regional or commercial option. A concise set of general resources often serves visitors better than a dense directory.
For businesses covered by Australian privacy and consumer laws, the missing page still carries obligations. The Privacy Act 1988 and Australian Privacy Principles may apply to analytics, stored searches or feedback data, so collect only information with a clear purpose and explain its handling. The Australian Consumer Law sets rules against misleading conduct. The Spam Act 2003 matters if visitors can join an email list.
Offer recovery options people can use
Start with the destination most likely to match the visitor's goal. Keep labels descriptive, place important links near the explanation and avoid repeated “click here” wording. A site search can help with typos, but should work without JavaScript where possible and should not trap visitors when no result exists.
Useful destinations
- The home page with a recognisable site name
- A search field for keywords or phrases
- A sitemap or category index
- The main contact or support page
- Related resources matching the failed URL's subject
Helpful page elements
- A clear statement that the address was not found
- The requested URL in selectable text
- A visible breadcrumb trail where applicable
- Touch-friendly button and link sizes
- A broken-link report option that does not block recovery
These options should form one coherent path. Put search first when the failure appears to be a typo, and foreground related material when the URL identifies a known section. A small informational site may need only a homepage, topic index and contact route. More choices can add clutter without improving the route onward.
Test the page and learn from real use
Test every link that can fail, including campaign destinations, content moved during a redesign and URLs printed externally. Check the server response and what visitors see. The page should return a 404 status, load on screen sizes and remain usable with unusual characters or long search phrases.
Usability sessions should include people with different digital confidence, access needs and locations. Participants from urban and regional Australia can reveal whether labels, contact details or assumptions about internet access make sense. Observe where they go after the error; a positive reaction can hide a dead-end path.
Use privacy-conscious analytics to see which recovery links visitors choose, which searches return nothing and where they leave. A high exit rate is not always failure because some missing pages correctly end a visit. Repeated searches may expose a content gap or broken label, so review them with server logs and broken-link reports.
Assign ownership and revisit the page whenever the information architecture changes. Search terms and popular resources shift over time. A maintained 404 page remains part of the site's navigation, giving each failed request a brief explanation and a practical route onward.