1. Separate a missing address from content that has moved
In our fictional example, a workshop has been removed from a training centre’s catalogue. Before writing an error message, ask the content owner whether the workshop has disappeared, moved to another address or has a genuine replacement. Record the old address, the decision and the chosen destination. A loosely related category is not automatically an equivalent page.
Status 404 means that no current representation was found, without deciding whether the absence is permanent. Status 410 expresses likely permanent unavailability. If the content has actually moved, ask the team to assess a redirect to its new address; Google recommends reserving this approach for relevant destinations.
Source : IETF — RFC 9110, 404 Not Found · Source : IETF — RFC 9110, 410 Gone · Source : Google Search Console — 404 (Page Not Found) errors
2. Write a message that explains the situation
Prepare a direct heading such as “This page cannot be found”, followed by a short sentence: “The link may have changed, or this page may no longer be available.” Avoid blaming visitors or promising a return without approved information. The number 404 can remain a secondary reference; it should not be the only explanation.
In our fictional catalogue, then offer “View available workshops”. Approve the wording and destination together. Avoid internal explanations or server details: readers mainly want to recover the information. An illustration may accompany the message, but keep the explanation and actions as readable text.
3. Choose clear ways forward that actually work
Limit choices to what helps in context: a main category, the home page or an existing search feature that has been checked. Do not add a decorative search box that does not work. A “Back” action alone leaves someone opening an old bookmark directly without a solution; provide an explicit destination too.
W3C explains that a link’s purpose should be understandable from its text or associated context. Prefer “View available workshops” to “Click here”. Open each destination in the appropriate language and check that it lets the reader continue. Do not replace the missing-page message with an unexpected automatic redirect.
4. Check the status as well as the appearance
Ask the team to test a deliberately nonexistent address chosen for acceptance testing in the preview environment. It should receive the intended response for a missing resource. Also check a real catalogue page: it should remain available. This paired check prevents accepting an error page that appears everywhere.
A page announcing missing content while returning a success status may be considered a soft 404 by Google. A screenshot of the message therefore does not prove the HTTP status. Keep the requested address, observed status and final destination, alongside a screenshot of the appearance. A 200 status does not guarantee indexing either.
5. Repeat the journey on mobile and in every language
Open the test address directly, reload it and follow the main way forward. Repeat from a test link in the preview. On a phone, check that the message and actions remain readable without horizontal scrolling across the whole page. Navigate the links by keyboard and clearly identify which one has focus.
In French, English and Arabic, check the message’s meaning, the destination language and the language selector’s behaviour. In Arabic, also read numbers and left-to-right address fragments in context. Do not require an invented translation of a deleted page: approve an existing destination in an available language and explain any language change.
6. Fix links at their source and keep useful evidence
A welcoming error page does not repair the link leading to it. If a menu, article or document you control contains the old address, have that link corrected. For a deleted page without an equivalent replacement, Google recommends a real 404 response; redirecting every missing address to the home page can confuse visitors and be treated as a soft 404.
Keep a short worksheet: entry address, link origin, editorial decision, language, tested version, status, chosen exit and observed result. After a correction, repeat the same journey and retain any remaining limits. This targeted acceptance check demonstrates neither complete accessibility compliance nor improved search engine rankings.
Source : Google Search Console — 404 (Page Not Found) errors
Missing-page acceptance worksheet
| Test case | Expected result | Evidence to keep |
|---|---|---|
| Missing address | Clear message and intended status | Address and observed status |
| Moved content | Approved equivalent destination | Decision and final address |
| Direct opening | An explicit way forward works | Journey from a bookmark |
| Mobile and keyboard | Readable, reachable actions | Device and steps |
| Other languages | Consistent message and destination | Language and destination |
| Corrected link | Journey reaches the right content | Version and repeated check |
Frequently asked questions
Should every 404 error be removed?
Start with addresses that should work and links you control. A genuinely missing address does not need unrelated replacement content. Decide case by case with the content owner.
Is a good illustration enough?
It can make the page more welcoming, but it does not replace a readable explanation, a useful way forward or a status check. Do not put the only instructions inside an image.
Does this guide change my website’s error page?
No. It helps prepare a brief and an acceptance check. Actual behaviour depends on your website and must be checked on the delivered version; no checks on your website are claimed here.
Prepare your next acceptance check
Choose a missing address and an existing page in your preview. Approve the message and a main way forward, check both responses with the team and record the result in each published language.
Sources and scope
Primary IETF, Google and W3C sources consulted on November 6, 2026. The training centre, wording and worksheet are fictional editorial examples. The proposed checks are not a certification, an SEO measurement or a description of a Dev Ring feature.
