ANATRA
← THINKING
Redesign5 min7 May 2026

How to Migrate Your Website Without Losing SEO

Website migrations destroy SEO rankings when done badly. Here's the checklist for preserving your traffic during a redesign or platform change.

Last updated: May 2026

You are redesigning your website or moving to a new platform. The new site looks better, loads faster, and has proper brand identity. Two weeks after launch, your organic traffic drops 40%. This happens constantly because website migrations are done without SEO planning. It is entirely preventable.

In brief: A website migration requires a URL mapping plan (every old URL redirected to the correct new URL), content preservation (do not delete pages that rank), technical SEO transfer (sitemaps, Search Console, schema), and a monitoring plan for the first 30 days. Skip any of these and you risk losing months or years of accumulated search authority.

What can go wrong

URL changes without redirects. Your old site had /services/web-design. Your new site has /services/website-design. Without a 301 redirect from the old URL to the new one, Google sees the old page as deleted and the new page as brand new. Every backlink pointing to the old URL now leads to a 404 error. Every ranking the old page accumulated is lost.

Content removal. Your old site had a blog with 20 articles that generate organic traffic. The new site launches without migrating those articles because "we are starting fresh." The traffic those articles generated disappears immediately and takes months to rebuild.

Domain change without planning. Moving from yourbusiness.co.uk to yourbusiness.com without proper domain migration protocol (Search Console change of address, complete URL mapping, DNS management) can temporarily or permanently damage search visibility.

The migration checklist

Before launch: create a complete URL map. Export every URL from the current site (Screaming Frog or a similar crawler). Map each old URL to its equivalent new URL. Set up 301 redirects for every changed URL. Test every redirect before going live.

Before launch: preserve ranking content. Identify pages that rank in Google Search Console (any page with impressions and clicks). Ensure those pages exist in the new site with equivalent or better content. Do not change the URL of a page that ranks well unless absolutely necessary.

Before launch: transfer technical SEO. Generate a new XML sitemap. Prepare Search Console for the new site (or reverify if the domain stays the same). Transfer schema markup, meta tags, and canonical tags. Verify robots.txt is not blocking important pages.

At launch: submit the new sitemap. In Google Search Console, submit the new sitemap immediately after launch. If the domain is changing, use the Change of Address tool. Request indexing for the most important pages.

After launch: monitor for 30 days. Check Search Console daily for the first week, then weekly for the next three weeks. Watch for crawl errors, dropped pages, and indexing issues. Monitor organic traffic in analytics. Compare to the pre-migration baseline.

After launch: fix issues fast. If traffic drops, check for missed redirects (404 errors in Search Console), blocked pages (check robots.txt), or deindexed pages (check the Coverage report). The faster you catch and fix migration issues, the less permanent the damage.

Common mistakes

Using 302 redirects instead of 301. A 302 is a temporary redirect. Google may not transfer ranking authority through a 302. Always use 301 (permanent) redirects for site migrations.

Redirecting everything to the homepage. Lazy redirect implementations send all old URLs to the new homepage. This tells Google that none of the original pages exist anymore. Each old URL should redirect to its specific equivalent page on the new site.

Not testing redirects before launch. A redirect map on a spreadsheet is not the same as working redirects on the server. Test every redirect before the new site goes live. Use a tool like Screaming Frog to crawl the old URLs and verify they redirect correctly.

Forgetting internal links. Your new site may have new URLs, but old internal links within the content still point to old URLs. Update internal links to point directly to new URLs rather than relying on redirects. This improves crawl efficiency and user experience.

Frequently asked questions

How long does SEO recovery take after a migration?

With proper planning (complete redirects, content preservation, immediate sitemap submission), most sites recover within two to four weeks. Without proper planning, recovery can take three to six months or longer. Some poorly executed migrations never fully recover.

Should I change my domain during a redesign?

Only if there is a strong business reason (rebranding, better domain name). Domain changes add significant migration complexity and risk. If you can keep the same domain, do so. The redesign itself carries enough SEO risk without adding a domain change.

Can I delete old blog posts during a migration?

Only if they generate zero traffic. Check Google Search Console for impressions and clicks on every post before deleting. A post that generates 50 visits per month may not seem significant, but those 50 visits compound across 20 posts. Redirect deleted posts to relevant existing content.

Do I need an SEO specialist for a migration?

For a straightforward redesign on the same domain with the same URL structure, a competent web developer can handle the technical SEO transfer. For domain changes, platform migrations (WordPress to Next.js, for example), or sites with significant organic traffic, an SEO specialist is strongly recommended.

What tools do I need for a migration?

Screaming Frog (to crawl old URLs and verify redirects), Google Search Console (to monitor indexing and submit sitemaps), Google Analytics (to track traffic changes), and a spreadsheet for URL mapping. All are free or have free tiers sufficient for most small business sites.

Sources

Anatra Design
Brand + website studio
KEEP READING

More ideas.

Ready to build?

Anatra Design — Design that converts.