
Why Website Migrations Kill Traffic (And How to Avoid It)
Website migrations are often driven by positive business changes: a new website, improved technology, a rebrand, international expansion, a domain change or the consolidation of multiple websites.
From a search perspective, however,
a migration introduces risk.
Search engines have already built an understanding of your existing website. URLs have been crawled and indexed, pages have accumulated search visibility, internal links establish relationships between content, and external websites may link to specific URLs.
A migration changes some
or all of those signals.
The objective of SEO migration planning is therefore not simply to redirect old pages to new ones. It is to understand what currently contributes to organic search performance, determine what will change during the migration and put controls in place to preserve those signals wherever possible.
For large, international or complex websites, this needs to begin well before launch.
What Is an SEO Migration?
An SEO migration is the process of managing significant website changes in a way that protects organic search visibility and allows search engines to understand the relationship between the old and new website.
SEO migration planning may be required when:
- moving to a new domain
- redesigning or rebuilding a website
- changing CMS or ecommerce platform
- changing URL structures
- consolidating multiple websites or domains
- merging brands or business units
- moving content between domains
- changing international or language architecture
- restructuring categories, products or services
- moving from subdomains to subfolders, or vice versa
Not every migration involves all of these changes. The greater the number of elements changing simultaneously, however, the more dependencies and potential failure points need to be managed.
Why Do Website Migrations Affect Rankings?
Search engines do not see a new website as simply a newer version of the old one.
They see URLs, content, links, canonical signals, status codes, structured data, internal relationships and numerous other technical and contextual signals.
During a migration, Google needs to crawl the changed website and process what has happened.
If an established page disappears and its replacement cannot be identified, some of the signals associated with the original URL can be lost.
The same applies when content is substantially changed, redirects point to irrelevant destinations, internal links are removed or important pages become difficult for search engines to discover.
This is why migration-related ranking losses are rarely caused by one isolated issue. They are often the cumulative result of multiple changes.
Start With a Complete Pre-Migration Benchmark
Before deciding how the new website should work, establish what you are trying to protect.
A pre-migration benchmark should document the current organic search position of the website and identify the URLs contributing to it.
Depending on the scale of the website, this can include:
- organic sessions and entrances
- Google Search Console clicks and impressions
- ranking keywords
- high-performing landing pages
- conversions and key events from organic search
- indexed URLs
- backlinks and externally linked URLs
- internal linking
- canonical URLs
- hreflang implementation
- structured data
- XML sitemaps
- crawlability and indexability
- Core Web Vitals and technical performance
This creates a baseline against which the migrated website can later be assessed.
It also prevents an important page from being removed simply because nobody involved in the redevelopment realised it generated organic search traffic.
Do Not Judge Page Importance by Traffic Alone
Traffic is important, but it should not be the only factor used when deciding whether a URL matters.
A page may receive relatively little traffic but rank strongly for a commercially important search, support another section through internal linking, attract valuable external links or serve a specific market.
Migration decisions should therefore consider the wider search value of each URL.
Crawl and Inventory the Existing Website
A complete crawl provides the technical foundation for migration planning.
For smaller websites this may be relatively straightforward. Enterprise websites can involve tens or hundreds of thousands of URLs spread across products, markets, languages, brands and legacy sections.
The inventory should establish what currently exists and identify issues such as:
- indexable URLs
- redirects
- canonicalised pages
- duplicate content
- broken links
- orphaned pages
- parameter URLs
- pagination
- international variants
- legacy URLs still receiving traffic or links
The purpose is not necessarily to recreate everything on the new website.
It is to make deliberate decisions about what happens to it.
Map Old URLs to Their New Destinations
Redirect mapping is one of the most important components of an SEO migration.
Every valuable existing URL should have a defined outcome.
Typically, this means one of four things:
- the URL remains unchanged
- the URL changes and redirects to an equivalent replacement
- the content is consolidated into another relevant page
- the page is intentionally retired
Where a replacement exists, the old URL should normally redirect to the most relevant equivalent page using a permanent server-side redirect.
Avoid redirecting large numbers of unrelated URLs to the homepage or a generic category simply because no direct replacement exists.
A redirect should help both users and search engines understand where the original content has moved.
Protect Content That Already Performs
A redesign often brings pressure to rewrite, shorten or reorganise content.
Some changes may be beneficial, but migration is a poor time to remove proven search signals without understanding their value.
Before changing an established page, review:
- the queries it ranks for
- its strongest sections
- headings and page structure
- internal links
- external links
- search intent
- supporting content
- metadata
- structured data
If a page already performs strongly, preserve the elements responsible for that performance unless there is a clear reason to change them.
Large-scale content changes can be introduced later once the migration has stabilised and their impact can be measured independently.
Preserve Internal Linking and Website Architecture
Redirects receive much of the attention during migration planning, but internal linking can be equally important.
Internal links help search engines discover pages and understand their relative importance and contextual relationships.
When navigation or architecture changes, check whether important pages will still receive appropriate internal links.
Pay particular attention to:
- primary navigation
- category and subcategory relationships
- product-to-category links
- related products or services
- contextual links within content
- breadcrumbs
- footer navigation
- international navigation
- links from high-authority pages
After launch, internal links should point directly to the final destination wherever possible rather than relying on redirects.
Account for International SEO
International migrations introduce additional dependencies.
Changes to country folders, language folders, domains or URL conventions can affect how search engines associate pages with particular markets.
Migration planning should review:
- hreflang annotations
- reciprocal hreflang relationships
- canonical tags
- country and language URLs
- XML sitemaps
- navigation between regional websites
- duplicate or near-duplicate market content
- redirects between old and new regional URLs
International architecture should be validated before launch rather than treated as a post-migration fix.
Build SEO Requirements Into Development
SEO should not sit at the end of the project
as a
launch checklist.
Requirements need to be incorporated into development specifications and QA.
These may include:
- URL structure
- redirect behaviour
- canonical implementation
- robots directives
- XML sitemap generation
- structured data
- pagination
- faceted navigation
- JavaScript rendering
- internal linking
- metadata templates
- hreflang
- HTTP status codes
- analytics and conversion tracking
Resolving these requirements during development is usually considerably easier than discovering them after the new website is live.
Crawl the Staging Website Before Launch
A staging crawl allows the proposed website to be compared against the existing website before users or search engines encounter it.
Check for:
- missing pages
- incorrect status codes
- broken internal links
- incorrect canonicals
- noindex directives
- blocked resources
- missing metadata
- heading changes
- missing structured data
- hreflang errors
- redirect logic
- unexpected URL changes
This is also the point at which the redirect map can be tested against the final URL structure.
Do not assume the development environment matches the original specification. Validate what has actually been built.
Create a Migration Launch Plan
A migration should have clearly defined responsibilities.
For complex projects, this may involve SEO, development, infrastructure, analytics, content, UX, product, legal and regional teams.
The launch plan should establish:
- who deploys redirects
- who removes staging restrictions
- who verifies analytics
- who submits XML sitemaps
- who performs the post-launch crawl
- who checks critical journeys
- who monitors Search Console
- who owns technical fixes
- how issues are prioritised and escalated
This becomes particularly important when teams are working across different systems, agencies, markets or time zones.
What Should Be Checked Immediately After Launch?
SEO migration work does not finish when the new website goes live.
The first post-launch checks should confirm that the implementation matches the approved migration plan.
Priority checks include:
- old URLs redirect correctly
- important new URLs return 200 status codes
- robots.txt is correct
- accidental noindex directives have been removed
- canonical tags reference the intended URLs
- XML sitemaps contain the correct URLs
- internal links point to live destinations
- analytics and conversion tracking work
- hreflang is implemented correctly
- structured data is present
- key user journeys function correctly
A complete crawl of the live website should then be compared with both the staging crawl and the original website.
Monitor More Than Overall Organic Traffic
Organic traffic is an important migration KPI, but monitoring only total traffic can conceal problems.
A migration should be monitored at several levels.
Compare performance by:
- individual URL
- website section
- page type
- product or service category
- country
- device
- keyword group
- branded versus non-branded searches
Google Search Console can be particularly useful for identifying changes in impressions, clicks and average position at URL and query level.
Some fluctuation following a migration can occur while search engines crawl and process the changes. What matters is being able to distinguish expected movement from an implementation problem requiring intervention.
Common SEO Migration Mistakes
Many migration problems can be traced back to planning rather than the migration itself.
Common examples include:
- involving SEO too late
- creating redirects after launch
- redirecting everything to the homepage
- removing valuable content without checking performance
- changing URLs unnecessarily
- launching with staging noindex directives
- breaking hreflang implementation
- changing content, architecture and URLs
- simultaneously without benchmarking
- failing to update internal links
- forgetting externally linked legacy URLs
- relying solely on an automated crawl
- failing to establish post-launch ownership
For enterprise migrations, another common problem is fragmented responsibility. SEO recommendations may be correct, but if ownership is unclear between developers, platform teams, agencies and internal stakeholders, implementation can still fail.
How Far in Advance Should SEO Migration Planning Begin?
There is no single timetable that applies to every website.
A small website changing a limited number of URLs may require relatively little preparation. A global website involving multiple domains, languages, platforms or thousands of products may require months of planning.
The important principle is that SEO migration planning should begin while architectural and technical decisions can still be influenced.
If SEO is introduced shortly before launch, many of the highest-risk decisions may already have been made.
Assess the Risk Before You Migrate
The level of SEO migration risk depends on what is changing, the size and complexity of the website, existing organic visibility and how well the migration is being governed.
Weston Dynamics’ free SEO Migration Risk Assessment can help identify potential areas of concern before launch and provides recommendations based on the migration being planned.
For complex migrations where organic search contributes materially to business performance, independent SEO migration governance can also provide oversight across planning, development, launch and post-launch monitoring.
The objective is not to prevent websites from changing.
It is to make sure those changes are understood, controlled and validated so that established search visibility is not unnecessarily placed at risk.
Speak to Weston Dynamics and let’s take a closer look at where your strategy is delivering value – and where it isn’t.



