Website Migration SEO: The Complete Checklist to Keep Your Rankings

Moving to a new domain, CMS, host, or URL structure looks like an IT project on paper. In practice, it is the moment a site can lose rankings it took years to earn. A well-planned website migration avoids that outcome, and can even be the chance to fix long-standing technical debt.

This guide pulls together everything you need for a website migration without losing SEO: the pre-migration checklist, the 301 redirect map, DNS and HTTPS cutover, the launch-day sequence, and post-migration performance testing.

Key takeaways

• A migration succeeds before launch: URL inventory, baseline metrics, and a tested redirect map.
• Every URL with traffic, backlinks, or rankings needs a direct 301 redirect to its closest equivalent.
• Lower DNS TTLs ahead of time and keep the old server running during propagation.
• An HTTPS move means a page-to-page 301 from every HTTP URL, with no mixed content.
• Post-migration monitoring (errors, indexing, Core Web Vitals, rankings) runs for at least three months.

What is an SEO migration?

An SEO migration is any major change that affects how search engines access or interpret your site, plus the safeguards that protect your visibility. If URLs change, you are running a migration, and your SEO is at risk. The main types, from lowest to highest risk:

• Hosting change with no URL changes: low risk, mostly about speed and uptime.
• HTTP to HTTPS: low to moderate risk if redirects are correct.
• Redesign with new URLs: high risk, depending on how many pages change.
• Platform change (for example WordPress to HubSpot CMS, or Magento to Shopify): high risk, because URLs, templates, and tags often change together.
• Domain change or merging several sites: highest risk, because all of your authority has to move.

If you are stacking changes, such as a new CMS and a new domain, consider splitting them. It is much easier to diagnose a drop when only one variable moved.

Why website migrations lose traffic

Post-migration traffic losses almost always come from the same causes, and nearly all of them are preventable.

• Changed URLs with no redirect, returning 404 errors.
• Bulk redirects to the homepage, which Google may treat as soft 404s.
• Redirect chains that slow down crawling.
• A staging robots.txt or noindex tag pushed to production.
• Content removed or heavily trimmed during the move.
• Canonical, hreflang, or structured data still pointing at the old site.
• A new site that is slower than the old one.

A short dip while Google recrawls the site is normal. A lasting drop means something is broken.

Pre-migration SEO checklist

This is the most important phase, and the one teams cut first when deadlines slip.

• Baseline metrics: export at least 12 months of Google Analytics 4 and Google Search Console data (clicks, impressions, pages, queries) and record rankings for priority keywords.
• Full URL inventory: combine a crawl (Screaming Frog or similar), your XML sitemaps, URLs with traffic in Analytics, and URLs with backlinks.
• Priority pages: flag the pages that drive most traffic and conversions. They get individual testing.
• Staging: build the new site on a password-protected or noindexed environment that bots cannot reach.
• SEO QA: on staging, check titles, meta descriptions, H1s, canonicals, hreflang, structured data, and internal links.
• Performance: measure the old site's Core Web Vitals so you have something to compare against.
• Timing: pick a slow period for your business, and avoid Friday evenings and the week before a trade show or campaign.
• Backups: back up files, database, and server configuration for the old site.

The 301 redirect map: the core of every migration

Your redirect map is the table that pairs every old URL with its new URL. It is what carries each page's history over to Google. Without it, every changed page starts from zero.

301 vs 302 vs 308: which redirect to use?

• 301 redirect: permanent. The default for any migration.
• 308 redirect: also permanent, and preserves the HTTP request method. Google treats it like a 301.
• 302 or 307 redirect: temporary. Only for genuinely temporary situations such as maintenance or tests.
• JavaScript or meta refresh redirects: avoid them and use server-side redirects whenever possible.

Build the mapping

Start from the full inventory and match each URL to the destination that serves the same intent. A product page goes to the same product's new page, a blog post to the same post, a category to its equivalent category. For pages with no equivalent, choose the closest parent page, or return a 410 if the content is truly gone.

Keep the map in a spreadsheet with three columns (old URL, new URL, status code) and a fourth for test results. Where the redirects live depends on your stack: server rules in Apache or Nginx, bulk redirects at the CDN level in Cloudflare, the URL Redirects screen in Shopify, or the URL redirects tool in HubSpot CMS. For large sites, pattern-based rules (one rule for every /blog/ URL, for example) are easier to maintain than thousands of one-to-one lines, but test them carefully because a single bad pattern can break a whole section.

Rules to follow

• Redirect straight to the final destination, with no chains.
• No bulk redirects to the homepage.
• Test redirects on staging or on a sample before launch.
• Update internal links to the new URLs so you do not rely on redirects.
• Keep redirects in place for a long time. Google recommends at least one year, and the simplest policy is never to remove them.

DNS, hosting, and HTTPS: the technical cutover

Prepare the DNS switch

If you are moving to a new host or domain, DNS is the last and most delicate step. A few days ahead, lower the TTL on the affected records (in Cloudflare, Route 53, or your registrar) so the change propagates quickly on launch day. Keep the old server running during propagation, double-check MX records so email keeps working, and keep the old domain registered so its redirects keep working.

Move to HTTPS

• Install a valid certificate that covers every hostname variant (www and non-www).
• 301 redirect every HTTP URL to its HTTPS version, page to page.
• Remove mixed content: images, scripts, and stylesheets must all load over HTTPS.
• Update canonicals, hreflang, sitemaps, and internal links to HTTPS URLs.
• Once everything is stable, enable the HSTS header to enforce HTTPS in browsers.

Pick one canonical version (HTTPS, with or without www) and send every other variant to it in a single hop.

Launch day: the migration sequence

1. Freeze content changes on the old site.
2. Deploy the new site and switch on redirects.
3. Remove noindex and check the production robots.txt.
4. Switch DNS if needed.
5. Test redirects for priority pages, then a broad sample.
6. Check forms, analytics tracking, and lead sync to HubSpot or Salesforce.
7. Submit the new XML sitemap in Search Console.
8. For a domain change, use the Change of Address tool in Search Console.

After the migration: performance testing and monitoring

The work does not stop at launch. The first weeks are when errors are cheapest to catch and fix.

• Day one: run a full crawl to catch 404s, redirect chains, and pages accidentally left on noindex.
• First week: check indexing and crawl error reports in Search Console every day.
• Performance testing: compare Core Web Vitals with your pre-migration baseline (LCP under 2.5 s, INP under 200 ms, CLS under 0.1) using PageSpeed Insights, then watch field data in Search Console.
• First month: compare clicks, impressions, and rankings for priority pages against the baseline period.
• First three months: keep reviewing new 404s (usually forgotten legacy URLs) and add missing redirects.

Update what lives outside your site too: LinkedIn and directory profiles, Google Business Profile, Google Ads and Microsoft Ads campaigns, email signatures, and ask partners who send you important backlinks to update them.

Website migration SEO FAQ

What is SEO migration?

It is the process of moving or restructuring a website (domain, CMS, hosting, URL structure, or protocol) while preserving its rankings, authority, and indexing signals.

How do you migrate a website without losing SEO?

Inventory every URL before the project, build a page-to-page 301 redirect map, test the new site on a noindexed staging environment, and monitor errors and indexing closely after launch.

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

It depends on site size and migration type. Google says a medium-sized site can take a few weeks for most pages to move in its index, and larger sites take longer. A drop that lasts beyond a few months almost always points to a technical issue.

How long should you keep 301 redirects?

At least one year, per Google's guidance, and ideally permanently. Old backlinks and bookmarks keep sending visitors to legacy URLs for years.

Do 301 redirects lose PageRank?

Google has stated that 30x redirects do not lose PageRank. Losses come from redirecting to irrelevant pages, from chains, or from missing redirects.

Protect your migration with Klickbee

At Klickbee, we run B2B website migrations end to end: URL inventory, redirect mapping, SEO QA on staging, DNS and HTTPS cutover, and post-launch monitoring. Our senior experts use in-house AI agents to validate redirect maps across thousands of URLs. Explore our technical SEO services, our website maintenance services for what comes after, or request a free action plan before you start.

Related guides

• Website redesign: process and checklist
• Core Web Vitals explained
• How to run an SEO audit