Website migrations are one of the highest-risk projects in digital marketing. A study by Ahrefs found that roughly 68 percent of migrations experience a measurable drop in organic traffic within the first three months. Many never fully recover. The risk is not the migration itself. It is treating SEO as an afterthought.
For a small business, a migration might mean moving from WordPress to a static site, switching domains, changing URL structures, or moving to a new ecommerce platform. Whatever the scope, the goal is the same: preserve the search equity you have already built while improving the site for users.
If you are also evaluating your current site, our technical SEO audit checklist will help you benchmark where you stand before any migration work begins.
Define the Scope Before You Start
Every migration changes something. The more variables you change at once, the harder it is to diagnose problems. The main types of migration include:
- Protocol change, such as HTTP to HTTPS
- Domain change, such as oldbrand.com to newbrand.com
- URL structure change, such as /blog/post-name to /news/post-name
- CMS or platform change, such as WordPress to Shopify
- Design and content change at the same time as a technical migration
If possible, avoid changing your URL structure and your design at the same time. Changing both at once makes it impossible to tell whether a ranking drop came from technical redirects or from content changes.
Benchmark Your Current Performance
You cannot measure success if you do not know where you started. Before touching anything, document:
- Average daily or weekly organic traffic
- Keyword rankings for your top terms
- Indexed page count in Google Search Console
- Core Web Vitals scores
- Top pages by traffic and conversions
- Backlink profile and referring domains
Export your full list of URLs from a crawler and from Google Search Console. Combine them so you do not miss orphan pages that still get traffic. This list becomes the foundation of your redirect map.
Build a Complete Redirect Map
The redirect map is the single most important piece of a migration. It matches every old URL to the most relevant new URL. Every old URL that will change needs a 301 permanent redirect to a specific destination.
Do not redirect everything to the homepage. That is called a soft 404 and it destroys the relevance signal. If an old page has no equivalent on the new site, use a 404 or 410 status code. Forced redirects to unrelated pages confuse users and search engines.
Pay special attention to pages with external backlinks. Those URLs carry authority from other sites. Losing them means losing trust signals. Make sure every backlinked URL has a working redirect to a relevant new page.
Implement server-side 301 redirects, not JavaScript redirects or meta refreshes. Test each redirect before launch to confirm it returns a 301 status and lands on the correct destination without chains or loops.
Preserve Content and Metadata
Moving to a new platform often tempts teams to rewrite everything. Resist that urge during the migration itself. If you change content, URLs, and design all at once, you cannot isolate what caused a ranking change.
Migrate your existing titles, meta descriptions, headings, and body content first. Get the site stable. Then run content improvements as a separate project with its own measurement.
If you must consolidate pages, make sure the new page covers all the user intents that the old pages satisfied. Deleting content that ranks for long-tail keywords is a common cause of traffic loss after migration.
Handle Technical Basics on the New Site
Before launch, confirm these technical elements on the new site:
- Canonical tags point to the correct preferred URLs
- XML sitemap lists only the new URLs
- Robots.txt does not accidentally block the entire site
- Internal links point directly to final URLs, not redirected URLs
- Structured data is present and valid
- Core Web Vitals scores meet Google’s targets. Our Core Web Vitals guide explains what to measure.
- Mobile rendering works correctly on real devices
A clean technical foundation reduces the chance that search engines struggle to crawl and index the new site.
Launch and Monitor Closely
Submit the new XML sitemap to Google Search Console immediately after launch. Monitor crawl errors, indexing status, and server response codes daily for the first two weeks.
Test your redirect map again after launch. Sometimes redirects work in staging but fail in production due to server configuration differences. Use a crawler to check that every old URL returns a 301 and lands on a 200 status page.
Watch rankings and traffic weekly for the first 60 days. Some volatility is normal. If a specific URL drops more than 20 positions, investigate immediately. Common causes include broken redirects, missing content, or internal links pointing to old URLs.
Update External Links When Possible
While 301 redirects preserve most link equity, direct links are still better. Contact your most valuable referring domains and ask them to update their links to your new URLs. This is especially important for local citations, partner sites, and press mentions.
If you changed your business name or domain as part of the migration, update your Google Business Profile, directory listings, and social media profiles to match. Inconsistent NAP data after a domain change can hurt local rankings. For help with the hosting side of a migration, our web hosting comparison breaks down the platforms worth considering.
Next Steps
A website migration is not just a technical move. It is a transfer of trust from the old site to the new one. The businesses that protect their rankings are the ones that plan redirects before launch, preserve content and metadata, validate technical signals, and monitor aggressively afterward.
Start with a clear scope and a full benchmark. Build your redirect map early. Test everything twice. Then watch the data and respond quickly. A well-managed migration can even leave you ranking better than before.
