A site migration is a major change to a website that can affect its URLs, domain, platform, content, architecture, or how search engines access and understand the site. A properly planned website migration SEO strategy helps manage those changes while protecting existing search performance.
Moving from one CMS to another is a site migration. Changing your domain name is a site migration. Switching from HTTP to HTTPS qualifies. So can a website redesign, major URL structure change, subdomain move, or large-scale content migration.
Some migrations combine several of these changes at once.
The problem is that a website migration changes more than what visitors see. Search engines have already built an understanding of your existing website. They know which URLs are indexed, which pages have earned backlinks, how internal links connect those pages, and which URLs should appear for particular searches.
A migration asks Google and other search engines to update some or all of that information.
Done correctly, the transition can be relatively uneventful. Done poorly, years of SEO work can disappear remarkably fast.
That is why SEO migration planning needs to start before the new website launches, not after somebody notices organic traffic falling.
What Is Site Migration?
Site migration is the process of making substantial changes to a website’s technology, location, structure, design, or content while transitioning users and search engines from the old version to the new one.
Think of it like moving a physical business.
Your customers need the new address. Your mail needs to be forwarded. Your signs and listings need to be updated. And you probably do not want to discover on Monday morning that half your inventory was left in the old building.
Website migration works similarly.
A page that previously lived at:
example.com/services/seo
might move to:
example.com/seo-services
If the old URL has rankings, backlinks, traffic, and years of history, simply deleting it and publishing the new URL breaks the connection between them.
A properly configured 301 redirect helps search engines understand that the resource has permanently moved. Internal links should also be updated, canonical tags should reference the appropriate URLs, and the new page needs to remain crawlable and indexable.
Multiply that process across hundreds or thousands of pages and you have an SEO migration.
What Counts as a Website Migration?
“Migration” sometimes gets used as shorthand for changing domains, but domain migration is only one type.
Any significant website change that affects how users or search engines find, crawl, render, index, or interpret the site may require migration planning.
Domain migration
A domain migration moves a website from one domain name to another.
For example:
oldbrand.com -> newbrand.com
This commonly happens during rebranding, acquisitions, mergers, or a move to a better domain.
Domain changes deserve particularly careful SEO planning because every existing URL changes simultaneously. Backlinks that previously pointed directly to the old domain also need to pass users and search engines toward appropriate destinations on the new site.
CMS migration
A CMS migration moves a website from one content management system to another.
Common examples include moving to or from WordPress, Shopify, Webflow, Drupal, or a custom CMS.
A CMS change can appear to be an infrastructure project while quietly changing URLs, HTML, metadata, internal links, structured data, navigation, JavaScript rendering, and page templates.
That makes replatforming SEO one of the migrations where technical SEO needs to be involved early.
HTTP to HTTPS migration
Moving from HTTP to HTTPS changes the protocol used by every affected URL.
Although HTTP to HTTPS migrations have become routine, they still need correct redirects, canonicalization, internal link updates, and sitemap configuration.
Subdomain and subfolder migrations
Moving content between a subdomain and the primary domain is another migration.
For example:
blog.example.com/article -> example.com/blog/article
The reverse can happen as well.
These projects require careful URL mapping because the location and internal architecture of the content are changing.
Website redesign
Not every website redesign is a migration.
If the design changes while URLs, content, navigation, markup, and underlying technology remain substantially identical, migration risk can be limited.
Most redesigns are not that clean.
Design projects often introduce new templates, navigation, wireframes, a different user experience, rewritten content, deleted pages, changed internal links, or a new URL structure. At that point, the redesign has become an SEO migration whether the project plan calls it one or not.
Content migration
A content migration moves, consolidates, rewrites, or reorganizes substantial portions of a website’s content.
That can affect landing pages that currently generate rankings and organic traffic.
Removing 300 old pages and replacing them with 80 new pages, for example, requires decisions about which old URLs should redirect, which should disappear, and which content needs to be preserved.
Why Site Migration Can Affect SEO
SEO is built partly on continuity.
Search engines crawl URLs, interpret their content and relationships, discover links, collect signals, and decide which pages belong in their indexes.
Migration changes those inputs.
Imagine Google has indexed 2,000 URLs from your existing website. Your new site launches with 1,500 URLs and a different architecture.
Google now has to figure out:
-
Which old URLs still exist?
-
Which URLs permanently moved?
-
Where did they move?
-
Which pages were intentionally removed?
-
Has the content changed?
-
Has the relationship between pages changed?
-
Are the new URLs crawlable?
-
Which URLs should be indexed?
-
Are existing ranking signals still applicable?
That processing does not happen because the homepage looks nicer.
The technical implementation has to communicate the changes.
This is where 301 redirects, canonical tags, XML sitemap files, internal links, metadata, robots.txt directives, and other technical signals become important.
Google’s John Mueller has also discussed the importance of planning and monitoring migrations, including expectations around temporary ranking fluctuations as Google processes site changes, as reported by Search Engine Journal in Google’s Mueller on Keys to a Successful Site Migration.
What Can Go Wrong During an SEO Migration?
Most migration failures are not mysterious algorithm events. They are implementation problems.
One of the most damaging is allowing valuable URLs to disappear without appropriate replacements.
Suppose a service page has earned strong search engine rankings and 40 external backlinks. During the redesign, the development team removes the page because it is not included in the new navigation.
The old URL starts returning a 404.
Search engines have now lost the original resource without being told whether an equivalent replacement exists.
Another common problem is redirecting every retired URL to the homepage. That may seem convenient, but it eliminates the page-to-page relevance that good redirect mapping is designed to preserve.
Other migration problems include broken links, redirect chains, incorrect canonical tags, missing metadata, accidental noindex directives, robots.txt rules blocking important sections, duplicate content, tracking failures, and pages that cannot be rendered properly because of JavaScript changes.
Individually, some are easy to repair.
Across 10,000 URLs, things get spicy.
The Key Steps in a Successful Site Migration
A good website migration starts long before launch.
The specific process depends on what is changing, but most migrations should include the following stages.
1. Establish your migration scope
Start by documenting exactly what is changing.
Is the domain changing? CMS? Hosting provider? Site architecture? URL structure? Design? Content?
You should also identify whether infrastructure such as the CDN, server configuration, or IP address will change.
The more variables you change simultaneously, the more difficult troubleshooting becomes.
2. Benchmark current SEO performance
You cannot determine whether the migration protected performance if nobody recorded performance before it happened.
Build a baseline for your most important KPIs.
That should typically include organic traffic, search visibility, rankings, conversions, indexed pages, and performance by landing page.
Google Analytics can establish the traffic and conversion baseline. Google Search Console provides search queries, clicks, impressions, and indexing information.
For a serious SEO migration, I also want an inventory of the URLs currently earning traffic, links, and meaningful search visibility.
3. Crawl the existing website
Before changing the site, capture what currently exists.
A crawler such as Screaming Frog can inventory URLs, status codes, titles, meta descriptions, canonical tags, headings, internal links, and other important elements.
Save that crawl.
It becomes the reference point for comparing the new website against the old one.
You are essentially taking fingerprints before moving the body. Fun dad metaphor? Probably not. Accurate? Yep.
4. Build the new site in a staging environment
The staging environment gives web developers and the SEO team somewhere to test the new website before customers and search engines encounter it.
Access controls matter here.
You generally do not want unfinished staging URLs becoming indexed and competing with the production site.
At the same time, the SEO consultant needs enough access to crawl and inspect staging before launch.
Waiting until production to perform technical QA is an expensive way to discover problems.
5. Map old URLs to new URLs
URL mapping is one of the most important parts of an SEO migration.
Every meaningful URL on the existing site should be evaluated and assigned an outcome.
Some URLs stay exactly the same.
Others move to equivalent new URLs.
Some pages consolidate into a stronger resource.
Others genuinely have no replacement and should be retired.
For URLs that move permanently, the objective is generally to create a direct 301 redirect from the old URL to the most relevant new destination.
Avoid unnecessary redirect chains such as:
Old URL -> temporary URL -> previous redesign URL -> new URL.
Where possible, the old address should point directly to its final destination.
6. Preserve important on-page signals
A new website can look dramatically better while becoming dramatically worse for search.
Before launch, compare important pages between the old and new sites.
Check titles, headings, copy, metadata, structured data where applicable, canonical tags, internal links, image handling, and indexability.
Pay particular attention to pages that already produce traffic, leads, or revenue.
Migration day is a bad time to accidentally cut 80 percent of the copy from your highest-performing landing pages because somebody preferred more whitespace.
7. Validate robots.txt and indexation controls
Development sites are often intentionally blocked from search engines.
Production sites should not inherit those restrictions by accident.
Review robots.txt, robots meta directives, canonical tags, authentication requirements, and other crawl or indexing controls before launch.
One incorrect directive can prevent large sections of the new website from being indexed.
8. Prepare the XML sitemap
Create an XML sitemap containing the canonical URLs you want search engines to discover and index on the new website.
Do not simply recycle an old sitemap filled with redirected or deleted URLs.
The sitemap should describe the website you actually want crawled.
9. Validate analytics and conversion tracking
SEO performance is not very useful if your measurement disappears on launch day.
Verify Google Analytics and any relevant tag management, CRM, call tracking, ecommerce, form, or conversion systems.
Test important events yourself.
Do not assume that seeing the Google Analytics script in the source means every conversion is working.
10. Launch and immediately QA production
Once the new website is live with minimal downtime, crawl it again.
Test the 301 redirects. Check for broken links. Confirm canonical tags. Validate important templates. Check robots.txt. Review status codes. Test forms and analytics.
For a domain change, complete applicable search engine change of address procedures as well.
This is where the pre-migration crawl becomes particularly valuable because you can compare the old and new sites systematically rather than clicking around and hoping everything looks right.
11. Monitor SEO after launch
Website migration does not end at deployment.
Search engines need time to crawl the changes and update their indexes.
Monitor Google Search Console, Google Analytics, rankings, indexed URL counts, crawl behavior, conversions, and organic visibility after launch.
Small fluctuations can occur while the new site is processed.
A sustained drop across important pages deserves investigation.
What Makes CMS Migrations Difficult?
Changing CMS platforms can create several migrations simultaneously.
Suppose a company moves from WordPress to another content management system.
The new CMS might generate URLs differently. It might handle canonical tags differently. It might use JavaScript for content that WordPress previously rendered in HTML. It could generate pagination, category pages, or metadata using completely different rules.
Plugins that previously handled redirects, structured data, XML sitemap generation, or SEO metadata may disappear.
Even when the pages look almost identical to visitors, the underlying signals available to search engines can change considerably.
This is why I treat CMS migrations as more than moving text and images between databases.
The question is not simply, “Did all the content migrate?”
It is, “Did everything search engines relied on migrate?”
How Long Does a Website Migration Take?
There is no universal timeline.
A small site with 50 URLs and an unchanged domain is a different project from an ecommerce site with hundreds of thousands of URLs moving to a new CMS.
For a mid-sized site, the SEO workstream can often require several weeks before launch, followed by post-launch monitoring.
Austin’s migration consulting process typically runs the SEO workstream four to eight weeks before launch for a mid-sized website, followed by 90 days of monitoring. Larger ecommerce catalogs and multi-domain projects can take longer.
The important point is that SEO needs enough time before launch to benchmark the old website, crawl it, map URLs, inspect staging, and resolve problems.
Compressing the schedule usually does not eliminate that work.
It eliminates the opportunity to do it before the mistakes become public.
How Much Does an SEO Migration Cost?
SEO migration pricing depends on scope.
A 100-page brochure site changing domains requires substantially less URL mapping and QA than a 50,000-page ecommerce site moving between platforms.
Cost can also depend on whether the engagement includes strategy only or hands-on implementation, analytics validation, developer coordination, redirect testing, technical QA, and extended monitoring.
Other major variables include the number of URLs, complexity of the CMS, amount of content migration, number of domains or subdomains involved, international configurations, custom JavaScript, and the condition of the existing site.
For that reason, a useful migration quote should be based on the actual website and proposed changes rather than a generic per-page number.
Should You Expect Rankings to Drop After a Site Migration?
A migration can produce temporary volatility while search engines crawl new URLs and process redirects.
That does not mean a major, sustained loss in search engine rankings should simply be accepted as the price of launching a new site.
Austin Lewis has documented domain and rebrand migrations where rankings or organic traffic were preserved through the transition, including Plumb Smart’s domain change and Allegiant Exteriors’ rebrand.
The practical goal of SEO migration is straightforward: preserve as much existing search equity and business performance as possible while giving search engines clear signals about what changed.
That requires planning before deployment and measurement afterward.
Why SEO Needs a Seat at the Table Before Launch
SEO migration gets much harder when the SEO consultant receives the staging URL three days before launch.
By then, the architecture may be approved. Wireframes became templates months ago. Developers implemented the URL structure. Content has been cut. Redirect logic may not exist. The launch date has already been promised internally.
At that point, an SEO review becomes triage.
The better sequence brings SEO into planning early enough to identify which pages and ranking signals need protection before decisions become expensive to reverse.
That does not mean SEO gets to dictate the redesign.
It means the migration team knows what it is changing and what those changes might cost.
Site Migration Is Risk Management
A website migration should not be scary.
It should be controlled.
You inventory what currently has value. You determine what is changing. You map old resources to new ones. You test the implementation. You launch. Then you measure what happened against the baseline.
That is much closer to engineering than SEO superstition.
The worst migrations I encounter usually skipped one of those steps and discovered the consequences after search visibility declined.
The safest approach is to involve an SEO migration specialist before URLs, architecture, content, and platform decisions are locked.
I handle website migration SEO from the initial benchmark and URL inventory through redirect mapping, staging QA, launch validation, and post-migration monitoring. The objective is simple: move the website without unnecessarily sacrificing the rankings, traffic, links, and conversions the existing site already earned.
For teams that want a repeatable framework before launch, this SEO migration checklist covers the major checks involved. For broader acquisition and measurement support beyond migrations, you can also work with a performance marketing agency.
Frequently Asked Questions
1. What is site migration?
Site migration is a significant change to a website’s domain, platform, URLs, architecture, content, protocol, or design that can affect how users and search engines access the site. Common examples include domain changes, CMS migrations, HTTP to HTTPS moves, major redesigns, and restructuring URLs. SEO migration is the process used to protect existing search performance through those changes.
2. What are common types of site migrations?
Common types include domain migration, CMS or platform migration, website redesign, content migration, URL restructuring, HTTP to HTTPS migration, rebranding, and moving content between a subdomain and subfolder. A single project can involve several types at once.
3. What are the key steps involved in a successful site migration?
A successful website migration typically includes establishing scope, benchmarking SEO performance, crawling the existing site, preparing a staging environment, mapping URLs, implementing 301 redirects, preserving important content and metadata, checking internal links and canonical tags, validating robots.txt and XML sitemap files, testing analytics, performing launch QA, and monitoring performance afterward. A formal website migration checklist helps keep these dependencies organized.
4. How long does site migration take?
The timeline depends on the size and complexity of the website. Austin’s SEO workstream for a mid-sized migration typically runs four to eight weeks before launch, with monitoring continuing for roughly 90 days afterward. Large ecommerce, multi-domain, or complex CMS migrations can require considerably more time.
5. What are the SEO implications of a site migration?
A migration can affect crawling, indexation, organic traffic, backlinks, ranking signals, internal link equity, and search engine rankings. Search engines need to understand where old content moved and which new URLs should be indexed. Incorrect redirects, missing pages, blocked crawling, duplicate content, and changed content can all damage organic visibility.
6. What special challenges arise when changing CMS?
Changing CMS can alter URL generation, page templates, metadata, canonical tags, internal links, structured data, XML sitemaps, rendering, navigation, and other technical SEO elements. Features previously handled by WordPress plugins or another CMS may need to be recreated on the new platform. Testing the new content management system in staging helps identify those differences before launch.
7. How much does an SEO migration cost?
SEO migration cost varies according to site size, migration type, platform complexity, number of URLs, redirect requirements, analytics setup, developer coordination, and the amount of pre- and post-launch QA required. A small site migration and a large enterprise replatform are fundamentally different scopes, so pricing should be based on the actual migration rather than a universal flat rate.