Website Migration SEO Checklist: How to Redesign Without Losing Traffic

A new website should bring in more business, not less. Yet many companies launch a fresh design, celebrate for a week, and then watch organic traffic and inquiries slide. Pages that ranked for years vanish, old links lead to error pages, and nobody is sure what went wrong.

The good news is that most migration losses are preventable. Search engines can follow a move cleanly when you tell them exactly where every page has gone and keep what made those pages rank. This website migration SEO checklist walks you through each step. If you would rather have specialists run it, our technical SEO experts can plan and check your migration from start to finish.

What Is Website Migration SEO?

A website migration is any significant change to a site's structure, platform, design, location or URLs. Website migration SEO is the work of making that change without losing the search visibility the old site built up. Common types include:

• Redesigns: new templates, navigation and content layout, often with new URLs.
• Platform (CMS) changes: moving from one system to another, for example to or from WordPress, Shopify or a custom build.
• Domain changes: rebranding to a new domain or merging several sites into one.
• Protocol changes: moving from HTTP to HTTPS.
• Structure changes: reorganizing folders, merging pages or moving a blog to a subdomain or subfolder.

Some migrations change only the look of a site and keep every URL. Others change everything at once. The more that changes, the more carefully you need to plan, because search engines have to re-crawl, re-process and re-evaluate more of your site.

Why Do Websites Lose Traffic After a Redesign?

Google ranks individual URLs. When a page's address changes without a redirect, Google sees the old page disappear and an unfamiliar new page appear, and the signals the old URL earned, including backlinks, do not automatically follow. The most common causes of post-launch drops are:

• Missing or wrong redirects: old URLs return 404 errors or all point to the homepage.
• Lost content: pages that ranked are removed or cut down because they did not fit the new design.
• Blocked crawling: a noindex tag or robots.txt block from staging goes live by mistake.
• Changed on-page signals: titles, headings and internal links are rewritten without regard to the keywords they targeted.
• Slower pages: heavy new templates hurt Core Web Vitals and user experience.

Each of these is something you can check before and after launch, which is what the rest of this checklist covers.

What Should You Benchmark Before a Migration?

You cannot tell whether a migration worked unless you know where you started. At least a few weeks before launch, record:

• A full crawl of the current site: use a crawler such as Screaming Frog or Sitebulb to export every URL, title, meta description, H1, canonical tag and status code.
• Top pages by traffic and conversions: export landing page data from Google Analytics and Google Search Console for the last 12 months.
• Keyword rankings: note positions for your priority keywords, especially those that drive leads.
• Backlinks: list the pages that external sites link to. These URLs must be redirected with extra care.
• Indexed pages and XML sitemaps: save the current sitemaps and the indexing report from Search Console.
• Speed and Core Web Vitals: record field data so you can compare after launch.

Combine the crawl, analytics and backlink lists into one master spreadsheet. Every URL that has traffic, rankings or links is a URL you must protect.

How Do You Build a 301 Redirect Map?

A redirect map is a two-column list: every old URL on the left, its new destination on the right. A permanent (301) redirect tells browsers and search engines that a page has moved for good, and Google uses it as a strong signal to transfer ranking signals to the new address. Follow these rules:

• Map one to one wherever possible. Each old page should point to the single new page that best matches its topic and intent.
• Do not send everything to the homepage. Google may treat mass redirects to an unrelated page as soft 404s, so those old pages lose their value.
• Avoid redirect chains and loops. Point old URLs straight to the final destination, and update any existing redirects from earlier site changes.
• Cover every version. Include HTTP and HTTPS, www and non-www, trailing slashes, URL parameters and image or PDF files that earn links.
• Use 410 or 404 only on purpose. If a page truly has no replacement and no value, it is fine to let it go, but make that a decision, not an accident.

Google recommends keeping redirects in place for as long as possible, and at least a year. Its guide to site moves with URL changes covers the process in detail.

Which On-Page SEO Elements Must You Carry Over?

A new design should not quietly erase the signals your pages rank on. For every important page, compare the old and new versions and carry over or improve:

• Title tags and meta descriptions: keep the target keyword and intent, even if you refresh the wording.
• Headings and body content: keep the depth and topics that earned rankings. Shorter, "cleaner" copy often means less relevance.
• Internal links: rebuild links between related pages in the new navigation and body copy, and point them at the new URLs, not at redirects.
• Canonical tags: make sure each points to the page's own new URL, not to the old site or staging.
• Structured data: move over schema markup such as LocalBusiness, FAQPage, Product and BreadcrumbList.
• Image alt text and file names: these help image search and accessibility.
• Hreflang tags: if you run a multilingual site, update every language version together. Our multilingual SEO guide explains how.

How Do You Keep a Staging Site Out of Google?

Your new site needs to be built and tested somewhere before launch, usually on a staging server. If Google finds and indexes it, you can end up with duplicate content competing against your live site. The safest way to protect staging is password protection (HTTP authentication), because it keeps out crawlers and the public alike.

A noindex tag or a robots.txt disallow rule also works, but these are the settings most often forgotten at launch. If you use them, add "remove staging blocks" to your launch checklist in bold. A site that goes live with a sitewide noindex can start dropping out of search results as Google re-crawls it.

What Should You Check on Launch Day?

Launch at a quiet time for your business, not on a Friday afternoon, and keep your developer available for the next few days. Then work through this list:

1. Remove staging blocks: check robots.txt and the page source for noindex on key templates.
2. Test redirects: crawl your list of old URLs and confirm each returns a single 301 to the right page.
3. Crawl the new site: look for 404 errors, redirect chains, missing titles and broken internal links.
4. Check canonicals and structured data: spot-check key templates with the Rich Results Test.
5. Submit a new XML sitemap: list only live, indexable new URLs and submit it in Search Console. Keeping the old sitemap available for a short time can help Google find the redirects faster.
6. Confirm tracking: make sure analytics, conversion goals, call tracking and form notifications all work.
7. Inspect key pages: use URL Inspection in Search Console on your most valuable pages and request indexing.

How Do You Monitor Rankings After Launch?

Some ranking movement is normal after a migration while Google re-crawls and re-processes the site. Google notes that a medium-sized site can take a few weeks for most pages to move, and larger sites take longer. What matters is that the trend recovers, not that nothing moves on day one.

For the first four to eight weeks:

• Check Search Console daily at first: watch the Pages (indexing) report, crawl stats and any new 404s.
• Compare against your benchmark: track traffic, rankings and conversions for your top pages, not just sitewide totals.
• Fix gaps fast: add redirects for any old URLs you missed, and restore content to pages that dropped sharply.
• Watch speed: re-check Core Web Vitals, since new templates often add scripts. Our guide to Core Web Vitals in 2026 explains what to look for.
• Update external links: ask key partners, directories and your Google Business Profile to point to the new URLs.

If traffic is still well below benchmark after a couple of months, run a full audit. Our post on the warning signs your website needs a technical SEO audit can help you decide.

What Extra Steps Does a Domain Change Need?

Moving to a new domain adds risk, because every URL changes at once. On top of the steps above:

• Verify both domains in Google Search Console before the move.
• Redirect every old URL to its matching page on the new domain, page by page.
• Use the Change of Address tool in Search Console for the old property once redirects are live. Google explains how in its Change of Address help page.
• Keep the old domain registered and its redirects running for the long term, so old links and bookmarks keep working.
• Update business listings and profiles so your name, address and website stay consistent everywhere. This matters for local SEO.

Avoid combining a domain change with a full redesign and new content at the same time if you can. Fewer simultaneous changes make problems easier to spot and fix.

What Website Migration Mistakes Should You Avoid?

• Bringing SEO in after the design is signed off. URL structure and content decisions are hardest to change late.
• Deleting "old" content without checking its traffic. An unglamorous page may be one of your best lead sources.
• Redirecting everything to the homepage. It is quick, but it throws away page-level relevance.
• Forgetting images, PDFs and subdomains. These can carry backlinks and traffic too.
• Launching without a rollback plan. Know how to restore the old site if something critical breaks.
• Stopping checks after week one. Problems can surface weeks later as Google re-crawls deeper pages. Our guide to common technical SEO issues covers many that show up after launch.

Conclusion

A redesign does not have to cost you traffic. A successful website migration comes down to knowing what you have before you start, telling search engines exactly where every page has moved, keeping the content and signals that earned your rankings, and watching closely after launch.

Treat this website migration SEO checklist as part of the project plan from day one, not a task for launch week. If you want experienced help, the Second Silicon Valley technical SEO team can benchmark your site, build your redirect map and monitor the move. Contact us for a free migration SEO review.