How to Migrate a Website Without Losing Your Google Rankings (SEO Checklist)

You have a site that brings in clients from Google and you want to move it: to a new platform, a new domain, or simply a rebuilt version. The biggest fear, and a fair one, is waking up the next day to half the traffic and a phone that has gone quiet.

The good news is that migration does not break rankings on its own. What breaks them is a handful of predictable mistakes: changed URLs with no redirect, important pages forgotten along the way, a new site slower than the old one. All of these are avoidable with a plan. Below is the checklist we run on every migration — order matters, and the step people skip most is the one that hurts most.

Before anything else: map the old site

You can't keep what you never inventoried. The first step, done BEFORE you touch anything, is to write down everything that brings traffic today.

• Export the full list of URLs from your current site — a crawl tool or your sitemap gives you the list.
• Pull from Google Search Console the pages that get impressions and clicks, and the terms you're found for.
• Note which pages have links from other sites — those are the most valuable and the easiest to lose.

The result is a simple list: old URL → what role it plays → where it lands on the new site. This list is the backbone of the whole migration. Without it, you're working on guesswork.

301 redirects: the piece that can't be missing

This is where rankings are lost most often. When a page changes its address, Google needs to know where it moved — otherwise it treats it as gone, and the position you earned over years evaporates.

The rule is simple: every old URL that had traffic or links gets a 301 (permanent) redirect to the equivalent page on the new site. "Equivalent" means the closest content, not the homepage for everything. An article about a service goes to the new service page, not to the homepage.

• Don't funnel dozens of pages all into the homepage — Google treats that almost like a 404.
• Avoid redirect chains (A→B→C); go straight A→C.
• If you keep the same URLs on the new platform, all the better: fewer redirects, less risk.

Keep the on-page structure, not just the text

Google recognizes a page by its internal signals too, not only its address. When you rebuild, keep the elements that say "this is the same page":

• Tab titles and meta descriptions — copy them, don't reinvent them all at once.
• The H1/H2 heading structure and the actual copy — if you rewrite everything from scratch, it's a new page in Google's eyes.
• Image alt text and file names.
• Structured data (schema) if you had it — for local businesses, the address, hours and reviews.

Migration is the perfect moment to improve weak content, but do it in stages, after the new site has settled. A big platform change AND a content change on the same day make it impossible to tell what caused any drop.

Speed and the technical side: where the new site wins or loses

A common reason traffic drops after a migration isn't SEO — it's that the new site is simply slower or has technical errors. Check:

• Mobile speed — Google looks at Core Web Vitals (LCP under 2.5 seconds is the benchmark). A slow-loading site loses both visitors and rankings.
• The robots.txt file and the noindex tag — the most common launch blunder is forgetting the site blocked from indexing during the test phase. Check that first.
• The HTTPS certificate active on the new domain, with no content loaded over http.
• A fresh, correct XML sitemap, ready to submit.

Here is where how the site is built matters. At MPO we deliver on a modern, fast foundation precisely so the migration becomes a chance to move up in speed, not down — and we show you a pre-built demo before you move anything, so you see the real result, not a promise.

Launch day and the first two weeks

Migration isn't over when the site is live. It's over when Google has re-processed everything and traffic is stable.

On launch day:

• Test a sample of old redirects — open 10-15 old URLs and check they land where they should.
• Submit the new sitemap in Google Search Console and request reindexing of the main pages.
• If you changed domains, use the change of address tool in Search Console.

In the first two weeks:

• Watch the coverage report in Search Console for new 404 errors and fix them with a redirect.
• It's normal for traffic to wobble for a few days; a slight temporary dip is not a reason to panic.

If you'd rather go through this with someone who has done it before, message us on WhatsApp — we'll look at your site map together before the move and tell you honestly where the risk is.