Website Migration SEO Checklist: How to Migrate Without Losing Rankings

A website migration is one of the highest-risk activities in SEO. When executed poorly, migrations can wipe out years of organic growth in a matter of days. Traffic drops of 30–60% are common after botched migrations, and some businesses never fully recover.

Yet migrations are often unavoidable. You might be moving to a new CMS, redesigning your site, changing your domain name, switching from HTTP to HTTPS, merging multiple sites, or restructuring your URL architecture. Each of these scenarios carries SEO risk — but that risk is entirely manageable with proper planning and execution.

This website migration SEO checklist covers every critical step, from pre-migration planning through to post-launch monitoring. Whether you are handling the migration in-house or working with a web design and technical SEO team, use this checklist to protect your rankings, traffic, and link equity.

Types of Website Migrations

Not all migrations carry the same level of SEO risk. Understanding the type of migration you are undertaking helps you calibrate your effort appropriately.

Platform or CMS Migration

Moving from one content management system to another — for example, from WordPress to Webflow, or from a custom-built site to Shopify. This is one of the most common migration types and carries moderate-to-high risk because URL structures, page templates, and internal linking often change significantly.

Domain Migration

Changing your domain name entirely — for example, from oldbrand.com.sg to newbrand.com.sg. This is the highest-risk migration type because all link equity must be transferred from the old domain to the new one, and search engines need time to recognise the new domain as authoritative.

Protocol Migration (HTTP to HTTPS)

Moving from HTTP to HTTPS. This is relatively low risk if done correctly, as Google treats HTTPS as a ranking signal. However, incorrect implementation — such as mixed content, broken redirects, or missing HSTS headers — can still cause problems.

Site Restructure

Changing your URL architecture, navigation, or information hierarchy without changing the platform or domain. This includes flattening your URL structure, reorganising categories, or consolidating pages. Risk varies depending on how many URLs change.

Site Consolidation or Merger

Merging two or more websites into a single domain. Common in acquisitions or when businesses consolidate multiple regional sites. This requires careful redirect mapping and content deduplication.

Regardless of the type, every migration that changes URLs requires the same core SEO checklist. The depth of each step may vary, but none should be skipped.

Pre-Migration Planning and Audit

The most important work happens before any code is written or any DNS record is changed. Thorough pre-migration planning is the single greatest factor in migration success.

Benchmark Current Performance

Before you change anything, document your current SEO performance in detail. You need these benchmarks to measure post-migration success and to identify any issues quickly.

Organic traffic: Monthly organic sessions for the past 12 months, broken down by landing page
Keyword rankings: Current rankings for your target keywords, especially those driving significant traffic
Indexed pages: Total pages indexed in Google (use the site: operator and Search Console)
Backlink profile: Full list of external links pointing to your site, with destination URLs
Top-performing pages: Pages generating the most organic traffic, conversions, and backlinks
Core Web Vitals: Current LCP, INP, and CLS scores
Crawl data: A complete crawl of your current site using Screaming Frog or a similar tool

Inventory All URLs

Create a comprehensive list of every URL on your current site. This includes:

All pages (including those not in the navigation)
All blog posts and articles
All media files (PDFs, images, videos)
All URL variations (with/without trailing slash, www vs non-www)
All URLs receiving organic traffic (check Search Console)
All URLs with external backlinks (check Ahrefs or SEMrush)

This URL inventory is the foundation of your redirect mapping. Missing URLs from this inventory means missing redirects — and missing redirects mean lost rankings and broken user experiences.

Identify Priority Pages

Not all pages are equally important. Identify your priority pages — those that drive organic traffic, have backlinks, or generate conversions. These pages require extra attention during migration. Verify that their content, meta data, and internal linking are preserved exactly.

URL Mapping and Redirect Strategy

URL mapping and redirects are the most critical technical element of any website migration. Errors here directly cause ranking losses.

Create a Complete URL Map

Build a spreadsheet mapping every old URL to its corresponding new URL. The map should include:

Old URL (full path)
New URL (full path)
Page title
Organic traffic (monthly)
Number of backlinks
Redirect type (301 permanent redirect in almost all cases)
Notes (e.g., “content merged with another page”)

Redirect Rules

Follow these principles for your redirect strategy:

Use 301 redirects: Permanent (301) redirects pass the most link equity. Use 302 redirects only for genuinely temporary moves.
Map one-to-one: Every old URL should redirect to the most relevant new URL. Redirecting everything to the homepage is lazy and destroys rankings.
Avoid redirect chains: If old URL A already redirects to B, and B is now moving to C, update the redirect so A goes directly to C.
Handle parameters: If your old site uses URL parameters (e.g., ?category=seo), ensure these are handled in your redirect rules.
Redirect all variations: Include redirects for both www and non-www versions, HTTP and HTTPS versions, and trailing-slash and non-trailing-slash versions.

For guidance on managing URL canonicalisation during and after migration, refer to our canonical tags SEO guide.

Test Redirects Before Launch

Set up your redirects on a staging environment and test a representative sample. At minimum, test all priority pages, all pages with backlinks, and a random sample of other pages. Use a tool like Screaming Frog to crawl the old URL list against the staging server and verify that every redirect resolves correctly.

Technical SEO Migration Checklist

Beyond redirects, several technical SEO elements must be addressed during migration. Use this checklist to ensure nothing is missed.

XML Sitemaps

Generate a new XML sitemap reflecting the new URL structure
Submit the new sitemap to Google Search Console immediately after launch
Keep the old sitemap accessible for a few weeks to help Google discover the redirects
Ensure the new sitemap contains only 200-status URLs (no redirects, no 404s)

Robots.txt

Ensure the new site’s robots.txt does not block important pages or resources
Verify that CSS, JavaScript, and image files are not blocked from crawling
Reference the new sitemap URL in the robots.txt file
Do not block the old site from crawling — Google needs to follow the redirects to discover the new URLs

Canonical Tags

Update all canonical tags to reference the new URLs
Verify that canonical tags are self-referencing on the new site (each page’s canonical points to itself)
Ensure no canonical tags point to old URLs or redirecting URLs

Internal Linking

Update all internal links to point directly to the new URLs (do not rely on redirects for internal links)
Check navigation menus, footer links, sidebar links, and in-content links
Verify that breadcrumb navigation reflects the new site structure

Structured Data

Migrate all structured data (Schema.org markup) to the new site
Update any URLs referenced in structured data to the new format
Test structured data using Google’s Rich Results Test after launch

Hreflang Tags (If Applicable)

Update all hreflang annotations to reference the new URLs
Verify that hreflang tags are consistent across all language/region versions

For a comprehensive list of technical SEO considerations beyond migration, see our technical SEO checklist.

Content and On-Page SEO Preservation

Migrations often coincide with redesigns, and redesigns often involve content changes. While refreshing content can be beneficial, making too many changes simultaneously makes it impossible to diagnose problems if rankings drop.

Preserve Key On-Page Elements

For priority pages, preserve the following elements during migration:

Title tags: Keep the same title tags unless you have a specific reason to change them
Meta descriptions: Maintain existing meta descriptions for pages ranking well
H1 tags: Keep the same primary heading on each page
Body content: Do not significantly rewrite content on pages that are ranking well
Image alt text: Ensure all image alt attributes are migrated
Internal link anchor text: Maintain the same anchor text patterns

Content Consolidation

A migration is a good opportunity to consolidate thin or duplicate content. If you have multiple pages targeting the same keyword, merge them into a single, stronger page and redirect the others. However, document every consolidation decision so you can trace any ranking changes back to specific actions.

Handling Removed Pages

If you are removing pages during migration (which is common during a website redesign), redirect them to the most relevant remaining page. Only use a 410 (Gone) status if the content is truly obsolete and there is no relevant alternative page. Never let removed pages return a 404 without a redirect, especially if they have backlinks or organic traffic.

Launch Day Process

Launch day is when preparation meets execution. A structured launch process minimises the chance of errors slipping through.

Pre-Launch Final Checks

Crawl the staging site one final time and compare against the old site crawl
Verify all redirects are working correctly
Confirm robots.txt is not blocking critical pages
Test the new XML sitemap for errors
Verify canonical tags on key pages
Check that Google Analytics and other tracking codes are installed correctly
Verify Google Search Console is set up for the new domain (if domain is changing)
Test page load speed on the new site

Launch Sequence

Deploy the new site
Activate all 301 redirects
Submit the new XML sitemap to Google Search Console
If changing domains, use Google Search Console’s Change of Address tool
Request indexing for priority pages through Search Console
Monitor server logs for crawl errors in real time
Spot-check a sample of redirects, pages, and functionality

Immediate Post-Launch Validation

Within the first 24 hours after launch:

Check Google Search Console for crawl errors, coverage issues, and indexing problems
Monitor server response codes for 404s, 500s, and redirect loops
Verify that Google is discovering and crawling the new URLs
Test critical user journeys (navigation, forms, checkout if applicable)
Confirm that analytics data is being collected accurately

Post-Migration Monitoring

The weeks following a migration are critical. Even a well-executed migration will show some temporary ranking fluctuations as Google reprocesses your site. The key is distinguishing between normal fluctuations and genuine problems.

Week 1: Daily Monitoring

Check organic traffic daily against pre-migration benchmarks
Monitor keyword rankings for priority terms
Review Search Console for new crawl errors
Check server logs for persistent 404s
Verify that Google is indexing new URLs (check the “Coverage” report)

Weeks 2–4: Weekly Monitoring

Compare weekly organic traffic to the same week in prior months
Track the number of indexed pages — it should stabilise near the pre-migration count
Monitor backlink data to ensure link equity is being attributed to new URLs
Check for any remaining old URLs that are still indexed (and should not be)

Months 2–3: Stabilisation

Most well-executed migrations recover to pre-migration traffic levels within four to eight weeks. Some see improvements if the new site is faster, better structured, or has better content. If traffic has not recovered after eight weeks, there is likely a technical issue that needs investigation.

Key metrics to track during stabilisation:

Organic traffic compared to pre-migration baseline
Keyword ranking positions for priority terms
Pages indexed versus pages submitted in sitemap
Crawl budget usage (pages crawled per day)
Core Web Vitals scores

What to Do If Rankings Drop

If you experience a significant and sustained traffic drop after migration, here is a systematic approach to diagnosis and recovery.

Step 1: Check for Technical Errors

The most common cause of post-migration ranking loss is technical errors:

Broken redirects (301s returning 404 or redirecting to wrong pages)
Redirect chains or loops
Canonical tags pointing to old URLs
Robots.txt blocking important pages
Noindex tags accidentally applied to pages
Missing or incorrect XML sitemap

Step 2: Compare Before and After

Crawl the new site and compare it to your pre-migration crawl. Look for differences in page count, title tags, meta descriptions, heading structure, internal links, and canonical tags. Any unexpected differences could be causing problems.

Step 3: Check Backlink Attribution

Verify that external links are being properly redirected and that link equity is flowing to the new URLs. Use Ahrefs or SEMrush to check whether backlinks to old URLs are being followed through to new URLs.

Step 4: Review Content Changes

If content was changed during migration, compare the old and new versions of pages that lost rankings. Sometimes seemingly minor content changes — a different H1, removed paragraphs, or restructured sections — can affect rankings.

If you need expert assistance with a problematic migration, our SEO services team can conduct a full migration audit and recovery plan.

Soalan Lazim

How long does it take for rankings to recover after a website migration?

A well-executed migration typically sees rankings stabilise within four to eight weeks. Some fluctuation during the first two weeks is normal as Google reprocesses your site. If rankings have not recovered after eight to twelve weeks, there is likely a technical issue — such as broken redirects, incorrect canonical tags, or accidentally blocked pages — that needs to be identified and fixed.

Should I change my content during a website migration?

We strongly recommend against making significant content changes during a migration. Changing URLs, design, and content simultaneously makes it impossible to diagnose the cause of any ranking changes. Complete the migration first, verify that rankings have stabilised, and then make content improvements incrementally so you can measure their impact independently.

How long should I keep redirects active after a migration?

Keep 301 redirects active indefinitely, or at minimum for two years. Google has confirmed that it takes time for link equity to be fully transferred through redirects. Removing redirects prematurely results in 404 errors for any external links pointing to old URLs, which means losing the link equity those backlinks provide.

Do I need to notify Google about a website migration?

Yes. Submit your new XML sitemap through Google Search Console immediately after launch. If you are changing domains, also use the Change of Address tool in Search Console. These steps help Google discover your new URLs and process your redirects more quickly. You should also request indexing for your most important pages individually.

Can a website migration actually improve SEO performance?

Yes, if the migration addresses existing technical issues. Moving to a faster hosting environment, adopting a cleaner URL structure, consolidating thin content, improving mobile responsiveness, and fixing crawlability issues can all result in improved rankings after the migration stabilisation period. The key is ensuring these improvements do not come at the cost of broken redirects or lost content.

Website Migration SEO Checklist: How to Migrate Without Losing Rankings