Website migration & SEO: how to move a website without losing rankings

An SEO migration is any significant change to a website that can affect how search engines crawl, interpret or rank its content.

While site migrations are often driven by business or technical needs, they carry inherent SEO risk because they disrupt the signals search engines rely on to rank pages.

In practice, most SEO migration failures don’t happen on launch day. They surface weeks or months later, when rankings don’t recover, legacy URLs keep getting crawled or redirect logic starts conflicting or overlapping. By the time teams notice, the original context has been lost.

Successful SEO migrations are not about avoiding change. They are about preserving identity. When URLs move, signals must move with them. Redirects are the mechanism that makes that possible.

Types of SEO migrations

Not all migrations carry the same level of risk. The impact on redirects, crawl behavior and search visibility depends heavily on what is actually changing. While the term website migration is often used broadly, it can describe several distinct scenarios involving platforms, infrastructure, URL structures or domain identity.

An SEO migration occurs when changes alter how search engines access, interpret or resolve URLs. This can include modifications to CMS platforms, site architecture, infrastructure, protocols or domains. Even when the content itself remains unchanged, differences in how URLs are generated, normalized or redirected can significantly affect indexing and rankings.

CMS migration

A CMS migration involves moving a site from one content management system to another, for example, from WordPress to Webflow, WordPress to HubSpot, or from a legacy CMS to a headless architecture.

The domain may remain the same, but URL structures, template routing, metadata handling and redirect logic often change. Different CMS platforms may generate URLs differently, enforce trailing slash rules differently or manage canonical tags in different ways.

CMS migrations frequently introduce redirect chains or missing redirects when legacy paths are not mapped precisely. Even when the domain stays intact, structural URL changes can affect internal linking and crawl paths.

The risk level is moderate to high, depending on how much the URL structure changes.

Cloud or infrastructure migration

A cloud migration moves infrastructure rather than content. Applications and data shift to new hosting environments, load balancers, CDNs or containerized platforms. In many cases, the public URLs do not change.

However, infrastructure migrations often alter how requests are processed. SSL termination may move, HTTP enforcement may occur at a different layer and routing logic may shift from application code to edge infrastructure.

Introducing a content delivery network (CDN) is a common example. CDNs can change where redirects, caching rules and SSL termination occur. While these platforms improve performance, they may also introduce additional redirect layers or modify header behavior, which can affect crawl paths and canonicalization.

Redirect issues during infrastructure migrations are usually caused by overlapping enforcement rules, caching behavior or header misconfiguration, rather than incorrect URL mappings.

The primary risk here is infrastructure-level redirect behavior changes.

Website migration (within the same domain)

A website migration typically involves structural or technical changes within the same domain. Examples include redesigning the site, reorganizing navigation or modifying URL patterns.

Reorganizing site architecture can alter how search engines interpret the hierarchy of the site. Examples include changing folder structures (such as /blog/post-name to /resources/post-name), removing categories from URLs or consolidating content sections.

Because the domain remains the same, search engines retain domain-level trust and historical authority. When redirects are implemented correctly, rankings often stabilize more quickly than in cross-domain moves.

The primary risk lies in URL restructuring, missing redirects and internal linking inconsistencies.

Protocol migration (HTTP to HTTPS)

Moving from HTTP to HTTPS changes the protocol across every URL on the site. Although often viewed as a technical upgrade, it is effectively a site-wide URL change.

If HTTPS enforcement, canonical tags and redirects are not implemented consistently, it can create redirect chains, duplicate content issues or indexing inconsistencies. Proper protocol migrations require site-wide redirects and consistent canonical signals to ensure search engines treat the HTTPS version as the authoritative version.

Domain migration

A domain migration moves content from one domain to another entirely, such as from oldbrand.com to newbrand.com.

From a search engine’s perspective, this is the most disruptive type of migration because the domain identity changes across all URLs simultaneously.

Without comprehensive 301 redirects, the new domain is treated as unrelated to the old one. Even with correct redirects, search engines must transfer signals and establish trust in the new domain, which often results in temporary ranking volatility.

Domain migrations demand the highest level of redirect accuracy and long-term management. Legacy URLs may continue receiving traffic and backlinks for years, making redirect durability critical.

WWW and apex domain migration

Switching between the www subdomain and the apex (root) domain is also considered a domain-level migration.

For example:

• www.example.com → example.com
• example.com → www.example.com

Although the content and domain name appear identical, search engines treat these as distinct hostnames. Every URL on the site changes, requiring consistent canonical signals, redirects and updated internal links.

If redirects, canonical tags, sitemaps and internal links are not aligned, search engines may treat both versions as separate sites, leading to duplicate content issues and diluted link equity.

Real-world example: Managing SEO continuity in a global migration

SEO migration risk becomes significantly more complex at the enterprise scale. In large, multi-region environments, redirect accuracy is not just a launch concern; it is a long-term infrastructure requirement.

During a global site migration with Berlitz, thousands of legacy URLs across multiple domains needed to be permanently redirected to new country-specific structures. These were not short-term campaign URLs. Many had accumulated years of backlinks, search visibility and regional authority.

The challenge was twofold:

1. Ensure every legacy URL resolves correctly on launch.
2. Maintain those redirects reliably across regions over time.

In global migrations, redirects cannot be treated as temporary fixes. They become structural components of the platform. Any degradation, expired rules, infrastructure drift, or redirect chains introduced later risks eroding accumulated SEO value and creating crawl inefficiencies.

By centralizing redirect management, Berlitz was able to maintain thousands of permanent redirects as stable infrastructure rather than scattered configuration rules. This preserved link equity, prevented legacy URLs from turning into crawl errors and ensured long-term continuity across domains and regions.

At enterprise scale, SEO migrations do not end at cutover. Redirect governance and monitoring are ongoing operational responsibilities.

What search engines experience during an SEO migration

From a search engine’s perspective, an SEO migration is not a single event, but an extended period of reprocessing. When URLs change, search engines continue to crawl legacy URLs, follow redirects and reassess how signals should transfer to new destinations over time. This process is gradual and often uneven across a site.

Even after a successful launch, search engines may request old URLs for weeks or months to confirm that redirect behavior is stable and consistent. This is expected behavior. If redirects change, break or introduce ambiguity during this period, confidence in the migration weakens.

Search engines also hedge rankings during migrations, temporarily reducing visibility while evaluating whether new URLs represent the same content and intent as the old ones. This is why correct redirects do not guarantee instant recovery and why short-term volatility is common.

Because evaluation happens over time, migrations that appear successful at launch can fail later. Redirect chains, overrides or missing mappings introduced post-launch are often detected only during subsequent crawls. From a search engine’s point of view, stability matters more than speed and migrations with predictable behavior recover more reliably.

Why SEO site migrations fail

SEO migrations fail when continuity is broken. Search engines need clear, consistent signals that content has moved, not disappeared. The most common failure patterns include:

Missing or incorrect redirects

When old URLs are not redirected or are redirected to the wrong destination, search engines treat them as removed pages. This results in lost rankings, broken backlinks and reduced trust. Even small gaps in redirect coverage can cause significant traffic drops if high-traffic pages are affected.

To mitigate this risk, many teams implement a catch-all redirect rule to handle any legacy URLs that may have been missed during mapping.

Redirect chains and loops

Chains (URL A → URL B → URL C) slow crawling and dilute signals, while loops prevent pages from resolving entirely. These issues often arise when legacy redirects are layered on top of new ones during a migration. Both patterns reduce crawl efficiency and can delay ranking stabilization.

Check out our articles for a more in-depth guide on how to fix redirect chains and loops.

Oversimplified redirect mappings

Redirecting large sections of a site to the homepage or a generic category page instead of mapping each old URL to its closest equivalent signals content loss rather than content movement. Search engines may interpret this as soft 404 behavior, meaning the original content is effectively gone, even if a redirect technically exists.

Make sure to redirect to an equivalent page when possible and don’t be afraid to have a 404 error if no equivalent exists.

Fragmented redirect ownership

Another common failure occurs when redirect logic is duplicated across multiple systems, such as the application, CMS, CDN, load balancer or web server. When multiple layers independently manage redirects, it becomes difficult to understand which rules actually control request behavior.

During migrations, this fragmented ownership often leads to conflicts, unintended overrides or duplicate redirect logic. A redirect implemented in one layer may be silently altered or bypassed by another, creating chains, loops or inconsistent behavior for search engines.

To avoid this, redirect rules should ideally be centralized or clearly documented, with ownership defined across teams. Keeping redirect logic consolidated makes migrations easier to audit, maintain and troubleshoot.

Redirect management is an ongoing process

Most of these failures are not caused by complexity, but by lack of visibility and ownership across teams.

Over the years, we’ve seen that some migrations appear successful at launch but fail later. Redirects added under pressure are rarely revisited, leading to chains, conflicts or silent overrides as new rules are introduced. Over time, this erodes crawl efficiency and weakens signal transfer without any single obvious breaking point. That’s why it’s important to treat reviewing redirects as part of your ongoing SEO strategy and not a set-and-forget item.

The role of redirects in SEO migrations

Redirects are the backbone of every successful SEO migration. They explicitly communicate that a URL has moved and instruct search engines on how to transfer signals such as authority, relevance and crawl history.

In a migration context, redirects must be accurate, intentional and maintained over time. The goal is not to create as many redirects as possible, but to ensure that every meaningful old URL resolves cleanly to its most relevant new destination. Redirect chains, loops and catch-all rules undermine this goal and introduce ambiguity.

Redirecting large sections of a site to the homepage is one of the most common migration mistakes. While it may reduce the number of redirects to manage, it removes topical relevance and creates soft 404s that search engines treat as content loss rather than movement.

Planning and executing an SEO migration

Step-by-step guide to planning and executing an SEO migration

SEO migrations succeed when they are treated as controlled infrastructure changes, not content updates. The following framework outlines how to reduce risk before, during and after launch.

Step 1: Inventory your existing URLs

Start by documenting the current state of your site.

Export:

• All indexable URLs.
• Top organic landing pages.
• High-backlink URLs.
• Sitemap URLs.
• Legacy or vanity URLs still receiving traffic.
• Non-HTML assets that matter (PDFs, gated resources, images with backlinks).

Pull data from:

• Google Search Console.
• Analytics.
• Crawlers.
• Server logs (if available).

This inventory becomes your source of truth. You cannot redirect what you do not know exists.

Step 2: Define the future URL structure

Before building redirects, finalize:

• New URL patterns.
• Canonical domain (www vs apex).
• HTTPS enforcement strategy.
• Trailing slash conventions.
• Folder hierarchy.
• Parameter handling rules.

Do not migrate while URL logic is still in flux. Structural indecision leads to redirect chains and rework.

Step 3: Create a one-to-one redirect map

Map every old URL to the most relevant new equivalent.

Avoid:

• Redirecting large sections to the homepage.
• Redirecting to loosely related category pages.
• Leaving low-traffic pages unmapped.

Each old URL should resolve in:

Old URL → Final URL (single hop)

Redirect chains should not exist at launch.

Step 4: Implement redirects in one authoritative layer

Decide where redirect logic lives:

• CDN.
• Load balancer.
• Server.
• Application.

Avoid duplicating logic across multiple layers.

Test in staging, but remember: staging environments rarely replicate full production routing behavior.

Step 5: Validate before launch

Before DNS cutover:

• Test URLs for redirect chains.
• Confirm correct status codes (301 for permanent changes).
• Verify canonical tags reflect new URLs.
• Confirm sitemap references only new URLs.
• Check internal links point directly to new destinations (not old ones).

Testing should simulate real requests, not just configuration review.

Step 6: Monitor immediately after launch

Once live, focus on:

• Crawl errors in Search Console.
• Index coverage changes.
• Redirect chains or loops.
• Latency spikes in redirect response times.
• Traffic to legacy URLs.

Expect volatility, but watch for patterns of broken continuity rather than normal reprocessing fluctuations.

Step 7: Continue monitoring for 4-8 weeks

SEO migrations are not finished at launch.

Search engines reprocess redirects gradually. During this period:

• Keep legacy redirects in place.
• Avoid structural changes.
• Monitor high-value URLs closely.
• Watch for unexpected redirect chains caused by post-launch tweaks.

Stability matters more than speed during this window.

Step 8: Be strategic about timing

Avoid stacking major changes together.

Risk increases when you combine:

• Domain migration.
• CMS change.
• URL restructuring.
• Design overhaul.
• Cloud infrastructure migration.

If possible, phase changes. For example:

1. Infrastructure migration.
2. Then URL restructuring.
3. Then design refresh.

Phased migrations typically stabilize faster, but they require disciplined redirect governance to prevent fragmentation between phases.

An SEO migration is fundamentally a continuity exercise.

If search engines can clearly understand that the content moved, not disappeared, recovery is faster. If redirect logic is imprecise or layered inconsistently, trust erodes and recovery time extends.

The difference between a smooth migration and a traffic collapse is almost always redirect precision and post-launch monitoring.

Measuring website migration success

Success is measured over time, not on launch day. Temporary volatility is common, especially for large or domain-level migrations. What matters is recovery and stability.

Healthy migrations show clean crawl paths, stable index coverage and gradual signal transfer to new URLs. Persistent crawl errors, redirect loops or soft 404s indicate unresolved continuity issues that can erode performance if left unaddressed.

In healthy migrations, long-tail traffic often recovers first, followed by category and head terms. Persistent losses beyond the expected reprocessing window usually indicate unresolved redirect or crawl issues rather than algorithmic re-evaluation.

SEO migrations as ongoing infrastructure

Many teams treat migrations as one-time projects, but their effects are long-lived. Old URLs continue to be requested by users, bots, bookmarks and external links long after launch. Redirects, therefore, need to be maintained as infrastructure, not looked at as temporary rules.

As seen above in the Berlitz case study, redirects are not a one-time task completed at launch. As infrastructure, content and routing rules evolve, redirects must be reviewed and monitored regularly to prevent silent regressions that erode SEO performance over time.

Treating redirects as temporary artifacts almost guarantees future issues. Each subsequent site change compounds the previous one, making the redirect layer more fragile and less transparent over time.

Frequently asked questions about website migrations

Do all website migrations affect SEO?

No. Only migrations that change URLs, responses or crawl paths affect SEO. Design updates or content changes that leave URLs and technical behavior unchanged are not considered SEO migrations.

Are redirects required for SEO migrations?

Yes. Redirects are the primary mechanism search engines use to understand that content has moved rather than disappeared. Without redirects, old URLs lose their accumulated signals and new URLs must be evaluated from scratch.

How long does an SEO migration take to stabilize?

Stabilization typically takes several weeks to a few months, depending on site size, crawl frequency and execution quality. Domain migrations often take longer than site migrations because search engines reassess domain identity as well as URLs.

Do SEO migrations always cause traffic drops?

Temporary volatility is common, especially for large or complex migrations. Sustained traffic loss usually indicates unresolved issues such as missing redirects, redirect chains, soft 404s or crawl inefficiencies rather than an unavoidable migration effect.

Why do some SEO migrations never recover?

Migrations fail to recover when continuity is permanently broken. Common causes include incomplete redirect coverage, many-to-one redirects that remove relevance, redirect logic that overlaps and conflicts over time or old URLs becoming inaccessible to crawlers.

How long should redirects stay in place after a migration?

In most cases, redirects should remain indefinitely. Old URLs continue to receive traffic from backlinks, bookmarks and crawlers long after a migration. Removing redirects too early can cause ranking losses and crawl errors months or even years later.

Can a failed SEO migration be reversed?

Partially. Restoring old URLs or fixing redirect logic can recover some lost signals, but recovery becomes harder the longer issues persist. The longer search engines treat old URLs as gone, the more historical signals are lost.

Is it safe to redirect everything to the homepage during a migration?

No. Redirecting large sections of a site to the homepage creates soft 404s and signals content loss rather than movement. Each meaningful URL should redirect to its most relevant equivalent to preserve intent and rankings. Using a 404 page is also acceptable if no equivalent page exists.

We recommend creating clear, custom 404 pages that explain the situation. Examples being, the page has been removed, the page has been replaced, the vanity URL has expired, the organization has rebranded, you’re being taken to a new site but that specific page no longer exists, etc.

Who should own an SEO migration?

Successful migrations require shared ownership. Engineering teams typically manage infrastructure and deployment, while SEO teams define URL strategy, redirect mappings and validation. Migrations fail when this ownership is unclear or fragmented.

By Sean Pasemko

SEO & Growth Marketing Specialist

Sean Pasemko is an SEO and growth marketer at urllo, where he works closely with SEO, IT and WebOps teams on redirect management, domain changes and site migrations.

His writing draws on practical experience analyzing redirect behavior, crawl efficiency and long-term site maintenance to help teams avoid common routing and performance issues.