The Website Migration Guide: SEO Strategy, Process, & Checklist – Moz

What Is a Website Migration?

A website migration is any major change to a site that can affect how search engines crawl, index, understand, or rank its pages. It is not limited to moving from one domain to another. A migration may involve changes to URLs, design, content, platform, hosting, internal linking, metadata, structured data, navigation, or site architecture.

In SEO terms, a migration is risky because search engines rely on consistency. They discover URLs, evaluate content, follow links, assign signals, and build a picture of your website over time. When you change that picture suddenly, you must give search engines very clear instructions. Otherwise, they may treat your new site like a suspicious stranger wearing your old site’s jacket.

Common Types of Website Migrations

• Domain migration: Moving from example.com to newexample.com.
• Protocol migration: Moving from HTTP to HTTPS.
• CMS migration: Moving from WordPress to Shopify, Webflow, HubSpot, Drupal, or another platform.
• URL structure migration: Changing folders, slugs, parameters, or permalink formats.
• Redesign migration: Launching a new design that changes templates, internal links, content blocks, or page hierarchy.
• Content consolidation: Merging several pages, blogs, subdomains, or entire websites.
• International migration: Changing hreflang, country folders, subdomains, or regional targeting.

Why Website Migrations Hurt SEO When They Go Wrong

Most SEO migration disasters are not caused by “Google being moody.” They are caused by preventable issues: missing redirects, blocked crawlers, deleted content, changed metadata, weak internal linking, slow pages, duplicate URLs, broken canonicals, and poor launch monitoring.

Search engines need to understand that old URLs have permanently moved to new URLs. Users need to land on relevant pages instead of error screens. Analytics tools need to keep tracking. Your highest-value content needs to stay discoverable. Your developers need a redirect map, not a vague Slack message that says, “Can we just redirect the old stuff somehow?” That way lies chaos, and possibly coffee stains on the project plan.

The Main SEO Risks

• Organic traffic drops after launch
• Keyword rankings fluctuate or disappear
• Backlink equity is lost through missing or irrelevant redirects
• Important pages return 404, 500, or soft 404 errors
• Search engines index staging URLs or duplicate versions
• Canonical tags point to old or incorrect URLs
• XML sitemaps contain outdated or non-indexable pages
• Robots.txt or noindex tags accidentally block key content
• Analytics, conversion tracking, and pixels stop firing

SEO Migration Strategy: Start Before Anyone Touches the Site

The best website migration SEO strategy begins early. Not two days before launch. Not after the designer says, “Surprise, we changed all the URLs.” Not when traffic has already dropped 48% and everyone is making the same face as a cat at bath time.

SEO should be part of discovery, planning, design, development, QA, launch, and post-launch measurement. A migration is not just a technical checklist. It is a cross-functional project involving SEO specialists, developers, designers, content teams, analytics teams, product owners, executives, and sometimes the brave soul who still knows where the old XML sitemap lives.

Define the Migration Goals

Before building a checklist, define why the migration is happening. Are you improving performance? Rebranding? Moving to a better CMS? Consolidating multiple sites? Cleaning up messy URLs? Expanding internationally? Each goal affects SEO priorities.

For example, a domain migration requires careful use of permanent redirects, Search Console verification, and change-of-address processes. A CMS migration requires template checks, metadata preservation, internal link updates, and structured data validation. A redesign may require content parity checks so the new “minimalist” design does not accidentally remove the paragraphs that helped pages rank.

Create SEO Benchmarks

Benchmarks are your before photo. Without them, you cannot prove whether the migration succeeded, failed, or merely sneezed.

• Organic sessions and users
• Revenue, leads, sign-ups, or conversions from organic search
• Keyword rankings for priority terms
• Top landing pages from organic search
• Indexed pages
• Crawl errors and coverage issues
• Backlink profile and linked-to URLs
• Core Web Vitals and page speed metrics
• Current metadata, canonical tags, headings, and schema markup

Pre-Migration SEO Process

The pre-migration phase is where most of the SEO protection happens. Launch day should be boring. Boring is beautiful. Boring means you planned well. Exciting launch days are for fireworks, not for discovering your robots.txt file blocks the entire website.

1. Crawl the Existing Website

Start by crawling the current site with a crawler such as Screaming Frog, Sitebulb, Semrush Site Audit, or a similar technical SEO tool. Export every indexable URL, status code, title tag, meta description, H1, canonical tag, word count, internal link count, structured data type, image URL, and redirect.

Do not rely only on your sitemap. Sitemaps often miss old landing pages, orphan URLs, PDFs, image assets, parameter URLs, and forgotten campaign pages that still receive backlinks or traffic. Combine crawl data with Google Search Console, Bing Webmaster Tools, analytics data, server logs, backlink tools, and CMS exports.

2. Build a Complete URL Inventory

Your URL inventory is the foundation of the redirect map. It should include all URLs that matter, not only the pages your team remembers. Add URLs from:

• Current crawl exports
• XML sitemaps
• Google Search Console performance reports
• Bing Webmaster Tools reports
• Google Analytics or other analytics platforms
• Backlink tools such as Ahrefs, Semrush, or Majestic
• Paid search landing pages
• Email campaign URLs
• PDFs, images, videos, and other indexed assets

3. Prioritize High-Value Pages

Not every page has the same SEO value. Some pages drive revenue, earn backlinks, rank for competitive keywords, attract qualified leads, or support the buyer journey. Mark these pages as high priority.

During migration, high-value pages should receive extra QA. Their content, metadata, internal links, schema, canonical tags, and redirects must be checked carefully. If a top-performing guide currently ranks because it answers a search query in depth, replacing it with three vague sentences and a hero image of smiling coworkers is not a redesign. It is an SEO crime scene.

4. Map Old URLs to New URLs

The redirect map is the heart of SEO migration. Every old URL that changes should map to the most relevant new URL using a permanent redirect. Avoid redirecting everything to the homepage. That may be easy, but it tells search engines and users, “We lost your page, please enjoy our lobby.”

Good redirect mapping follows relevance. A discontinued product page may redirect to the closest replacement product or category. An old blog post may redirect to an updated version of the same topic. A merged service page may redirect to the consolidated service page. If no relevant replacement exists and the page has no meaningful traffic, links, or business value, a 404 or 410 may be acceptable.

5. Preserve Metadata and On-Page Signals

During redesigns and CMS migrations, title tags, meta descriptions, headings, alt text, copy, internal links, and structured data can disappear. Sometimes this happens because templates were rebuilt. Sometimes it happens because someone thought “clean design” meant “remove all the words.” Search engines, tragically, are not mind readers.

Export old metadata and compare it with the staging site. Important pages should retain or improve their title tags, headings, body content, image alt text, canonical tags, and schema markup. This does not mean every word must remain identical, but the page should continue satisfying the same search intent.

6. Audit the Staging Site

The staging environment should be blocked from indexing but available for QA. Use password protection or proper access controls. Be careful with noindex tags and robots.txt rules because these can accidentally move to production. The phrase “we launched with noindex on everything” is short, but the emotional damage is long.

Crawl the staging site to check status codes, indexability, internal links, canonicals, redirects, metadata, structured data, pagination, hreflang, XML sitemaps, robots.txt, mobile rendering, and page speed. Compare the staging crawl with the live crawl to identify missing pages, changed titles, removed headings, and altered internal link depth.

Launch-Day Website Migration Checklist

Launch day should follow a written plan. Everyone should know who is deploying, who is validating redirects, who is checking analytics, who can roll back changes, and who is definitely not “just making one quick update” without telling the team.

Technical Launch Checks

• Confirm DNS, hosting, CDN, SSL, and security settings are ready.
• Remove staging blocks from the live site.
• Ensure production pages are crawlable and indexable where appropriate.
• Implement 301 redirects for changed URLs.
• Test redirect rules before and after deployment.
• Update internal links so they point directly to final URLs.
• Update canonical tags to the correct production URLs.
• Generate and submit clean XML sitemaps.
• Update robots.txt with the correct sitemap location.
• Verify Google Search Console and Bing Webmaster Tools access.
• Check analytics, tag manager, conversion tracking, forms, and ecommerce events.
• Validate structured data with testing tools.
• Test mobile usability and page templates.

Redirect Testing

Test a sample of redirects across page types: homepage, category pages, product pages, blog posts, resource pages, PDFs, old campaign pages, and URLs with backlinks. For large websites, test redirects in bulk. Watch for 302 redirects where 301 redirects are needed, redirect chains, redirect loops, non-relevant targets, and old URLs that still return 200 status codes.

A clean redirect should send users and crawlers from the old URL directly to the best new URL in one hop. Old URL to new URL. No scenic tour through six historical redirects and a retired subdomain.

Search Console and Bing Steps

For domain moves, verify the old and new properties in Google Search Console. After redirects are live, use Google’s Change of Address tool when appropriate. Bing also provides webmaster guidance for site moves, and Bing Webmaster Tools should be checked for crawl issues, submitted URLs, sitemap processing, and indexing changes.

For non-domain migrations, such as URL restructuring or CMS changes on the same domain, the Change of Address tool is usually not relevant. Instead, focus on redirects, sitemaps, crawlability, indexation, and monitoring.

Post-Migration SEO Monitoring

The migration is not finished when the site goes live. That is when the monitoring begins. Search engines need time to crawl old URLs, process redirects, discover new pages, update canonical signals, and adjust rankings. Some fluctuation is normal. Total silence from your analytics dashboard is not.

First 24 to 72 Hours

• Crawl the live site and compare it with the staging and old-site crawls.
• Test redirect maps in bulk.
• Check robots.txt, noindex tags, canonical tags, and sitemap URLs.
• Confirm analytics and conversions are recording correctly.
• Review server logs for search engine crawling behavior.
• Inspect top pages manually in Google Search Console.
• Fix critical 404s, 500 errors, redirect loops, and blocked resources immediately.

First 2 to 8 Weeks

Monitor organic traffic, keyword rankings, crawl stats, indexed pages, sitemap processing, backlinks, conversions, and top landing pages. Compare performance against the benchmark data you collected before migration.

Look for patterns. If one directory lost traffic, inspect templates, redirects, internal links, and canonicals in that section. If rankings dropped for blog content, check whether content depth, headings, schema, and internal links changed. If ecommerce category pages declined, examine faceted navigation, pagination, canonical rules, and product availability signals.

What Recovery Should Look Like

A well-planned migration may still cause temporary fluctuations. Search engines need time to process changes. However, if the migration preserved content, relevance, redirects, internal links, crawlability, and performance, traffic should stabilize and may improve over time. If traffic keeps falling, do not wait politely for the algorithm fairy. Investigate.

Website Migration SEO Checklist

Use this checklist as a practical framework for your next migration.

Planning

• Define migration type, scope, goals, and timeline.
• Assign owners for SEO, development, analytics, content, QA, and project management.
• Identify launch risks and rollback options.
• Choose a low-risk launch window, avoiding peak sales periods when possible.

Benchmarking

• Export organic traffic and conversion data.
• Export keyword rankings.
• Identify top organic landing pages.
• Export backlink data and linked URLs.
• Document current indexation, crawl errors, and sitemap status.

URL and Redirect Mapping

• Crawl the current site.
• Collect URLs from analytics, sitemaps, backlinks, and Search Console.
• Map every changing URL to the most relevant new URL.
• Use 301 redirects for permanent moves.
• Avoid redirect chains, loops, and homepage dumping.
• Test redirect rules before launch.

Content and Metadata

• Preserve or improve title tags, meta descriptions, H1s, and body copy.
• Check image alt text and media assets.
• Validate structured data.
• Confirm important pages still satisfy search intent.
• Review thin, duplicate, outdated, or consolidated content.

Technical SEO

• Audit robots.txt.
• Check noindex and canonical tags.
• Generate clean XML sitemaps.
• Update internal links to final URLs.
• Check hreflang for international sites.
• Test mobile rendering and Core Web Vitals.
• Verify status codes and crawl depth.

Analytics and Tracking

• Confirm GA4 or analytics platform installation.
• Check Google Tag Manager containers.
• Test form submissions, calls, purchases, downloads, and lead events.
• Add an annotation or internal note marking the migration date.
• Verify Search Console and Bing Webmaster Tools properties.

Post-Launch

• Crawl the new site immediately.
• Test redirects in bulk.
• Submit new XML sitemaps.
• Monitor crawl errors and indexing issues.
• Track rankings, traffic, and conversions weekly.
• Fix critical issues quickly and document every change.

Specific Examples of Migration Problems and Fixes

Example 1: The Homepage Redirect Trap

A company redesigns its website and redirects hundreds of old blog posts to the homepage. Organic traffic drops because search engines cannot connect the old topic pages to relevant new content. The fix is to create one-to-one redirects wherever possible. Old blog posts should redirect to updated articles, equivalent resources, or closely related category pages.

Example 2: The Forgotten Staging Noindex Tag

A staging site uses noindex tags to keep test pages out of search results. During launch, those tags accidentally remain on production pages. Search engines crawl the new site and see instructions not to index important content. The fix is immediate removal of the noindex tags, followed by sitemap resubmission and URL inspection for priority pages.

Example 3: The Beautiful Redesign That Deleted the Content

A service page ranks well because it explains pricing, use cases, FAQs, and comparisons. During redesign, the page becomes a short visual landing page with almost no text. Rankings drop because the page no longer answers the same queries. The fix is to restore useful content in a user-friendly layout, keeping design clean without starving search engines of context.

Example 4: The CMS Migration With Broken Canonicals

A website moves to a new CMS, but templates generate canonical tags pointing to old URLs. Search engines receive mixed signals: redirects say the new URL matters, canonicals say the old URL matters. The fix is to update canonical logic across templates and verify it at scale through crawling.

Extra Field Notes: Real-World Website Migration Experience

After working through many migration-style projects, one lesson becomes obvious: the spreadsheet is not glamorous, but it is the hero. Designers may get the applause, developers may push the launch button, executives may announce the rebrand, but the humble URL mapping spreadsheet is often what saves organic traffic from taking a dramatic vacation.

The most successful migrations usually have a calm rhythm. First, the team agrees on scope. Then SEO creates a current-state inventory. Developers explain what will change technically. Content teams identify pages that need rewriting or consolidation. Analytics teams confirm what must be tracked. Everyone knows that launch is not a magic trick; it is a controlled handoff from old signals to new signals.

One of the most common experiences in migration work is discovering that the existing site is messier than anyone realized. There are old landing pages from campaigns nobody remembers, duplicate blog categories, PDFs with backlinks, outdated author pages, strange parameter URLs, and one mysterious page from 2017 that still gets traffic for a keyword nobody targets. This is normal. Websites are living things. They grow. They shed. They collect digital lint behind the sofa.

The trick is not to panic. The trick is to classify. Which URLs drive traffic? Which have backlinks? Which convert? Which support important topics? Which are obsolete? Which should be merged? Which can return a clean 404? A migration is a rare opportunity to clean house without throwing away the family silver.

Another real-world lesson: developers appreciate precise SEO requirements. “Please preserve SEO” is not a requirement. It is a wish. “Redirect /old-service/ to /services/new-service/ with a 301 status code and update all internal links to the new URL” is a requirement. “Canonical tags must self-reference indexable production URLs” is a requirement. “The XML sitemap should include only 200-status, canonical, indexable URLs” is a requirement. Clear instructions prevent confused implementation.

Stakeholder communication also matters. During a migration, rankings may fluctuate. Traffic may dip briefly. Search engines may take time to process the move. Executives should know this before launch, not after they open the analytics dashboard and begin typing in all caps. Set expectations with benchmark reports, risk notes, and recovery timelines. Show what will be monitored and what actions will be taken if something breaks.

The best post-launch habit is daily checking during the first week. Review crawl errors, redirects, analytics, conversions, server logs, Search Console, Bing Webmaster Tools, and top landing pages. Do not only check the homepage. The homepage is usually fine. The gremlins live in pagination, old blog posts, product filters, hreflang clusters, forgotten subfolders, and templates used by exactly 11 pages but somehow responsible for 30% of leads.

Finally, remember that migration can be an SEO upgrade, not just an SEO defense mission. If you are already touching URLs, templates, navigation, internal links, structured data, performance, and content, you have a chance to make the site stronger. Improve crawl paths. Clarify topic clusters. Strengthen high-intent pages. Remove dead weight. Fix duplicate content. Improve speed. Make the site easier for users and search engines to understand.

A website migration is not something to fear. It is something to respect. Treat it like a major construction project: measure twice, redirect once, and do not remove the staircase before checking whether people still need to reach the second floor.

Conclusion

A successful website migration depends on planning, precision, and patience. The core idea is simple: preserve what already works, clearly guide search engines from old URLs to new URLs, and use the migration as a chance to improve technical SEO, content quality, user experience, and site performance.

The process starts with discovery and benchmarking, continues through URL inventory and redirect mapping, moves into staging audits and launch-day validation, and finishes with weeks of post-launch monitoring. Skip any of those phases and the migration becomes a gamble. Follow them carefully and the migration becomes a strategic upgrade.

SEO migrations are not about avoiding every fluctuation. Some movement is normal. The real goal is to avoid preventable damage: missing redirects, blocked pages, lost content, bad canonicals, broken tracking, and weak internal links. With the right checklist and a team that communicates clearly, your new site can keep its search equity, serve users better, and give Google and Bing fewer reasons to look confused.