How to Migrate a Website Without Losing Rankings

A website migration is the most common way businesses destroy their own search rankings. Not because migrations are inherently dangerous, but because most people treat them as a design project and forget about SEO until after launch.

The short answer

To migrate without losing rankings, do three things: before launch, audit every URL and record current rankings. During launch, implement 301 redirects from every old URL to its new equivalent and preserve your content. After launch, submit the new sitemap to Search Console, monitor for 404 errors, and watch your rankings for two to four weeks. The most common mistakes are forgetting redirects, rewriting content during the migration, and not updating the sitemap.

Before the migration

Audit your current URLs

Before you change anything, you need a complete list of every URL on your current site that search engines have indexed. If you do not know what you have, you cannot protect it.

1. Go to Google Search Console. Export your indexed pages report.
2. Run a site crawl using Screaming Frog or a similar tool. This catches pages Google has not indexed but that still exist.
3. Combine both lists into a master URL inventory.

Record your current rankings

Document where you currently rank for your target keywords. If rankings drop after launch, you need to know what you lost.

1. Use a rank tracking tool (Ahrefs, Semrush, or Search Console's performance report).
2. Record the top 20 to 50 keywords you care about, the URL that ranks for each, and the position.
3. Save this. You will compare against it after launch.

Map old URLs to new URLs

This is the most important pre-migration step. For every URL on your current site, decide what its new URL will be. Create a redirect map.

Rules for the redirect map:

• If a page's content is moving, map it to the closest equivalent new page.
• If a page is being deleted, redirect it to the most relevant parent page, not the homepage.
• If a page's URL is not changing, no redirect is needed.
• Do not redirect everything to the homepage. That wastes the link equity.

During the migration

Implement 301 redirects

A 301 redirect is a permanent redirect. It tells search engines and browsers that a page has permanently moved, and it passes most of the original page's search ranking value to the new page.

• Use 301 (permanent) redirects, not 302 (temporary). A 302 tells Google the move is temporary, so it does not transfer ranking signals.
• Implement redirects at the server level, not via JavaScript or meta refresh tags. Server-level redirects are the only type search engines reliably follow.
• Test every redirect before launch. Load the old URL and confirm it goes to the correct new URL with a 301 status code.

Preserve your content

People use the redesign as an opportunity to rewrite everything. Do not do this.

• Keep the content on each page as close to the original as possible during the migration.
• If you want to rewrite content, do it as a separate project after the migration is stable. Mixing a redesign with a content rewrite makes it impossible to tell which change caused a ranking drop.
• Preserve title tags, meta descriptions, and heading structure where possible.

Keep URL structure where possible

The fewer URLs that change, the fewer redirects you need. If your current URL structure is reasonable, keep it. If it is messy, this may be the time to clean it up, but do so with the redirect map ready.

Update internal links

Every internal link that points to an old URL needs to point to the new URL. If your internal links go through redirects, it still works, but it is cleaner to point directly to the final URL.

• Crawl the new site before launch.
• Find every internal link.
• Update any that point to old URLs.

After the migration

Submit the new sitemap

Once the new site is live, generate a new XML sitemap and submit it to Google Search Console.

1. Generate the sitemap (most CMS platforms and static site generators do this automatically).
2. Submit it in Search Console under Sitemaps.
3. Keep the old sitemap active for a few weeks so Google can process the redirects.

Monitor for 404 errors

A 404 means a page was not found. After a migration, 404s usually mean a redirect is missing or an internal link is broken.

1. Check Search Console's Coverage report daily for the first week.
2. For every 404, either add a redirect or fix the internal link.

Check Search Console

Search Console tells you what Google sees on the new site. Watch for:

• New pages being indexed (good)
• Old URLs still showing as indexed (normal for a few weeks, then they should drop)
• Coverage errors and mobile usability errors (fix immediately)

Watch your rankings

Compare your post-migration rankings to the pre-migration baseline.

• Expect some fluctuation in the first 1 to 2 weeks. Rankings may dip and recover as Google processes the redirects.
• If rankings have not recovered after 3 to 4 weeks, something is wrong. Check for missing redirects, changed content, or indexing errors.
• If a specific page dropped, compare its old and new content. Did the title tag change? Did the content get shorter?

Common mistakes

• Forgetting redirects. Every old URL that is not redirected loses its ranking value.
• Rewriting content during the migration. Google sees a new URL with new content and treats it as a new page. The old page's ranking signals do not transfer cleanly.
• Not updating the sitemap. If Google does not know about the new URLs, it cannot index them.
• Redirecting everything to the homepage. This tells Google nothing about where the content actually went.
• Not testing before launch. Redirects that point to the wrong place are only caught if you test them.
• Ignoring it after launch. The post-launch monitoring is where you catch problems before they become permanent ranking losses.

Specific redirect patterns that work

The redirect map is only useful if the patterns cover the real cases. Here are the mappings I see most often, with the exact old-to-new structure.

For Gatsby and Netlify, these go in netlify.toml or a _redirects file. The format is:

/about-us/    /about/    301
/services/web-design/    /services/website-redesign/    301
/blog/old-post-title/    /blog/new-post-title/    301
/contact-form/    /contact/    301

Test each one with curl -I https://yoursite.com/old-url/ and confirm the response includes HTTP/2 301 and a location header pointing to the correct new URL. Do this before you celebrate launch.

Pre-migration checklist

Before you touch anything, complete this checklist. If you skip a step, you are flying blind after launch.

1. Sitemap exported. Download your current XML sitemap and save a copy. This is your URL inventory baseline.
2. Backlink report pulled. Use Ahrefs, Semrush, or Google Search Console to export every URL that has external backlinks. These pages must redirect perfectly, or you lose link equity.
3. Analytics baseline recorded. Note your current organic traffic, top landing pages, top keywords, and conversion rates. Screenshot the charts. You need a before picture to compare against.
4. Rank tracking snapshot saved. Record the top 20-50 keywords, the ranking URL, and the position. Save it in a spreadsheet.
5. Redirect map built and reviewed. Every old URL mapped to a new URL. Reviewed by someone other than the person who built it.
6. Crawl completed. Run Screaming Frog on the current site. Export the full URL list plus status codes. This catches pages that are not in the sitemap.
7. Staging environment tested. The new site is built on a staging URL. Redirects are tested there before production launch.

Post-migration monitoring

The first 30 days after launch are when you catch problems. Here is what to check and when.

Day 1: Submit the new sitemap in Search Console. Check the Coverage report for immediate errors. Crawl the new site with Screaming Frog and look for 404s, broken internal links, and missing canonical tags. Compare the URL count against your redirect map — if the new site has 50 fewer pages than expected, something is missing.

Day 7: Check Search Console's Performance report. Compare impressions and clicks to your pre-migration baseline. A small dip is normal. A 30%+ drop is a red flag. Check the Coverage report for new errors. Look at the old URLs — they should be dropping out of the index as Google processes the redirects.

Day 30: Rankings should be back to baseline or close to it. If they are not, check for missing redirects, changed content, or pages that lost their title tags. Pull a fresh backlink report and confirm no external links are pointing at URLs that 404.

A real migration timeline

Here is what a clean migration actually looks like, day by day.

Day 1 (launch): New site goes live. Redirects are active. Sitemap submitted. Traffic dips 10-15% as Google re-crawls. This is expected.

Day 2-3: Search Console starts showing the new URLs in the Coverage report. Old URLs are still indexed. Some 404s appear — usually internal links you missed. Fix them immediately.

Day 7: Traffic is recovering. Most old URLs have been re-crawled and redirected. Rankings are fluctuating but trending toward baseline. The old sitemap can be removed from Search Console.

Day 14: Rankings are stable. Traffic is at or above pre-migration levels. The new site is fully indexed.

Day 30: Migration is complete. Old URLs are mostly de-indexed. No new 404s. If you are not here by day 30, something went wrong and you need to investigate.

When to get help

If you are migrating a site that currently ranks well and brings in business, the risk is real. A botched migration can wipe out years of SEO work in a week. If you want someone to handle the redirect mapping and post-launch monitoring, I do this as part of my website redesign service. Get in touch before you start the migration.

The bottom line

Migrations do not have to cost you rankings. The process is straightforward: know what you have, map where it is going, redirect every old URL, preserve the content, and watch what happens after launch. The businesses that lose rankings skip the pre-migration audit. The ones that keep their rankings treat SEO as part of the migration, not an afterthought.