Site migration SEO is the process of preserving and protecting organic search rankings during major website changes — including domain changes, CMS switches, HTTPS migrations, URL restructures, or site redesigns. Without a proper migration plan, organic traffic losses of 20–80% are common.
Quick Answer
Site migration SEO is the process of preserving and protecting organic search rankings during major website changes — including domain changes, CMS switches, HTTPS migrations, URL restructures, or site redesigns. Without a proper migration plan, organic traffic losses of 20–80% are common.
Migration dip is normal — even perfect migrations see 10–20% temporary ranking decline; losses beyond that signal redirect or crawl issues
Redirect completeness is non-negotiable — every URL in the old crawl must have a corresponding 301 redirect; orphaned URLs leak permanent ranking equity
Monitor for 6 weeks post-launch — daily GSC crawl error checks and weekly ranking reviews catch issues before they compound into major traffic losses
Key Takeaways
Migration dip is normal — even perfect migrations see 10–20% temporary ranking decline; losses beyond that signal redirect or crawl issues
Redirect completeness is non-negotiable — every URL in the old crawl must have a corresponding 301 redirect; orphaned URLs leak permanent ranking equity
Monitor for 6 weeks post-launch — daily GSC crawl error checks and weekly ranking reviews catch issues before they compound into major traffic losses
How Site Migration SEO Works
A site migration is any change that affects a website's URL structure, domain, protocol, or technical platform in a way that could disrupt Google's ability to crawl, index, and rank existing pages. The most common migration types are: domain migrations (e.g., rebrand to a new .com), CMS migrations (e.g., moving from WordPress to Webflow), HTTPS migrations (HTTP to HTTPS), URL restructures (changing slug formats), and platform consolidations (merging multiple sites). Each type carries distinct SEO risks, but all share the same core requirement: every old URL must 301 redirect to the correct new URL.
Why Site Migration SEO Matters for B2B Marketing
The business impact of a botched migration can be severe and long-lasting. Google data shows that even well-executed migrations cause a temporary 10–20% traffic dip lasting 3–6 weeks as Google recrawls and re-indexes the new URLs. Poorly executed migrations — missing redirects, redirect chains, broken internal links — can cause 50–80% traffic losses that take 6–18 months to recover. For B2B companies where organic search drives significant pipeline, a migration gone wrong is a material revenue event.
Site Migration SEO: Best Practices & Strategic Application
A proper migration SEO checklist includes: crawling the old site before migration to capture all URLs, building a complete URL mapping document (old URL → new URL), implementing 301 redirects at the server level, updating the XML sitemap, updating internal links to point directly to new URLs (not through redirects), setting up Google Search Console for the new domain/protocol, and monitoring crawl errors and ranking changes daily for 4–6 weeks post-launch.
Agency Perspective: Site Migration SEO in Practice
The most expensive agency mistake in site migrations is launching without a complete redirect map. Development teams frequently focus on the new site's design and functionality while treating SEO redirects as an afterthought. MV3's migration protocol requires sign-off on a 100% complete redirect map — verified against Screaming Frog crawl data — before any migration goes live. We also maintain pre-migration ranking baselines in Ahrefs so we can measure recovery velocity and identify specific pages that require additional remediation.
Frequently Asked Questions: Site Migration SEO
Site migration SEO is the process of preserving and protecting organic search rankings during major website changes — including domain changes, CMS switches, HTTPS migrations, URL restructures, or site redesigns. Without a proper migration plan, organic traffic losses of 20–80% are common.
A well-executed migration with complete 301 redirects typically recovers to pre-migration ranking levels within 4–12 weeks. Migrations with redirect errors, missing pages, or significant content changes can take 6–18 months to fully recover. The recovery timeline correlates directly with crawl budget — larger sites with lower crawl frequency take longer for Google to re-index after changes.
HTTPS is now a baseline requirement — sites still on HTTP face a ranking disadvantage and Chrome security warnings. An HTTP-to-HTTPS migration done correctly (proper 301s, updated canonical tags, updated sitemaps, updated internal links) carries minimal long-term SEO risk and is net positive for both rankings and user trust.
Ideally, complete the migration first and allow rankings to stabilize (6–8 weeks) before beginning active SEO work. Starting a link-building or content campaign on a site mid-migration creates attribution confusion and can dilute the impact of both efforts. If the migration timeline is uncertain, a technical SEO audit can often yield quick wins on the existing site while migration planning proceeds.
MV3 Marketing helps B2B companies apply these strategies to drive measurable pipeline growth. Our team executes technical seo audit for technology, SaaS, and professional services companies.
ID used to identify users for 24 hours after last activity
24 hours
_gat
Used to monitor number of Google Analytics server requests when using Google Tag Manager
1 minute
_gac_
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
__utma
ID used to identify users and sessions
2 years after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
_ga
ID used to identify users
2 years
_gali
Used by Google Analytics to determine which links on a page are being clicked
