November 16, 2026

How to Review a 404 or Dead-End Page

Keep a 404 or dead-end page that says the page is missing, does not blame the visitor, and offers a way onward.

A small white enamel sign on a chrome post and round base, with a blue diagonal stripe on the left and a raised pink arrow pointing right, on a yellow background.
In this guide

A visitor follows an old link to a spring recital at the fictional music school Reed & Meter. The recital has moved, and the address no longer exists. The page they reach says only “Not Found.” There is no explanation, no link to current events, and no path back to classes. The visitor followed a reasonable link and should not be treated as having made a mistake.

Reed & Meter is a teaching example, not a test result. The useful question is whether this missing-page response gives the visitor a credible way onward.

Use these questions as a way to think, not as a score:

  • Can the visitor tell what happened?
  • Is it clear they are not being blamed?
  • Is there a useful way onward?

Say the Page Is Missing, and Offer a Way Onward

MDN describes a 404 response as the server being unable to find the requested resource. That is the technical status. The visitor needs a plain explanation of what it means for them.

The GOV.UK page-not-found pattern is one government system’s pattern, not a study of marketing sites. It says to use the pattern if someone is trying to view a page that does not exist, to put “Page not found” as the heading, to keep the content clear and concise, and to include contact information when it exists and helps meet a user need.

Nielsen Norman Group’s error-message guidelines (2023) advise avoiding technical jargon and using language familiar to the visitor. The same guidelines note that the web’s most common error message, the 404 page, often violates that advice. The GOV.UK pattern above likewise says not to use technical jargon like “404” or “bad request.”

A useful page therefore does three things that a visitor can notice quickly: it says the page is missing, it does not blame them, and it offers a way onward. On Reed & Meter’s recital address, that onward route might be current events, the classes list, or the homepage. A generic “go home” link is better than a dead end, but a route tied to what the visitor was looking for is more useful when you can offer one.

Humor Is a Judgment Call

Sources do not agree about jokes on error pages. GOV.UK and Nielsen Norman Group treat humor as a risk. The GOV.UK pattern says not to use informal or humorous words like “oops,” and Nielsen Norman Group’s guidelines say to avoid humor because it can become stale if users encounter the same error frequently.

A 2022 online survey by Eojin Kim, Jiwoong Yoo, and Soyeon Kim, with 141 participants and four error-page conditions, found that witty messages had higher positive-affect ratings and higher continued-use intention than neutral ones in that experiment (Archives of Design Research). That is one study, not a reason to require a joke.

If you use humor, check that the missing-page explanation and the next step remain easy to notice. The joke should not hide either one.

Keeping the site header and navigation so a visitor can recover is common sense, not a finding from a test of 404 pages. GOV.UK’s own example is a minimal page. If familiar navigation stays, it should not overwhelm the explanation or the way onward.

Check the Real 404 on the Live Site

Check the 404 on the live site, using an address you know is missing. If you do not have one, ask the team for a safe missing address. Confirm what the live site actually returns before you send a note about wording, tone, or recovery routes.

Once you have confirmed the live 404, you can paste that same address into Online Website Previewer and press Preview to compare layout at phone 390 by 844, tablet 820 by 1180, and desktop 1920 by 1080 CSS pixels. The previewer is a visual check of layout in your current browser, not a test of a particular device. Look at whether the explanation and the way onward stay easy to notice at each width.

This Is Not a Search Empty State

A search that returns no matches is a different situation from a missing address. That empty state belongs in Search Results Pages: What “No Results” and Good Results Should Look Like.

If the recovery includes a way to get in touch, What a Contact Page Needs to Show covers what that contact page should include. If two recovery actions compete visually, use Button Hierarchy: Primary vs Secondary Buttons. The footer’s contents, including a Contact link, are covered in What to Put in a Website Footer. For choosing pages in a wider pre-launch pass, see How to Test Your Website Before Launch: A Checklist.

Send a Keep or Rework Note

A useful note might say: “At [address checked] on the live site, the missing recital address returns a page that only says ‘Not Found.’ A visitor who followed an old events link has no way onward to current recitals or classes, and the wording does not explain that the page is missing. Please add a plain heading, a short explanation that does not blame the visitor, and a useful next step.”

For how to phrase the note, see How to Give Useful Feedback on a Website Design.