Website migration is any significant change to your site's platform, domain, URL structure, or design that affects how search engines and AI assistants find, understand, and rank it.
Key Takeaways
- Website migration covers five distinct types: platform, domain, URL structure, protocol, and design. Most real migrations are more than one at once.
- The risk is not the move itself. It is losing the search equity you spent years building, which happens through broken redirects, changed URLs, and lost metadata.
- Traffic drops after a migration are normal for two to eight weeks. Drops that persist past three months are a problem, not a settling period.
- In 2026 a migration puts your AI visibility at risk too, because assistants cite URLs and a broken citation is a lost mention that no rank tracker reports.
- The single highest-value artifact is a complete redirect map built before launch, not after.
- Migrations are also the cheapest moment to fix structural problems you would otherwise never get budget to touch.
Most website migrations lose traffic, and most of that loss was avoidable.
Website migration is the project teams underestimate most reliably. It looks like a design and development job, so it gets scoped as one, and the search consequences show up six weeks later when nobody is looking. This page covers what website migration means, the types that exist, how to plan one, and how to move without losing what you have already earned.
What is Website Migration?
Website migration refers to any substantial change to your website that alters how it is built, where it lives, or how its pages are addressed. That includes moving to a new CMS, changing domains, restructuring URLs, or rebuilding the design on the same platform.
Think of it this way. Moving house is not just carrying boxes. It is the change of address, the mail forwarding, and the hundred people who need to know where to find you now. A website migration is the same problem. The content survives the move easily. The connections to it are what break.
The word covers a wide range of projects, which is why it causes confusion. A five-page brochure site moving from Squarespace to Webflow and an enterprise site consolidating four domains into one are both migrations. They share the same failure modes at wildly different scales.
Why Website Migration Matters
A migration is the single riskiest routine project in a website's life. It is also the single best opportunity to fix things.
Here is what is actually at stake:
Every ranking you hold depends on Google being able to connect an old URL to a new one. Miss the connection and the ranking resets.
Every backlink you have earned points at a specific address. Those links are the hardest asset to rebuild and the easiest to break.
Every AI citation of your content points at a URL too. A broken citation does not degrade gracefully. It disappears.
Your internal links, canonical tags, and structured data all reference paths that may no longer exist.
The upside runs just as deep. A migration is the only time you have permission and budget to fix a bad URL structure, consolidate duplicate pages, kill thin content, and rebuild the technical foundation. Teams that treat it purely as a risk to survive waste that window.
What are the types of website migration?
There are five types. Most real projects combine two or three, which is where complexity compounds.
Platform migration moves your site to a new system, such as WordPress to Webflow or a custom build to a CMS. Also called CMS migration. The content model usually changes, which means the URL structure usually changes with it.
Domain migration changes your web address, whether through a rebrand, a merger, or consolidating multiple domains into one. The highest-risk type, because every single URL changes at once.
URL structure migration keeps the platform and domain but reorganizes the paths, for example moving /post/ to /glossary/ or flattening a deep hierarchy. Deceptively risky, because it looks small.
Protocol migration moves from HTTP to HTTPS. Mostly historical now, but still appears in older estates.
Design migration rebuilds the front end without changing the addresses. The lowest-risk type on paper, though template-level changes to headings, canonical tags, and schema can quietly break things the URLs did not.
If you are weighing a platform move specifically, our breakdown of what a Webflow migration costs covers the scoping variables that drive the number.
Why do website migrations lose traffic?
Migrations lose traffic because the redirect map is incomplete, and because nobody checks the parts of the move that no URL touches.
The redirect failure is the well-known one. Every old URL needs a 301 to its closest new equivalent. Miss one and you lose whatever that page had earned. Chain several together and you leak equity at every hop. Point them all at the homepage, which happens more than it should, and you lose the lot.
The second failure is quieter and more common: partial migrations. When both the old and new URL stay live and serve identical content, you have not migrated anything. You have created a duplicate, and the search engine now has to guess which one is canonical.
We hit exactly this on our own site. During a partial move from /post/ to /glossary/, both paths returned a 200 with identical content and neither carried a canonical tag, while the og:url on one still pointed at the other. The page kept ranking, so nothing looked wrong. It was splitting its own equity across two addresses the entire time.
Then there is what breaks below the URL layer. A new template can render your body headings at the wrong level, drop your structured data, or change canonical behaviour sitewide. None of that shows up in a redirect audit, and all of it affects how machines read the page. That is the same structural work that decides website ranking in the first place.
Is a website migration still just an SEO risk in 2026?
No. A migration now puts two systems at risk, and only one of them appears in your rank tracker.
Search visibility recovers predictably. You redirect properly, Google recrawls, rankings return. The mechanics are well understood and the timeline is roughly two to eight weeks.
AI visibility does not work that way. Assistants cite specific URLs, and much of what they cite about you sits on other people's websites. When you change your addresses, every third-party page linking to your old URLs is now pointing at a redirect or a 404, and you have no control over whether those sources ever update. Your rank tracker will show a clean recovery while your citation rate quietly falls, because nothing in a standard SEO stack measures citations at all.
The practical consequence is that a 2026 migration plan needs a citation baseline alongside the redirect map. Record which URLs assistants currently cite before you move, then check the same set afterwards. Our guide to measuring AI search visibility covers the eight metrics worth tracking, and website visibility explains why the two halves behave differently.
How do you plan a website migration?
Work in five stages, and do not compress the first one.
Inventory everything first. Crawl the existing site and export every URL with its traffic, impressions, backlinks, and rankings. This is your baseline and your priority list. You cannot redirect what you have not counted.
Build the redirect map before you build the site. Every old URL gets a row and a destination. Highest-traffic and most-linked pages get mapped first and checked twice. Redirects should be 301s, one hop, no chains.
Decide what does not move. A migration is the moment to retire thin pages, consolidate near-duplicates, and stop carrying content that has earned nothing in two years. Redirect them to the closest relevant page rather than deleting them outright.
Stage and test. Check the new site on staging for correct canonicals, correct heading levels, intact structured data, and working internal links. Verify redirects against your map before launch, not after.
Launch and monitor daily for four weeks. Watch Search Console for crawl errors, coverage drops, and impression changes. Resubmit your sitemap. Expect a dip. Investigate anything still down after eight weeks.
Speed matters more after a migration than before it, because you are asking Google to recrawl everything at once. Our Webflow speed optimization guide covers the technical basics worth fixing while the site is still on staging.
How long does a website migration take?
Plan for four to twelve weeks of project time, and two to eight weeks of ranking recovery after launch.
The project timeline depends on page count and how many migration types you are combining. A 50-page platform migration on one domain is a few weeks. A multi-domain consolidation with a URL restructure is a quarter, and the redirect mapping alone can take longer than the build.
Recovery is more predictable than most teams expect. A dip in the first two weeks is normal and not a signal of anything. By week eight, most of your traffic should be back. If you are still meaningfully down at three months, the cause is structural rather than temporal, and the usual culprits are missed redirects, redirect chains, or a page-level change that removed something Google was using.
AI citations recover on a different and slower clock, because they depend on third-party sources updating their links. Budget more patience there and less certainty.
Planning a migration?
We handle platform, domain, and URL migrations for B2B tech and SaaS companies, including the redirect mapping, the pre-launch technical audit, and the search and AI visibility baseline most teams skip. Talk to us about your migration
Frequently Asked Questions
Yes, and it is not covered by standard SEO monitoring. AI assistants cite specific URLs, and much of what they cite about you sits on third-party sites you do not control. When your addresses change, those citations point at redirects or dead pages, and there is no guarantee the sources update. Take a citation baseline before you move.Get the foundations right first with website visibility and website ranking, then work through our Webflow SEO checklist before you launch.
A redirect map is a complete list of every URL on the old site paired with its destination on the new one, implemented as 301 redirects. It is the single most important migration artifact, and it should be built before development starts rather than assembled during launch week.
A redesign changes how the site looks. A migration changes how it is built, where it lives, or how its pages are addressed. A redesign on the same platform with the same URLs is the lowest-risk type of migration, though template-level changes to headings, canonicals, and schema can still cause damage.
Cost scales with page count, how many migration types you are combining, and how much content needs restructuring rather than copying. The redirect mapping and technical audit are the line items teams forget to budget. We break the variables down in our guide to Webflow migration cost.
You will see a temporary dip, and you should not see a permanent loss. Rankings return once Google recrawls and follows your redirects, usually within eight weeks. Permanent loss comes from missed redirects, redirect chains, pointing everything at the homepage, or leaving old URLs live alongside new ones.
Four to twelve weeks of project time depending on page count and complexity, plus two to eight weeks of ranking recovery after launch. Multi-domain consolidations with URL restructures run longer. A traffic dip in the first two weeks is normal. A dip still present at three months is a problem to diagnose.
CMS migration is moving your website from one content management system to another, such as WordPress to Webflow or Drupal to a headless setup. It is a type of website migration, and it almost always brings a URL structure change with it because the new system models content differently.
Website migration is any substantial change to your site’s platform, domain, URL structure, protocol, or design that affects how search engines and AI assistants find and understand it. Moving from WordPress to Webflow, changing domains after a rebrand, and restructuring your URL paths are all migrations.
