Alejandro Rioja.
Business

How To Migrate A Website Successfully?

Alejandro Rioja
Alejandro Rioja
10 min read
TL;DR

A successful website migration comes down to three things: meticulous pre-migration auditing, airtight 301 redirects, and at least 90 days of post-launch monitoring. Get those right and you protect both your Google rankings and your emerging AI-search presence.

Free newsletter

Every Wednesday. 28,400+ operators. Zero fluff.

Table of contents

Open Table of contents

What is a Website Migration?

A website migration is any structural change significant enough to affect crawling, indexing, or traffic. Common types:

The risk is real. A poorly executed migration can cut organic traffic in half — sometimes permanently. That said, a well-planned migration is also one of the highest-leverage SEO projects you can do: you fix technical debt, consolidate authority, and often come out stronger.

Essential Factors to Consider Before Migration

Before touching anything, work through this checklist:

  1. Document exactly why you’re migrating and what success looks like (traffic parity? 20% traffic lift? faster Core Web Vitals?).
  2. Set a realistic timeline with a hard content freeze date — no new pages or URL changes once you start.
  3. Identify every stakeholder: SEO, dev, content, analytics, comms.
  4. Build your monitoring stack before you migrate so you have clean pre-migration baselines.
  5. Crawl the entire current site and export a complete URL inventory.
  6. Map every URL that will change to its new destination (your redirect plan).
  7. Schedule the cutover for a low-traffic window (Tuesday–Thursday is usually best).
  8. Plan a rollback path — if something goes critically wrong, how do you restore the old site?

Website Migration Steps

1. Define Your Objectives

The goal shapes everything else. Migrating to consolidate two domains is a completely different project than migrating from HTTP to HTTPS or switching from WordPress to a headless CMS.

Write down specific, measurable targets before you start:

One goal I always add now: preserve AI-search visibility. ChatGPT, Perplexity, Gemini, and Google’s AI Overviews all cite sources. If your site is being cited, a migration that breaks crawlability or changes your canonical URLs without proper redirects will cost you that real estate too. More on this in the FAQ below.

Bring in your full team early. SEO, developers, analytics, and content all have blind spots the others will catch.

2. Perform a Full Site Audit

Before you migrate, you need to know exactly what you have. Run a full crawl using Screaming Frog, Ahrefs Site Audit, or a comparable tool. Export:

In Google Search Console (GSC) and GA4, identify your highest-value pages — the ones driving the most conversions and traffic. These get extra scrutiny during redirect mapping and post-launch testing.

For each URL, decide: keep it, redirect it, consolidate it, or remove it. You need this decision logged before you build any redirects.

3. Choose the Right Platform

Platform choice is out of scope for this guide, but the migration process is not. Before you commit to a new platform:

If you’re evaluating CMS options, make sure the SEO fundamentals are handled natively or via a first-party plugin before you commit.

4. Back Up Everything

Before any file or database changes: full backup. This is non-negotiable.

Options:

Store the backup somewhere separate from your hosting environment. If the server goes down mid-migration, your backup on the same server is useless.

5. Build Your 301 Redirect Map

This is the most critical technical deliverable in any migration. Every URL that is changing needs a 301 (permanent) redirect pointing to its new equivalent. Not a 302, not a JavaScript redirect — a server-side 301.

Rules I follow:

Use a spreadsheet: Column A = old URL, Column B = new URL, Column C = HTTP status verified. Test every row before go-live.

6. Inform Stakeholders and Users

For a domain migration or major redesign, internal communication matters as much as technical execution. Tell your team exactly what’s happening and when. For external users:

7. Set Up a Test Environment

Launch the new site on a staging environment — blocked from indexing via noindex or a password — before it goes anywhere near production.

Test against this checklist on staging:

Don’t assign testing to one person. Cross-functional teams catch more bugs.

8. Execute the Migration in Phases

For large sites (thousands of pages), phase the migration by section — blog first, then product pages, then the homepage. For smaller sites, you can go all-at-once, but still do it in a low-traffic window.

Migration day sequence:

  1. Take a final pre-migration crawl snapshot
  2. Deploy the new site and enable redirects
  3. Update robots.txt on the new site (remove any noindex/disallow from staging)
  4. Verify redirects are firing correctly on production
  5. Submit the new XML sitemap to Google Search Console
  6. If it’s a domain migration, use GSC’s Change of Address tool (Settings → Change of Address) — this signals Google directly that the site has moved and accelerates re-indexing

Minimize downtime. The longer the site is offline, the harder the recovery.

9. Post-Migration: Check for SEO Impact

Within 24–48 hours of launch:

Within the first two weeks:

10. Monitor for 90 Days

Most migration damage shows up in the first 30 days. Full recovery (or confirmation you’re in trouble) typically takes 60–90 days. Track weekly:

Set up alerts in GA4 and GSC so drops don’t go unnoticed. If traffic falls more than 20% and stays there after two weeks, go back to your redirect map — a missed or broken redirect is almost always the culprit.

A website migration done well protects your traffic, improves your site’s technical health, and positions you for growth. Done poorly, it can cost months of recovery time.

The formula is straightforward even if the execution isn’t: define clear goals, audit everything, map every redirect, test before you launch, and monitor aggressively afterward.

If you found this useful, these posts cover related ground:

Website Migration — 2026 FAQ

Does a domain migration hurt SEO permanently?

Not if it’s executed properly. Google has stated that domain migrations with correct 301 redirects pass link equity and that rankings typically recover within a few weeks to a few months. The key word is “typically” — I’ve seen badly executed migrations take 6–12 months to recover. The single biggest mistake is redirecting everything to the homepage instead of matching URLs 1-to-1.

What is the GSC Change of Address tool and do I need it?

The Change of Address tool in Google Search Console is a direct signal to Google that your site has moved to a new domain. You submit it in GSC under Settings → Change of Address after you’ve set up 301 redirects. It’s only relevant for domain-to-domain migrations (not subdomain changes, HTTPS upgrades, or URL restructuring). It speeds up re-crawling and re-indexing — I always use it for domain migrations.

How do website migrations affect AI-search visibility (ChatGPT, Perplexity, Gemini)?

AI search tools like Perplexity, ChatGPT with browsing, and Google’s AI Overviews pull from crawled web content. If your site was being cited before the migration and your redirects break or your crawlability drops, you’ll lose that visibility — and it takes longer to recover in AI search than in traditional Google rankings because the re-training or re-indexing cycles are less transparent. To protect it: keep redirects airtight, submit your sitemap immediately post-launch, avoid any period where your pages return errors, and maintain consistent canonical URLs wherever possible.

How long should I keep old 301 redirects in place?

Indefinitely, or at minimum 2–3 years. Removing 301 redirects early breaks backlinks, breaks bookmarks, and breaks any citations in AI-search systems that captured the old URL. The server overhead for a redirect is negligible. There’s no upside to removing them.

Related reading: How to Drive 10x Traffic to Your Website · How Does SEO Improve Marketing On The Global Scale · .Com vs .Net

This guide is part of alejandrorioja.com — written by Alejandro Rioja, who now builds AI agent systems for founders. Including the agent that keeps this site current. How it works →

Updated for May 2026

A short note from May 2026: the workflow this post describes was checked against the current state of the underlying tools and platforms. Where specific tools, UIs, or features have evolved, the structural advice still holds — the implementation will look slightly different in 2026. If you hit a step that doesn’t match what you see on screen, that’s likely a UI refresh, not a fundamental change in approach. Drop a note via the contact form and I’ll patch it explicitly.

Keep reading

Get the AI playbook in your inbox

Every Wednesday. 28,400+ operators. Zero fluff.

⌕
↵ ↵ to see all results esc esc to close