A website migration is one of the highest-risk events in the lifecycle of any online business. Whether you are moving to a new domain, restructuring your URL architecture, switching CMS platforms, or migrating from HTTP to HTTPS, a single oversight can wipe out years of accumulated SEO equity overnight. Studies show that poorly executed migrations can cause traffic drops of 20-80%, and recovery can take months. Digimau has managed hundreds of SEO migrations, and the difference between success and catastrophe comes down to one thing: meticulous planning and execution.
In 2026, website migrations are more complex than ever. With Google’s crawl budget becoming increasingly selective, JavaScript rendering requirements, and the growing importance of Core Web Vitals, there are more moving parts to manage. This guide walks you through every phase of a migration—from initial planning through post-launch monitoring—so you can execute your migration with confidence and preserve (or even grow) your organic search traffic.
—Table of Contents
Types of Website Migrations and SEO Risks
Website migrations come in many forms, each with its own set of SEO risks and considerations. Understanding which type of migration you are undertaking is the first step in planning an effective SEO strategy. The most common types include domain migrations, platform or CMS migrations, site structure migrations (URL changes), HTTP to HTTPS migrations, and design or template overhauls. Each type carries different levels of risk and requires specific mitigation strategies.
Domain migrations involve moving your website from one domain to another. This is often the riskiest type of migration because all URLs change and you lose the historical authority signals associated with your old domain. Digimau has seen domain migrations that were perfectly executed maintain 95%+ of their organic traffic, but we have also seen poorly executed migrations lose 60% or more of traffic permanently. The key to success is a flawless 1:1 redirect map and proactive communication with Google.
Platform migrations involve switching from one CMS or e-commerce platform to another (e.g., WordPress to Shopify, Magento to BigCommerce). These migrations are risky because URL structures often change, metadata may be lost, structured data may be removed, and page content may be altered by the new platform’s rendering engine. The SEO risks multiply when the new platform generates different HTML, which can affect how Google interprets your content.
Site structure migrations involve changing the URL structure or content hierarchy without changing domains or platforms. Examples include flattening a deep URL structure, consolidating pages, or reorganizing categories. While less risky than domain migrations, structure changes still require careful redirect planning to maintain link equity and rankings.
| Migration Type | Traffic Risk Level | Typical Recovery Time | Key SEO Action |
|---|---|---|---|
| Domain Migration | High | 4-12 weeks | 1:1 redirect map, GSC change of address |
| Platform/CMS Migration | High | 4-8 weeks | Preserve metadata, content, structured data |
| URL Structure Change | Medium | 2-6 weeks | 301 redirects, update internal links |
| HTTP to HTTPS | Low-Medium | 1-4 weeks | 301 redirects, update canonicals |
| Design Overhaul | Low-Medium | 2-4 weeks | Preserve content, Core Web Vitals check |
Pre-Migration Planning and Auditing
The success of any website migration is determined long before the actual switch happens. Pre-migration planning is where you identify risks, document your current state, and create a roadmap for a seamless transition. Skipping or rushing this phase is the single most common cause of post-migration traffic loss. Digimau typically spends 3-6 weeks on pre-migration planning for large enterprise sites.
The first step is to crawl and document your entire current site. Use Screaming Frog, Sitebulb, or DeepCrawl to capture a complete snapshot of your URL structure, metadata, heading tags, structured data, internal links, and canonical tags. Export this data and store it as your baseline. After migration, you will compare the new site against this baseline to ensure nothing was lost. This crawl should include every page type: product pages, category pages, blog posts, landing pages, and pagination.
Next, export all SEO-critical data from Google Search Console. This includes your performance data (impressions, clicks, CTR, position), sitemap status, crawl errors, manual actions, and indexed page count. Also export your top landing pages by organic traffic from Google Analytics 4. This data will be your post-migration benchmark—if traffic drops after migration, you need to know exactly where and by how much.
You should also inventory all external backlinks pointing to your current site. Use Ahrefs, Semrush, or Majestic to identify your most valuable backlink targets. After migration, these backlinks will need to be redirected to the corresponding new URLs. If high-value backlinks point to URLs that 404 after migration, you lose significant link equity. Create a plan to either redirect these URLs or reach out to linking sites to update their links.
Finally, staging thoroughly before launch. Set up the new site on a staging environment (blocked from indexing via robots.txt or basic auth) and perform a complete crawl. Compare every page against the baseline crawl to identify missing metadata, changed URLs, broken internal links, or missing content. This is your last chance to catch issues before they affect your live site.
Creating a Comprehensive 301 Redirect Map
The 301 redirect map is the single most important artifact in any website migration. It is a document—typically a spreadsheet—that maps every old URL to its corresponding new URL. The redirect map ensures that when Google and users visit old URLs, they are automatically forwarded to the correct new pages, preserving link equity and rankings. A single missed redirect can result in lost traffic, and hundreds of missed redirects can be catastrophic.
Start by listing every URL from your current site crawl. For each URL, identify the corresponding new URL on the migrated site. The goal should be a 1:1 redirect for every page—meaning each old URL maps to exactly one new URL that contains equivalent or better content. If a page no longer exists, redirect to the closest related page rather than allowing a 404. Digimau recommends redirecting to category pages or related content rather than to the homepage, which Google treats as a soft 404.
For large sites with thousands of URLs, create redirect rules using pattern matching (regular expressions) rather than mapping each URL individually. For example, if all blog posts are moving from /blog/post-name/ to /resources/post-name/, a single regex rule can handle thousands of URLs. However, always verify that pattern-based redirects land on valid pages by testing a sample of URLs.
Pay special attention to URL parameters and query strings. E-commerce sites often have faceted navigation that generates thousands of URL variations. Decide which parameter combinations need redirects and which should be canonicalized or blocked. Document your parameter handling strategy so it can be consistently implemented on the new site.
After the redirect map is complete, test it thoroughly on the staging environment. Use Screaming Frog to crawl the old URLs and verify they redirect correctly to the new URLs with a 301 status code. Check for redirect chains (old URL → intermediate URL → final URL), which should be eliminated in favor of direct redirects. Digimau has a zero-tolerance policy for redirect chains: every old URL must redirect directly to its final destination in a single hop.
Preserving On-Page SEO Elements
A successful migration preserves not just URLs and redirects, but every on-page SEO element that contributes to your search rankings. During a platform migration or redesign, it is common for metadata to be lost, heading tags to change, structured data to disappear, and content to be altered. Each of these changes can negatively impact your rankings, so meticulous attention to detail is required.
Title tags and meta descriptions must be carried over from the old site to the new site for every page. Export these from your pre-migration crawl and import them into the new CMS. Do not rely on the new platform’s auto-generated titles, which are typically generic and poorly optimized. Digimau has seen migrations where every title tag was replaced by the platform default, causing significant ranking drops until manually corrected.
Heading structure (H1, H2, H3) should be preserved on equivalent pages. The new site’s design may change how headings look visually, but the HTML structure should remain the same. Verify that each page has exactly one H1 and that subheadings follow a logical hierarchy. Changes in heading structure can confuse Google about the topical focus of each page.
Structured data (schema markup) is frequently lost during migrations, especially when switching CMS platforms. Inventory all schema types on your current site (FAQPage, Product, BreadcrumbList, Article, LocalBusiness, etc.) and ensure they are implemented on the new site. Test with Google’s Rich Results Test to verify that structured data is valid and complete.
Content equivalence is critical. The word count, keyword usage, and topical coverage of each page should be equivalent or better on the new site. If a page loses 50% of its content during migration, its rankings will suffer. Compare content between old and new pages during the staging phase and flag any significant discrepancies for remediation.
Technical SEO Checklist for Launch Day
Launch day is when all your preparation pays off—or falls apart. A technical SEO checklist ensures nothing is missed during the transition. Digimau follows a rigorous launch-day protocol that covers every critical SEO element, from redirects to server configurations.
Before launch: Finalize and upload the 301 redirect file to the server. Submit the new XML sitemap to Google Search Console. Remove the robots.txt block from staging. Configure canonical tags to point to the correct new URLs. Ensure HTTPS is properly configured with valid SSL certificates. Set up the new Google Search Console property if migrating domains.
At launch: Verify that old URLs redirect with 301 status codes (not 302 or 307). Confirm the homepage loads correctly. Test a sample of key landing pages. Check that the XML sitemap is accessible and contains only new URLs. Verify structured data using the Rich Results Test. Monitor server logs for crawl errors.
Immediately after launch: Submit the Change of Address tool in Google Search Console (for domain migrations). Request indexing for your most important pages. Monitor Google Search Console for new crawl errors. Check Google Analytics for traffic anomalies. Begin monitoring rankings for your top keywords.
For domain migrations specifically, use the Change of Address tool in Google Search Console. This tool signals to Google that your site has permanently moved to a new domain, accelerating the transfer of indexed pages and link equity. Combined with a flawless 1:1 redirect map, the Change of Address tool is the most effective way to communicate a domain change to Google.
Post-Migration Monitoring and Recovery
The first 2-4 weeks after a migration are critical. Expect a temporary fluctuation in rankings and traffic as Google processes the redirects and re-crawls your new site. Some volatility is normal, but sustained traffic drops indicate a problem that needs immediate attention. Digimau monitors migrated sites daily for the first two weeks, with detailed weekly reports for the first month.
Key metrics to monitor include: organic traffic (compare to pre-migration baseline), indexation count (ensure new pages are being indexed and old URLs are being de-indexed), crawl errors in Google Search Console, average position for target keywords, and Core Web Vitals scores. If any metric deviates significantly from baseline, investigate immediately.
Common post-migration issues include: missing redirects (old URLs returning 404), incorrect canonical tags pointing to old URLs, structured data errors, lost internal links, content that was not migrated, and server errors (500-level) on the new site. Address each issue as quickly as possible. The faster you fix post-migration issues, the faster Google will recover your rankings.
If traffic drops significantly and does not recover within 2-3 weeks, conduct a comprehensive post-migration audit. Compare the new site against your pre-migration baseline crawl to identify what changed. Common culprits include lost metadata, significantly reduced content, missing structured data, or redirect errors. Create a prioritized fix list and execute systematically.
Frequently Asked Questions
How long does it take to recover SEO traffic after a migration?
With a well-executed migration (proper 301 redirects, preserved metadata, updated sitemaps), most sites see traffic stabilize within 2-4 weeks. Domain migrations may take 4-12 weeks for full recovery. If traffic has not recovered after 4 weeks, conduct a comprehensive audit to identify issues. Sites with thousands of pages may take longer as Google re-crawls and re-indexes all new URLs.
What is a 301 redirect and why is it important for migrations?
A 301 redirect is an HTTP status code that permanently redirects one URL to another. It passes approximately 90-99% of link equity from the old URL to the new URL. During a migration, 301 redirects ensure that users and search engines visiting old URLs are forwarded to the correct new pages, preserving rankings and traffic. Without proper 301 redirects, old URLs return 404 errors, causing immediate traffic loss.
Should I use 301 or 302 redirects for a website migration?
Always use 301 (permanent) redirects for migrations. 302 (temporary) redirects do not pass link equity and signal to Google that the move is temporary. Using 302 redirects during a permanent migration can prevent Google from updating its index and transferring rankings to the new URLs. Every redirect in a migration should be a 301.
How do I notify Google about a domain migration?
Use the Change of Address tool in Google Search Console. Add and verify both your old and new domain properties in GSC, then use the Change of Address tool to signal the permanent move. Additionally, submit the new XML sitemap, ensure 301 redirects are in place, and update internal links and canonical tags to point to the new domain.
What are the most common migration mistakes?
The most common mistakes are: incomplete redirect maps (missing URLs), using 302 instead of 301 redirects, losing title tags and meta descriptions, not migrating structured data, creating redirect chains, forgetting to update internal links, not submitting the new XML sitemap, and not monitoring traffic post-launch. Each of these can cause significant traffic loss.
Can a website migration improve SEO performance?
Yes. While migrations are primarily about preserving existing SEO equity, a well-executed migration can actually improve performance. Benefits may include improved site speed (better Core Web Vitals), cleaner URL structure, improved mobile experience, better internal linking architecture, and a more crawlable site. Plan these improvements as part of your migration strategy to come out stronger.
How do I handle URL parameters during a migration?
Document all URL parameters from the old site and decide which need redirects, which should be canonicalized, and which should be blocked from crawling. Use Google Search Console’s URL Parameters tool (if still available) or robots.txt directives to manage parameter handling. Ensure the new platform generates consistent URL structures for faceted navigation.
Should I update my XML sitemap after a migration?
Yes, absolutely. Create a new XML sitemap containing only the new URLs and submit it to Google Search Console immediately after launch. Remove the old sitemap or update it to reflect the new URL structure. A clean, accurate sitemap helps Google discover and index your new pages faster, accelerating post-migration recovery.
What should I monitor after a website migration?
Monitor organic traffic, indexation count, crawl errors, keyword rankings, Core Web Vitals, and Google Search Console reports for at least 4-6 weeks post-migration. Compare metrics against your pre-migration baseline. Address any significant deviations immediately. Use Google Analytics 4 to track traffic by landing page and identify specific pages that lost traffic.
How do I preserve structured data during a migration?
Inventory all schema markup types on your old site (Product, FAQPage, BreadcrumbList, Article, etc.). Ensure the new site implements equivalent structured data on corresponding pages. Test with Google’s Rich Results Test to validate the markup. Missing structured data can result in the loss of rich results in SERPs, reducing visibility and CTR.
