Most local business websites have a 404 page that says "Page not found" in 24pt Helvetica, with a link to the homepage. We treat the 404 as a landing page. Every Built Local site ships with a handwritten 404 specific to that client. This is why, and what we put on it.
How often anyone sees it
On a busy local trade site, between 0.5% and 1.5% of sessions hit a 404. The sources, in order of frequency:
- Old social media posts linking to URLs that have since been restructured.
- Mis-typed direct URLs ("buit-local.uk").
- Crawler / bot traffic looking for /wp-admin etc.
- Old blog post links that the founder forgot to redirect.
Across a typical site that's 30-50 real human sessions hitting the 404 per month. For a trade where each new customer is worth £150-£600 in lifetime value, recovering even a handful of those is meaningful.
The three components on every Built Local 404
- An apology in the founder's voice. Not "404 - Page not found". Something like: "Sorry - that page seems to have gone walkabout. Probably my fault."
- The phone number, big. Larger than the surrounding text, with a tap-to-call link. The single most useful action for a confused visitor is "ring the business".
- Three contextual links to the most likely pages they were trying to reach. For a plumber: "Emergency plumber callouts", "Boiler repair pricing", "Service areas we cover". Not the homepage - the homepage is the bounce option.
This is, in effect, a mini landing page. It treats the visitor as a potential customer rather than a routing error.
The conversion data
On three sites where we A/B tested personalised vs generic 404 pages:
- Generic "page not found" page: 1-3% of 404-hit visitors took a meaningful action (call, form fill, click to a service page).
- Handwritten 404 with the three components: 12-18% took a meaningful action.
The delta is the apology and the prominent phone number. People are forgiving when the site sounds like a person; they're impatient when it sounds like a server.
The technical bit
Every Built Local site has the 404 set up as a proper HTTP 404 (not a soft 404 redirect to the homepage) so Google correctly indexes the missing page as missing. The 404 returns the personalised page in the body, not an empty template. The page is statically rendered at build time, so it loads instantly even on patchy connections.
One technical caveat: a true 404 must return a 404 status code. Returning a 200 with a "page not found" message is a soft 404 and Google will eventually clean it up out of the index. We see this mistake on roughly half the trade sites we audit.
What we never do
- Auto-redirect after 5 seconds. Hostile. The user has no time to read what happened.
- A search box as the only action. Most visitors won't use it.
- A funny 404 with no useful action. The joke wears off when they still can't find what they wanted.
- A homepage redirect on every 404. Soft-404 problem in Google, lost conversion opportunity for the visitor.
The unexpected benefit
Several clients have told us their 404 is the page they get the most compliments on. It's the page where the brand voice is most concentrated - 40 words doing the work of a 600-word about page. It's also one of the cheapest things to build well: 30 minutes of writing per client, zero additional infrastructure.
Why this matters for UK local web design
The 404 page is the canary for whether the rest of the site has been built with attention or assembled from defaults. A studio that takes the 404 seriously almost always takes the rest of the build seriously too. A studio that ships the generic Bootstrap 404 has skipped a lot of other small decisions.
Every Built Local site ships with the handwritten 404 as part of the £99 setup. See the broader list of small mistakes that quietly kill leads for the rest of the pattern, or browse Built Local for local web design for tradespeople that takes the small things seriously.