404s, 301s, and what to do with the old pages you don't need.

Old pages don't disappear quietly. When you delete a page without a plan, you leave a gap in your site that search engines and real visitors will fall into. The fix is straightforward once you understand the difference between a 404, a 301, and when each one is the right call.

Most small business sites accumulate dead pages over time — old service areas, retired staff bios, promotions that ended two years ago, blog posts that went nowhere. None of that is unusual. What matters is how you handle them when you finally clean house.

What a 404 actually tells Google

A 404 means the page is gone and you have no replacement for it. Google reads that as a dead end. It will stop crawling the URL, drop any ranking signals the page had built up, and serve an error to anyone who lands on it from an old link, a bookmark, or a search result that hasn't refreshed yet.

That last point matters more than most people realize. Google's index doesn't update the moment you delete a page. A URL can sit in search results for days or weeks after it returns a 404. Anyone who clicks that result during that window gets an error page instead of your content. That is a lost visit, and often a lost lead.

Not every 404 is a problem worth solving. If a page never ranked, never earned a link, and no one is clicking to it, letting it return a 404 is fine. You don't need to redirect every dead URL on your site. The question is whether the page had any value — in traffic, in links from other sites, or in ranking position — before it went down.

What a 301 does and why it matters

A 301 is a permanent redirect. It tells browsers and search engines: this URL has moved, and it is not coming back. Go here instead.

When you set up a 301 from an old URL to a new one, you pass most of the ranking signals from the old page to the new destination. Not all of them — there is some loss in the transfer — but enough that a well-placed redirect can preserve months or years of work your old page had done in search.

A 301 also keeps real visitors moving. Instead of hitting a dead end, they land where you want them. For a service page that moved, or a blog post that got merged into a longer piece, a 301 keeps the user experience intact and keeps Google from treating your site as full of broken paths.

The alternative — a 302 redirect — tells search engines the move is temporary. Use a 302 when you genuinely mean to bring the old page back. For most page consolidations and deletions, 301 is the right call.

How to decide: redirect, delete, or leave it

Every old page falls into one of three categories.

Redirect it when the page had traffic, ranked for anything, or has inbound links from other sites. Check Google Search Console for impressions and clicks on the old URL. Pull the URL into a backlink tool and see if any external sites link to it. If either of those is true, redirect the page to the closest matching live page on your site. A retired service page for a town you no longer cover should redirect to your main services page, or to your nearest active service-area page. A staff bio for someone who left should redirect to your team page or your homepage.

Delete it without a redirect when the page had zero traffic, zero links, and no ranking history. There is no value to preserve. A 404 on a page nobody visits costs you nothing. Redirecting every orphaned page to your homepage, just to avoid 404s, can actually create problems — Google sees a mass of redirects all pointing to one irrelevant destination and may stop treating them as meaningful signals.

Leave it when the page is outdated but still useful. A blog post from three years ago that still ranks and still answers a real question doesn't need to go anywhere. Update the content or add a note about when it was written. Killing a page that still earns traffic because it feels old is a common mistake.

The redirect chain problem

A redirect chain is what happens when URL A redirects to URL B, which redirects to URL C. Chains slow down page loads, dilute the signals being passed, and frustrate crawlers. Google will follow a chain, but it loses patience after a few hops, and the ranking value that transfers gets thinner with each step.

Chains happen when you add redirects on top of redirects without cleaning up the old ones. A site that's been through two or three redesigns often has chains three or four deep that nobody has audited in years. Core Web Vitals: the three numbers that decide if Google bothers covers page speed and crawl performance in more detail — but redirect chains are one of the quieter ways a site's technical health degrades without anyone noticing.

The fix is to flatten chains. If A → B → C, update A to redirect directly to C and remove the B step. Do this across every chain on your site. It is tedious work and it is exactly the kind of cleanup that pays off over months rather than days, which is why most sites never do it.

Running the audit: a working process

You cannot fix what you have not mapped. Start with a crawl of your site using a tool like Screaming Frog or Sitebulb. Both have free tiers that cover small sites. The crawl will surface every URL your site touches — live pages, redirects, and 404s — along with the response code for each one.

Export the list of 4xx URLs. Cross-reference them against Google Search Console to see which ones received impressions or clicks in the last 12 months. Those are your priority cases. Any URL with measurable search traffic needs a destination, not a dead end.

Next, export all 3xx (redirect) URLs and map the chains. Any redirect that points to another redirect is a chain that needs flattening. Mark each destination URL and confirm it is still live and still the right landing point for someone following that original link.

Finally, check your XML sitemap. A sitemap that includes redirected or dead URLs is noise. It tells Google to crawl pages that no longer exist, which wastes crawl budget and makes your site look poorly maintained. Update the sitemap to include only canonical, live, indexable URLs.

This process — crawl, audit, fix, update — is part of the technical groundwork covered in Search Foundations. It is not glamorous. It is the kind of work that makes the rest of your SEO effort actually function.

Where this breaks down

Redirects fix technical problems. They do not create good content, build authority, or fix a page that never deserved to rank in the first place. If your old pages had no traffic because they covered topics nobody searches for, redirecting them doesn't change that. The signals they pass are proportional to the signals they had.

A redirect is also not a substitute for a strong destination page. If you redirect a retired service page to your homepage because you don't have a good live page to send it to, you're passing thin value to a generic destination. The better answer is often to build the right page first, then redirect.

And while why your slow site is a sales problem, not an IT problem makes the case for site performance as a revenue issue, it's worth saying plainly: fixing 404s alone will not rescue a site with no content strategy, no backlinks, and no clear positioning. Technical fixes remove drag. They don't create lift by themselves.

What a clean technical foundation actually looks like in practice

When we worked through the technical audit for McShanes Solicitors, a significant part of the early work involved mapping what the site had accumulated over time — pages that existed without purpose, redirect chains that had formed through multiple updates, and URLs in the sitemap that returned errors. None of it was catastrophic on its own. Together, it was drag on a site that needed to move cleanly in search.

The fix wasn't complicated. It was methodical. Map what's there, decide what each page deserves — redirect, delete, or update — and execute without cutting corners. Flatten the chains. Clean the sitemap. Confirm nothing valuable is left returning a 404.

That work doesn't show up in a dashboard the next morning. It shows up over months, as Google recrawls, updates its index, and stops hitting dead ends on your domain. That is how technical SEO works. Slow to show, durable once it does.

The rule to carry into any site cleanup: if the page had value, protect it with a 301. If it didn't, let it go cleanly. Redirecting everything to your homepage to avoid 404s is not a strategy — it is housekeeping theater that search engines see through.