Before You Build Another Landing Page, Read Your 404 Log

There is a strange kind of optimism in launching a new landing page while your site is quietly turning away visitors who have already arrived. Most UK shops and small businesses have a 404 page somewhere, usually with an apologetic sentence and a search box. It gets built once, forgotten, and then treated as an IT problem when someone notices it.

That is a mistake. A 404 is not just a broken link. It is a record of somebody who clicked, typed, scanned a QR code or followed an old campaign URL and ended up on a dead end. In marketing terms, that is traffic you earned and then lost at the final metre. Before you spend another penny filling the top of the funnel, it is worth reading the bottom of it.

The 404 page is a receipt, not a rubbish bin

Think about how people reach a 404. They do not usually arrive there by accident. They arrive because an old product page is still indexed, a paid ad points at a URL that was retired, a supplier sent a catalogue with a typo, or an internal link on your own site has quietly rotted. Each of those is a signal about demand, navigation or campaign hygiene.

A homepage redirect is the usual response. Someone spots a 404, points it at the homepage, and considers the job done. But dumping every lost visitor on the homepage is like redirecting every missed train to the nearest bus station and hoping for the best. It technically moves them. It does not help them. In many cases, a specific category page, a similar product or a clear explanation will do far more for conversion and for your analytics story.

Start with GA4, but do not stop there

GA4 can give you a quick view of where these dead ends are happening. Open the Pages and screens report and look for page paths or titles containing 404, not found or page not found. The exact wording depends on how your site is set up, so check what your 404 template actually calls itself. Then add a secondary dimension such as landing page or session source / medium. That helps you separate people who landed directly on a dead end from people who hit one halfway through a browse.

One useful filter is to look at sessions where the landing page is the 404 page. These are the visitors who never got a chance to see your shop properly. If a campaign URL is sending paid traffic to a dead page, that should be fixed today, not added to a quarterly review.

GA4 will not tell you the whole story, though. It samples, it misses some hits and it cannot always distinguish a curious bot from a genuine shopper. That is where server logs earn their keep. Ask your host or developer for access logs covering the last 30 to 90 days and filter for status code 404. You will usually find a long tail of strange URLs, plus a short head of repeated offenders that actually matter.

Read the referrer like a marketing clue

The referrer field in your server logs is underrated. If a 404 is being hit repeatedly from a particular affiliate, marketplace, newsletter or ad platform, that is not a random technical blip. It is a broken hand-off between somebody else's traffic and your site. Fixing it can recover visitors without spending anything extra.

Also look at the requested URL itself. Old product pages often contain a SKU or product name that tells you exactly what the visitor wanted. If the product is gone forever, a 410 status code may be more honest than a redirect. If it has been replaced by a newer model, send the visitor there. If it belongs to a discontinued range, a category page for the nearest alternative is usually better than the homepage.

Be careful with bots. A large chunk of 404 traffic can come from crawlers probing for WordPress login pages or old asset files. Filter out obvious bot user agents before you panic, but do not filter out everything you do not recognise. Some of those requests may be real people using privacy tools or unusual browsers.

Build a redirect map that a human can actually use

A spreadsheet is enough. You want four columns: the requested URL, the number of human hits, the best destination and the reason. Add a fifth column for status code if you are using both 301 and 410. Keep it short. A redirect map with 400 rows will never be maintained; a list of the top 20 to 30 money-losing dead ends will.

Prioritise in this order:

1. Paid or campaign URLs sending traffic to a 404. These are direct budget leaks.
2. Product pages with clear replacements or close alternatives. These have commercial intent baked in.
3. High-traffic blog or guide URLs that still attract search visits. These can be redirected to an updated resource.
4. Internal broken links. Fix the link itself as well as adding the redirect.
5. Low-value noise. Ignore or block obvious bot traffic.

Use 301 redirects for permanent moves, and avoid chains where possible. A redirect that goes from an old product to a category, then to another category, then to a filtered page is slow and muddy for both users and search engines. Point it at the final destination in one hop. If your CMS makes redirects painful, that is a sign to fix the process, not to keep dumping everything on the homepage.

Make it a monthly habit, not a spring clean

UK retail has a predictable rhythm of campaign URLs, seasonal ranges and expiring offers. Old Father's Day pages, back-to-school bundles and Black Friday landing pages can all become 404s if nobody owns them. A short monthly check catches those before they accumulate.

Set aside 30 minutes once a month. Export the top 404s, filter out obvious bots, check the referrers and add any new human-heavy URLs to the redirect map. If you use GA4, create a simple exploration or alert for spikes in 404 page views so you hear about a broken campaign link before a customer does. If your site has a search box on the 404 page, review those searches too. They often reveal what people expected to find.

The bigger point is cultural. A 404 is not a badge of shame for the developer. It is feedback from the market. Treat it as a traffic report written by the people who almost became customers, and you will start finding recoverable visits in the least glamorous corner of your analytics.