The SEO Website Migration Checklist: Best Practices for a Move That Does Not Tank Your Traffic
.avif)
A website migration is one of the few SEO projects that can wipe out years of progress in a single afternoon. New design, new platform, new domain, cleaner URLs. It all sounds like an upgrade. Then the redirects break, rankings slide, and organic traffic falls off a cliff while everyone stares at the analytics dashboard wondering what happened.
It does not have to go that way though.
Most migration disasters are not caused by Google being cruel. They are caused by missed steps, rushed timelines, and nobody owning the SEO side of the project. A migration done with a real plan can limit visibility loss, but a migration done poorly can take months to recover from.
This is the SEO website migration checklist we use to protect organic performance before, during, and after a move. It is built for marketers, SEOs, developers, and anyone who has been handed a migration and told to "make sure SEO is fine."
Key Takeaways:
- A website migration is any major change to your site's domain, platform, structure, URLs, or design that affects how search engines crawl, index, and rank it.
- The single biggest cause of traffic loss during migration is broken or missing redirects. One-to-one redirect mapping for priority URLs is non-negotiable.
- Benchmark everything before you migrate. You cannot prove a migration succeeded or diagnose a drop if you never recorded what "normal" looked like.
- Migrations now also put your AI Overview and answer engine visibility at risk, not just your blue-link rankings. Structure and content parity matter more than ever.
- Recovery is normal. Expect a dip in traffic, monitor closely for four to eight weeks, and do not panic-edit on day three.
What Is a Website Migration in SEO?
A website migration is any significant change to a site's setup that affects how search engines crawl, index, and rank it. That includes moving to a new domain, switching platforms or CMS, restructuring URLs, redesigning the site, moving from HTTP to HTTPS, or merging two sites into one.
The common thread is risk. Anytime URLs, content, or site architecture change, the equity those pages have earned, including rankings, backlinks, and crawl history, is in play. The goal of an SEO migration plan is to carry that equity across to the new site with as little loss as possible.
Common Types of Website Migration
Not every migration carries the same level of risk. Knowing which type you are dealing with shapes the entire plan.
- Domain change or rebrand: Moving from olddomain.com to newdomain.com. High risk because Google has to relearn and re-trust an entirely new domain.
- Platform or CMS migration: Moving from WordPress to Shopify, Drupal to Webflow, or a custom build to a SaaS platform. URL structures and templates almost always change.
- URL structure changes: Cleaning up messy URLs, flattening folder depth, or changing category paths. Risk lives entirely in redirect mapping.
- HTTP to HTTPS: Lower risk today since it is well understood, but still requires full redirects and updated internal links.
- Site consolidation or merger: Combining multiple sites or domains into one. Among the highest-risk migrations because of redirect complexity and content overlap.
- Site redesign: A new look on the same domain. Often underestimated because people assume "we are not moving anything." Template, content, and internal linking changes still move the SEO needle.
The lower the change, the lower the risk, but every type on this list has tanked someone's traffic when handled carelessly.
The 5 Stages of an SEO Website Migration
Every successful migration follows the same arc. You can rename the phases, but you cannot skip them.
- Plan and scope the migration so everyone knows the why, the when, and the who.
- Prepare by crawling the old site, mapping redirects, and benchmarking performance.
- Test everything on staging before it ever touches the live site.
- Launch with a tight day-of checklist and immediate validation.
- Monitor and recover for weeks afterward, not just the first 24 hours.
The full checklist below walks through each stage in order.
Stage 1: Plan and Scope the Migration
Skipping planning is how a "simple redesign" becomes a quarter of lost revenue. This stage costs you almost nothing and prevents almost everything.
Define Why You Are Migrating
Before anyone touches code, get the actual business reason in writing. Rebrand? Performance? Platform consolidation? The reason shapes the scope, the risk tolerance, and what success looks like. It also surfaces whether the migration is even necessary, or whether the same goal could be hit with a smaller change.
Pick the Right Timing
Migrate during a seasonal low, never during your peak. Pull at least 12 months of analytics and identify when traffic and revenue are at their lowest. If something goes wrong, and something usually does, you want it going wrong in your slowest week, not during your biggest sales push.
Avoid launching right before a holiday, a major campaign, or a product launch. And never migrate on a Friday. If it breaks, you want a full team available, not voicemails.
Assign Owners and a Project Plan
Migrations fail in the gaps between teams. Developers assume SEO has the redirects. SEO assumes dev is handling the sitemap. Nobody owns Search Console.
Build one project plan with named owners for every task and clear dependencies. Loop in paid media early, because their campaign URLs are about to change too. A migration is a cross-functional project that happens to involve SEO, not an SEO project that happens to involve other teams.
Forecast the Impact and Set Expectations
Leadership will ask "what happens to traffic?" Answer it before they ask. Model a realistic case and a worst case so a short post-launch dip does not trigger a panic. Setting the expectation that a temporary dip is normal is one of the most valuable things you can do in this phase.
Lock In Access Before You Need It
Get hands on every platform now, not the night before launch:
- Google Analytics and Google Search Console (old and, where relevant, new properties)
- Rank tracking tools
- Backlink data (Ahrefs, Semrush, or similar)
- Paid media accounts
- CMS, hosting, and DNS access
Chasing a password while redirects are failing in production is a special kind of pain. Avoid it.
Stage 2: Prepare and Map Everything
This is the stage that actually protects your rankings. Get it right and the rest is execution.
Crawl the Entire Existing Site
Run a full crawl of the current site with a tool like Screaming Frog, Moz, or Semrush. This crawl is your source of truth and your backup. It captures every URL, status code, title, heading, and internal link as they exist today. If something looks wrong post-launch, this is what you compare against.
Build a Complete URL Inventory
A crawl alone misses pages that are not internally linked but still earn traffic or links. Pull URLs from every source and combine them:
- Analytics: Every URL that received traffic in the last 12 months, by channel.
- Search Console: Every URL that earned impressions or clicks.
- Backlink tools: Every URL with external links pointing to it. These carry authority you cannot afford to lose.
- XML sitemaps: Everything you intended to be indexed.
- Paid and email: Landing pages used in active campaigns.
- Stakeholder list: Pages that matter to the business even if the data does not show it yet.
Deduplicate into one master URL sheet with status codes, traffic, and backlink data attached.
Create a Priority URL List
On large sites, one-to-one mapping of every URL may not be realistic. So rank them. A page is high priority if it meets criteria like:
- Meaningful organic traffic in the last 12 months
- Backlinks from quality domains
- Strong conversions or revenue
- Strategic importance flagged by stakeholders
Priority URLs get one-to-one redirects, no exceptions. Lower-value pages can use pattern-based or blanket rules. The point is to consciously decide, not discover the gaps after launch.
Map Your Redirects
Broken or missing redirects are the number one cause of traffic loss in a migration. Build a redirect map that pairs every old URL with the single most relevant new URL.
- Use 301 (permanent) redirects for migrated pages. This passes ranking signals to the new URL.
- Map to the closest equivalent page, never lazily to the homepage. Homepage redirects at scale are treated like soft 404s and waste the equity you are trying to save.
- Avoid redirect chains. Old A pointing to old B pointing to new C dilutes signals and slows crawling. Point everything directly to the final destination.
- Account for legacy redirects from past migrations so you do not rebuild a chain you already created years ago.
Benchmark Performance Before You Touch Anything
You cannot prove success or diagnose a problem without a "before" picture. Record, with dates:
- Priority keyword rankings, desktop and mobile
- Organic traffic and conversions by key page and template
- Indexed page count
- Core Web Vitals and load times by template
- A snapshot of your branded SERP and any AI Overview presence
- Status code distribution across the site
Annotate the planned launch date in analytics now so future-you knows exactly when the world changed.
Prep Everything Downstream of the URLs
Changing URLs breaks more than organic. Before launch, line up updates for:
- Paid media campaign destination URLs
- Email and automation links
- Third-party tools and integrations (CRM, review platforms, marketing automation)
- Analytics and tag manager configuration on the new site
Stage 3: Test on Staging Before It Goes Live
Staging is where you find the problems while they are still cheap to fix.
Lock the Staging Site Out of Google
This is the most common catastrophic migration mistake: launching a site that is still blocked from search engines, or letting the staging site get indexed and create duplicates.
Protect staging with password authentication, or at minimum a Disallow: / robots rule. Then, and this matters, make sure that block does not survive to production. Countless rankings have vanished because a noindex tag or disallow rule rode along into the live site. Put removing it on the launch checklist in writing.
Run a Full Technical Audit on Staging
Crawl the staging environment and hunt for issues before users and Googlebot ever see them:
- Broken links and unexpected 404s
- Missing or duplicated titles, meta descriptions, and H1s
- Missing or incorrect canonical tags
- Pages not rendering correctly, especially JavaScript-dependent content
- Missing structured data and schema markup
- Thin or accidentally dropped content versus the old site
- Internal links still pointing at old URLs
Verify Content and Structure Parity
A redesign often quietly strips content. If the old page ranked on 800 words of useful copy and the redesigned version has 200 words and a hero image, rankings will follow the content down. Confirm that valuable content, internal links, and on-page signals carried over. Migrate the SEO value, not just the visual design.
Test Redirects on Staging
Have developers stand up the redirect rules in staging and crawl the old URL list against them. Confirm:
- Old URLs return a single 301 to the correct new URL
- No redirect chains or loops
- WWW versus non-WWW resolves to one version
- Trailing slash behavior is consistent
- HTTP resolves to HTTPS
Stage 4: Launch Day Checklist
Launch day is execution, not exploration. Everything was decided already. Now you validate fast.
- Push redirects live and immediately crawl your priority URL list. Do not wait for a full-site crawl. Confirm your money pages redirect correctly within minutes, not hours.
- Check the production robots.txt and meta robots tags. Confirm there is no Disallow: / and no stray noindex. This is the single highest-leverage 60 seconds of the entire project.
- Submit the new XML sitemap in Google Search Console. If the domain changed, use the Change of Address tool on the old property and keep the old property verified.
- Validate analytics and tracking fired on the new site. Confirm GA, tag manager, and conversion tracking are live before you lose a day of data.
- Update paid, email, and affiliate URLs so campaigns do not drive paid clicks into 404s.
- Spot-check key templates manually for rendering, content, and internal links.
- Annotate the launch in analytics so every future report has the line in the sand.
Stage 5: Monitor, Measure, and Recover
The migration is not "done" at launch. The first eight weeks decide whether it actually succeeded.
Watch the First 72 Hours Closely
Re-crawl priority URLs daily for the first few days. Redirect rules that worked in staging sometimes break under production load or get overwritten by a later deployment. Watch Search Console for crawl errors, indexing drops, and coverage warnings, and fix them fast.
Expect a Dip, Then Hold Your Nerve
A temporary ranking and traffic dip after migration is normal. Google needs time to recrawl, reprocess redirects, and re-trust the new structure. A clean migration usually stabilizes within a few weeks to a couple of months. The mistake is panic-editing on day three and changing five more things, which only adds variables and makes diagnosis impossible.
There is a real line, though, between an expected dip and a genuine problem. Investigate immediately if you see redirects returning 404s or 302s, indexed pages collapsing, the staging block live in production, or priority keywords vanishing entirely rather than wobbling. Those are not "wait it out" situations.
Report Against Your Benchmarks
This is why you benchmarked. Compare post-launch performance to the pre-launch baseline:
- Priority keyword rankings, before versus after
- Organic traffic and conversions week over week and year over year
- Indexed URL count over time
- Status code distribution (watch 404s and 302s)
- Core Web Vitals and load times
- AI Overview and answer engine presence for priority queries
Do Not Forget Your AI and Answer Engine Visibility
This is where most migration checklists are still stuck in 2019. A migration does not just risk your blue-link rankings. It risks your presence in AI Overviews, ChatGPT, and other answer engines that pull from your content's structure and clarity.
If a redesign flattens your headings, strips your FAQ blocks, removes structured data, or buries the concise answers that AI systems extract, you can hold blue-link rankings and still lose AI visibility.
Track answer engine presence as a first-class migration metric, not an afterthought. For a deeper playbook on protecting and growing that visibility, our work in answer engine optimization goes well beyond the migration window.
The Biggest Website Migration Mistakes to Avoid
Most failed migrations die from the same short list of errors. Memorize it.
- Redirecting everything to the homepage: It looks like you handled redirects. Google reads it as soft 404s and you lose the equity anyway.
- Letting the staging block reach production: A single surviving noindex or Disallow: / can deindex the whole site.
- No benchmarks: Without a "before," you cannot tell a normal dip from a disaster, and you cannot prove the project worked.
- Redirect chains: Old to old to new dilutes signals and slows recrawling. Always point to the final URL.
- Dropping content in a redesign: New look, half the words, lost rankings. Visual upgrade, SEO downgrade.
- Migrating at peak season or on a Friday: Maximize the blast radius and minimize who is around to fix it. Do the opposite.
- Treating launch day as the finish line: The real work is the monitoring that follows.
How to Migrate Without Losing SEO: The Short Version
If you remember nothing else, remember this at-a-glance summary:
- Plan it, time it for a seasonal low, and assign clear owners.
- Crawl the old site and build a complete URL inventory.
- Map one-to-one 301 redirects for every priority URL, no chains, no homepage dumping.
- Benchmark rankings, traffic, indexing, and AI visibility before launch.
- Test everything on a search-blocked staging site, then confirm the block is gone in production.
- Launch, validate redirects and robots within minutes, submit the new sitemap.
- Monitor for eight weeks, expect a short dip, and only act on real signals.
A website migration is not where SEO goes to die. It is where careful SEO quietly proves its value. If your team is staring down a domain change, a replatform, or a full redesign, the difference between a smooth move and a six-month recovery is almost entirely in the preparation. And if you want to come out the other side stronger in AI-powered search, our AI SEO services are built for exactly that transition.
Frequently Asked Questions About SEO Website Migration
Will my website migration hurt SEO?
A poorly executed migration can significantly hurt SEO, while a carefully planned one usually has minimal lasting impact. A short dip in rankings and traffic immediately after launch is normal as search engines recrawl and reprocess your site. The lasting damage almost always comes from preventable mistakes like broken redirects, missing content, or a staging block left live in production.
How long does it take to recover from a website migration?
Most clean migrations stabilize within a few weeks to two or three months. Larger or higher-risk migrations, like domain changes or site mergers, can take longer. If performance is still declining after eight to twelve weeks with no signs of recovery, that points to an unresolved technical issue rather than a normal recovery curve.
What is the most important step in an SEO website migration?
One-to-one 301 redirect mapping for priority URLs is the single most important step. Broken or missing redirects are the leading cause of traffic loss during migration. Every old URL with value should point directly to its closest equivalent new URL, with no redirect chains and no mass redirects to the homepage.
Do I need to redirect old URLs after a website migration?
Yes. Any URL that changes needs a 301 redirect to its new equivalent so users and search engines reach the right page and ranking signals transfer. This applies to URL structure changes, domain changes, HTTPS migrations, and most redesigns. Skipping redirects is one of the fastest ways to lose rankings and backlinks.
What is the difference between a 301 and 302 redirect in a migration?
A 301 is a permanent redirect and is the correct choice for migrations because it passes ranking signals to the new URL. A 302 is a temporary redirect and tells search engines the move is not permanent, so it does not reliably transfer equity. Using 302s by mistake during a migration is a common and costly error.
Should I migrate my whole site at once or in phases?
It depends on size and risk. Smaller sites are usually safest moving all at once so the transition period is short. Very large or complex sites sometimes phase the migration by section to limit blast radius, but phasing adds its own coordination and redirect complexity. Whichever approach you choose, the redirect mapping and benchmarking requirements do not change.
Does a website redesign count as a migration?
Yes, if it changes URLs, templates, content, or site structure. Redesigns are frequently underestimated because the domain stays the same, but stripped content, changed internal linking, and altered URL paths can affect rankings just as much as a domain move. Treat a meaningful redesign with the same SEO rigor as any other migration.
Note: Website migrations are high-stakes projects where small oversights create outsized consequences. If you want a second set of expert eyes on your migration plan, PBJ Marketing's SEO team helps brands move platforms, domains, and designs without surrendering hard-won organic visibility.
