A 404 Page That Doesn't Waste the Visit

A 404 page is one of the few pages on a site where you can say with total confidence what the visitor's state of mind is: they wanted something specific, followed a link or typed a URL to get it, and hit a dead end instead. That's a moment of real intent colliding with a broken path — and most 404 pages waste it entirely.

The default is worse than it looks

A generic "404 Not Found" with no navigation, no search, and no suggestion of where to go next isn't neutral — it's actively worse than it needs to be, for a reason more specific than just looking unpolished: it gives a frustrated, intent-driven visitor exactly zero paths forward except hitting the back button, which for a visitor who arrived via search is often the last interaction they have with your site at all.

What a 404 page should actually do

Confirm what happened, briefly. A short, plain statement that the page they wanted doesn't exist (anymore, or ever) — not an apologetic essay, not a joke that outstays its welcome on a second or third visit from the same confused user.

Offer real navigation, not just a link back to the homepage. A search box, links to the main sections of the site, or — if you can detect it — a guess at what they meant based on the broken URL's structure (a common pattern for e-commerce: a 404 on /products/discontinued-item can still route to the product category it belonged to).

Never return a 200 status code. This is a technical detail with real consequences: a "soft 404" — a page that looks like an error page but returns HTTP 200 instead of 404 — actively confuses search engines into treating a broken page as valid content worth indexing, which is a worse outcome than the broken link itself. Confirm your framework's error page actually returns the correct status code; it's a surprisingly common oversight, especially with client-side routing where the URL never actually hits the server to receive a proper status at all.

The pages that generate the most 404s deserve a real fix, not just a good error page

A well-designed 404 page is damage control. The actual fix, for whichever specific URLs are generating the most hits, is a redirect to wherever that content now lives — found via Search Console's coverage reports or server log analysis, which will usually reveal a small number of URLs responsible for a disproportionate share of 404 traffic. Point each old URL straight at its final destination rather than chaining redirects. A good 404 page handles the long tail gracefully; a redirect handles the URLs worth fixing directly.