Google re-crawls and re-indexes pages after a migration to understand what changed – so some ranking fluctuation is expected. Without a documented plan, you risk losing the backlink equity and organic traffic you've spent years building. Google treats migrated sites as partially "new," which means ranking fluctuations are normal – but preventable with the right planning.
Here's what to plan for: the documents and decisions that belong in your migration, the exact steps before, during, and after launch, and the mistakes that catch even seasoned teams off guard.
What is a website migration
A website migration is a step-by-step process to move your site to a new domain, host, platform, or structure without losing visitors or search engine rankings. The term covers everything from switching hosting providers to completely rebuilding on a new CMS.
Google treats a migrated site as partially "new." The search engine re-crawls pages to understand what changed, which means some ranking fluctuation is normal. Without a documented plan, though, you risk losing the traffic and backlink equity you've spent years building.
A solid migration plan protects what you've built while opening the door to better performance and cleaner architecture.
Types of website migrations
The type of migration determines your planning approach. Some are straightforward; others take months of preparation.
Replatform and CMS migrations
Moving from one content management system to another – WordPress to Webflow, for example – means adapting to different content structures and URL patterns. CMS architecture differences often require rethinking how pages are organized, which adds complexity to redirect mapping.
Redesign and restructure migrations
Changing your site's information architecture or navigation without necessarily switching platforms. This often accompanies a rebrand or a shift in how visitors move through your site.
Domain and URL migrations
Changing your domain name or restructuring URL patterns introduces significant redirect complexity. Every old URL pointing to your site – from backlinks to bookmarks – requires a new destination.
Hosting and server migrations
Moving to a new hosting provider or server infrastructure. Generally lower SEO risk if URLs remain unchanged, though performance improvements can positively affect rankings.
Protocol migrations from HTTP to HTTPS
Implementing SSL certificates and secure protocols. Most modern platforms handle this automatically, and it's now standard practice.
How a website migration affects SEO
Search engines treat a migrated site as partially unfamiliar. Google re-crawls and re-indexes pages, so ranking fluctuations during the transition period are normal – even expected.
The real damage comes from broken redirects, missing pages, and lost backlinks. Here's what's at risk:
- Indexation: Pages may temporarily disappear from search results while Google processes the changes
- Rankings: Keyword positions often fluctuate for two to four weeks, sometimes longer
- Backlink equity: Links pointing to old URLs lose their value if redirects fail
- Internal linking: Broken internal links hurt both user experience and crawl efficiency
Proper planning preserves this equity. The goal isn't to avoid all fluctuation – it's to minimize it and recover quickly.
What to include in a website migration plan
Before diving into the phases, here's what every migration plan covers:
- Content inventory and audit: A complete catalog of every page, asset, and URL on your current site
- URL mapping and redirect plan: A spreadsheet matching every old URL to its new destination
- Technical SEO checklist: Metadata, canonicals, robots.txt, sitemap, and structured data
- Stakeholder alignment and timeline: Sign-off from everyone involved, with clear milestones
- Rollback contingency: A documented plan to revert if critical issues emerge
- Post-launch monitoring protocol: What you'll track, how often, and what triggers action
Before you move
Most migration failures trace back to inadequate pre-migration work. This phase takes longer than the actual launch – and that's by design.
1. Set goals and success metrics
Define what success looks like before you start. Include both business goals (lead generation, conversions) and technical metrics (page speed, crawl efficiency, Core Web Vitals).
2. Capture a baseline of analytics and rankings
Document your current organic traffic, keyword rankings, top landing pages, and conversion rates. This becomes your benchmark for post-migration comparison. This also becomes your clearest signal for what's working after launch.
3. Build a content inventory and site audit
Crawl your entire site to catalog every URL, page title, meta description, and content asset. Identify which pages to migrate, which to consolidate, and which to retire.
4. Map old URLs to new URLs
Create a complete spreadsheet matching every old URL to its new destination. This document drives your redirect implementation and becomes your single source of truth.
5. Plan your 301 redirects
A 301 redirect is a permanent redirect that tells search engines the old URL has moved to a new location – Google confirms ranking signals pass across 301 redirects. Implement one for every URL change. Avoid redirect chains (old URL → intermediate URL → final URL) – each additional hop can dilute link equity. Preserve backlink equity by redirecting linked pages accurately.
6. Align stakeholders and lock the timeline
Get sign-off from marketing, development, content, and leadership. Establish a realistic timeline with clear milestones and a firm launch date. Scope creep kills migrations.
7. Document a rollback plan
Prepare a contingency to revert to the old site if critical issues emerge post-launch. Include hosting backup details and DNS reversion steps. Document who makes the call and under what conditions..
8. Build and lock down your staging site
Develop the new site in a staging environment – a private test server where you can build without affecting your live site. Block search engines from indexing staging via robots.txt or password protection. Duplicate content issues are real.
During the move
Execution day. Thoroughness here prevents post-launch firefighting.
1. Run a pre-launch technical SEO audit
Crawl the staging site to catch broken links, missing metadata, duplicate content, and crawl errors before going live. Tools like Screaming Frog or Sitebulb work well here.
2. Verify redirects, canonicals, robots.txt, and site configuration
Test your redirect mappings. Confirm canonical tags point to correct URLs. Ensure robots.txt allows crawling of production pages.
3. Update DNS and push the new site live
Point DNS to the new server. Reduce TTL (time to live) in advance to speed propagation – this controls how quickly the change reaches browsers worldwide.
4. Submit your XML sitemap to Google Search Console
Upload the new sitemap immediately after launch. Request indexing for priority pages. Google confirms sitemaps are especially helpful after a site move.
5. Confirm GA4 and conversion tracking
Verify that Google Analytics 4 and any conversion tracking (form submissions, purchases) fire correctly on the new site. Test before you celebrate.
After you move
Post-migration is an active monitoring phase, not a finish line. The first few weeks determine long-term SEO recovery.
1. Monitor crawl errors and indexation
Check Google Search Console daily for 404 errors, crawl anomalies, and indexation status. Address issues immediately – small problems compound quickly.
2. Track rankings, traffic, and conversions
Compare post-migration metrics against your pre-migration baseline. Expect some fluctuation, but watch for sustained drops that signal deeper issues.
3. Fix broken redirects and orphaned pages
Identify and repair any redirects that failed or pages that lost internal links during migration. Orphaned pages – pages with no internal links pointing to them – often get missed.
4. Update external backlinks and citations
Reach out to high-value referring domains and directories to update links pointing to old URLs. This is tedious but worthwhile for your most valuable backlinks.
5. Document the migration and sunset the old site
Create a migration log for future reference. Cancel old hosting only after confirming full functionality and indexation – give it at least 30 days.
Common website migration pitfalls and how to avoid them
Skipping the pre-migration baseline
Without documented benchmarks, you cannot measure success or diagnose problems. Always capture analytics before launch.
Forgetting redirects for deep pages and backlinks
Teams often redirect the homepage and top pages but miss blog posts, PDFs, deep links, and image assets that carry SEO value. Your URL map catches these.
Leaving staging sites indexable
If search engines index your staging environment, duplicate content issues arise. Password-protect or noindex staging until launch.
Breaking analytics on launch day
Misconfigured tracking means you fly blind during the most critical monitoring period. Test all tracking before and after launch.
Treating launch as the finish line
Migrations require weeks of post-launch monitoring and iteration. Budget time and resources for the aftermath.
How long a website migration takes
Timeline depends on site size, migration type, and team capacity. Planning typically takes longer than execution – and rushing pre-migration work leads to post-launch problems.
Migrating to Webflow without losing SEO equity
Webflow gives marketing teams control without heavy developer dependency. Native hosting, built-in SSL, and clean URL structures simplify protocol and hosting concerns.
Successful Webflow migrations require careful CMS architecture planning. Content models differ from WordPress or other platforms, so URL structures and page hierarchies often change. Redirect mapping becomes especially important.
Qontour builds Webflow migrations on Client-First methodology – clean and documented, with structured systems so your marketing team can ship new pages without coming back to us for every change. We own redirect mapping, CMS architecture, and post-migration monitoring, and we keep tracking Core Web Vitals and technical health through ongoing maintenance after launch – not just on day one.
Plan your migration with Qontour
Website migrations are high-stakes projects. The difference between a smooth transition and months of recovery often comes down to planning, documentation, and post-launch attention.
Qontour works with B2B companies in cybersecurity, deeptech, and SaaS to plan, execute, and monitor migrations that protect organic rankings, redirect equity, and technical performance – and set you up for better conversion on the other side. Our phased approach – Plan, Build, Launch, Maintain – keeps momentum while reducing risk.
Frequently asked questions about website migration plans
How much does a website migration cost?
Migration costs vary based on site size, complexity, and platform. Simple hosting changes cost far less than full CMS replatforms with redirect mapping, CMS architecture, and custom development. Qontour scopes each migration individually – no retainers, no hourly billing – so you know what's included before we start. Schedule a call to talk through your specific situation.
What are the seven common migration strategies?
The seven Rs – rehost, replatform, repurchase, refactor, retire, retain, relocate – come from cloud infrastructure planning but map usefully onto website decisions. For most B2B marketing sites, the relevant choices are replatform, refactor, or retire: moving to a better CMS, restructuring your existing one, or sunsetting pages that no longer serve you.
How do I migrate a website without losing SEO rankings?
Preserve rankings by documenting your baseline, implementing accurate 301 redirects for every URL, submitting updated sitemaps, and monitoring Google Search Console closely during the first weeks post-launch.
Do I need a staging site for a website migration?
A staging site lets you build, test, and QA the new site without affecting your live environment. It's essential for catching issues before they impact visitors or search engines.
When is the right time to start planning a website migration?
Begin planning as early as possible. The pre-migration phase typically requires more time than the actual launch, especially for content audits, URL mapping, and stakeholder alignment.
