Website migration means moving a site to a new domain, a new CMS, a new protocol (HTTPS), or a new URL structure. The main risk of any migration is a collapse in rankings and organic traffic if the search engine loses the old pages and doesn’t connect them to the new ones. An accurate 301 redirect map, preserving structure and content, and monitoring indexing before and after the move keep losses to a minimum.
Key points in 30 seconds
- A migration without a plan almost always causes a temporary dip of 10–30%; a well-run move keeps it to a minimum, and traffic recovers in 2–8 weeks.
- The core of a safe migration is an “old URL → new URL” redirect map with permanent 301 redirects.
- Before the move, you must have: a full list of URLs, a backup, and a snapshot of rankings and traffic as a baseline.
- After launch, check redirects, indexing, Search Console, speed, and broken links.
- A sharp drop after the move is a signal for urgent diagnostics, not a reason to wait a month.
What website migration is and why traffic drops
Migration means any large-scale change that affects page addresses or how they’re served to the search engine. That includes changing the domain, moving from http to https, a redesign that changes the layout and URLs, switching CMS or platform, merging several sites into one, or, conversely, moving a section to a separate subdomain.
Traffic doesn’t drop because of the “move” itself, but because Google temporarily loses the connection between the old and new versions. If the bot visits an old address and gets a 404 error instead of a proper redirect, the page drops out of the index along with all its accumulated signals: link equity, history, user behavior signals. The more such breaks there are, the deeper the dip.
A small, temporary fluctuation in rankings during a migration is considered normal: Google recrawls the site and recalculates signals. The SEO’s job is to keep this fluctuation minimal and short, not to heroically pull the site out of a hole a month after the move.
Types of migrations and their risks
Different kinds of migrations carry different threats. Knowing the type helps you close its weak spot in advance.
| Migration type | What changes | Main risk |
| Domain change | Domain name | Loss of link equity due to wrong redirects |
| Move to HTTPS | Protocol http → https | http/https duplicates, mixed content |
| Redesign | Design, layout, often URLs | Lost content and changed URLs without redirects |
| CMS/platform change | Engine, URL structure | Mass address changes, lost metadata |
| URL structure change | Friendly URLs, nesting | Broken internal linking |
| Merging/splitting sites | Number of domains | Cannibalization or diluted topic focus |
Migration checklist by stage
Stage 1. Preparation (before the move)
Collect a full list of current URLs: export it from Search Console, the XML sitemap, a crawler (Screaming Frog, Netpeak Spider), and your analytics, then merge the sources and remove duplicates. Record a baseline: a snapshot of rankings for your keywords, traffic by section, a list of the most visited and most linked-to pages. Make a full backup of the old site. Build a redirect map (more on it below).
Stage 2. Transfer and setup
Deploy the new version in a staging environment closed to indexing with Basic authentication, not just robots.txt. Transfer content and meta tags one to one: title, description, H1, alt, structured data. Keep the heading structure and internal linking. Set up 301 redirects according to the map. Prepare a new XML sitemap and robots.txt.
Stage 3. Launch
Pick the time with the least traffic. Open the site for indexing (remove the blocks). Check that every old URL returns a 301 to the correct new address. Submit the new sitemap in Search Console; for a domain change, use the Change of Address tool. Update canonical, hreflang, and the sitemap.
Stage 4. Post-launch monitoring
In the first days, check the indexing and coverage reports in Search Console daily, and watch for crawl errors, a rise in 404s, and speed. For 2–8 weeks, track rankings and traffic against the recorded baseline. Gradually bring back pages that dropped out.
The redirect map: the heart of a safe migration
A redirect map is an “old URL → new URL” mapping table used to set up permanent redirects. It’s what passes the old page’s accumulated equity to the new one and tells Google that the content has moved for good.
For a move, you almost always use a 301 redirect (permanent), not a 302 (temporary): a 301 passes link signals and replaces the old address in the index. For more on the difference between 301 and 302 and how to set them up, see our article on technical SEO: robots.txt, sitemap, and canonicals.
Rules for a working map: each old URL points to the closest matching new page, not everything in bulk to the home page, otherwise Google will treat it as a soft 404; avoid redirect chains (A → B → C) and go directly A → C; make sure redirects don’t lead to pages that themselves redirect or return 404.
What to check before the migration
- A full list of URLs has been collected from at least three sources and exported.
- A snapshot of rankings and traffic has been saved as a baseline.
- Top pages by traffic and by backlinks have been identified: they get the most attention.
- The redirect map has been built and checked for chains and loops.
- The staging version is closed to indexing.
- A full backup of the old site has been made.
Separately, export pages with impressions, queries, and external links from Search Console. You’ll be comparing “before” and “after” for several months, and it’s handier to keep the old data in a spreadsheet. And agree with your team on a release day. Tuesday or Wednesday works best: there’s enough time to catch bugs before the weekend. A Friday evening move almost always ends with problems being found on Monday.
What to check after the migration
- Every old URL returns a single 301 to a relevant new address.
- No spike in 404s and soft 404s in Search Console.
- The new XML sitemap has been submitted and is being processed.
- Robots.txt doesn’t block important sections; noindex has been removed from live pages.
- Canonicals point to the new addresses; hreflang is correct for language versions.
- Speed and Core Web Vitals haven’t dropped.
- Internal links point directly to the new URLs, without intermediate redirects.
- Backlinks from top donors have been updated to the new address where possible.
Typical traffic losses and how to avoid them
| Mistake | Consequence | How to avoid it |
| All redirects to the home page | Soft 404, lost page equity | A page-by-page redirect map |
| Some URLs forgotten | Pages drop out of the index | A full list from several sources |
| Redirect chains | Lost equity, slower crawling | Direct 301s A → C |
| Staging open for indexing | Duplicates, cannibalization | Basic authentication on staging |
| Meta tags lost | Lower CTR and rankings | Transfer title/description one to one |
| Internal links not updated | Unnecessary redirects, lost equity | Replace links with the new URLs |
| No monitoring afterwards | Late reaction to a drop | Daily checks for 2–4 weeks |
Case study: moving an online store to a new domain
A store with ~4,000 pages changed its domain during a rebrand. Before the move, the team collected a full list of URLs from Search Console, the sitemap, and a crawler, recorded rankings for 600 keywords, and set up a page-by-page 301 redirect map, separately checking the top 200 pages by traffic and the top 100 by backlinks.
In the first two weeks after launch, organic traffic dipped by about 18%, the expected reindexing effect. Thanks to correct redirects and preserved meta tags, by the end of the fourth week traffic was back to its previous level, and by the eighth it was 6% higher thanks to faster load times on the new platform. Two factors played the key role: not a single top URL got lost, and internal linking pointed to the new addresses right away.
The most common cause of a prolonged drop is not the migration itself but unnoticed technical breaks: redirect chains, forgotten URLs, an accidental noindex. A technical SEO audit, a full check of redirects, indexing, and structure before and after the move, helps you find them before they tank your traffic. And if rankings did drop and aren’t recovering, our separate guide what to do if your rankings dropped will help you find the causes.
Planning a move?
A domain change, redesign, or move to a new platform goes without losses when the redirect map is built in advance and the site is checked before and after launch. Order an SEO audit, and we’ll prepare the redirect map and run the migration without a drop in rankings or traffic. Prices are approximate and depend on the niche, scope, and competition; we’ll calculate the exact cost for your project.
