How to Migrate a Website Without Losing Your Google Rankings

The redesign that quietly killed a business

A few years ago we got a call from a company whose traffic had dropped by more than half in about three weeks. Nothing dramatic had happened on the surface. They had simply launched a new website. New design, new agency, new hosting. Everyone was proud of it internally. Then the phone stopped ringing.

What had happened was straightforward and depressingly common. The old site had a few hundred pages, each with its own URL structure, built up over a decade of blog posts, service pages and location pages. The new site had a cleaner structure, which sounds like a good thing, except nobody mapped the old URLs to the new ones. Google had thousands of links pointing at pages that no longer existed. All of that authority evaporated overnight.

This is the part of a website migration that nobody wants to think about, because it is not glamorous. Everyone wants to talk about the new design, the faster load times, the modern feel. Almost nobody wants to spend a day building a redirect spreadsheet. But that spreadsheet is often the single most important deliverable in the entire project.

Why rankings disappear during a migration

Search engines do not understand your business the way a person does. They understand pages, links and signals accumulated over time. When you change a domain, a URL structure, or even just the underlying platform, you are asking Google to re-evaluate a huge number of signals it had already settled on.

Rankings drop during migrations for a small number of predictable reasons. URLs change and nothing tells search engines where the old page went. Content gets rewritten or shortened in a way that removes the exact terms people were searching for. Page speed gets worse because the new build is heavier than the old one, even if it looks nicer. Internal linking gets reshuffled so that pages which used to be one click from the homepage are now buried three levels deep. Technical basics like title tags, meta descriptions and heading structure get lost in the shuffle because the new content management system handles them differently.

None of this is exotic. It is mostly a matter of discipline and sequencing, done in the wrong order or skipped under deadline pressure.

What we actually do before touching anything

Before a single line of new code goes live, we pull a full inventory of the existing site. Every indexed URL, every page that has earned backlinks, every page that is actually pulling in search traffic. Not every page is equally valuable, and knowing which ones matter changes how carefully you treat them.

From there we build a redirect map. Old URL to new URL, one to one wherever possible. Where a page genuinely no longer has an equivalent, we redirect it to the closest relevant page rather than the homepage, since a homepage catch-all redirect is a common shortcut that quietly tells Google the redirect is not to be trusted.

We also keep the content itself intact where it is working. A redesign is a chance to improve layout, imagery and navigation. It is not automatically an excuse to rewrite every paragraph. If a page currently ranks for a set of terms, we make sure those terms and that page's core structure survive the move, even as the visual design changes completely.

The technical checklist that gets skipped under deadline pressure

Most ranking losses trace back to a handful of technical items that are easy to forget when a launch date is looming.

• 301 redirects set up for every meaningful old URL, tested individually rather than assumed to work
• XML sitemap regenerated and submitted the day of launch, not a week later
• Canonical tags, title tags and meta descriptions carried over or improved, never left blank
• Page speed checked against the old site's benchmark, not just against a general standard
• Analytics and search console properties reconnected before launch day, not after someone notices the data gap

We treat this list as non negotiable. It is unglamorous work and it rarely shows up in the final presentation to the client, but it is the difference between a smooth transition and a three month recovery project.

Launch day and the weeks after

The migration itself should happen at a quiet time, with monitoring in place immediately afterwards. We watch crawl activity, indexation rates and any spike in server errors for the first few days. If Google is struggling to find or process pages, that shows up quickly in search console, and it is far easier to fix on day two than to discover it a month later when someone asks why enquiries have dried up.

We also resist the urge to change everything at once. A new domain, a new design and a new content strategy launched simultaneously makes it almost impossible to diagnose a problem if one shows up. Where a client's situation allows it, we prefer to separate structural changes from content changes, so that if rankings dip, we know which variable to look at first.

This is not a reason to avoid redesigning

None of this is an argument for keeping an old, tired website out of fear. Sites need to be rebuilt. Platforms age, design expectations shift, and a site that looked fine in 2019 often looks dated and loads slowly today. The point is that a redesign and a ranking collapse are not the same thing, and they should not be treated as an inevitable package deal.

We have moved sites across platforms, consolidated multiple domains into one, and rebuilt outdated CMS platforms into modern web apps, all without the traffic cliff that scares business owners away from touching their site at all. It takes planning rather than luck.

If you are sitting on a website you know needs rebuilding but you are worried about what happens to your search traffic in the process, that is exactly the conversation worth having before any design work starts. Get in touch through our contact page or start a project at /start and we will walk through what a safe migration looks like for your specific site.