SEO migration: changing site while reducing the risk of losing traffic
The plan comes before development, not after launch.
Every migration is a moment of risk because it forces Google to re-interpret the site: new URLs to discover, authority signals to transfer, indexing to rebuild. The margin for error is narrow and some mistakes are hard to correct afterwards. That is why SEO consulting treats the migration with a dedicated plan, anchored to theSEO audit and involved before the technical decisions have already been made.
The scopeSEO site migration: domain, CMS, platform and URLs
SEO migration is the set of activities that protects a site’s organic traffic when something structural changes: the domain, the protocol, the CMS or platform, the URL structure, the merging or splitting of several sites, a deep restyling. The core of the work is a complete, verified redirect map — built on the correct HTTP status codes — a controlled test environment and close monitoring after launch. Done well, the migration is almost invisible in the data; done badly, it produces traffic drops that can take months to recover.
When a company faces an SEO site migration, the technical migration project can include a domain change or a change of domain, a CMS change, a platform change, a hosting change or a migration from HTTP to HTTPS. The same scope covers HTTP-to-HTTPS migration, TLD changes, rebranding, redesign, content consolidation and merging of sites. Even an architecture restructuring, a URL structure change or other URL and technical modifications can alter the SEO value if they are not planned together with optimization and project continuity.
What an SEO migration is and what types exist
We speak of migration whenever the address at which a resource can be reached changes, or the way the site is built. The most frequent cases:
- Domain change (rebranding, acquisition, new TLD).
- Move to HTTPS or consolidation between versions with and without www.
- CMS or platform change (for example to WordPress or, for e-commerce, to PrestaShop).
- URL restructuring and of the information architecture.
- Merging several sites into one, or splitting a site into several properties.
- Deep restyling with a change of template, content and internal structure.
- Internationalization: introduction of language or country versions with hreflang.
The operational reference is the guidance in Google’s documentation on site moves.
Why migrations lose traffic
The most common causes of drops are almost always the same: missing or wrong redirects (302 instead of 301, redirect chains, redirects all pointing to the home page), new URLs not equivalent to the old ones in content and intent, loss of internal links, accidental crawl block left over from staging, structured data not carried over, sitemaps not updated. Each of these problems, on its own, can cost positions; combined, they produce a collapse.
THE PROJECT TIMELINE
WITHOUT A BENCHMARK, A DROP HAS NOTHING TO BE COMPARED WITH
The phases of an SEO migration
The migration planning starts from a technical audit and from technical checks shared between SEO, development and marketing. In this phase I define the technical activities, the risk indicators, the verification tools and the responsibilities: the goal is to protect organic traffic, SEO value and rankings, not simply to put a new version online.
Pre-migration: crawl and benchmark
You take a snapshot of the current state: a full crawl of all indexed URLs, a list of the pages that generate traffic and rankings, link profile, existing structured data, performance. It is the reference against which the site will be compared after launch.
1:1 redirect map
The redirect map establishes which redirect to use for every URL structure change and every URL modification. 301 redirects follow Google’s official procedure and help preserve rankings and signals when the destination is truly equivalent; chains, generic rules and redirects to the home page increase the risks. Every old URL is matched to the new URL that is most equivalent in content and intent. Pages with no direct counterpart are mapped to the most relevant page, not to the home page. The map is verified line by line.
Staging environment: verification
Staging also serves to validate the URL architecture and the technical restructuring: I check site performance, image weight reduction, code refinement and verification of the code still to be refined, canonicals, structured data and every optimization element before go-live. Before launch you check that the new site can be crawled and indexed, that titles, headings, canonicals and structured data are correct, that internal linking is consistent and that no block (robots.txt, noindex) meant only for the test environment has been left behind.
Launch
You publish in a low-traffic window, activate the redirects, update robots.txt and sitemaps, and notify Google Search Console of the change (for a domain change, with the dedicated tool).
Post-launch: close monitoring
The post-launch monitoring compares the results of a migration with the benchmark every day: organic traffic, visibility, loss of visibility, loss of traffic, rankings, visibility drops and visibility recovery. Results monitoring lets me protect ranking continuity and keep traffic, correcting deviations immediately instead of waiting for the drop to become structural.
My method for migrations
My clear method combines advanced tools, CMS experience and coordinated SEO management. Migration strategies are translated into a verifiable plan, with technical priorities, responsibilities and acceptance criteria: this way traffic protection and traffic retention become measurable activities, not generic promises.
Pre-migration audit and benchmark
Complete map of URLs, traffic and signals to preserve.
Migration plan
Architecture and destination URLs, redirect map, technical checklist, schedule.
Staging verification
Checks on crawling, indexability, on-page, structured data, internal links.
Go-live support
Activation of redirects, robots.txt, sitemap, notifications to search engines.
Post-launch monitoring
Comparison with the benchmark, quick correction of deviations.
Closing report
State of indexing, traffic recovery, residual actions.
A well-done migration is almost invisible in the data.— my SEO migration method
Checklist by phase
| Phase | Key checks |
|---|---|
| Pre-migration | Full crawl, list of URLs with traffic, link profile, structured data, performance |
| Preparation | 1:1 redirect map, destination URLs, canonicals, hreflang, sitemap plan |
| Staging | No residual noindex or block, correct on-page, consistent internal links, markup present |
| Go-live | 301 redirects active, robots.txt and sitemaps updated, Search Console notified |
| Post-launch | Indexing coverage, crawl errors, rankings and traffic against the benchmark |
Common SEO migration mistakes
A migration without best practices can produce ranking problems, migration errors, traffic drops, loss of rankings and visibility declines. The costliest planning errors and strategy errors are the ones that stay invisible until launch: that is why I first analyze migration risks and every possible risk of loss.
- 01
Redirects to the home page
Instead of to the page equivalent in content and intent.
- 02
Redirect chains
Old URL → intermediate → final: every hop disperses authority.
- 03
302 instead of 301
For moves that are in fact permanent.
- 04
Block left over from staging
A test robots.txt or noindex that survived the launch.
- 05
New URLs not equivalent
The destination doesn’t answer the same intent as the page it replaces.
- 06
Sitemaps and internal links not updated
They keep pointing to the old URLs even after go-live.
- 07
Involving SEO afterwards
When development and structure are already defined and changing them costs double.
E-commerce migration
In the move to a new platform, from WordPress to Shopify or to another solution, the platform update must preserve product pages, categories, filters, structured data and URLs. A platform change therefore requires a dedicated map, site performance tests and checks on orders and organic traffic.
On an e-commerce site the migration is more delicate because of the number of URLs and the volatility of the catalog: you must handle discontinued products, category pages that change structure, parameterized filter URLs, product structured data. The redirect map is larger and the post-launch monitoring longer. When the platform change is part of the project, the work integrates with website creation.
Migration and structured data
Title, headings, canonicals, hreflang and structured data must be carried over to the new site without regressions: a missing or inconsistent schema after the migration loses rich results and reduces the likelihood of being cited by answer engines. Staging verification always includes a markup check, page by template.
How long a migration lasts and who is involved
Duration depends on the size of the site and the type of change. For a showcase site of a few dozen pages, preparation generally takes one or two weeks, go-live a few hours, and close monitoring the following two to four weeks. For an e-commerce site or a portal with many thousands of URLs, building and verifying the redirect map alone can take weeks, and post-launch monitoring extends over several months, because Google reprocesses a large catalog over longer times.
A well-managed migration involves several roles in a coordinated way: development for implementing the redirects and configuring the new environment, systems administration for DNS, certificates and server-level rules, content to guarantee the equivalence of the destination pages, and SEO as the direction that holds the plan together, verifies staging and oversees the post-launch. The moment to involve SEO consulting is when architecture, URLs and platform are still under discussion: intervening after development almost always means redoing choices already implemented, with costs and delays.
International migration and hreflang
When the project spans several markets, TLD changes, rebranding and content consolidation must be assessed together with hreflang, canonicals and local signals. Merging sites or redesigning an international version requires a documented architecture restructuring, not a simple domain swap.
Introducing language or country versions is one of the most delicate migrations. The main risk is the duplication between similar versions — for example two variants of the same language for different markets — which confuses the crawler and disperses rankings. Handling it requires bidirectional, consistent hreflang annotations, a clear structure (subfolders, subdomains or dedicated domains, chosen based on the project), correct canonical URLs for each version and real localization of the content, not a simple translation. Here too the work starts from a pre-migration benchmark per language and ends with separate monitoring for each market.
Frequently asked questions about SEO migration
How do you do an SEO migration without losing traffic?+
You start from crawl, benchmark and 1:1 redirect map; then you verify staging, update the sitemap and monitor organic traffic after launch. There is no guarantee based on a single command: the result depends on the quality of the planning and the speed of correcting deviations.
What are the types of SEO migration?+
The most common cases are domain change, CMS change, platform change, move from HTTP to HTTPS, URL restructuring, site merging, redesign and international migration. Complexity depends on the number of URLs and the signals that must be preserved.
How do you check a site migration after go-live?+
You check indexing, redirects, crawl errors, canonicals, structured data, internal links, ranking, visibility and conversions. Comparison with the benchmark and results monitoring immediately bring out any ranking problem or loss of traffic.
What happens to backlinks after a domain change?+
External links keep pointing to the old URLs: 301 redirects transfer most of the value to the new address, but part of the signal may fade, and only if the old URLs respond with truly relevant redirects. The map must avoid chains and generic destinations; I also monitor the link profile, the most authoritative pages and references that need a manual update, and for the most important links it is worth contacting the source sites and asking for a direct update to the new URL.
How much does it cost to migrate a website?+
The cost depends on the number of URLs, CMS, e-commerce, markets, integrations and level of risk. Professional SEO consulting quantifies the work after the technical audit and defines activities, technical checks, launch support and post-launch monitoring.
How much traffic is lost during a migration?+
With a well-managed migration, a slight, temporary drop in the first weeks is normal, followed by recovery. Marked or prolonged drops almost always indicate a problem in the redirects, in indexability or in content equivalence.
How long does recovery take after launch?+
Google has to discover the new URLs, process the redirects and transfer the signals: usually from a few weeks to a couple of months for small sites, longer for e-commerce and complex portals.
Can I make several changes together (domain, CMS and URL structure)?+
It is possible but not advisable: the more variables change together, the harder it is to isolate the cause of any drop. When you can, it is better to proceed in steps.
Should 301 redirects be kept forever?+
They should be kept as long as external links and references to the old URLs exist — in practice for a long time, often indefinitely. Removing them too early generates 404s and loss of authority.
Is SEO needed even for a simple graphic restyling?+
If only colors and style change, the impact is minimal. If templates, content structure, URLs or internal linking change, it is for all intents and purposes a migration and must be handled as such.
When should SEO consulting be involved?+
As early as possible, while architecture, URLs and platform are still being decided. Involving it after development often means redoing choices already implemented.
Is it better to migrate in a low-traffic period?+
Yes. Choosing a reduced-traffic window limits the impact of any problems in the first hours and makes it easier to isolate deviations in the data. Commercial peak periods and the weeks around important business events should be avoided.
How do I know if the migration went well?+
When, within a few weeks for a small site and a few months for a large one, indexing, rankings and organic traffic return in line with the pre-migration benchmark or exceed it, with no persistent crawl errors and no structural drops on the pages that generated value.
The role of the pre-migration benchmark
The benchmark is the element that distinguishes a controlled migration from a migration in the dark. It consists of taking a snapshot, before touching anything, of everything the new site will have to preserve: the complete list of indexed URLs, which ones generate traffic and on which queries, the average position for the main keywords, the link profile with the most important domains, the structured data present by page type, performance. During post-launch monitoring every deviation is compared with this baseline: if a page that generated traffic disappears from the results, the benchmark immediately tells you which redirect to check; if the link profile changes, you know where you started from. Without a benchmark, a drop becomes hard to diagnose, because there is nothing to compare it with.
Request SEO migration consulting
I plan and follow the migration from pre-launch analysis to post-launch monitoring, with a verified redirect map and constant comparison with the benchmark. Insights from the blog: the guides on SEO.
To prepare for the migration
Blog guides on what is worth knowing before changing site.
About to change something?
An assessment of the risk and of the migration plan, with no commitment.
Request a first analysis