Website Migration SEO Checklist: How to Redesign Without Losing Rankings

A website redesign does not have to destroy your organic rankings. The safest approach is to document what currently performs, preserve valuable content and URLs, map every necessary redirect, test the new site before launch, and monitor search performance closely after migration.

The biggest migration risk is not the new design itself. Ranking losses are often caused by missing pages, changed content, broken internal links, incorrect redirects, blocked crawling, conflicting canonical tags or weaker page templates.

Use this website migration SEO checklist to protect your traffic before, during, and after launch.

Website Migration SEO Checklist: Quick Overview

A temporary fluctuation in rankings is normal while Google recrawls and processes changed URLs; how long that takes depends on your site's size and the scope of the changes, covered in detail later in this guide.

How Do You Redesign a Website Without Losing SEO?

To redesign a website without losing SEO, preserve high-performing URLs and content, map changed URLs with permanent redirects, maintain important internal links and metadata, test crawlability on staging, verify canonicals and tracking before launch, and monitor Search Console closely after the new site goes live.

What Is an SEO Website Migration?

An SEO website migration is any substantial website change that can affect how search engines crawl, understand, index or rank its pages.

Common website migrations include:

• Moving to a new domain
• Changing the CMS or ecommerce platform
• Redesigning the website
• Changing URL structures
• Combining multiple websites
• Moving from HTTP to HTTPS
• Changing hosting providers
• Moving content between subdomains and folders
• Rebuilding the website using a new framework
• Consolidating or deleting large numbers of pages

A redesign can become an SEO migration even when the domain remains unchanged. New templates, navigation, copy, headings, internal links, JavaScript rendering and page speed can all affect organic performance.

Pre-Migration SEO Checklist

Benchmark and Audit the Existing Website

Before changing the site, create a clear record of its current SEO performance. This gives you a baseline for measuring the migration and helps identify the pages that need the most protection.

Record:

• Organic traffic and keyword rankings
• Leads, sales and other conversions
• Top organic landing pages
• Pages with strong backlinks
• Indexed and indexable URLs
• Crawl errors, redirects and broken links
• Core Web Vitals and page-speed performance

Export Your Search Console Data

Before the migration, export your existing Google Search Console performance data so you have a reliable baseline for comparison after launch.

Save data for:

• Top organic queries
• Highest-performing landing pages
• Clicks and impressions
• Average positions
• Indexing and coverage issues
• Pages receiving the most organic visibility

Google Search Console retains a limited amount of historical performance data, and a domain change can split reporting between old and new properties. Keeping your own export makes it easier to measure ranking, traffic and visibility changes after migration.

Crawl and Inventory the Existing Website

Run a full crawl of the current website before making structural or URL changes. This creates a record of the site's existing SEO setup and helps prevent valuable pages or signals from being lost during migration.

Export and review:

• URLs and status codes
• Title tags and meta descriptions
• H1 and other important headings
• Canonical tags
• Internal links
• Indexability settings
• Redirects and broken links
• Structured data
• Crawl depth

Then group pages by SEO and business value. Prioritise URLs that generate organic traffic, conversions, keyword rankings or backlinks.

These high-value pages should be preserved wherever possible and tested individually before and after launch. Outdated, duplicate or low-value pages can be consolidated or removed, but only after confirming that they do not support important rankings, backlinks or conversions.

Preserve Valuable URLs and Plan Redirects

Do not change URLs simply because the website is being redesigned. Keeping established URLs reduces migration risk and preserves the signals those pages have already built.

Change a URL only when there is a clear structural, usability or consolidation reason.

For every URL that must change, create a page-to-page redirect map containing:

• The current URL
• The new destination
• The required redirect type
• The page’s traffic, rankings and backlinks
• The person responsible for implementation
• Testing status

Use permanent 301 or 308 redirects to send each old URL directly to its closest relevant replacement. Avoid redirecting large groups of unrelated pages to the homepage, and avoid redirect chains where one old URL passes through several destinations before reaching the final page.

The new destination should also preserve the original page’s search intent and important content. A redirect cannot protect rankings if a detailed, useful page is replaced by a thin or unrelated destination.

Before launch, compare high-value old and new pages for:

• Main topic and search intent
• Important products or services
• Headings and supporting sections
• Metadata
• Internal links
• Calls to action
• Structured data
• Trust and conversion elements

The objective is to improve the website without removing the information and relevance that helped its pages rank.

Audit the Staging Website

Before launch, crawl and review the staging website as if it were already live. This is the best opportunity to identify problems without affecting users or search visibility.

Check that the new site preserves:

• Main navigation links
• Breadcrumbs
• Contextual internal links
• Product, service and category relationships
• Blog-to-service links
• Footer navigation
• Crawl depth
• Important conversion paths

Update all internal links so they point directly to the final production URLs. Do not rely on redirects to correct links within the new website.

Also review every major page template for:

• Title tags
• Meta descriptions
• H1 headings
• Canonical tags
• Structured data
• Image alt text
• Hreflang annotations
• Indexability
• Mobile layout
• Forms and calls to action

The staging environment should remain protected from search indexing during development. However, any temporary noindex directives, password restrictions or robots.txt blocks must be documented so they can be removed at launch.

Pay particular attention to staging-domain references. Canonical tags, internal links, image paths and structured data should not point to the development website once the site goes live.

Test Performance, Tracking and Technical SEO

A visually improved website can still perform worse if the redesign introduces slow templates, heavy scripts or broken tracking.

Test page speed across several templates, not only the homepage. Include:

• Service pages
• Product or category pages
• Blog posts
• Contact pages
• Conversion landing pages
• Checkout pages, where applicable

Review the main Core Web Vitals:

• Largest Contentful Paint: How quickly the main content appears
• Interaction to Next Paint: How responsive the page feels
• Cumulative Layout Shift: How stable the layout remains while loading

Look for oversized images, unnecessary scripts, autoplay media, slow fonts, excessive tracking tags and third-party tools that delay page loading.

Before launch, also confirm that the new site retains:

• Google Analytics tracking
• Google Tag Manager
• Form-submission tracking
• Call tracking
• Ecommerce tracking
• Advertising pixels
• Cookie consent settings
• CRM integrations
• Google Search Console verification

Complete test form submissions and conversions on staging wherever possible. Record the expected behaviour so the team can quickly confirm that tracking still works after launch.

Launch-Day SEO Checklist

Launch day should follow an approved checklist rather than relying on memory.

Complete these checks as soon as the new site goes live:

Activate and Test Redirects

• Implement all approved 301 or 308 redirects.
• Test high-value URLs manually.
• Crawl the full list of old URLs.
• Confirm each redirect reaches the final page directly.
• Check for redirect loops and chains.
• Confirm destination pages return a 200 status code.

Remove Staging Restrictions

• Remove temporary noindex
• Remove staging password protection.
• Check the live robots.txt file.
• Confirm important CSS, JavaScript and image files are crawlable.
• Check for X-Robots-Tag headers blocking indexing.

Check Canonical Tags

Every indexable page should reference its final production URL. This one gets missed constantly: developers copy a staging build to production and forget to update the canonical tags, so live pages quietly tell Google their staging-domain twin is the "real" version and Google can start indexing (or ignoring) the wrong URL entirely.

Check for canonicals pointing to:

• The staging domain
• The old domain
• HTTP versions
• Redirected URLs
• Unrelated pages

Redirects, internal links, canonicals and XML sitemaps should all support the same preferred URL.

Publish and Submit the XML Sitemap

The new XML sitemap should contain only:

• Live production URLs
• Indexable pages
• Canonical URLs
• Pages returning a 200 status code

Remove redirected, broken, duplicate and noindex URLs from the sitemap.

Submit the sitemap through Google Search Console after launch.

Crawl the Live Website

Run a full crawl and compare it with the staging and pre-migration crawls.

Look for unexpected changes in:

• Indexable page count
• Status codes
• Internal links
• Metadata
• Canonical tags
• Structured data
• Hreflang
• Crawl depth
• Orphan pages

Verify Tracking and Conversions

Test important user actions on the live site:

• Contact forms
• Phone-number clicks
• Purchases
• Quote requests
• Downloads
• Newsletter sign-ups
• Live chat
• Key buttons and calls to action

Confirm that traffic and conversions are recorded under the correct website property.

Use the Change of Address Tool When Required

Use Google Search Console’s Change of Address tool when the website moves to a different domain or subdomain.

It is not normally required for:

• A redesign on the same domain
• URL changes within the same domain
• HTTP-to-HTTPS moves
• Hosting changes where URLs remain unchanged

The tool supports a domain move, but it does not replace redirects, sitemaps or technical migration work.

Post-Migration SEO Checklist

Monitor SEO Performance After Migration

Migration work does not end when the website launches. The first few days and weeks are critical for identifying issues before they cause long-term losses.

Monitor the website after:

• 24 hours
• 3 days
• 7 days
• 14 days
• 30 days
• 60 days
• 90 days

Track:

• Organic clicks and impressions
• Keyword rankings
• Organic landing-page traffic
• Leads, sales and conversions
• Indexed-page count
• 404 errors
• Server errors
• Redirect failures
• Canonical selection
• Core Web Vitals
• Crawl activity

Monitor performance by page group rather than looking only at total traffic.

For example, compare:

• Service pages
• Product or category pages
• Blog content
• Location pages
• High-converting landing pages

Total traffic may appear stable while an important commercial section loses rankings.

Investigate quickly when:

• A valuable directory disappears from search
• 404 errors increase sharply
• Google selects unexpected canonical URLs
• Rankings transfer to the wrong pages
• Conversions fall despite stable traffic
• Important pages become excluded from indexing
• Redirect chains continue to be crawled

Keep migration redirects active for at least one year. In many cases, useful redirects should remain permanently because old backlinks, bookmarks and documents may continue sending visitors to previous URLs.

Also contact the owners of important backlinks and ask them to update links to the final URLs. Prioritise links from publications, directories, partners and high-traffic referral sources.

How Long Does SEO Recovery Take After a Website Migration?

There is no fixed recovery period.

The timeline depends on:

• Website size
• Number of changed URLs
• Server performance
• Crawl frequency
• Redirect quality
• Internal linking
• Content changes
• Domain history
• Technical errors
• Backlink strength

Google states that many pages on a medium-sized site may take several weeks to move in its index, while large websites can take longer. Rankings can fluctuate during this processing period.

A migration with unchanged URLs and strong technical execution may stabilize quickly. A domain move involving thousands of changed pages will normally require more time and monitoring.

When Should You Delay the Launch?

Delay the migration when:

• The redirect map is incomplete
• Priority pages have missing content
• Tracking is not working
• The live robots.txt file is unknown
• Canonicals point to staging or old URLs
• Forms or checkout are failing
• The sitemap contains incorrect URLs
• The new server cannot handle expected traffic
• No rollback plan exists
• Key stakeholders have not approved SEO testing

A delayed launch is inconvenient. An avoidable organic traffic collapse is more expensive.

Need Help With Your Website Migration?

A poorly planned migration can create long-term ranking and traffic problems. BridgeWay Digital plans and executes migrations with 1:1 redirect mapping, staging audits and 90-day post-launch monitoring to reduce the risk of avoidable SEO losses.

Talk to us before you launch.

Final Website Migration SEO Checklist

Before approving launch, confirm that:

• Performance baseline saved
• Existing website crawled
• Search Console data exported
• High-value URLs identified
• Redirect map completed
• Content/search intent preserved
• Internal links updated
• Staging site crawled
• Canonicals checked
• Noindex/staging restrictions documented
• Analytics and conversion tracking tested
• XML sitemap validated
• Permanent redirects activated
• Live site recrawled
• Search Console sitemap submitted
• Domain Change of Address completed when applicable
• Indexing/rankings monitored
• Redirects retained for at least one year

Following a structured website migration SEO checklist cannot remove every possibility of ranking movement. It can prevent the technical, content and planning mistakes that turn manageable fluctuations into long-term traffic loss.

Frequently Asked Questions

Does Website Migration Affect SEO?

Yes. A migration can affect crawling, indexing, internal links, content relevance, backlinks, page experience and canonical signals. Careful planning reduces the risk of permanent losses.

How Do You Redesign a Website Without Losing SEO?

Preserve valuable URLs and content, map necessary redirects, maintain internal links, test the staging site, remove indexing blocks at launch and monitor performance after deployment.

Do 301 Redirects Preserve SEO Value?

Google states that permanent redirects such as 301 and 308 redirects do not cause a loss of PageRank. They must still point to accurate, relevant and working destinations.

Should URLs Change During a Website Redesign?

Only when there is a meaningful structural or usability reason. Keeping established URLs reduces migration complexity and preserves existing signals.

How Long Should Website Migration Redirects Remain?

Google recommends keeping them for at least one year and as long as possible. Many businesses keep useful redirects indefinitely to support old links and bookmarks.