Website Migration Checklist for SEO in 2026

Every website migration carries the same risk: the site you launch performs worse than the one you replaced. Search rankings drop. Organic traffic disappears. Revenue declines while your team scrambles to diagnose what broke. The problem is not the migration itself.

The problem is that 60-70% of migration success depends on work that happens before launch, and most teams skip it. This checklist covers the pre-launch planning, redirect strategy, technical validation, and post-launch monitoring you need to protect your organic traffic during a website migration, then explains how modern AI growth platforms eliminate the manual work that makes migrations so painful in the first place.

Key takeaways

• Start with a complete pre-migration SEO audit. Benchmark organic traffic, keyword rankings, indexed pages, backlinks, and conversions before making changes. This gives you a baseline to measure migration success.
• Map old URLs to their new destinations. Use permanent 301 redirects for changed URLs, preserve high-value pages, and avoid redirecting unrelated content to the homepage.
• Validate technical SEO before launch. Check canonical tags, XML sitemaps, robots.txt, structured data, internal links, and Core Web Vitals to prevent crawlability and indexing issues.
• Monitor SEO performance closely after migration. Track organic traffic, rankings, 404 errors, and indexing in Google Search Console daily during the first week. Investigate unexpected or sustained declines.
• Preserve existing content while improving site structure. Keep high-performing pages intact, consolidate outdated content where appropriate, and maintain clear internal linking to protect search visibility.
• Plan for continuous optimization after launch. An SEO-safe migration extends beyond the initial transition. Platforms like Ploy support ongoing technical SEO monitoring, performance improvements, and AI search visibility, helping teams maintain and improve their sites over time.

What is a website migration and why is it critical for SEO?

A website migration moves your site from one platform, domain, URL structure, or technology stack to another. The term covers several distinct scenarios, each with different SEO implications:

• Domain migration changes your web address entirely (example.com to newbrand.com) and requires all URLs to redirect while you wait for search engines to transfer authority
• CMS migration moves your content between platforms (WordPress to Shopify, custom build to a modern platform) and typically changes URL patterns, template structures, and metadata handling
• URL restructure reorganizes your site architecture on the same domain, requiring careful redirect mapping for every changed path
• HTTPS migration upgrades your protocol and creates technically new URLs that need canonical signals and redirect handling
• Site consolidation combines multiple domains or subdomains into one property, requiring decisions about which content survives and which redirects where

Each migration type carries different risk levels. Domain changes represent the highest SEO risk, with recovery taking 4-12 weeks for well-executed migrations and 3-6 months for enterprise sites with 50,000+ pages. Hosting migrations on the same domain are lower risk when DNS is handled properly. The key variable is how many URLs change and whether your redirect strategy preserves the connection between old pages and new ones.

The SEO stakes of a flawed migration

The consequences of a poorly executed migration are severe and often permanent. When migrations fail, organic traffic drops immediately and recovery takes months. When SEO is not treated as a priority during planning, recovery can take 523 days on average, and nearly 17% of sites never recover to pre-migration levels.

The damage happens through several mechanisms:

• Broken redirects leave search engines pointing to pages that return 404 errors, causing rankings to disappear
• Lost link equity occurs when high-authority pages redirect to your homepage instead of equivalent content
• Noindex leaks from staging environments tell Google to remove your pages from search entirely
• Orphaned content becomes invisible when internal links break and pages have no path from navigation
• Duplicate content emerges when both old and new URLs remain accessible without proper canonical signals

A 32% traffic decline from a CMS migration required nine months of recovery work at one company. The direct revenue impact of organic traffic loss varies by business, but sites earning $5-50 per organic visitor feel the effect immediately in revenue and closed deals.

Pre-migration SEO audit: preparing your site for a smooth transition

Before you change anything, document exactly what you have. This baseline becomes your reference for validating the new site and diagnosing problems after launch.

Export your performance data:

• Pull 12+ months of Google Search Console data including queries, pages, clicks, impressions, and average positions
• Export Google Analytics reports showing organic sessions, conversions, and revenue by landing page
• Run a complete site crawl with a tool like Screaming Frog or Sitebulb to capture all URLs, title tags, meta descriptions, H1s, canonical tags, and internal link counts

Identify high-value pages:

• List your top 100 pages by organic traffic
• List your top 50 pages by backlink count
• Flag all pages that generate conversions or revenue
• Cross-reference these lists to prioritize which pages absolutely cannot break

Document your current technical setup:

• Export your existing robots.txt file
• Download all XML sitemaps
• Record current redirect rules
• Note any custom canonical tag settings
• Capture structured data (schema markup) from key page templates

This audit takes 8-16 hours for a medium-sized site but prevents far more time spent troubleshooting after launch.

Baseline performance metrics to track

Establish clear benchmarks before migration so you can measure the impact afterward:

For teams running continuous optimization, Ploy Web monitors these metrics automatically and surfaces changes that require attention. Rather than running manual audits before migrations, you maintain a constantly updated view of site health and can compare against any historical point.

Crafting your redirect strategy: 301s, 302s, and beyond

When to use a 301 vs. a 302 redirect

The redirect type you choose signals different things to search engines:

301 redirects indicate a permanent move. Use 301s for:

• Every URL that changes during migration
• Consolidated pages where multiple old URLs now point to one new page
• Domain changes where the old domain should pass authority to the new one

302 redirects indicate a temporary move. Use 302s only when:

• The old URL will return to service (rare during migrations)
• Testing redirect behavior before committing to permanent changes

In practice, nearly every migration redirect should be a 301. Permanent 301 redirects tell search engines that a URL has moved permanently and that the destination should generally become the canonical page. Temporary 302 redirects indicate that the original URL should remain the preferred version. For permanent website migrations, use 301 redirects to establish clear canonical signals and help search engines process the move.

Building your redirect map

Create a spreadsheet with these columns:

Mapping principles:

• Map every old URL receiving traffic or backlinks to its closest equivalent new URL
• Prioritize one-to-one mapping where content relationship is clear
• Never redirect multiple important pages to the homepage (search engines treat this as a soft 404)
• Flag pages for retirement with 410 status codes rather than redirecting thin content to unrelated pages

For sites with thousands of URLs, pattern-based redirects using regex rules reduce manual mapping. A redirect rule that transforms /blog/2024/post-title to /articles/post-title handles hundreds of URLs with one setting.

Implementing redirects on different platforms

Implementation varies by platform:

• Server-level (.htaccess, nginx): Most reliable for Apache and nginx servers; handles redirects before the application layer
• CMS plugins: WordPress plugins like Redirection or Yoast handle redirects within the application
• Platform settings: Managed platforms like Shopify provide redirect interfaces in admin settings
• Edge/CDN rules: Cloudflare and similar services can handle redirects at the network edge before requests reach your server

Ploy handles redirects through Routing Rules at the edge, enabling gradual migration where some paths serve from Ploy while others proxy to your existing infrastructure. This lets you migrate in phases rather than committing to a complete cutover on launch day.

Testing requirements:

• Test every redirect in your map before launch
• Verify redirects resolve in one hop (no chains)
• Confirm final destinations return 200 status codes
• Check that redirects work with and without trailing slashes

Content and on-page SEO considerations for your new site

Updating and optimizing existing content

Migration is not just about preservation. It is an opportunity to improve. Simms Fishing achieved 126% organic traffic growth during their Magento to Shopify migration by creating more granular category pages and optimizing content per category rather than simply copying their old structure.

Content audit decisions:

On-page elements to verify:

• Title tags transfer to new pages with appropriate length and keywords
• Meta descriptions migrate without truncation
• H1 tags match content hierarchy on each template
• Image alt text carries over (often lost in platform migrations)
• Internal links point to new URLs directly (not through redirects)

Integrating AEO for AI answer engines

Search in 2026 includes AI answer engines like ChatGPT, Perplexity, Gemini, and Google AI Overviews. Your migration should prepare content for Answer Engine Optimization alongside traditional SEO.

AEO requirements during migration:

• Implement FAQ schema on relevant pages
• Structure content with clear question-and-answer formats
• Add HowTo schema for instructional content
• Ensure JSON-LD structured data transfers to new templates
• Create direct-answer paragraphs that AI engines can cite

Prawomat achieved a 6.4x increase in AI answers within 19 days of their migration by treating URL decisions as data-driven choices based on clicks and backlinks per page, then optimizing new content for AI citation.

Ploy Web automatically structures pages for AI answer engines and tracks citations across ChatGPT, Perplexity, Gemini, Claude, and Google AI Overviews. Rather than manually implementing schema markup across templates, the platform handles structured data as part of continuous optimization.

Technical SEO health check: Core Web Vitals, crawlability, and indexability

Core Web Vitals measure real user experience and affect search rankings. Migration often changes these metrics because new platforms use different code, hosting, and asset delivery.

Key metrics to benchmark and validate:

• Largest Contentful Paint (LCP): How quickly the main content loads; target under 2.5 seconds
• Interaction to Next Paint (INP): Measures how quickly a page responds to user interactions throughout a visit. Aim for an INP of 200 milliseconds or less at the 75th percentile of real-user experiences.
• Cumulative Layout Shift (CLS): How much content moves during loading; target under 0.1

Test these metrics on staging before launch using PageSpeed Insights and Chrome DevTools. Field data (real user metrics) takes 28 days to stabilize in Google Search Console after launch, so lab data during staging is your best pre-launch validation.

Common performance killers during migration:

• Unoptimized images that are larger than the old site used
• Third-party scripts loading synchronously instead of deferred
• Web fonts without proper preloading or fallbacks
• JavaScript frameworks that require full hydration before interaction

Ploy runs on Cloudflare Workers with global edge infrastructure, automatic SSL, and built-in CDN performance. This architecture handles the technical optimization that typically requires dedicated engineering time during and after migration.

Ensuring search engine crawlability and indexability

Search engines need to access, crawl, and index your new site. Verify these elements before and immediately after launch:

robots.txt validation:

• Confirm robots.txt does not block important sections
• Remove any staging-specific disallow rules
• Keep crawl-delay directives reasonable for your server capacity

XML sitemap requirements:

• Generate new sitemaps reflecting current URL structure
• Remove old URLs that no longer exist
• Include only canonical, indexable pages
• Submit updated sitemaps through Google Search Console immediately after launch

Canonical tag verification:

• Ensure canonicals point to production URLs (not staging)
• Confirm self-referencing canonicals on all indexable pages
• Verify canonical consistency with hreflang tags for international sites

Critical indexability checks:

• Search HTML source for “noindex” on production pages (the number one migration killer)
• Confirm pages return 200 status codes
• Verify JavaScript-rendered content is accessible to search engine crawlers

Technical SEO issues discovered after launch cost far more to fix than issues caught during staging. Spend the time to validate thoroughly before going live.

Post-migration monitoring and troubleshooting with Google Search Console

Setting up and monitoring your new property in GSC

Google Search Console is your primary tool for monitoring migration health. Complete these steps immediately:

If your domain changed:

• Verify the new domain as a property in GSC
• Use the Change of Address tool to notify Google of the domain migration
• Keep both old and new properties verified for monitoring

For all migrations:

• Submit your updated XML sitemap within hours of launch
• Use the URL Inspection tool to check 5-10 important pages
• Request indexing for high-priority pages to accelerate discovery

Daily monitoring (days 1-7)

The first week requires daily attention:

Normal patterns:

• 10-20% traffic dip for 2-4 weeks
• Branded queries remain stable while unbranded fluctuate
• “Page with redirect” count rising in GSC coverage report
• Some position volatility as Google reprocesses pages

Concerning patterns requiring immediate action:

• 30%+ sustained traffic drop
• Entire sections disappearing from index
• 404 count climbing after the first week
• Conversions falling while traffic holds (indicates broken tracking)

Common post-migration issues and solutions

Ploy’s built-in analytics combine server-side and client-side tracking to capture visitors that traditional browser-based analytics miss. Server-side events fire before the browser loads, providing a more complete picture during the post-launch monitoring period when accuracy matters most.

Advanced migration strategies for enterprise and high-growth teams

Minimizing risk with gradual migrations

Enterprise sites with thousands of pages benefit from staged migration methods that reduce risk:

Phase-based rollout:

• Migrate one section at a time (blog first, then product pages, then support docs)
• Monitor each phase for 2-4 weeks before proceeding
• Roll back individual sections if problems emerge without affecting the full site

Reverse proxy method:

• New platform serves some paths while old platform serves others
• Traffic splits at the edge based on URL patterns
• Gradually shift paths to the new platform as confidence builds

A/B testing during migration:

• Route a percentage of traffic to the new site
• Compare conversion rates and engagement
• Validate performance before full cutover

Ploy supports Routing Rules and reverse proxy for exactly this purpose. You can migrate gradually without the all-or-nothing commitment that makes traditional migrations so risky.

Leveraging AI for continuous post-launch optimization

Traditional migrations treat launch day as the finish line. Teams complete the checklist, monitor for a few weeks, then move on to other priorities. Six months later, technical debt has accumulated, content has become outdated, and the optimization work starts again.

Modern AI growth platforms flip this model. Instead of periodic migrations and redesigns, they continuously monitor, optimize, and improve.

What continuous optimization replaces:

• Manual technical SEO audits (quarterly becomes continuous)
• Spreadsheet-based redirect management (rules become automated)
• Periodic Core Web Vitals checks (monitoring becomes real-time)
• Content freshness reviews (staleness detection becomes automatic)

For enterprise teams, Ploy operates as an AI growth platform where Ploy Web, Ploy Grow, and Ploy Ads work together continuously. After migration, the platform keeps improving technical SEO, Core Web Vitals, internal linking, and conversion opportunities without waiting for the next migration project to address accumulated issues.

The future of SEO migrations: AI, AEO, and continuous optimization (2026)

Anticipating 2026: AI’s role in search and site transitions

Search behavior has changed. Users now find information through AI answer engines, not just traditional search results. Your migration strategy needs to account for visibility across both channels.

AI search visibility factors:

• Direct-answer content that AI engines can cite
• Structured data that signals entity relationships
• Content freshness and authority signals
• Technical accessibility for AI crawlers (distinct from Googlebot)

Migration planning for AI visibility:

• Audit current AI search visibility before migration (where do you appear in ChatGPT, Perplexity, Gemini responses?)
• Ensure structured data transfers to new templates
• Create content formatted for AI citation, not just human readers
• Monitor AI visibility post-launch alongside traditional metrics

Prawomat’s 2.9x increase in Google clicks and 6.4x increase in AI answer appearances within 19 days demonstrates that migrations done well improve both traditional and AI search performance.

From manual audits to automated growth platforms

The manual work of website management has always been highest around migrations. Teams need to coordinate across web, design, engineering, content, and SEO just to launch something that immediately starts degrading.

That manual work disappears when your platform continuously handles the work that previously required team coordination:

What Ploy automates:

• Technical SEO optimization that runs continuously, not annually
• Answer Engine Optimization with automatic schema markup and citation tracking
• Core Web Vitals monitoring and improvement recommendations
• Internal linking optimization based on content relationships
• Content freshness detection and update recommendations

What Ploybooks enable:

• Pre-built workflows for SEO and AEO audits
• Automated GSC keyword optimization
• Comparison page creation designed for AI citation
• Content refresh workflows triggered by performance signals

For teams evaluating their next migration, the question is not just “how do we move safely” but “how do we stop doing migrations entirely?” When your platform continuously optimizes itself, the periodic rebuild becomes unnecessary. You ship improvements daily instead of launching projects quarterly.

The website that keeps working after launch is not a vision for the future. It is available now for teams ready to eliminate the manual work that makes every migration a risk.