The Website Migration SEO Checklist: How to Redesign Your Site Without Losing Your Rankings

06 September 2026·6 min read

Quick answer: A website redesign or platform migration is the single riskiest moment in your site's SEO life — Google has to re-crawl, re-index and re-evaluate every page from scratch, and any gap between old and new gets read as “this page is gone.” The fix is a proper pre-launch, launch-day and post-launch checklist covering redirect mapping, removing the staging noindex, resubmitting your sitemap in Search Console, and auditing your backlinks. Done properly, most sites hold their rankings within a few weeks. Done casually, you can lose 30-60% of organic traffic overnight. 📈

If you've ever heard a horror story about a business “redesigning their site and losing all their Google traffic overnight,” it wasn't bad luck — it was a missing checklist. Migrations don't have to be scary, but they do have to be methodical, because Google doesn't transfer your rankings automatically just because your new site looks nicer.

We've project-managed enough platform switches to know the pattern: the design gets all the 💖, and the technical SEO handover gets ten rushed minutes the night before launch. That's exactly backwards.

What most businesses get wrong

The single biggest failure point is assuming a “redesign” only touches how the site looks. In reality, almost every migration changes URLs — even subtly, like adding or dropping a trailing slash, switching from .html endings to clean URLs, or restructuring category folders. Google has indexed your old URLs. If the new ones don't have a 301 redirect pointing to them, every one of those old links — and the ranking signal attached to them — dies on impact. The second most common failure is launching the new site while it's still marked “noindex” from staging, which quietly tells Google not to show any of it.

The Website Migration SEO Checklist

2-4 weeks before launch
☐ Crawl the old site and export every live URL (Screaming Frog or a free tool like Xenu will do this)
☐ Pull your top 100 landing pages by traffic from Google Analytics/Search Console — these are non-negotiable to redirect correctly
☐ Build a redirect map: old URL → new URL, one row per page, in a spreadsheet
☐ Export your current backlink list from Search Console or Ahrefs/Semrush so you know who's linking to what
☐ Note your current top-ranking keywords per page so you can compare after launch

Launch day
☐ Implement all 301 redirects from the map above — no redirect chains, redirect straight to the final URL
☐ Remove the “Discourage search engines from indexing this site” checkbox or noindex meta tag from the new (now live) site
☐ Update your XML sitemap to reflect the new URLs and submit it fresh in Google Search Console
☐ Check robots.txt isn't accidentally blocking the new site
☐ Update internal links across the site to point directly to new URLs (not through redirects)
☐ Set up 404 monitoring so you catch anything missed in the first 48 hours

First 4-6 weeks after launch
☐ Check Search Console's Coverage report weekly for a spike in “not found” or “crawled, not indexed” errors
☐ Compare rankings for your top keywords weekly against your pre-launch benchmark
☐ Reach out to your 10-20 highest-value backlink sources and ask them to update the link directly (redirects lose a small amount of value over time)
☐ Re-verify your Google Business Profile website link and any other directory listings point to the new domain/URLs

Bricks-and-mortar retailer moving platforms: A homewares store moving from an older platform to Shopify had 340 product URLs. Their web developer redirected the 40 “main” category pages but left individual product URLs to 404, assuming Google would “figure it out.” Within three weeks, organic traffic to product pages dropped 52% — a 340-row redirect map from old slug to new slug would have taken about two hours to build.

Local service business refreshing a dated site before spring: A business refreshing a seven-year-old site kept the same URL structure deliberately (no redirects needed) but forgot the new site was still set to noindex from the staging server. It sat invisible to Google for 11 days before anyone noticed traffic had flatlined — a five-second checkbox that cost nearly two weeks of visibility.

Multi-location business consolidating three separate mini-sites into one: Merging three location subdomains into one main domain meant redirecting roughly 90 pages. They prioritised the highest-traffic pages in week one, then handled the long tail over the following month — rankings dipped for about 10 days before recovering to pre-migration levels.

How redirect mapping actually works

A redirect map is nothing fancier than a two-column spreadsheet: old URL, new URL. The skill is matching intent, not just similarity — send visitors and Google to the closest equivalent page on the new site, not the homepage as a lazy catch-all. Redirecting everything to the homepage is technically “a redirect,” but Google treats it as a weak signal and most of the page-specific ranking value is lost.

Use a 301 (permanent) redirect, not a 302 (temporary) — a 302 tells Google “this might change back,” so it hesitates to transfer ranking signals. Keep redirect chains to one hop: if A redirects to B and B has since moved to C, point A straight to C rather than stacking redirects.

After launch, submit your new sitemap under Sitemaps and use the URL Inspection tool on your 10-20 most important pages to request indexing manually, rather than waiting on Google's normal crawl schedule.

💡 Build the redirect map before you build the new site. Treat it as a launch dependency, not a nice-to-have — if the map isn't ready, the launch date should move, not the other way around.

Mistakes to avoid

Redirecting everything to the homepage. It “resolves” the 404 but tells Google the page's specific relevance is gone — you'll rank for the homepage keyword, not the one that page used to own.
Launching with the staging noindex tag still in place. This is invisible in a normal browser visit, so it's easy to miss — always check “view page source” for a noindex meta tag on launch day.
Waiting to see if rankings drop before acting. By the time you notice the drop in Analytics, Google has already recrawled and recorded the missing pages — early monitoring in Search Console catches it days sooner.
Only redirecting your “important” pages. Old blog posts and thin category pages often carry more backlink equity than you'd expect — a partial redirect map leaves real value on the table.
Not telling your backlink sources. A redirect preserves most link value but not all of it — asking your best referring sites to update the link directly is worth the email.

Frequently asked questions

How long does it take to recover rankings after a migration?

With a clean redirect map and no noindex issues, most sites recover within 2-6 weeks as Google recrawls the new URLs. Larger or more structurally different sites can take longer — treat any estimate, including ours, as a guide, not a guarantee.

Will I definitely keep all my rankings if I follow this checklist?

No, and it's worth being upfront about that. A checklist minimises risk, it doesn't eliminate it — some ranking movement is normal even done correctly, since Google re-evaluates technical signals like speed and structure alongside the redirects.

Do I need to redirect every single old URL, even ones with almost no traffic?

Ideally yes, but on a genuinely huge site, prioritise by traffic and backlinks first, then work through the long tail afterwards rather than delaying launch to map every last URL.

What's the difference between a redirect and just deleting the old page?

Deleting a page without a redirect returns a 404 — the ranking value attached to it is lost. A redirect tells Google “this content lives here now,” transferring most (not all) of that value to the new URL.