Migrating a Website Without Losing Rankings: A Practical Playbook

The Redesign That Tanked Three Years of SEO Work

A clinic owner called us in a panic. Her new website had launched two weeks earlier, built by a designer who did beautiful work. Clean layout, faster load times, better photos. Then her phone stopped ringing.

Traffic had dropped by more than half. Rankings for terms she'd spent years earning, her city name plus her specialty, her clinic name, "near me" searches, had simply vanished. The old site was gone. The new one was invisible.

This happens more often than anyone likes to admit. Redesigns and platform moves are treated as a design project. They're actually an SEO project that happens to involve design. Miss that distinction and you can lose rankings that took years to build, sometimes permanently.

Why Migrations Break Rankings

Google doesn't index a website once and leave it alone. It re-crawls constantly, and every time it finds your pages, it checks whether they still exist where they used to, whether they still say what they used to, and whether they still link to the same things.

A migration changes all three at once. URLs shift. Content gets rewritten or trimmed "for a cleaner look." Internal links break. Old pages that ranked well get merged, deleted, or renamed without anyone tracking what happened to them.

From Google's side, it looks like the old site vanished and a new, unrelated site appeared. There's no automatic reason for it to assume they're the same business with the same authority. You have to tell it, carefully, page by page.

What Actually Needs to Happen Before Launch

The single biggest mistake is treating the old site as disposable once the new one is ready. The old site is your map. Before anything goes live, someone needs to document:

• Every URL that currently exists and gets any traffic or ranking, not just the obvious ones
• Which pages bring in search traffic versus which are dead weight
• The exact title tags, meta descriptions, and headings that are working
• All the internal links pointing between pages
• Any inbound links from other websites, directories, or press mentions

This sounds tedious because it is. It's also the difference between a migration that's invisible to your rankings and one that sets your business back a year.

Redirects Are Not Optional

Every URL that changes needs a 301 redirect pointing the old address to its new equivalent. Not to the homepage. Not to a generic category page. To the actual page that replaced it, or the closest match if the content moved.

We see this go wrong constantly. A business redesigns their site, the developer redirects everything to the homepage "to be safe," and Google interprets that as the entire old site disappearing. Rankings reset to zero and rebuild slowly, if they rebuild at all.

Done properly, a redirect map is built page by page before launch, tested after launch, and monitored for months afterward because crawlers don't update instantly.

Content Changes Matter More Than People Expect

New websites often come with a content refresh, and that's usually a good thing. Old copy gets tightened, pages get restructured, sections get combined. The risk is that the pages doing the actual ranking work get rewritten by someone who doesn't know why they were ranking in the first place.

If a page ranks for "emergency plumber Brampton," the phrase needs to survive the redesign in some form, even if the sentence around it changes. We've seen redesigns strip out the exact language customers were searching for because it read better without it. Readability matters, but not at the cost of relevance signals that took years to build.

The safer approach is auditing what's currently working before touching the words, then rewriting with those signals preserved rather than guessed at afterward.

Technical Details That Get Overlooked

A few things consistently slip through on migrations, especially when a business changes platforms entirely, moving from WordPress to a custom build, or switching hosting providers.

Sitemaps need to be regenerated and resubmitted to Google Search Console the day the new site goes live, not weeks later. Robots.txt files sometimes get copied over from a staging environment and accidentally block the entire site from being crawled, which happens more than you'd think. Page speed and mobile rendering need checking on the actual live environment, not just the staging preview. Structured data, if the old site had it for reviews, services, or business hours, needs to be rebuilt exactly, because losing it can affect how listings appear in search results even if rankings hold.

None of these are difficult individually. They're just easy to forget when everyone's focused on how the new site looks.

The Weeks After Launch Matter Most

Migration isn't finished when the new site goes live. The first four to eight weeks are when problems surface, redirect chains that loop incorrectly, pages that got missed in the audit, crawl errors that only show up once Google starts reprocessing the site.

Watching Search Console during this window, checking that key pages are being indexed under their new URLs, and confirming rankings are holding rather than sliding, is where most of the actual protection happens. If something's wrong, catching it in week two is very different from catching it in month three.

Migrations Are Routine, When Planned as SEO Work

None of this means a redesign or platform switch is risky by nature. We've moved plenty of sites, sometimes for cosmetic reasons, sometimes because a business has outgrown its old CMS, sometimes because they need a proper CRM integration a template site can't support. Done with a proper audit, redirect plan, and post launch monitoring, rankings typically hold steady or improve, because the new site is faster and better structured.

The failures happen when migration is treated purely as a design refresh, handled by someone thinking about visuals rather than what Google sees underneath.

If you're planning a redesign, a platform move, or a rebuild and want to keep what you've already earned in search, get in touch through /contact or start a project at /start. We'll map what you have before we touch anything.