TL;DR: An SEO plan for website migration is a structured process for moving a website without losing the organic traffic and authority it has already earned. It covers three phases: pre-migration preparation (which accounts for the bulk of the work), launch-day execution, and post-migration monitoring over 90 or more days. In 2026, this plan must also account for AI search visibility across platforms like Google AI Overviews, ChatGPT, and Perplexity. Without a plan, expect 30 to 50 percent organic traffic loss that can take six months or longer to recover.
A website migration is one of the highest-stakes projects in digital marketing. Change your domain, switch your CMS, restructure your URLs, or move hosting providers, and you are essentially asking Google to re-evaluate everything it knows about your site. Do that without a plan and the consequences are predictable: rankings disappear, traffic craters, and revenue follows.
The good news is that these outcomes are preventable. An SEO plan for website migration gives you the framework to preserve what you have built and, in some cases, come out ahead.
This guide covers what the plan includes, how to execute each phase, and what has changed in 2026 now that AI search engines are part of the equation.
Talk to our team about website strategy, SEO, and migration planning.
What Is an SEO Plan for Website Migration?
An SEO plan for website migration is a documented strategy for moving a website, whether that means changing domains, switching platforms, restructuring URLs, upgrading to HTTPS, or redesigning the entire site, while protecting the organic search equity you have already built.
That equity includes rankings, indexed pages, backlinks, structured data, internal link authority, and increasingly, your citations in AI-generated search answers.
The plan itself is not a single checklist. It is a phased process that begins weeks or months before the migration goes live and continues for at least 90 days after launch. Every top-ranking guide on this topic follows the same three-phase structure: pre-migration, launch day, and post-migration monitoring. There is strong consensus on this because it works.
Why You Need a Plan Before Migrating
Joost de Valk, founder of Yoast, puts it bluntly: a successful migration is roughly 90% preparation and 10% execution. That ratio is worth remembering because it runs counter to how most organisations approach a website rebuild. The typical pattern is months of design and development, then a rushed launch where SEO becomes an afterthought.
The data on what happens when SEO gets excluded is stark:
9 out of 10 website migrations damage SEO in some measurable way.
60 to 80 percent of migrations show measurable traffic loss, and only about 10% end with improved rankings.
A poorly executed ecommerce migration can wipe out 20 to 40 percent of organic traffic, with recovery taking 6 to 12 months.
One study cited by Search Engine Journal found it took 523 days for a domain migration to recover, and 17% of sites in that study never recovered at all after 1,000 days.
These are not abstract SEO metrics. For a business generating leads or revenue through organic search, a 30% traffic drop translates directly to lost pipeline. If organic search drives €50,000 a month in qualified leads, a botched migration could cost €15,000 or more per month for half a year. That framing, connecting SEO performance to revenue, is what separates a technical checklist from a business protection strategy.
Migration Types and Their Risk Profiles
Not all migrations carry equal risk. Understanding where yours falls helps calibrate the level of preparation required.
Migration Type | Risk Level | Key Concerns |
|---|---|---|
HTTP to HTTPS | Medium | 301 redirects, canonical tag updates, mixed content |
Hosting change | Low to Medium | Site speed changes, server response times, downtime |
CMS replatform | High | URL structure changes, template/metadata loss, internal linking |
Domain change | High | Full URL mapping, 301 redirects, Google Change of Address tool, authority transfer |
Full redesign + replatform | Very High | Combines content, URL, template, and platform changes simultaneously |
A practitioner on SEJ’s migration webinar, Cody Gault, made an important point about combined migrations: “The more you change, the harder it is to diagnose what caused a drop. Keep the migration as simple and ‘clean’ as possible. Consider saving some changes for after the bulk of the migration.”
What an SEO Plan for Website Migration Includes
Phase 1: Pre-Migration Planning (4 to 8 Weeks Before Launch)
Pre-migration preparation accounts for 60 to 70 percent of SEO success in a migration. Skip this phase and no amount of post-launch firefighting will compensate.
Run a full site crawl and URL inventory. Use Screaming Frog, Google Search Console, and GA4, then cross-reference all three. No single tool catches every URL. Your goal is a complete list of every live page, its current URL, and its performance data.
Benchmark current performance. Export at least 12 months of Google Search Console data covering clicks, impressions, and average position. Crawl and export all live URLs with their page titles, meta descriptions, H1 headings, image alt text, and structured data markup. Document your internal linking structure. This baseline becomes your reference point for measuring post-migration impact.
Identify high-value pages. Not all pages matter equally. Sort by three criteria: organic traffic, number of backlinks, and conversion rate. Pages ranking in positions 1 through 10 for your target keywords need the most careful handling. These are the pages where a broken redirect or lost metadata costs real money.
Build a complete redirect map. This is the single most important deliverable in the entire plan. Map every old URL to its most relevant new URL, ideally one-to-one. Use 301 redirects for permanent moves, never 302 temporary redirects. Avoid redirect chains (old URL redirects to intermediate URL, which redirects to final URL). Test every redirect on staging before deploying to production.
In one documented SaaS migration, the team moved 14,200 URLs across a simultaneous domain change, WordPress-to-headless replatform, and complete URL restructure with zero percent organic traffic loss and 18% growth at eight weeks. The key? A six-week pre-migration phase and 1:1 redirects for all 14,200 URLs.
Preserve on-page SEO elements. Export your current title tags, meta descriptions, H1 headings, and structured data so they can be replicated exactly on the new site. Changing content during a migration is one of the most common and most damaging mistakes. As Cody Gault noted, “Changing content removes a formerly stable element. Google already needs to re-evaluate the site based on changes made during the migration.”
Fix existing issues first. Address broken links, crawl errors, duplicate content, and technical debt before the migration. Carrying SEO problems forward into a new site makes it nearly impossible to separate migration-related drops from pre-existing issues.
Understanding how structured content architecture connects to both SEO and AI discoverability is critical during this phase.
Phase 2: Launch Day Execution
The first 48 hours after migration determine long-term ranking recovery. This is not the time for improvisation.
Activate all 301 redirects. Confirm none of your developers substituted 302s or JavaScript-based redirects. Both are common mistakes that prevent authority transfer.
Remove staging restrictions. Check your robots.txt file and noindex tags to ensure nothing blocks search engine bots from crawling the new site. Staging environments almost always have crawl restrictions in place. Forgetting to remove them is one of the most frequent and most devastating launch-day errors.
Verify analytics tracking. Double-check that all tracking codes for Google Analytics, Google Tag Manager, and Google Search Console are installed correctly on the new site. If tracking breaks on launch day, you lose the ability to measure what is happening during the most critical window.
Submit a new sitemap. Submit an updated XML sitemap to Google Search Console to accelerate indexing of new URLs and surface crawl errors that were missed during migration testing.
Use the Change of Address tool (for domain moves). Google’s Change of Address tool in Google Search Console flags a domain change directly to Google and speeds up the recrawling process. This only applies to domain migrations, but when it applies, it matters significantly.
Phase 3: Post-Migration Monitoring (90+ Days)
Many teams treat launch day as the finish line. It is not. Post-migration monitoring must run for at least 90 days, and ideally longer for large or complex sites.
Monitor daily for the first two weeks, then weekly. Track indexed page counts in Google Search Console, crawl errors, Core Web Vitals, and organic traffic. Compare everything against your pre-migration baseline.
Hit Core Web Vitals thresholds. Your new site needs to meet or exceed Google’s performance benchmarks: Largest Contentful Paint under 2.5 seconds, Interaction to Next Paint under 200 milliseconds, and Cumulative Layout Shift under 0.1. Performance regressions are common after platform changes and can suppress rankings independently of any other migration issue.
Compare against your baseline relentlessly. Some volatility is normal. A well-executed migration typically shows around 10% or less traffic fluctuation for 4 to 8 weeks while Google recrawls the new site. Sites that follow a structured process typically cut full recovery to under 90 days. If you are seeing drops of 30% or more, something went wrong and the baseline data from Phase 1 is how you diagnose it.
Patrick Stox, Ahrefs’ technical SEO expert and moderator of r/TechSEO, offers a useful diagnostic framework: if you see a drop, it is likely related to redirects, something not being able to be crawled, something noindexed, changes to the content, changes to internal links, or something that changed related to technical SEO. Work through that list systematically.
Setting up commercial intelligence dashboards before the migration gives you the reporting infrastructure to catch problems early.
The 2026 Factor: AI Search Visibility and Migration
Here is what most migration guides still get wrong: they were written for a world where Google’s organic results were the only thing that mattered. In 2026, that world no longer exists.
An SE Ranking study of 1,000 US brand keywords found AI Overviews appearing on 82.5% of US brand searches, with the brand’s own website supplying 33.8% of all AI Overview citations. Even more striking, 62.2% of those cited pages did not rank in the organic top 10 for that search.
What this means for migration planning is significant. If a migration drops, merges, or restructures a product page or About page that Google was citing in an AI Overview, your brand’s AI visibility can change even when your traditional rankings look stable. You can run a flawless redirect map, keep every ranking intact, and still lose visibility in ChatGPT, Gemini, and Perplexity because those platforms read your site differently than Google does.
How to Protect AI Search Visibility During Migration
Export your current schema markup. This includes Organization schema, product schema, FAQ schema, and any entity-level structured data. This is the piece that protects your AI search visibility, and it is the piece almost every migration checklist skips entirely. As BrightEdge noted in their 2025 migration guide, you need to preserve your AI equity: the structured signals, schema, and associations that feed your presence in AI search results.
Record your AI search visibility baseline. Before migration, note whether you appear in Google AI Overviews for your key queries. Run the same set of prompts in ChatGPT, Perplexity, and Gemini. Save which of your URLs get cited. This gives you a comparison point that no traditional SEO tool currently provides.
Re-validate schema after launch. Structured data often breaks during migration, especially during CMS replatforms where templates change. Test every page type with Google’s Rich Results Test and Schema Markup Validator.
The upside is real. In one documented migration, Google clicks rose 2.9x, Bing clicks rose 2.0x, and appearances in Google’s AI answers rose 6.4x in the 19 days after the switch. A migration done right does not just preserve AI visibility; it can amplify it.
For a deeper look at how AI search is changing discoverability, explore our AI website audit framework.
Common Mistakes That Destroy SEO During Migration
Knowing what to do matters, but knowing what not to do matters just as much. These are the errors that show up repeatedly in practitioner discussions and post-mortem analyses.
Using 302 redirects instead of 301s. A 302 tells Google the move is temporary, so it does not transfer ranking authority. This single mistake can cause 30 to 50 percent traffic loss when old URLs effectively become dead ends for link equity.
JavaScript-based redirects. Search engines handle JavaScript redirects inconsistently. Server-side 301 redirects are the only reliable option.
Redirect chains and loops. Old URL points to an intermediate URL, which points to the final URL. Each hop in the chain dilutes authority and slows crawling. Map directly from old to final destination.
Not preserving metadata and structured data. New templates often ship with generic or missing title tags, meta descriptions, and schema markup. If these elements are not explicitly carried over, you are starting from scratch in Google’s evaluation.
Changing content at the same time as migrating. This introduces a second variable that makes it impossible to diagnose the cause of any ranking changes. Save content updates for after the migration stabilises.
Not involving SEO from the planning stage. Practical Ecommerce’s research found that most sites neglect to include an SEO professional in the planning, design, development, and launch phases, resulting in traffic loss that typically takes three to six months of rework to address.
Stopping monitoring too early. A practitioner on the DEV Community described opening Google Search Console a week after migration to find a 30% drop in organic traffic. Delayed monitoring means delayed diagnosis, which means longer recovery. Commit to 90 days minimum.
How Long Does SEO Recovery Take After Migration?
Recovery timeline depends almost entirely on preparation quality.
Execution Quality | Expected Traffic Impact | Recovery Timeline |
|---|---|---|
Well-planned, clean redirects | 10% or less temporary dip | 4 to 8 weeks |
Adequate planning, minor gaps | 10 to 30% loss in first month | 2 to 3 months |
Poor planning, redirect gaps | 30 to 50% or more loss | 6 to 12 months |
No SEO plan | 50%+ loss possible | 12+ months, some never recover |
For a mid-sized site, plan on 8 to 16 weeks total from initial planning through post-migration stabilisation. Larger sites with thousands of pages need longer, sometimes 3 to 6 months of planning alone before the migration even happens.
Joost de Valk offers a realistic timeline: one to three months to plan and scope, one month to one year to clean up the existing domain and prepare the new one, and six to twelve months for the migration to fully “come through” in search results.
The takeaway: if someone tells you a major website migration can be planned and executed in two weeks, they are describing the process that leads to the 523-day recovery statistic.
Building Your SEO Migration Plan: A Summary Checklist
Pre-migration (4 to 8 weeks before launch):
Complete site crawl and URL inventory using Screaming Frog, GSC, and GA4
Export 12 months of performance benchmarks
Identify and prioritise high-value pages
Build and test a 1:1 redirect map
Preserve all metadata, structured data, and schema markup
Record AI search visibility baseline (AI Overviews, ChatGPT, Perplexity, Gemini)
Fix existing SEO issues before migrating
Launch day:
Activate all 301 redirects and verify none are 302s or JavaScript-based
Remove staging robots.txt restrictions and noindex tags
Verify all analytics and tracking code
Submit new XML sitemap to Google Search Console
Use Change of Address tool for domain moves
Post-migration (90+ days):
Monitor daily for two weeks, then weekly
Track indexed pages, crawl errors, Core Web Vitals, and organic traffic
Compare all metrics against pre-migration baseline
Re-validate structured data and schema markup
Re-check AI search citations for key brand queries
A website migration is not just a technical project. It is a commercial decision that puts your organic revenue at risk. The difference between a migration that costs you six months of growth and one that preserves everything comes down to the quality of the plan.
Get in touch to discuss your migration with a team that connects SEO to business outcomes.
Frequently Asked Questions
What is an SEO plan for website migration?
An SEO plan for website migration is a structured, phased strategy for moving a website (changing domains, platforms, URLs, or hosting) while preserving its organic search rankings, backlink authority, structured data, and increasingly, its visibility in AI search engines. The plan covers benchmarking, redirect mapping, launch-day execution, and post-migration monitoring.
How long does it take to recover SEO after a website migration?
Recovery depends on preparation quality. A well-executed migration with clean 1:1 redirects typically sees minor fluctuations (10% or less) that resolve within 4 to 8 weeks. A poorly planned migration can lose 30 to 50 percent of traffic and take 6 to 12 months to recover. One study found an average recovery time of 523 days for domain migrations, and 17% of sites never fully recovered.
What is the biggest risk during a website migration?
Missing or incorrect redirects. When old URLs return 404 errors instead of redirecting to the correct new pages, you lose both the ranking authority of those pages and the value of every external link pointing to them. This single issue is responsible for the majority of catastrophic post-migration traffic drops.
Should I change my content during a website migration?
No, not if you can avoid it. Changing content during a migration introduces a second variable that makes it impossible to diagnose the cause of any ranking changes. Complete the migration first, let it stabilise for 8 to 12 weeks, and then make content changes in a separate phase.
Do I need to worry about AI search during a migration?
Yes. In 2026, AI Overviews appear on over 82% of US brand searches, and platforms like ChatGPT and Perplexity cite specific pages from your site. A migration that breaks structured data or removes pages being cited by AI engines can reduce your AI search visibility even when traditional rankings remain stable. Export and preserve your schema markup, and benchmark your AI citations before migrating.
How long should post-migration monitoring last?
At minimum 90 days. Monitor daily for the first two weeks, then shift to weekly reviews. Track indexed page counts, crawl errors, Core Web Vitals, and organic traffic. Compare everything against your pre-migration baseline to distinguish normal volatility from genuine problems.
What tools do I need for an SEO website migration?
The core toolkit includes Screaming Frog (for crawling and URL inventory), Google Search Console (for indexing data, performance benchmarks, and the Change of Address tool), Google Analytics 4 (for traffic and conversion baseline), and a backlink tool like Ahrefs or Semrush (for identifying high-authority pages). For AI search visibility, you will also need to manually test queries in ChatGPT, Perplexity, and Gemini before and after the migration.
When should SEO be involved in a migration project?
From the very beginning. SEO should be part of the planning, design, development, and launch phases. Most organisations bring SEO in after launch, when the damage is already done and recovery requires months of rework. The 90/10 rule applies: 90% of migration success is preparation, and that preparation requires SEO expertise from day one.