Website migration is the process of making significant changes to a website’s technical infrastructure, moving it to a new domain, switching to a different content management system, restructuring its URL architecture, changing its hosting environment, or any combination of these, while preserving as much accumulated SEO equity, organic traffic, and search ranking as possible. A migration is distinguished from routine site maintenance by its scope and risk, migrations involve coordinated changes to multiple systems simultaneously and carry meaningful risk of SEO disruption if not executed correctly.

The term website migration encompasses several distinct scenarios, each with different technical requirements and risk profiles. A platform migration, moving from WordPress to a custom CMS, may change URL structures, template designs, and content organisation simultaneously. A domain migration: moving from one domain to another, primarily involves redirect configuration and Search Console updates. A protocol migration, moving from HTTP to HTTPS, requires SSL certificate provisioning and redirect configuration. A hosting migration, moving to different server infrastructure, primarily involves DNS configuration and server setup. Many migrations combine multiple changes, a company might simultaneously change domain, CMS platform, and URL structure as part of a complete site overhaul.

Website migrations are among the highest-risk SEO operations because they change multiple signals simultaneously, the domain, the URLs, the page templates, the content organisation, each of which independently affects how search engines understand and rank the site. When these changes are executed without comprehensive redirect coverage and careful signal management the result can be significant, lasting ranking declines. When executed correctly with thorough planning, comprehensive redirects, and careful monitoring migrations proceed with minimal disruption.

Types of website migrations

Different migration types have different technical requirements, understanding the specific type of migration being executed determines the appropriate preparation and execution approach.

Platform migrations: moving from one content management system to another. WordPress to Webflow, Drupal to WordPress, custom CMS to Contentful, each CMS generates URLs differently, structures content differently, and produces different HTML markup. Platform migrations frequently change URL structures, a WordPress blog at /blog/2024/01/post-title/ might become /blog/post-title/ on the new platform, requiring comprehensive redirect mapping from old URL patterns to new equivalents.

Platform migrations also change page templates, the HTML structure of every page changes simultaneously. Search engines must re-evaluate the new page structures, determining whether the same content signals are present in the new template. Poorly designed new templates that bury important content in JavaScript or fail to implement canonical tags correctly can cause indexation problems independent of any URL changes.

Domain migrations: moving from one domain to another without necessarily changing the platform or URL structure. When only the domain changes, paths remain identical, the redirect map is straightforward, every old-domain.com/path maps to new-domain.com/path. Domain migrations combined with URL restructuring require full URL-by-URL mapping.

HTTP to HTTPS migrations: upgrading from unencrypted HTTP to encrypted HTTPS. Every HTTP URL redirects to its HTTPS equivalent. Requires SSL certificate provisioning, HTTPS configuration on the server, and canonical tag updates. Among the simplest migration types when executed in isolation, but frequently bundled with other migrations as part of a comprehensive site overhaul.

URL structure migrations: changing the URL architecture without changing the domain or platform. Removing date segments from blog URLs, changing category structures, moving from parameter-based URLs to clean path URLs. URL structure migrations require redirect mapping for every affected URL, which may be the entire site if the URL format changes globally.

Hosting migrations: moving to different server infrastructure, changing hosting provider, moving to cloud hosting, migrating to containerised deployment. Hosting migrations primarily affect DNS configuration, changing A records to point to the new infrastructure. If the new hosting uses different web server software the redirect configuration may need to be converted,.htaccess rules for Apache to Nginx configuration for example.

Combined migrations: the most complex and highest-risk scenario. A company simultaneously rebranding, moving to a new CMS, restructuring URLs, and upgrading to HTTPS combines the complexity of all individual migration types. Combined migrations require exceptionally thorough planning, each change type introduces its own risks and the interactions between simultaneous changes can create unexpected complications.

Pre-migration planning

The planning phase is the most important phase of any website migration, thorough preparation determines whether the migration succeeds or causes lasting damage.

Complete site audit: crawl the existing site and document its current state before making any changes. The pre-migration audit establishes the baseline for measuring migration success and provides the raw data for building the redirect map.

URL inventory, every page, every asset, every resource. Response codes, identifying any existing 404 errors or redirect chains before migration. Page metadata, titles, descriptions, canonical tags, robots directives. Internal link structure, mapping which pages link to which other pages.

Performance baseline: document current SEO performance comprehensively:

Organic traffic by URL, identifying the highest-traffic pages requiring careful redirect treatment. Keyword rankings, current positions for all tracked queries. Crawl budget data, crawl frequency, crawl errors from Google Search Console. Backlink profile: complete backlink exports from multiple tools. Index coverage, total indexed pages, exclusion reasons, crawl anomalies.

This baseline data enables post-migration comparison, determining whether the migration is proceeding correctly or whether remediation is needed.

Building the redirect map: the most critical planning deliverable. The redirect map documents every old URL and its new destination. For platform migrations where URL structures change each URL requires individual mapping or pattern-based grouping. For domain-only migrations a path-preserving global redirect rule may handle the entire migration.

Redirect map quality directly determines migration success, unmapped URLs become 404 errors, incorrectly mapped URLs deliver poor user experiences, and imprecise destination selection wastes backlink equity.

New site validation: before deploying redirects verify that every redirect destination on the new site exists and returns 200 OK. Crawl the new site, or the staging environment, to identify any missing pages, broken internal links, or technical issues that should be resolved before launch.

Staging environment testing: replicate the complete migration in a staging environment before executing on production. Test redirect rules, verify canonical tags, check XML sitemaps, validate page rendering, and confirm SSL certificate functionality. Issues discovered in staging can be resolved without affecting live users or incurring SEO costs.

Migration execution

The execution phase implements the planned changes in a coordinated sequence, minimising the window during which both old and new sites are simultaneously accessible without clear canonical signals.

Pre-migration DNS TTL reduction: reduce DNS TTL for all affected domains to 300 seconds, 5 minutes, at least 24 hours before the migration window. Low TTL ensures DNS changes propagate quickly when made, minimising the window during which some users resolve to old infrastructure and others to new.

SSL certificate provisioning: all new domains and redirect source domains must have valid SSL certificates before migration. HTTPS visitors need valid certificates to complete TLS handshakes, an invalid or missing certificate makes the domain inaccessible to HTTPS visitors before they can receive redirect responses.

Redirect rule deployment: deploy the complete redirect map according to the planned configuration. Test each redirect, particularly for high-priority URLs, immediately after deployment. Verify that every redirect returns a 301 status code, that destinations are correct, and that no redirect chains are introduced.

Canonical tag updates: update all canonical tags throughout the new site to reference the new canonical URLs. No page on the new domain should have canonical tags pointing to the old domain, canonical tags should be self-referencing or point to canonical pages on the new domain.

XML sitemap updates: generate new XML sitemaps containing only the new canonical URLs. Submit updated sitemaps to Google Search Console and Bing Webmaster Tools immediately after migration launch.

Google Search Console configuration: add all new domains as verified properties in Google Search Console. Submit new sitemaps. Use the Change of Address tool for domain migrations, explicitly notifying Google of the domain change accelerates index update processing.

Post-migration monitoring

Intensive monitoring in the weeks following migration identifies problems before they cause lasting damage.

Traffic monitoring: compare post-migration organic traffic against the pre-migration baseline. Overall traffic decline immediately after migration is normal, the index is updating from old to new URLs. Severe or persistent traffic decline indicates migration problems requiring investigation. Monitor traffic at the URL level, specific pages experiencing disproportionate decline may have misconfigured redirects or missing destination pages.

Index transition monitoring: track indexed URL counts for both old and new domains through Google Search Console. A healthy migration shows old domain indexation decreasing, as Googlebot processes redirect signals and de-indexes old URLs, and new domain indexation increasing, as new URLs are crawled and indexed. Stalled transitions indicate problems with redirect processing or canonical signal clarity.

Ranking monitoring: track keyword rankings throughout the migration period. Significant ranking drops for specific queries that do not recover within 4-6 weeks may indicate that the pages ranking for those queries were not correctly redirected to equivalent new domain pages.

Crawl error monitoring: Google Search Console Coverage reports show URLs returning errors, 404s on the new domain indicate missing redirect destinations or incorrectly mapped redirects. 404 errors on old domain URLs that should be redirecting indicate broken redirect configurations.

Server log analysis: analysing web server logs for both old and new domains provides detailed visibility into how Googlebot is processing the migration. Googlebot requests to old domain URLs confirm that redirects are being crawled. Googlebot requests to new domain URLs confirm that redirect destinations are being discovered and crawled.

Content migrations alongside URL migrations

Website migrations often involve migrating content from one platform to another, a content dimension that is separate from but interacts with the URL migration.

Content parity verification: every page that exists on the old site should have its content present on the new site before redirects are deployed. Content parity ensures redirect destinations serve equivalent content, users who follow redirects arrive at pages that satisfy their original intent.

Content quality improvements: migration is an opportunity to improve content quality, fixing outdated information, improving thin content, consolidating duplicate content. However content improvements should be incremental, making many simultaneous content changes alongside structural changes makes it difficult to isolate the cause of any post-migration performance changes.

Duplicate content prevention: if both old and new sites are temporarily accessible simultaneously search engines may index both, creating duplicate content. Clear canonical signals on the new site, canonical tags pointing to new domain URLs, and rapid deployment of redirects on the old domain minimise the duplicate content window.

Common website migration mistakes

Insufficient pre-migration testing: not thoroughly testing redirect configurations in a staging environment before production deployment. Errors discovered after production launch affect live users and may be difficult to roll back cleanly.

Deploying redirects before new site is ready: redirecting old URLs to new domain destinations before the new site content is in place. Visitors and crawlers encounter 404 errors at redirect destinations, wasting backlink equity and creating poor user experiences.

Missing high-value page redirects: failing to map pages with significant backlink equity to relevant new domain pages. Even a small number of missed high-value pages can represent substantial equity loss.

Temporary redirects for permanent migrations: using 302 redirects rather than 301 for permanent migrations. Old URLs remain indexed indefinitely and equity does not transfer to new URLs.

Removing old domain redirects prematurely: allowing old domain registrations to lapse or removing redirect configurations before all backlinks have been updated. Old domain backlink equity is permanently lost when redirects are removed.

Not using Google Search Console Change of Address: skipping the Change of Address tool notification for domain migrations. The tool significantly accelerates Google’s processing of migration signals, skipping it extends the disruption period unnecessarily.