Site migration

On this page 7

A site migration is a planned, large-scale change to a website’s domain, URLs, platform, structure, protocol or hosting that can alter how search engines discover, crawl, index and rank its pages. In technical SEO, the term covers any change big enough to put accumulated organic visibility at risk, from moving HTTP to HTTPS to merging several domains into one.

The core challenge is continuity: search engines have stored signals such as links, relevance and crawl history against the old URLs, and a migration succeeds only when those signals are transferred to the new URLs quickly and completely. A well-run migration usually causes a temporary fluctuation of a few weeks; a poorly run one can cause losses that last for months.

How a site migration transfers search signals

A site migration transfers search signals by mapping every valuable old URL to its closest new equivalent and telling search engines about the change through permanent redirects, updated canonical tags, internal links and sitemaps. Search engines then recrawl the old URLs, follow the redirects and gradually consolidate ranking signals on the destinations.

The central artifact is the redirect map, a one-to-one list of old and new addresses. A 301 redirect signals a permanent move and is the standard choice; a 302 redirect signals a temporary move and should not be used for a migration intended to last. Search engines can treat long-standing 302 redirects as permanent, but relying on that inference adds unnecessary uncertainty.

Signal transfer is not instant. Large sites with millions of URLs may need several weeks or months before most redirected addresses are recrawled, because crawl frequency depends on page importance and crawl capacity. During that period, old and new URLs may appear side by side in search results.

The table below lists the main mechanisms that carry signals from the old site to the new one.

MechanismWhat it tells search enginesTypical failure
Server-side 301 redirectThe old URL has moved permanentlyChains, loops or redirects to the homepage
Canonical tagWhich URL is the preferred versionCanonicals still pointing at old URLs
Internal linksWhich URLs the site itself considers currentNavigation still linking through redirects
XML sitemapWhich new URLs should be crawledSitemap listing old or non-indexable URLs
Change of address toolA whole domain has moved to another domainUsed before redirects are live
Mechanisms that carry signals during a migration

Types of site migration and their risk levels

Site migrations differ mainly in how many URLs change and how much of the content, template and technology changes at the same time. The more variables change together, the harder it becomes to diagnose a traffic drop after launch.

The following table compares common migration types by scope and relative risk.

Migration typeWhat changesRelative SEO risk
Protocol migrationHTTP to HTTPS, same URLs otherwiseLow
Hosting or server moveInfrastructure only, URLs unchangedLow to medium
Domain migrationNew domain or subdomain, paths often unchangedMedium
URL restructuringPaths, folders or URL structureMedium to high
Platform migrationCMS or ecommerce engine, often templates and URLsHigh
Site merger or splitContent consolidated or separated across domainsHigh
Redesign with content changesTemplates, copy, site architecture and internal linkingHigh
Common migration types compared

A frequent and costly pattern is the combined migration, in which a team changes domain, platform and design in one release. Experienced practitioners prefer to separate changes into phases where the business allows it, so that each effect can be measured on its own.

Planning and executing the migration

Successful migrations follow a structured process with clear owners, a staging environment and defined rollback criteria. The work before launch usually takes far longer than the launch itself.

  1. Crawl the existing site and export all indexable URLs, plus URLs that receive backlinks or organic traffic.
  2. Benchmark rankings, organic sessions, conversions and index coverage for comparison after launch.
  3. Build the redirect map, matching each old URL to the most relevant new URL rather than to a generic page.
  4. Test the new site on a protected staging server that is blocked from indexing by authentication.
  5. Launch, verify redirects at scale, submit new sitemaps and monitor server logs for crawl behavior.
  6. Keep redirects in place for at least one year, and preferably permanently, because external links continue to point at old URLs.

Timing matters as well. Launching during a seasonal peak, just before a holiday or on a Friday leaves little capacity to fix problems. Teams that have engineering support available for several days after launch recover faster from the inevitable surprises.

Measuring the outcome after launch

The outcome of a site migration is measured by comparing post-launch metrics against the pre-launch benchmark, segmented by page type, so that a loss in one template is not hidden by stable totals elsewhere.

The table below shows which signals to monitor and what each one reveals.

SignalWhere to observe itWhat a problem looks like
Organic clicks and impressionsSearch performance reportsSustained decline beyond four to six weeks
Indexed pagesIndex coverage reportsNew URLs excluded or old URLs lingering
Crawl activityServer logsBots stuck on redirects or error pages
Status codesFull site crawlRising 404 or 5xx responses
Rankings for key queriesRank trackingPositions lost on high-value pages
Post-migration monitoring checklist

A small dip followed by recovery within two to six weeks is common for domain and URL changes. A drop that deepens over time usually points to a technical defect rather than normal reprocessing and should be investigated immediately.

Common mistakes and how to avoid them

Most migration failures come from a small set of repeatable errors, and nearly all of them can be detected on staging or within hours of launch with a crawler.

MistakeConsequencePrevention
Redirecting everything to the homepageTreated as soft 404s, relevance lostMap each URL to its closest equivalent
Leaving noindex or robots blocksNew site disappears from searchRemove staging restrictions at launch
Redirect chainsSlower crawling and diluted signalsPoint old URLs straight to final targets
Dropping content during redesignRankings lost for removed topicsAudit content before deleting pages
Ignoring hreflang and canonicalsWrong language or duplicate versions indexedUpdate all annotations to new URLs
Frequent migration errors

Another widespread misconception is that redirects alone guarantee identical rankings. When content, internal linking or page experience change, search engines reassess the pages, and rankings can move up or down on their own merit.

A non-technical view

Think of a site migration as moving a shop to a new address. Regular customers and delivery drivers know the old location, so the owner leaves a clear forwarding notice on the old door and updates every map listing.

Search engines work the same way. If each old page points clearly to its new home, the website keeps most of its visitors. If the notices are missing or point to the wrong place, people get lost and the website can lose traffic for months.

A concrete example

A mid-sized online retailer with about 40,000 product and category URLs moves from an aging ecommerce platform to a new one that uses a different URL format. The SEO team crawls the old site, combines the crawl with analytics and backlink data, and builds a redirect map that sends every product, category and article to its direct equivalent.

On staging, a crawler finds 1,200 redirect chains and a forgotten noindex tag on category templates, which the developers fix before launch. The team launches on a Tuesday in a quiet sales month, submits new sitemaps and watches server logs daily.

Organic clicks fall by roughly 8 percent in the first two weeks as search engines reprocess the URLs, then return to the benchmark by week five. Pages that were improved during the move even gain positions, and the retailer avoids the long-term traffic loss that often follows rushed platform changes.