A Strategic guide to website migrations

A website migration is the process of making substantial changes to a site’s location, platform, structure, content, or design. It can be as simple as moving from HTTP to HTTPS or as complex as a full domain and CMS change.

While often necessary for growth and technological advancement, a poorly executed migration is one of the quickest ways to destroy years of accumulated SEO value. A successful one, however, is barely noticed by users and search engines, preserving your organic visibility.

This is not just a technical checklist; it is a strategic guide. It breaks the process down into three distinct phases to ensure nothing is left to chance.

This guide is for you if you are:

• Changing your domain name (e.g., brand.com to newbrand.com).
• Moving from HTTP to HTTPS.
• Changing your site’s CMS (e.g., WordPress to a custom build).
• Undertaking a major redesign that changes URL structures.
• Merging multiple websites into one.

Phase 1. Pre-migration – The blueprint for success

This is the most important phase. Thorough planning (90% of the work) determines the outcome. Rushing this stage will guarantee problems later.

Define the scope and goals

First, understand exactly what is changing and why. Are you only changing the domain, or are you also changing the URL structure and redesigning the layout? The more variables you introduce at once, the higher the risk. If possible, avoid changing everything simultaneously.

Assemble the migration team

A migration is not a solo task. You need a dedicated team with clear roles. Core team members –

• SEO Specialist – to lead the SEO strategy, create the URL map, and monitor performance.
• Project Manager – to coordinate all moving parts and keep the project on schedule.
• Developers (Backend & Frontend) – to implement redirects, manage the server, and build the new site.
• Content & UX Specialists – to ensure content quality and user experience are maintained or improved.
• PPC & Marketing Team – to update ad campaigns and external links.

Conduct a full pre-migration benchmark audit

You cannot measure success if you don’t know where you started. Before you touch anything, you must create a complete snapshot of your current site’s performance.

Action 1. Perform a complete crawl – Use a tool like Screaming Frog to crawl your entire existing website. Export all data, including URLs, page titles, meta descriptions, headings, status codes, and word counts. This is your master list of all known assets.

Action 2. Benchmark your performance – Record your key metrics for the last 30, 90, and 365 days.

• From Google Search Console – Clicks, impressions, average CTR, and average position. Export your top 1,000 queries and top 1,000 pages.
• From Google Analytics (or equivalent) – Total organic traffic, conversions from organic traffic, bounce rate, and top-performing organic landing pages.
• From a Rank Tracker in Ahrefs- Your rankings for a core set of strategic keywords.

Create the master URL mapping document

This is the heart of a technical migration. It is a spreadsheet that acts as the instruction manual for the redirects, telling the server where to send users and search engines for every single URL on your old site.

What it must include –

• Column A. Old URL – Every URL found in your initial crawl.
• Column B. New URL – The corresponding destination URL on the new site.
• Column C. Redirect Type – This should be 301 (Permanent Redirect) for almost all cases, as it passes the most link equity.
• Column D. Status – A column to track if the redirect has been tested and implemented.

Every URL from the old site must be mapped to the most relevant page on the new site. Do not redirect all old pages to the new homepage. This is a common and devastating mistake that tells Google the old pages no longer have value.

Prepare and audit the staging environment

Your new website should be built on a staging (or development) server that is not accessible to the public or search engines (ensure it is password-protected or blocked via robots.txt).

Before launch, you must crawl the staging site to ensure everything works as expected. Check for broken links, incorrect canonical tags, missing meta tags, and mobile-friendliness issues. Test the user experience and ensure all critical functionality is working.

Phase 2. The Launch – Execution and go-live

This is the day the new site goes live. It should be a carefully orchestrated event, preferably during a period of low traffic (e.g., late on a Monday night).

The go-live checklist

• Step 1 – Choose your launch time. Inform the entire team.
• Step 2 – Implement all 301 redirects from your master mapping file.
• Step 3 – Update DNS records to point your domain to the new server.
• Step 4 – Remove any blocks from the robots.txt file on the new site (e.g., change Disallow: / to Allow: /). This is a critical step. Step 5 – Launch the new site.
• Step 6 – Immediately run a Screaming Frog crawl on the new live site. Use a list of the old URLs and crawl them to verify that they are all correctly 301 redirecting to the new URLs.
• Step 7 – Submit your new XML sitemap(s) via Google Search Console.
• Step 8 – If you have changed your domain, use the “Change of Address” tool in Google Search Console.
• Step 9 – Update URLs in your advertising platforms (Google Ads, Facebook Ads), social media profiles, and email marketing templates.
• Step 10 – Manually check a sample of your most important pages to ensure they are loading correctly.

Phase 3. Post-Migration – Monitoring and troubleshooting

The job is not finished at launch. The weeks following the migration are critical for identifying and fixing issues before they cause lasting damage.

3.1 Immediate monitoring (the first 72 hours)

Watch your analytics and server logs like a hawk. Look for any immediate signs of trouble:

• Spikes in 404 errors in GSC or your live crawl.
• Server errors (5xx codes).
• Sharp drops in real-time organic traffic.

3.2 Ongoing monitoring (the first 8 weeks)

Continuously compare your post-launch data with the pre-migration benchmarks you saved.

• In Google Search Console – Monitor the Indexing > Pages report for any issues. Watch your clicks and impressions closely. Are they recovering to pre-migration levels?
• In Google Analytics – Compare organic traffic and conversions week-over-week and year-over-year.
• Using a Rank Tracker – Monitor your core keywords. Some fluctuation is normal, but you are looking for a trend of recovery.
• Run weekly crawls – Continue to crawl the site to find and fix broken internal links or new redirect chains.

3.3 Common post-migration issues and fixes

• Problem: Traffic has dropped significantly – Check that your redirects are implemented correctly, that the site is not blocked by robots.txt, and that your analytics tracking code is installed and working on the new site.
• Problem GSC shows a spike in 404 errors – Your URL mapping was likely incomplete. Identify the top 404s and implement 301 redirects for them immediately.
• Problem Rankings are fluctuating wildly – Some fluctuation is expected as Google processes the changes. However, if the trend is consistently downward after 2-3 weeks, it may indicate a deeper issue with content quality, internal linking, or lost backlinks.

The most devastating migration mistakes to avoid

1. Failure to plan – the biggest mistake is treating a migration as a purely technical task without involving an SEO specialist from day one.
2. Incomplete URL mapping – missing even a small percentage of your 301 redirects can result in significant traffic loss, especially if those pages had valuable backlinks.
3. Blocking the new website – forgetting to remove Disallow: / from the robots.txt file on the live site is a simple mistake that will make your entire website invisible to search engines.
4. Changing too much at once – if you change your domain, URL structure, and content all at the same time, it is nearly impossible to diagnose what caused a traffic drop. If possible, stagger major changes.
5. Forgetting to update internal links – your new site should not contain any internal links pointing to the old URLs. While redirects will catch them, they create unnecessary redirect chains that slow down the website and waste crawl budget.