Migrate without losing ground

A redesign is supposed to make a business stronger. Too often it does the opposite, and the owner does not find out until the calls slow down a month later. The new site looks beautiful, everyone is pleased, and then traffic that took years to earn quietly evaporates because the redesign treated the old site as garbage to throw out instead of an asset to protect. The pages that ranked are gone or moved, the links pointing at them now lead nowhere, and Google, which had learned to trust the old site, has to start over. We do not let that happen. A redesign should carry the earned ground forward, not surrender it.

Why redesigns tank rankings

The damage almost always comes from the same handful of mistakes, and every one of them is avoidable.

Broken URLs are the biggest. The old site had a page at one address that ranked well and brought in steady traffic. The new site puts that content somewhere else, or drops it, and the old address now returns a not-found error. Every link to it, from Google, from other sites, from a customer’s bookmark, now lands on a dead end. The ranking that page held does not transfer. It just disappears.

Lost content is next. In the rush to make the new site cleaner, words get cut. But some of those words were the reason the page ranked at all. A redesign that trades a page of helpful, specific content for a sparse, pretty layout often trades away the traffic with it.

And missing redirects tie it all together. When a URL has to change, there is a right way to move it that tells search engines and browsers where it went. Skip that step, and the equity the old page built is stranded with the dead address. Most ranking loss after a redesign is not bad luck. It is these three steps skipped.

Our migration checklist

So before we change anything, we treat the old site as evidence. We are eager to ship live first, but on a redesign that speed has to protect what already ranks, so the mapping comes before the launch. This is the same instinct we bring when we audit before building, and it pays off most here.

First, we map the old URLs. Every page that exists, what it is, and how it performs. We find the pages that bring in traffic and the searches that send it, so we know exactly what is worth protecting before we touch a thing.

Second, we keep what ranks. The pages earning traffic keep their addresses when we can, and keep the content that earns them. If a page ranks for a question customers actually ask, that page and its answer survive the redesign, dressed in the new design but not stripped of what made it work.

Third, we redirect what changes. When a URL genuinely has to move, we set up a permanent redirect from the old address to the new one. That is the move that carries the ranking forward. The old link still works, the visitor lands in the right place, and search engines learn the page relocated rather than vanished.

Fourth, we submit a fresh sitemap. Once the new site is live, we give search engines a current map of every page so they can find and re-index the new structure quickly instead of stumbling through it.

Fifth, we verify in Search Console. We watch the tool that shows what Google sees, looking for errors, dead pages, and anything that dropped. It is how we catch a problem in days instead of finding out from a quiet phone in a month.

How we verify nothing dropped

Launch is not the finish line on a migration. It is the start of the watching.

For the weeks after a redesign goes live, we keep an eye on the pages that mattered most. Did the traffic hold? Are the redirects sending people where they should go? Did any page that used to rank slip? Because we mapped the old site first, we know precisely what to compare against. We are not hoping nothing broke, we are checking against a list.

When something does dip, and on a big migration something usually needs a nudge, we catch it early and fix it. A redirect that was missed gets added. A page that lost a little ground gets the content it needed back. Small corrections in week one are easy. The same problems found in month two, after the rankings have settled lower, are far harder to climb back from. Watching closely right after launch is what turns a risky redesign into a safe one.

The goal through all of it is simple. The business should come out of a redesign with more, not less. A better site, a clearer path to the one number, and every bit of the traffic and trust it spent years earning, still intact. That is the difference between a redesign that grows a business and one that quietly sets it back.

A migration done right protects what the old site earned. The next job is making sure the new site can prove what it earns from here, which is why we wire up measurement from day one.