What Does a Good 404 Page Do on a Content Heavy Site?

What does a good 404 page do on a content heavy site?

It answers one question fast: what were you probably looking for. On a site with a handful of pages a 404 can be a joke and a link home. On a site with a thousand articles, that is a dead end, because the visitor had a specific intent and your homepage does not serve it.

This is a design problem more than a technical one. The status code takes five minutes. Deciding what to put on the page is the part that needs actual thought, and it is the part most teams skip.

Here is what I put on a 404 for a large archive, what the research has said for a very long time, and what the status code still has to do underneath it.

Why is a 404 a design problem rather than a technical one?

Because the visitor arriving on it is unusually motivated. They clicked a link, followed a search result, or typed something from memory, which means they wanted a specific thing on your site. That is a better starting position than most of your traffic, and a generic error page throws it away.

The design job is to convert intent into a next step with the least effort from the reader. Everything else on the page, the illustration, the joke, the brand personality, is decoration that either supports that job or gets in its way.

Nielsen Norman Group has been saying versions of this since 1998, and the fact that the advice is that old is the point. Their guidance is that error messages should be written in plain language that is easy to understand for non-technical users, precise in specifying exactly what was done wrong, and constructive in suggesting steps the user can take to correct the problem.

What should the page actually say?

Start with a plain apology and a plain fact. The original guidance is a simple and slightly apologetic statement that the requested URL could not be found on your site. That is still the right opening, and it beats every clever alternative I have seen tried.

Do not blame the reader. The guidance is explicit that an error message should not imply that the mistake is the user's fault, and on a content site it usually is not. Links rot, posts get renamed, and someone shared a URL that worked in 2023.

Keep the apology to one sentence. The reader is not upset, they are interrupted, and the fastest way to be useful is to stop talking about the error and start showing them content.

Should a 404 page have a search box?

Yes, and on a large archive it is the single most valuable element on the page. The same guidance from Nielsen Norman Group says the error page should have a search field linked to the site's search engine. That recommendation has aged perfectly because the underlying problem never changed.

Put the search field above the fold and give it focus when the page loads. A visitor who has to scroll to find the search box on an error page will leave instead, because leaving is easier than scrolling and you have already spent their patience.

Prefill it if you can. If the broken URL was your site slug for an article about pricing pages, seed the search box with the readable words from that slug. You know what they were looking for, so say it back to them rather than asking.

What else belongs on the page?

A best guess and a short list of real destinations. The classic version of this is to perform a spelling check on the requested URL and list any close matches made into hyperlinks. On a CMS driven site the modern equivalent is matching the slug against your existing posts and showing the closest few.

Below that, show the handful of destinations that genuinely serve most visitors. Not your full navigation repeated, which is already in the header, but the three or four pages that answer most intents, chosen deliberately rather than by traffic.

What I would not do is dump a list of recent posts. Recency is not relevance, and a wall of unrelated links looks like an admission that you have no idea what the visitor wanted. If your archive has grown past the point where a few links can cover it, the deeper fix is structural, which I went into in navigation for a blog with a thousand posts.

Why does the status code still matter underneath the design?

Because the page has two audiences and only one of them reads. Google's documentation states that all 4xx errors except 429 are treated the same, with crawlers informing the next processing system that the content does not exist. That is the signal your pretty page has to carry correctly.

The consequence is specific. Google says the indexing pipeline removes the URL from the index if it was previously indexed, that newly encountered 404 pages are not processed, and that the crawling frequency gradually decreases. That is the system working as intended, not a penalty.

Worth noting for honesty: that documentation describes how Google handles the codes it receives, and does not tell you which code you should choose for a page you removed on purpose. That decision is yours, and I worked through it in what happens to a URL after you delete a post.

What is a soft 404, and why should you care about it?

It is the failure mode where your design and your status code disagree. Google describes a soft 404 as an error Search Console displays when the content suggests an error for Google Search, an empty page or an error message, despite the page returning a success code.

This happens constantly on CMS sites, and almost always by accident. A template renders a nicely designed not found message while the server quietly returns a 200, usually because the error page is implemented as a normal page rather than as a real error response.

So the check is simple and nobody runs it. Request a URL that definitely does not exist on your site and look at the status code that comes back, not at what the screen says. If it says 200, your beautiful 404 page is lying to every crawler that visits it.

How should the page look?

Like the rest of your site, with less of it. Keep the header and footer so the visitor knows where they are, drop anything promotional, and give the search field and the suggested links the visual weight that a hero section would normally take.

Resist the illustration. I have built plenty of them and I have never seen one earn its space on a content site, because the visitor is not in a mood to be charmed and the image pushes the useful part down the screen. Personality belongs in the sentence, not in a graphic.

Check the page on a phone, because a large share of broken link traffic arrives from messaging apps and social posts. A search field that is reachable without scrolling on a small screen is the whole design brief in one requirement. I covered the build side of this in designing a Webflow 404 page that recovers visitors.

How do you know whether it is working?

Track two things. How many people who land on the 404 go on to view another page, and what they type into the search box when they do. The second one is the more valuable number by a distance. Set both up before you redesign the page, so you have a baseline to compare against.

Those search queries are a free list of what people expected to find on your site and did not. On my own archive that list has repeatedly told me what to write next, more reliably than keyword research has, because it is real demand from people who already trusted me enough to arrive.

Also watch the volume itself. A sudden rise in 404 traffic usually means something broke in a template or a migration rather than that the internet suddenly found your old links, and the error page is where that evidence shows up first.

What should you do next?

Request a URL on your own site that cannot exist, and check two things: what the page shows, and what status code the server returns. That takes two minutes and it settles whether you have a design problem, a technical problem, or both.

Then rebuild the page around a focused search field, a best guess at the broken slug, and three or four deliberately chosen destinations. Leave the illustration for a project where charm is the job. The page at the opposite end of the journey deserves the same attention and almost never gets it, which is why I wrote what a good thank-you page actually does.

With more than 350 articles on my own site I have had to take my own advice here, and the search box was worth more than everything else on the page combined. If you want a second opinion on what your 404 should be doing for the size of archive you actually have, reach out and let's chat.