How to Migrate a Website Without Losing SEO Rankings

A website migration is one of the riskiest SEO actions you can take. Done incorrectly, it can lead to a drop of 30 to 80 percent in organic traffic, sometimes permanently. Done correctly, a migration is almost transparent to search engines.

What is a website migration?

A website migration is any significant technical change to a website that affects how search engines crawl and index it. The most common types: domain change (from old-domain.com to new-domain.com), CMS migration (from WordPress to Webflow, from Joomla to WordPress), HTTP to HTTPS migration, and redesigns with URL structure changes.

SEO risks of a website migration

The three biggest SEO risks in a migration are: loss of indexed URLs (when pages disappear without redirects), loss of link value (when backlinks to old URLs are not forwarded), and temporary ranking instability (while Google processes the new structure).

Before migration: preparation

1. SEO audit of the current website

Export all indexed URLs via Google Search Console (all pages in the indexing report). This is your baseline. Also export all backlinks via Ahrefs or Google Search Console. These are the URLs receiving your backlink value and which you must always redirect.

2. Build a redirect map

Create a spreadsheet with column A = old URL and column B = new URL. Every indexed page and every page with external backlinks gets a 301 redirect to the most relevant new page. This is the most time-consuming but also the most critical step.

3. Set benchmarks

Note current organic traffic numbers via Google Analytics 4 and current rankings for your top 20 keywords via Google Search Console. These are the reference figures against which you measure the success of the migration.

4. Test on the staging environment

Run the complete migration first on a staging environment. Manually check all redirects for your top 50 URLs. Verify the new website has no technical SEO problems (noindex tags, robots.txt blocking pages, missing canonical tags).

During migration

1. Migrate during off-peak hours to limit the impact of any issues
2. Activate all 301 redirects simultaneously with the launch of the new website
3. Update the XML sitemap with all new URLs and submit it immediately via Google Search Console
4. Check robots.txt on the new website: make sure it does not accidentally contain 'Disallow: /'
5. Update Google Search Console: add the new domain name or HTTPS variant as a property and request indexing of the homepage

After migration: monitoring

The first four weeks after a migration are critical. Monitor daily via Google Search Console: the Indexing report (are new pages being indexed?), the Performance report (are you retaining clicks and impressions?), and the Page Experience report (are there new Core Web Vitals issues?).

A slight drop of 5 to 15 percent in the first two to four weeks is normal while Google processes the new structure. A drop of more than 30 percent is a signal that there are serious problems with the redirect implementation or the technical SEO of the new site.

Frequently asked questions

How long does it take for Google to index my new site?

For small websites (under 500 pages), re-crawling typically takes 2 to 4 weeks. Larger websites may need 2 to 3 months before Google has processed all pages. Submit your sitemap and use URL inspection in Search Console to index priority pages faster.

What if I lose rankings after a migration?

First check whether the redirect map is fully implemented. Check the indexing report in Search Console for new errors. Compare the technical SEO of the new pages with the originals. In most cases the problem is either a missing redirect or a technical issue on the new site that wasn't present before.

Should I avoid a migration if my website ranks well?

Not necessarily, but be extra careful. A well-ranking website has more to lose. Plan extra time for preparation, run a full staging test and keep a rollback plan ready. Sometimes a migration is essential for long-term SEO: an outdated CMS, slow load times or a poor URL structure that can't be changed are good reasons to migrate.

How long should I keep 301 redirects active?

At minimum one year after the migration. In practice, keep redirects permanently unless there's a good reason to remove them. If you remove redirects too early, you lose the link value of backlinks still pointing to old URLs.

What is the difference between a 301 and a 302 redirect?

A 301 redirect (permanent) signals to Google that a page has definitively moved and passes almost all link value. A 302 redirect (temporary) signals a temporary redirect and passes no or less link value. Always use 301 redirects for a website migration.