A 404 page: help customers return to what they came for
Explain a missing address, offer useful routes back and verify server status and redirects.
Article language: English

In this article
A 404 is a response code, not a plan for the customer's onward journey. When an address has no content, the page should say so clearly and offer a few relevant exits. It also needs the right server response. A witty heading can help, but it cannot replace a link to the service someone came looking for. Recover context before the visitor decides the shortest route leads to a competitor.
The most important decision comes before designing the screen: should the address actually return an error? If an old offer has a clear equivalent, consider the appropriate redirect. If it does not, an honest absence message is better than an automatic trip to the homepage. Below are ways to design both cases, example wording and an acceptance scenario for a service website.
First establish what happened to the address
Imagine a company designing commercial interiors. An older catalogue contains a link to a page about restaurant projects. After the website changes, a customer opens that link from a saved document. If the relevant service still exists at a new address, the customer needs it without another puzzle. If the company has withdrawn it entirely, a current office-design page should not pretend to answer the same question.
The content owner should assign the old address to one of three situations: moved content, content removed without an equivalent, or an unknown address the company never published. This is an editorial and business decision. A developer can build the mechanism but cannot guess whether the new service truly replaces the old one.
For larger changes, use an address map during website migration (in Polish). Record the person responsible and a short reason for each decision. Similar names are not enough: beginner training and board-level advice can concern the same technology while meeting entirely different needs.
Pay particular attention to old links in sent proposals, email signatures and downloadable materials. A new navigation deployment cannot correct them all. Check where they lead after the change and whether the visitor still receives the promised information. If the address is also printed, check the journey from a QR code and an alternative without scanning (in Polish): that entry point remains outside the new menu.
Separate the error's appearance from the server response
404 is an HTTP status, the server's technical response to a request for an address. MDN explains 404: the server did not find the requested resource. The code alone does not establish whether the absence is permanent. An illustration of a lost astronaut does not replace that response, even if the astronaut has an impeccable suit.
A page can display “Page not found” while technically returning a success status. Google describes such a case as a soft 404. The same documentation distinguishes missing from moved content and recommends appropriate behaviour for each. This is an implementation checkpoint, not a matter of design taste.
In the brief, record the expected appearance and status separately. Ask for a test of a random nonexistent address nested several levels deep. A mechanism may work at a simple test address but fail elsewhere in the structure. A single screenshot cannot answer that question.
Do not promise improved search rankings on that basis. The aim is clear handling of an absence and orderly addresses. Wider dependencies are covered in technical SEO acceptance before publication (in Polish).
Write a message that does not blame the customer
“Invalid address” sounds like an assessment of the visitor's action, although they may have clicked your own link. A safer opening is “We could not find a page at this address.” It explains the situation without assigning blame or inventing an unconfirmed cause.
The next sentence should enable action. For example: “Explore services, search a topic or tell us what information you need.” This is suitable only for a site that actually offers those three routes. If there is no search, do not promise one. If the form only handles new enquiries, do not present it as urgent technical support.
A brand can retain its character without entering a joke contest. “This address moved out without leaving a card” may be charming, but needs a plain explanation immediately. For serious tasks such as finding complaint instructions, humour can postpone the answer. Choose the tone for the task, not the empty space in the design. Apply the same principle to brand voice in interface messages (in Polish): character should help people recognise the state and next action.
Test the words without the illustration. A reader should be able to say what happened and what they can do next. If they remember only the space metaphor, the message remains in orbit instead of leading to a destination.
Offer a few exits for specific reasons
On a service site, main services, search and contact are often enough. Their order depends on the site. Search may be most important in a large knowledge library; a small studio may be better served by a return to its services list. Do not add six sections merely because an error screen looks empty.
Choose links from the site's B2B information architecture (in Polish). Use the same service names as the normal navigation. Otherwise a customer encounters a second vocabulary for the same company just when they have lost their bearings. “Explore options” says less than “See website design projects”.
If you suggest content from part of the address, present it as a suggestion. Do not automatically redirect to a loosely similar page. Someone looking for a job should not arrive without explanation at a customer offer simply because both addresses contain “offer”.
A back button also needs thought. Someone may have arrived from search, email or an external system. You cannot know whether going back will help. A fixed link to a useful place on the site is more predictable than a sole option based on browser history.
Search should help even when it finds nothing
A search field on a 404 is useful when it handles the names, abbreviations and questions people actually use. An empty field with a magnifying glass cannot solve the problem if the internal index covers only article titles while the visitor seeks a service. First determine which collections the search covers.

An example exercise for a hypothetical training company: search for an old course name, its common name and the topic it taught. Record which queries lead to a useful next step. Absence of an exact product does not rule out a useful answer, but the suggestion should distinguish a current replacement from merely related material.
After an unsuccessful search, allow the visitor to change the query or contact you. Do not create another dead end. Designing internal search (in Polish) requires a separate decision about relevance; placing it on a 404 only exposes existing weaknesses more clearly.
Do not automatically put the entire failed address into a visible field or a message sent through an external service. An address may contain parameters the customer did not intend to share. Diagnosis usually needs far less information than a complete record of their journey.
Preserve language and ordinary usability
An error is no reason to change the language of the conversation. Someone using the Polish part of a site should receive a Polish message and suitable links. For an address with no recognised language, choose a deliberate default. A random switch may make the visitor feel they have reached another company.
The error page should retain basic identity and navigation, but needs no heavy production. On a weaker connection, contact details and services should appear without waiting for a large video. Decoration should support orientation, not stage a premiere during a minor fault.
Check the heading, visible keyboard focus and meaningful link names. If the screen says “Back”, specify where. If a report-problem button opens a form, check how it closes and what happens next. The basics are covered in business website accessibility practice (in Polish).
Do not make the return to content depend on guessing a gesture, precisely hitting a tiny icon or watching an animation. A 404 is a useful place to see whether visual character can coexist with simple, dependable operation.
Decide when an error report needs action
Not every missing address is an outage, but each needs correct interpretation. A single typo in an unknown address differs from all service pages suddenly disappearing. Give the team a simple way to determine whether the address existed before, appears in current materials and whether the problem can be reproduced from normal navigation.
In a hypothetical consultancy, a customer may report a broken workshop-programme link. The recipient checks the current service description and finds a working document. That is not the end: they must also check the address sent to the customer. An automatic confirmation overlooked during the website change may still point to the old file. Fixing the current page will not repair that link.
Make reporting simple. A description of the content sought and the problematic place is usually enough. Do not require a customer to create an account, select a technical category and reconstruct their whole browsing history. The company needs evidence for diagnosis; the form should not transfer the whole investigation to the visitor.
Assign responsibility for assessing reports. A submission option helps little if messages reach an unattended inbox. Record who checks the link target, who decides on a replacement and who confirms the outcome after a fix. In a small site two people may cover these roles, but the roles still need names.
If many previously working addresses are affected, do not fix each with an individual redirect before identifying the cause. Publication configuration or content retrieval may have changed. Adding exceptions could hide the underlying problem and complicate recovery. First establish whether one page is missing or a shared mechanism is failing.
For monitoring, collect only what is needed for diagnosis. Instead of a full address, consider aggregated data or a safely redacted route pattern: omit the query and fragment, and identify and redact sensitive or dynamic path segments. Limit access and retention to the purpose. Assess the actual data and configuration before applying this: these steps alone do not guarantee anonymisation or compliance. See the OWASP logging guidance.
Test a scenario, not one screen
Before testing, define a correct outcome for each case. For a moved service it may be direct arrival at the relevant description. For removed content, understanding that it is gone and finding contact or related material. For a typo, a useful return without losing orientation. This avoids judging every case by one button or changing the test until it suits the finished design.
In a small exercise, ask someone outside the team to begin with an old link. Do not tell them where to click. Afterwards ask what they sought and what they think caused the absence. If they recognise only “a broken company”, improve the explanation and nearest route to help.
Prepare a short test with fictional, safe addresses: a customer opens the old address of a removed service with no clear equivalent, recognises the absence, reaches a current offer as an alternative and finds contact. A second begins with a typo. A third starts from a removed article without a replacement. Each should end in an understandable state even when the original content cannot be recovered.
For each case record the fictional test address, server status, visible message, working exits and mobile outcome. Include keyboard-only operation. Such evidence can be added to a website acceptance checklist (in Polish). An elaborate report is not needed to distinguish a corrected screen from a repaired customer journey.
After publication, review recurring missing addresses and possible sources. If the error comes from your menu, fix the menu. If it comes from an old publication, assess an appropriate redirect. If it concerns random addresses never used, do not force content into existence for them. The significance of the problem matters, not the mere occurrence of 404.
Apply the same principle of a clear state to a form thank-you page (in Polish): the visitor needs to know what just happened and what comes next. To improve this journey on your site, start with the scope of Aeneia Design.






