A new website should be an upgrade, yet many redesigns cause sudden drops in organic traffic. The cause is rarely the design. It is lost URLs, missing redirects, removed content and staging settings that slip into production. An SEO website migration plan prevents these mistakes.

Types of website migration

Website migration types and SEO risk
Migration typeExampleSEO risk
Redesign without URL changesNew design and templates, same URLsLow to medium
Content restructurePages merged, URLs changedMedium to high
ReplatformingWordPress to a new CMSMedium to high
Domain migrationoldbrand.com to newbrand.comHigh
Protocol or subdomain changeHTTP to HTTPS, www to non-wwwLow to medium if redirects are correct

The more URLs change, the more carefully you need to plan. Google's guidance on site moves with URL changes explains the recommended process.

Phase 1: Plan and benchmark

  1. Define the scope: what changes in URLs, content, design and platform.
  2. Export current performance: top pages by organic traffic, conversions and backlinks; keyword rankings for priority terms.
  3. Crawl the current site to capture every URL, title, meta description, H1, canonical and status code.
  4. Export URLs from the XML sitemap, analytics and Search Console to catch pages a crawl misses.
  5. Choose a launch date away from your busiest season.

Phase 2: Build the redirect map

The redirect map is the heart of the migration. Each old URL that changes should point to the single most relevant new URL with a 301 redirect.

  • Map one-to-one wherever possible.
  • When pages are merged, redirect all old URLs to the combined page.
  • Avoid redirecting everything to the homepage; it frustrates users and loses relevance.
  • Avoid redirect chains: old URLs should point directly to final destinations.
  • Include images, PDFs and other files with external links.

Phase 3: Preserve SEO elements on the new site

  • Keep or improve content on pages that rank. Removing sections from top pages is a common cause of ranking loss.
  • Carry over titles, meta descriptions and headings, improving them where useful.
  • Rebuild internal links so they point directly to new URLs.
  • Recreate structured data, canonical tags and hreflang where used.
  • Keep page speed at least as good as before; see our Core Web Vitals guide.

Phase 4: Test on staging

  1. Protect staging with authentication so it is not indexed.
  2. Crawl the staging site and compare with the old crawl.
  3. Test redirects in bulk using the redirect map.
  4. Check templates for titles, canonicals, meta robots, structured data and analytics tags.
  5. Test forms, tracking and key conversion paths end to end.

Our QA and testing service runs these checks as part of launch preparation.

Phase 5: Launch day checklist

  • Remove staging blocks: robots.txt disallow rules, noindex tags and password protection.
  • Activate redirects and spot-check the top 50 URLs.
  • Submit the new XML sitemap in Search Console.
  • For domain changes, use the Change of Address tool in Search Console.
  • Confirm analytics and conversion tracking are recording.
  • Crawl the live site for errors.

Phase 6: Monitor and fix

Watch closely for at least four to eight weeks:

  • Search Console coverage and page indexing reports.
  • 404 errors and unexpected redirects.
  • Rankings and traffic for the pages you benchmarked.
  • Conversions and lead volume.

Fix issues as soon as they appear. Fluctuations are normal for a few weeks; sustained drops on specific pages usually point to a missing redirect or removed content.

Diagnosing a traffic drop after migration

If traffic falls after launch, check in this order:

  1. Are pages indexable? Look for noindex, robots blocks and canonical errors.
  2. Are redirects working and pointing to relevant pages?
  3. Did important content, internal links or structured data disappear?
  4. Did page speed or rendering get worse?
  5. Is the drop limited to certain sections, which suggests template issues?

Compare old and new versions of the pages that lost the most traffic. The answer is usually visible.

Who should be involved in a migration

Migrations fail when SEO is consulted only at the end. Involve the right people from the start: an SEO lead who owns the redirect map and benchmarks, developers who implement templates and redirects, content owners who decide what is kept, merged or retired, an analytics owner who ensures tracking continues, and a project lead who protects time for testing. Hold a short go/no-go meeting before launch to confirm every critical check has passed.

SEO website migration timeline

Plan at least four to eight weeks of SEO work before launch for a medium-sized site, and longer for complex replatforming or domain changes. Rushing the redirect map and testing is the most common reason migrations fail.

If you are planning a redesign or platform move, our website redesign and migration service builds SEO protection into the project from the first workshop. Related reading: our website launch checklist and technical SEO audit checklist.

Frequently asked questions

Will I lose rankings when I redesign my website?
Some short-term fluctuation is common, but significant losses are usually avoidable with a complete redirect map, preserved content and thorough testing.
How long do 301 redirects need to stay in place?
Keep redirects for at least a year, and preferably permanently for URLs with backlinks or ongoing traffic.
How long does it take to recover after a website migration?
Well-executed migrations often stabilise within a few weeks. Domain changes and large restructures can take several months for search engines to fully process.
Should I change URLs during a redesign?
Only when there is a clear benefit, such as a better structure. Every changed URL adds risk and must be redirected correctly.
What is the difference between a 301 and a 302 redirect?
A 301 redirect signals a permanent move and is the standard for migrations. A 302 signals a temporary move and should be used only when the original URL will return.