How to Design a 404 Page That Keeps Visitors

No matter how carefully you manage redirects, some visitors will land on a missing page. Typos, old bookmarks and broken external links make that unavoidable. The 404 page decides whether those visitors leave or continue.

1. Return a real 404 status code

This is the most important rule and the most commonly broken one. A custom error page must still return HTTP 404 (or 410). If it returns 200 OK, search engines see a thin page that claims to exist, and report it as a soft 404. See 404 vs Soft 404 vs 410 Explained.

Check the status with your browser's developer tools or curl -I https://example.com/random-url.

2. Keep your site's header and navigation

A 404 page that looks like a different site feels broken. Keep your logo, main menu and footer, so visitors immediately know where they are and can navigate on their own.

3. Explain briefly and clearly

One short sentence is enough: "We couldn't find this page. It may have been moved or removed." Avoid technical jargon and avoid blaming the visitor.

Humor is fine, but not at the expense of clarity. The message should be readable in two seconds.

4. Offer a clear next step

Useful elements, depending on your site:

• A search box, ideally pre-filled with words from the requested URL.
• Popular categories or pages, not a full sitemap.
• Best sellers or new products for e-commerce stores.
• Recent articles for blogs and content sites.
• A contact or support link for SaaS products.

Two or three options work better than twenty links.

5. Don't auto-redirect after a few seconds

A countdown that sends visitors to the homepage looks helpful but isn't. It interrupts people who are reading, hides the original problem and may be treated as a soft 404 by search engines. Let visitors choose.

6. Keep it lightweight

The 404 page should load fast and should not trigger heavy scripts, pop-ups or chat widgets. It is a recovery page, not a landing page.

7. Localize it

On multilingual sites, show the 404 message in the language of the requested URL. A visitor on /de/... shouldn't see an English error.

8. Log every 404

The design of the page reduces the damage; logging prevents the next one. Every hit should record the URL, referrer and time, so you can find the source and add a redirect where it makes sense. Our guide How to Recover Lost Traffic and Conversions from 404 Logs shows how to use this data.

Common mistakes

• 200 status on the error page: Soft 404 in Search Console
• Redirecting all 404s to the homepage: Confusing for users, soft 404 risk
• Blank page or server default error: Visitors leave immediately
• Auto-redirect countdown: Removes user choice
• Heavy animations and scripts: Slow page for already-frustrated users

Summary

A good 404 page returns the correct status, keeps your branding, explains the situation in one sentence and offers a few relevant next steps. Pair it with 404 logging so you can fix the URLs that keep sending visitors there. no404 handles the logging and redirect side, so your 404 page only has to catch the rare cases left over.