Website Migration Redirects: Why Rankings Drop

I have watched this pattern repeat more times than I can count, across more trades than I would have guessed a broken URL could touch. A kitchen and bathroom fitter working out of a showroom near Mullingar, County Westmeath, switched to a new website last spring. New designer, new templates, better photography of finished jobs. Within three weeks the enquiry form had gone quiet in a way it had not been quiet in over a year. The old service pages, the ones that had spent two years climbing for local searches, were simply gone. Not redesigned. Gone. The new site used a different URL structure, and nobody had told Google where the old pages had moved to.

Within days, the Page indexing report in Search Console was full of "Not Found (404)" entries. Every one of those was a page that used to rank, used to get clicked, and used to bring in a phone call. Nobody had done anything wrong in the conventional sense. Nobody had been hacked. Nobody had let a certificate lapse. They had simply moved house without leaving a forwarding address, and Google, along with every customer who had bookmarked or linked to the old pages, kept knocking on an empty door.

The 404 Itself Is Not What Costs You

Here is the part almost every article on this topic gets slightly wrong, and it is worth correcting before going any further. Google has said plainly, and has said it consistently since a 2011 post on its own Search Central blog, that 404 errors do not themselves count against a site in search rankings. A 404 is a normal, expected part of how the web works. Pages get retired. Products get discontinued. Google's crawlers see millions of them a day and do not penalise a domain for having some.

What actually costs you is everything a careless 404 represents. A visitor who clicked a Google result, or an old bookmark, or a link from another website, and hit a dead end. A page that used to carry backlinks and topical relevance, gone the moment the URL stopped resolving to anything. A lead who was ready to enquire and instead landed on a generic "page not found" message with no obvious way back to what they wanted. None of that shows up as a ranking penalty in the technical sense. All of it shows up as fewer enquiries, which is the number that actually matters to the person reading this.

Soft 404s Are the Quieter, Worse Version

There is a second failure mode worse than a clean 404, and most business owners have never heard of it. A soft 404 is a page that tells a human visitor the content is gone but still returns an HTTP 200 "success" status code to Google, rather than a proper 404 or 410. Google's own guidance is direct about the consequence: a success code tells search engines there is a real page at that address, so the empty page can get indexed, and Google keeps trying to crawl a URL that leads nowhere instead of spending that time on pages that actually matter.

This happens more often than you would expect on a WordPress site, usually because a theme or page builder swaps in a generic "content coming soon" template instead of triggering a genuine 404 response. The page looks broken to a visitor and looks fine to a lazily configured server, which is the worst combination going. For an owner, the practical effect is this: Google keeps circling back to a phantom page instead of finding and indexing the new content you actually want ranked.

A redirected link and a dead one look identical to a visitor for about half a second. After that, one keeps them on the site and one loses them.

Broken Links Are Not Just a Migration Problem

It is tempting to file all of this under "things that happen when you move house." That undersells it. Links break constantly, on every website, with no migration involved at all. A large-scale study by Ahrefs, which crawled billions of links over several years, found that at least 66.5% of links pointing to a set of sampled pages had rotted since 2013, with the decay running at a fairly steady rate rather than arriving in one dramatic event. That is one company's own dataset rather than an independent academic study, so treat the exact figure as directional. The pattern still lines up with what any maintained website will see if nobody checks for broken links on a regular basis.

A supplier changes their website and the page you linked to for a spec sheet disappears. A blog post from two years ago links to a news article that has since been taken down. An old service page gets renamed for clarity and the internal link from your homepage never gets updated. None of this needs a full site rebuild to happen. It happens quietly, a link at a time, on a schedule nobody is watching. Redirects and dead links are one piece of a much larger performance and reliability picture. Our complete WordPress performance guide for business owners covers the rest of what actually determines how a WordPress site holds up under real traffic.

Where I Got This Wrong Myself

Years ago, before I fully appreciated how unforgiving this is, I moved a client's site to a new domain structure over a weekend and treated redirects as a cleanup task for "sometime next week." Rankings that had taken over a year to build were mostly gone within a fortnight, because Google had nothing telling it the new URLs were the same content under a new address. I would not make that call again. Redirects are part of the migration itself, not an afterthought for after launch.

How 301 Redirects Actually Protect What You Have Built

A permanent 301 redirect tells both browsers and search engines that a page has moved for good, and that the old address should be treated as the new one going forward. Google's own documentation recommends a server-side redirect wherever possible, because it is the most reliable way to point both people and crawlers at the correct destination. Independent studies from Moz and Ahrefs, both worth a pinch of salt as single-vendor benchmarks rather than peer-reviewed research, put the amount of link equity a clean 301 preserves somewhere in the 90% to 99% range. Close enough to a full transfer that a well-executed redirect map should not cost you meaningful ranking ground at all.

The word "clean" is doing real work in that sentence. Redirect a URL straight to its closest genuine equivalent, in one hop. Chained redirects, where an old URL bounces through two or three intermediate addresses before landing on the final page, dilute that signal and slow the page down for every visitor who follows the chain. JavaScript redirects and meta-refresh tags are worse again. Google's guidance is explicit that a server-side redirect is what it wants to see, not a client-side workaround a crawler has to render before it even understands where the page went.

If you are moving to an entirely new domain rather than restructuring existing URLs, re-indexing takes real time regardless of how clean the redirects are. We cover exactly how long that process runs, and what to expect from Google in the meantime, in our breakdown of how long a new website takes to rank on Google.

The Honest Limit: Redirects Are Not Free Either

None of this is a reason to redirect everything indiscriminately. Every redirect adds a small delay to a page load, and a chain of three or four adds up to something a real visitor will notice on a slow mobile connection. A redirect map with thousands of legacy entries, most for pages nobody has linked to in years, is dead weight your server checks on every request for no practical benefit. Prune what genuinely does not matter. Redirect what does.

There is also a scale point worth being straight about. Google's own crawl budget guidance is aimed at sites with tens of thousands of pages, updated frequently, where Googlebot genuinely has to ration its attention. A local business site with a few dozen or a few hundred pages is nowhere near that ceiling. If a vendor tries to sell a crawl budget audit to a business running a five-page service site, that is a solution shopping for a problem that does not exist yet. The real risk for a site that size is not crawl budget. It is a stack of quietly broken links nobody has looked at since the last redesign.

The So What of All This

A broken internal link on a service page is not a cosmetic issue. It is a customer who found you through a search that matched exactly what they needed, clicked through, and hit a wall instead of a phone number. By the time anyone checks the analytics and notices the drop in enquiries, that lead has already rung the next business on the list. That is the real cost of a stale redirect map. Not a ranking number on a spreadsheet, but a specific person who wanted to give you money and could not find their way to you.

Fixing Broken Links Without Losing the Traffic You Already Have

Crawl. Run a full site crawl, using a free tool like Google Search Console's Page indexing report or a dedicated crawler, and export every URL currently returning a 404 or a soft 404.

Prioritise. Sort the list by how much it matters. Pages with real backlinks, meaningful organic traffic, or that used to convert enquiries go first. A forgotten post nobody ever linked to can wait.

Redirect. Set up a single server-side 301 from each old URL to its closest current equivalent, not a generic homepage redirect that leaves the visitor no better off than before.

Verify. Check each redirect actually returns a 301, resolves in one hop, and lands on a page that genuinely answers what the visitor was looking for.

Monitor. Recheck the Page indexing report every few weeks. New broken links appear on a live site constantly, not just after a migration.

Five steps, run on a schedule, catch most of what a migration or an ordinary redesign quietly breaks.

A Proper 404 Page Still Earns Its Keep

For whatever genuinely is gone, Google's own design guidance for 404 pages is worth following regardless of the technical fix underneath it. Keep the site's normal navigation visible, say plainly that the page cannot be found, and offer a way back to popular content or the homepage rather than a dead end with nothing on it. A well-designed 404 page will not save a lost ranking, but it can save a visitor who would otherwise have bounced straight to a competitor's search result instead of exploring the rest of your site.

Where the Platform Underneath You Actually Helps

This is where the hosting and the platform you are on stops being background noise and starts mattering directly. WordPress's open plugin ecosystem includes dedicated redirect managers, such as the widely used Redirection plugin, that let a non-technical owner set up and audit 301s from inside the WordPress dashboard rather than editing server configuration files directly. Whether that specific tool is available to you depends on your hosting provider allowing full plugin access rather than restricting you to a closed template system, so check before assuming it is there.

On Web60, full WordPress access is the default rather than a locked-down subset, so the redirect tooling the wider WordPress ecosystem has built over two decades is available from day one. Testing a redirect map before it goes live matters too. A one-click staging environment lets you build and check the full set of redirects in a copy of the site first, so a migration does not mean guessing correctly in production and finding out from a drop in enquiries a week later. Automatic nightly backups, plus a safety snapshot taken before any major change, mean that if a redirect map does go wrong, rolling back to the previous state takes minutes rather than a frantic afternoon rebuilding from memory.

The scenario that started this article, a rebuild that quietly orphaned every existing URL, is exactly what Web60's free migration service exists to prevent. Moving a site's hosting should never mean losing the addresses that took years to earn their rankings. A migration done properly maps every existing URL to its new home before the switch happens, not after somebody notices the enquiries have stopped.

Which Businesses Feel a Broken Redirect Map Fastest

Trades and local services. A missing service page after a rebuild means a customer searching for a nearby provider hits a dead end at the exact moment they were ready to call, and calls the next result instead.
Anyone mid-migration or mid-redesign. Almost all of this damage happens in the window between the old site going down and the new redirect map being verified, and it is entirely avoidable with a proper checklist.
Content-heavy sites with a real backlink history. Years of guest posts, press mentions, and directory listings all point at specific URLs. Change those addresses without redirecting and that accumulated authority evaporates in a single deployment.

Conclusion

The Westmeath fitter's site was fixed within a week once the redirect map went in properly. Every old service URL pointed to its new equivalent, the 404 count in Search Console dropped back to nearly nothing, and the enquiries that had gone quiet picked back up. Nothing about the new website itself was the problem. The gap between the old addresses and the new ones was.

If you are planning a redesign, a rebrand, or a move to new hosting, treat the redirect map as part of the build, not a task for after launch. Check Search Console for existing 404s today, even if nothing about your site has changed recently, because link rot happens with or without a migration. The fix is rarely dramatic. It just has to happen before someone goes looking for a page that used to be there, not after.

Frequently Asked Questions

Do 404 errors hurt my Google rankings?

No, not directly. Google has stated consistently, including in its own Search Central documentation, that having some 404 errors on a site is normal and does not count against it in search rankings. What actually costs you is the lost traffic, lost backlink value, and lost conversions that a genuinely broken link represents, not a ranking penalty triggered by the 404 status code itself.

What is the difference between a 404 and a soft 404?

A standard 404 correctly tells both visitors and Google that a page no longer exists. A soft 404 shows a visitor a "not found" style message but still returns an HTTP 200 success code to search engines, which can cause Google to keep trying to index and crawl a page that has no real content, wasting crawl attention that should go to your genuine pages.

How do I find broken links on my WordPress site?

Google Search Console's Page indexing report, under Indexing then Pages, lists every URL Google has tried to crawl and flags the reasons pages were not indexed, including "Not found (404)". A dedicated site crawler can also check both internal and outbound links across the whole site in one pass, which Search Console does not fully cover.

Do I need to redirect every single old URL when I move my website?

No. Redirect anything with real traffic, backlinks, or search visibility, and prune the rest. A redirect map bloated with entries for pages nobody has visited in years adds unnecessary overhead without protecting anything worth protecting.

How long does it take for a 301 redirect to take full effect?

Google typically recognises and follows a new 301 redirect within days of crawling it, though full re-ranking of the new URL under the old page's previous signals can take several weeks depending on how frequently Google crawls that part of your site. Submitting the new URLs through Search Console's URL inspection tool can help speed up the initial crawl.

Can having too many redirects slow down my website?

Yes, particularly redirect chains, where one old URL bounces through several intermediate addresses before reaching its final destination. Each hop adds a small delay. Keep every redirect to a single hop from the old URL straight to its current equivalent, and remove redirects for pages that no longer need them.