Website Migration SEO Checklist for Safe Moves

Last Updated on 27/06/2026

A website migration SEO checklist helps you move, redesign, replatform, or rename your website without losing rankings. It covers pre-migration audits, URL mapping, 301 redirects, staging checks, launch-day testing, Google Search Console updates, analytics validation, and post-migration monitoring.

A website migration can improve your brand, user experience, speed, structure, and conversions.

It can also damage your rankings if you move pages without protecting the SEO signals that already help your site perform.

The website migration SEO checklist below gives you a practical process to follow before, during, and after launch.

It is built for business owners, SEO teams, developers, agencies, and website managers who need a clear plan instead of vague migration advice.

At a minimum, your SEO migration checklist should cover:

• A full crawl of the old website
• Keyword and traffic benchmarks
• URL export and redirect mapping
• Metadata, headings, schema, and canonical checks
• Staging site SEO review
• Launch-day crawl testing
• Google Search Console migration steps
• XML sitemap update
• Post migration SEO audit
• 30, 60, and 90-day monitoring

Google recommends using the Change of Address tool only when moving a site from one domain or subdomain to another, and only after the move and redirects are in place.

Google also recommends keeping redirects for as long as possible, generally at least one year, when URLs change.

What Is Website Migration?

Website migration means making a major change to your website that can affect how search engines crawl, index, understand, or rank your pages.

That change might be technical, structural, visual, or brand-related.

You may be moving from WordPress to Shopify, changing your domain name, redesigning your website, switching from HTTP to HTTPS, moving to a new hosting provider, or changing your URL structure.

From an SEO point of view, a migration is risky because search engines need to understand what changed and where each old page now lives.

If that connection is broken, Google may treat important pages as missing, duplicated, blocked, weakened, or completely new.

A safe SEO website migration keeps the relationship between old and new pages clear.

Your goal is not just to launch a better site. Your goal is to preserve as much search equity as possible while improving the parts of the site that were holding you back.

A proper website migration SEO process protects:

• Organic rankings
• Indexed URLs
• Backlink value
• Internal link equity
• Metadata
• Content relevance
• Schema markup
• Canonical tags
• Image visibility
• Crawlability
• Conversion tracking
• Analytics accuracy

Many ranking drops after migration happen because teams treat the project as a design or development task only. SEO gets checked after launch, when the damage has already happened.

The safer approach is to treat migration as an SEO, development, content, analytics, and project management task from day one.

Types of Website Migration

Not every migration carries the same level of SEO risk. A simple hosting move where URLs stay the same is usually less risky than a full domain change, CMS migration, and redesign happening at the same time.

The more things you change at once, the more carefully you need to plan your technical SEO migration.

Domain Migration

A domain migration happens when you move from one domain to another, such as:

• oldbrand.com to newbrand.com
• example.net to example.com
• subdomain.example.com to example.com
• country-specific domains to one global domain

Domain migration SEO is high risk because every important URL changes. Google needs strong signals that the new domain replaces the old one.

You need accurate 301 redirect mapping, verified Google Search Console properties, updated XML sitemaps, updated internal links, and a Change of Address request when applicable.

The Change of Address tool is intended for domain or subdomain moves, not simple HTTP to HTTPS moves.

CMS Migration

A CMS migration means moving your site from one content management system to another.

Common examples include:

• WordPress to Webflow
• WordPress to Shopify
• Shopify to custom CMS
• Wix to WordPress
• Headless CMS migration

CMS migrations often create SEO issues because templates, URLs, metadata, canonical tags, schema, pagination, image paths, and internal links can change automatically.

Before launch, compare the old and new CMS output page by page. Do not assume the new platform handles SEO settings correctly by default.

Website Redesign Migration

A website redesign SEO checklist is essential when you change layouts, templates, navigation, content blocks, headings, or conversion paths.

A redesign can hurt SEO when important copy is removed, internal links disappear, headings are rewritten poorly, or pages become slower due to heavy media and scripts.

A redesign should improve user experience without weakening search intent. Before removing content, check whether that section helps the page rank.

URL Structure Migration

A URL migration checklist is needed when you change slugs, folders, categories, product URLs, blog URLs, or parameter handling.

Examples include:

• /blog/post-name/ to /resources/post-name/
• /product/category/item/ to /products/item/
• /services/seo-company/ to /seo-services/
• URLs with dates to clean evergreen URLs

URL changes require one-to-one redirects wherever possible. Do not redirect everything to the homepage.

Hosting, Protocol, or Server Migration

A hosting or server migration may not change visible URLs, but it can still affect SEO through speed, uptime, crawl access, SSL configuration, CDN behavior, and server response codes.

Google has separate guidance for hosting moves where user-visible URLs do not change. The main goal is to reduce disruption to crawling and performance.

Why SEO Drops During Website Migration

SEO can drop during migration because search engines rely on consistency. When URLs, content, links, code, and signals change at the same time, Google has to recrawl and reassess the site.

Some temporary fluctuation is normal. A serious traffic loss usually means something went wrong.

The most common causes of organic traffic loss during migration include:

• Missing 301 redirects
• Redirect chains or loops
• Important pages are returning 404 errors
• Robots.txt blocking crawlers
• Noindex tags left on live pages
• Canonical tags pointing to old URLs
• XML sitemap still listing old URLs
• Internal links still point to redirected URLs
• Metadata is missing from the new templates
• Headings changed without SEO review
• Content removed from ranking pages
• Schema markup removed or broken
• Slow page speed after redesign
• Tracking code missing after launch
• Staging site accidentally indexed
• Important images moved without redirects or alt text
• Backlinks pointing to dead pages
• Pagination, faceted navigation, or filters are mishandled

Ranking drops after migration are easier to prevent than to fix. That is why your site migration SEO checklist should start weeks before launch, not after your developer pushes the new site live.

Bad Website Migration vs SEO-Safe Website Migration

Website Migration SEO Checklist: Complete Table

Pre-Migration SEO Checklist

Your pre-migration work decides whether the launch is controlled or chaotic. This is where you capture the current SEO value of the website and create a clear migration plan.

Audit Your Current Website

Start by documenting the current state of the site. You need a reliable before-and-after comparison.

Audit:

• Organic landing pages
• Keyword rankings
• Indexed pages
• Backlinks
• Top converting pages
• Current URL structure
• Metadata
• H1 and H2 tags
• Internal links
• Canonical tags
• Schema markup
• XML sitemap
• Robots.txt
• Crawl errors
• Broken links
• Redirects already in place
• Page speed
• Mobile usability

Pay special attention to pages that drive revenue, leads, demo requests, product sales, or local enquiries. These pages need extra care during migration.

Do not rely only on the pages visible in your CMS. Many important URLs may exist outside your CMS, such as PDFs, old landing pages, campaign pages, product filters, author pages, tag pages, help pages, and legacy blog URLs.

Use multiple sources to build your full URL list:

• CMS export
• XML sitemap
• Google Search Console pages report
• GA4 landing page report
• Backlink export
• Crawl data
• Server logs, if available
• Paid search landing pages
• CRM or email campaign links

The goal is simple: no valuable URL should disappear without a plan.

Crawl and Export All URLs

Crawl your current site before anything changes. Save the crawl file in a shared migration folder.

Export these fields:

• URL
• Status code
• Indexability
• Title tag
• Meta description
• H1
• H2s
• Canonical URL
• Word count
• Internal links
• Inlinks
• Outlinks
• Structured data
• Image URLs
• Alt text
• Response time
• Redirect status

This crawl becomes your SEO backup. If something breaks after launch, you can compare the new site against the old version.

Also, crawl your XML sitemap separately. Compare sitemap URLs against crawlable URLs. If the sitemap includes redirected, non-canonical, noindex, or 404 pages, clean that up before migration.

Build Your 301 Redirect Mapping File

301 redirect mapping is one of the most important parts of any website migration SEO checklist.

A redirect map tells browsers and search engines where each old URL should go on the new website. Use permanent 301 redirects for URLs that have permanently moved.

Your redirect map should include:

• Old URL
• New URL
• Redirect type
• Page type
• Priority
• Traffic level
• Backlink count
• Notes
• QA status

Example:

Best practices for redirect mapping:

• Map each old URL to the closest relevant new page
• Avoid redirecting all old pages to the homepage
• Avoid redirect chains
• Avoid redirect loops
• Update internal links to final URLs
• Keep query parameters only when needed
• Test redirects before launch
• Prioritize pages with traffic, rankings, backlinks, and conversions

For deleted content, redirect only when there is a relevant replacement. If there is no useful alternative, a 404 or 410 may be more honest than sending users to an unrelated page.

Protect Metadata, Headings, Schema, Canonicals, Images, and Content

Migration often breaks SEO because teams focus on URLs and forget everything else.

Before launch, export and review:

• Title tags
• Meta descriptions
• H1 tags
• H2 and H3 structure
• Body content
• Internal links
• Image files
• Image alt text
• Schema markup
• Canonical tags
• Open Graph tags
• Breadcrumbs
• Pagination tags
• Hreflang tags, if used

Do not automatically copy everything if the old site had weak SEO. Migration is a good time to improve poor metadata, thin content, duplicate pages, and confusing navigation.

But be careful with pages that already rank well. If a page drives traffic, do not rewrite it heavily during migration unless you have a clear SEO reason.

For important pages, compare the old and new versions side by side:

• Does the page still answer the same search intent?
• Is the primary keyword still included naturally?
• Is the H1 still clear?
• Are important sections still present?
• Are FAQs, schema, and internal links preserved?
• Are images compressed and described properly?
• Does the canonical tag point to the final live URL?

This is especially important for a website redesign SEO checklist because design teams may remove copy to make pages cleaner. Cleaner is good only when the page still satisfies users and search engines.

Prepare Analytics, Tracking, and Benchmarks

Before launch, record your baseline performance. Without benchmarks, you cannot tell whether the migration caused a real SEO issue.

Track:

• Organic sessions
• Organic conversions
• Organic revenue
• Top landing pages
• Keyword rankings
• Branded vs non-branded traffic
• Indexed pages
• Crawl errors
• Backlink profile
• Core Web Vitals
• Form submissions
• Calls
• Demo requests
• Ecommerce transactions

Set up a simple migration dashboard in Looker Studio, GA4, or your SEO reporting tool.

At minimum, compare:

• Last 7 days
• Last 28 days
• Same period previous year, if seasonality matters
• Top 50 organic landing pages
• Top 50 keywords
• Top conversion pages

Also, annotate the migration date in your reporting tools. This makes future analysis much easier.

Staging Site SEO Checklist

Your staging site is where you catch migration problems before users and search engines see them.

What Developers Must Check Before Launch

A staging site should be accessible to your team but blocked from indexing. The safest option is password protection. Noindex tags can help, but they are not a complete substitute if pages are publicly accessible and linked.

Developers should check:

• Staging is blocked from search indexing
• Live URLs are not accidentally canonicalized to staging URLs
• All final URLs are crawlable
• Important pages return 200 status codes
• Redirects work in the staging or pre-launch environment
• No internal links point to staging URLs
• No internal links point to old URLs
• No key templates are missing metadata fields
• Canonical tags are self-referencing where appropriate
• XML sitemap includes only final indexable URLs
• Robots.txt is correct for launch
• Pagination works
• Filters and parameters are controlled
• Structured data is valid
• Images load from final paths
• Lazy loading does not hide important content
• JavaScript rendering does not block key content
• Forms work
• Tracking scripts fire correctly
• Page speed is acceptable
• Mobile layouts are usable
• 404 page works properly
• Server response codes are correct

A technical SEO migration should include a staging crawl and a manual page template review. Do not only test the homepage. Test service pages, product pages, blog posts, category pages, author pages, location pages, gated pages, and search result pages.

Platform-Specific Advice for WordPress, Shopify, Webflow, Custom CMS, and Domain Changes

Different platforms create different migration risks.

WordPress

Check permalink settings before launch. A small permalink change can alter every URL on the site. Use a reliable redirect plugin or server-level redirects where possible. Review SEO plugin settings in Yoast, Rank Math, or All in One SEO.

Watch for:

• Noindex settings copied from staging
• Missing title and meta templates
• Changed category or tag URLs
• Image attachment pages
• Broken shortcodes
• Page builder bloat
• Redirect plugin conflicts
• XML sitemap plugin conflicts

Shopify

Shopify has a specific URL structure for products, collections, pages, and blogs. You may not be able to fully replicate old URLs from another CMS.

Watch for:

• Product URLs
• Collection URLs
• Variant URLs
• Duplicate product paths
• Canonical behavior
• App-generated schema
• Redirect imports
• Theme speed
• Filtered collection pages
• Out-of-stock product handling

Create redirects for old product and category URLs before launch. For discontinued products, redirect to the closest category or replacement product when relevant.

Webflow

Webflow is flexible, but SEO mistakes often happen through CMS collections, slug changes, and staging domains.

Watch for:

• webflow.io staging URLs
• Collection page slugs
• Auto-generated sitemap settings
• Missing 301 redirects
• Canonical tags
• Custom code placement
• CMS field mapping
• Image compression
• Heading hierarchy

Make sure the live custom domain is the canonical version and that staging URLs are not indexable.

Custom CMS

A custom CMS gives you more control, but it also gives developers more responsibility.

Check that the CMS supports:

• Editable title tags
• Editable meta descriptions
• Editable H1s
• Canonical tags
• 301 redirects
• XML sitemap generation
• Robots.txt control
• Schema markup
• Alt text
• Breadcrumbs
• Pagination rules
• Hreflang, if needed
• Log file access

SEO should not depend on developers for every title, redirect, or canonical update after launch. Build SEO controls into the CMS where possible.

Domain Changes

For domain migration SEO, verify old and new domains in Google Search Console. After the move and redirects are live, use the Change of Address tool where appropriate. Google states that this tool is for moves from one domain or subdomain to another, and that HTTP to HTTPS moves do not require it.

Also update:

• Internal links
• Canonical tags
• XML sitemaps
• hreflang references
• Schema organization URLs
• Social profiles
• Paid ads
• Email templates
• CRM links
• Directory listings
• Important backlinks where possible

Launch-Day Website Migration SEO Checklist

Launch day should not be experimental. It should be a controlled release where every critical SEO item is checked quickly.

Use this launch-day checklist:

• Confirm DNS and hosting are working
• Confirm the SSL certificate is active
• Confirm the preferred domain version resolves correctly
• Check HTTP to HTTPS redirects
• Check www vs non-www redirects
• Push 301 redirects live
• Test top priority redirects manually
• Crawl the redirect list
• Crawl the new live site
• Check robots.txt
• Confirm no staging noindex tags are live
• Confirm canonical tags point to live URLs
• Confirm title tags and meta descriptions are present
• Confirm H1 tags are present
• Confirm XML sitemap update is live
• Submit sitemap in Google Search Console
• Inspect key URLs in Google Search Console
• Test GA4 tracking
• Test Google Tag Manager
• Test forms, calls, purchases, and lead events
• Test schema markup
• Check broken links
• Check 404 errors
• Check page speed
• Check mobile rendering
• Check important templates
• Check payment or checkout pages, if ecommerce
• Check login or account pages, if relevant

Use a priority URL list for launch-day testing. This should include:

• Homepage
• Main service pages
• Main product pages
• Top blog posts
• Top organic landing pages
• High backlink pages
• Lead generation pages
• Contact page
• Pricing page
• Location pages
• Category pages
• Conversion pages

Do not wait a week to run the first crawl. Crawl the site as soon as it is live.

Google Search Console Migration and Analytics Checks

Google Search Console migration checks help you understand how Google is reading the new site.

After launch, check:

• Sitemap submission status
• Indexing report
• Page indexing errors
• Crawl errors
• Soft 404s
• Redirect errors
• Server errors
• Duplicate pages
• Canonical selections
• Mobile usability
• Core Web Vitals
• HTTPS report
• Manual actions
• Security issues
• Search performance
• Top pages
• Top queries

For domain changes, verify both the old and new domain properties. Then use the Change of Address tool when the migration qualifies. Again, this is for domain or subdomain moves, not every type of migration.

In GA4 and analytics tools, check:

• Organic traffic is being recorded
• Conversions are firing
• Ecommerce tracking works
• Contact forms submit correctly
• Thank-you pages load
• Event tracking works
• Referral exclusions are correct
• Cross-domain tracking works, if needed
• UTM tracking still works
• CRM integrations are passing data
• Call tracking is active

A migration can look like an SEO failure when the real issue is broken tracking. Always confirm analytics before making traffic conclusions.

Post-Migration SEO Monitoring Plan

SEO migration does not end on launch day. The real test happens as Google recrawls old URLs, processes redirects, discovers new URLs, and updates rankings.

First 30 Days

The first month is about finding urgent problems fast.

Check daily or several times per week:

• Organic traffic
• Top landing pages
• Keyword rankings
• Crawl errors
• Broken links
• Redirect errors
• 404 pages
• Indexed pages
• Sitemap processing
• Server errors
• Conversion tracking
• Core Web Vitals changes

Run a full post-migration SEO audit within the first week.

Focus on:

• Top old URLs redirecting correctly
• New pages returning 200 status codes
• No important pages blocked by robots.txt
• No important pages marked noindex
• Canonicals pointing to the correct new URLs
• Internal links updated
• XML sitemap clean
• Metadata present
• Schema valid
• Content not missing
• Images loading correctly

A small ranking movement is normal. Large drops on important pages need immediate review.

Days 31 to 60

By the second month, you should have enough data to identify patterns.

Review:

• Pages that lost traffic
• Keywords that dropped
• Pages not indexed
• Redirected pages still receiving traffic
• 404s with backlinks
• Pages with weaker engagement
• Pages with lower conversions
• Internal link changes
• Crawl depth changes

This is where you start improving the weaker migrated pages. Do not change everything at once. Prioritize pages with high business value.

Useful actions include:

• Restoring removed content
• Improving internal links
• Fixing title tags
• Reworking headings
• Adding missing schema
• Updating redirects
• Fixing slow templates
• Consolidating duplicate pages
• Updating outdated content

Days 61 to 90

By 90 days, most healthy migrations should show clearer stabilization. Some large sites, ecommerce stores, and domain migrations may take longer.

At this stage, compare performance against your original benchmark.

Review:

• Organic traffic trend
• Non-branded keyword visibility
• Conversion recovery
• Indexed URL count
• Crawl error reduction
• Page speed improvements
• Revenue or lead impact
• Ranking distribution
• Backlink equity preservation
• Top page performance

Then decide whether the migration is stable or needs a deeper technical review.

Run another crawl and compare it against:

• Pre-migration crawl
• Staging crawl
• Launch-day crawl
• 30-day crawl

This gives you a clear view of what improved, what broke, and what still needs attention.

Recovery Steps If Traffic Drops After Migration

If you see ranking drops after migration, do not panic. Diagnose the cause before making broad changes.

Start with these recovery steps:

1. Check tracking first
   Confirm GA4, Google Tag Manager, CRM tracking, ecommerce tracking, and form tracking are working. A reporting issue can look like organic traffic loss.
2. Check Google Search Console
   Look for indexing issues, crawl errors, server errors, canonical problems, and sitemap warnings.
3. Review the top dropped pages.
   Compare the old and new versions. Check content, metadata, headings, internal links, schema, canonical tags, and page speed.
4. Test redirects
   Make sure old high-value URLs redirect to the correct new URLs with 301 redirects. Fix chains, loops, 302s, and irrelevant redirects.
5. Check robots.txt and the noindex tag
   A single bad directive can block important sections of the site.
6. Review canonical tags
   Make sure canonicals do not point to old URLs, staging URLs, HTTP URLs, or the wrong page.
7. Check internal links
   Update links so they point directly to the new final URLs instead of passing through redirects.
8. Find broken backlinks
   Use backlink tools to find old URLs with links that now return 404 errors. Add or fix redirects.
9. Restore lost content
   If ranking pages lost important sections, FAQs, comparison details, or supporting copy, restore or improve them.
10. Run a technical cra.wl
    Look for patterns across templates. One template issue can affect hundreds or thousands of pages.
11. Inspect pages manually
    Use Google Search Console URL Inspection for important pages. Check whether Google can crawl and index them.
12. Improve weak pages
    If the migration changed search intent alignment, update the page to better match the query.

Avoid making random sitewide changes. Fix the most likely causes first.

Common Website Migration SEO Mistakes

Most migration problems are preventable. The issue is usually not that the migration happened. The issue is that SEO was treated as a final QA task.

Avoid these common mistakes:

• Launching without a website migration SEO checklist
• Creating redirects after launch instead of before launch
• Redirecting all old URLs to the homepage
• Using 302 redirects instead of 301 redirects for permanent moves
• Ignoring old URLs with backlinks
• Forgetting to update internal links
• Leaving staging noindex tags on live pages
• Blocking the live site in robots.txt
• Allowing staging URLs to be indexed
• Removing ranking content during redesign
• Changing titles and H1s without SEO review
• Losing schema markup
• Setting canonical tags incorrectly
• Forgetting the XML sitemap update
• Not submitting the new sitemap
• Not using Google Search Console migration tools for domain moves
• Not testing mobile pages
• Not checking page speed
• Breaking forms or conversion tracking
• Not monitoring the site after launch
• Assuming traffic will recover without investigation

A good SEO migration checklist creates accountability. Everyone knows what must be done, who owns it, and when it must be checked.

Pros and Cons of Website Migration

Website migration is not always bad for SEO. In many cases, it is necessary. The key is understanding both the upside and the risk.

The best reason to migrate is not that the site looks old. The best reason is that the new website will be easier to use, easier to manage, easier to crawl, faster, clearer, and better aligned with your business goals.

Final Thoughts

A website migration can either strengthen your SEO foundation or damage years of organic growth. The difference is planning.

Use this website migration SEO checklist before you change your domain, redesign your site, move to a new CMS, restructure URLs, or relaunch your website.

Start with a full audit, protect your best-performing pages, build a detailed 301 redirect mapping file, test everything on staging, check every critical item on launch day, and monitor performance for at least 90 days.

The safest migrations are not rushed. They are documented, tested, and measured.

If you are planning a redesign, domain change, or CMS migration, follow this website migration SEO checklist before launch to protect your rankings, traffic, and leads.

For expert support with SEO website migration, technical SEO migration, or a post-migration SEO audit, MarketingLad.io can help you plan the move without putting your organic growth at risk.

Frequently Asked Questions