The Ultimate SEO Website Migration Checklist for 2026: Protect Rankings, Traffic & Revenue

Executing a website migration is like performing surgery on a living digital ecosystem, where seemingly minor oversights can affect organic visibility, traffic, and revenue. At Global Media Insight (GMI), our experience includes guiding complex CMS, ecommerce, and enterprise migrations, which has helped us develop a practical framework for minimising migration risks.

Google recommends allowing time for search engines to recrawl, reindex, and process a migrated website. Ranking fluctuations are normal during this period, and the time required for a migration to settle can vary depending on the size and complexity of the site.

In 2026, protecting organic visibility means looking beyond URL redirects alone. A successful migration must preserve technical SEO fundamentals, internal linking, content quality, structured data, entity signals, analytics, and other important search signals. It should also account for visibility across AI-powered search experiences such as Google AI Overviews and AI Mode, where Google’s guidance continues to emphasize strong foundational SEO and helpful, reliable content.

This step-by-step framework covers the key stages of a successful website migration in 2026—from pre-migration audits and URL mapping to launch-day checks and post-migration monitoring—to help protect rankings, traffic, and revenue.

Table of Contents

What Is an SEO Website Migration?

An SEO website migration is the process of making significant changes to a website while minimising the risk of losing organic rankings, search visibility, and traffic. These changes can involve the website’s domain, URL structure, CMS or platform, site architecture, hosting environment, or other technical elements that affect how search engines crawl and index the site.

A standard website redesign primarily focuses on the site’s design, user experience, and functionality. However, a redesign can also affect SEO if it changes URLs, content, internal linking, technical signals, or how search engines access the site. A migration is generally a broader change involving the website’s platform, domain, URL structure, architecture, or hosting environment. A redesign can therefore be part of a migration, but not every redesign qualifies as one.

SEO should be involved from the earliest planning stages, ideally before development begins. Early involvement allows the team to identify potential risks, map legacy URLs to their new destinations, plan redirects, review the proposed site architecture, and protect important organic landing pages before changes reach production.

A well-planned SEO migration helps protect:

Keyword rankings that drive valuable organic traffic
Organic search traffic from potential customers
The value of backlinks pointing to existing pages
Important indexed pages that already receive organic visibility
Critical conversion paths, including forms, checkout flows, purchases, and lead-generation journeys
Search visibility across Google Search, AI Overviews, AI Mode, and other AI-powered search experiences

What Are the Different Types of Website Migrations?

Not all website migrations carry the same level of risk. The potential impact depends on what is changing, the size and complexity of the website, and how carefully the migration is planned and implemented.

These migration types are not mutually exclusive. A single project can involve several types at once—for example, a CMS migration combined with a website redesign, URL structure change, and domain migration. The more elements that change simultaneously, the more important comprehensive SEO planning, testing, and monitoring become.

Domain Migration

A domain migration happens when you move a website from one domain name to another. It can be a high-risk migration because search engines need to discover and process the new URLs, follow redirects from the old URLs, and update their understanding of the site’s signals. Ranking fluctuations can occur while this happens.

Common scenarios include:

Company rebranding
Business mergers and acquisitions
Changing from a generic domain to a country-specific domain
Moving to a shorter or more relevant domain name

CMS Migration

A CMS migration occurs when you move a website from one content management system to another. It can improve functionality, flexibility, performance, or content management, but it can also affect URLs, metadata, templates, internal linking, structured data, and other SEO settings.

Examples include:

Moving from WordPress to Drupal
Moving from Drupal to WordPress
Moving a custom-built website to WordPress

Website Redesign Migration

A redesign migration focuses on updating a site’s visual design, layout, navigation, functionality, and sometimes its content. Even when URLs remain unchanged, changes to page content, internal linking, navigation, structured data, rendering, or technical SEO elements can affect organic search performance.

URL Structure Migration

This type of migration involves changing URL paths, folder names, or page categories. When URLs change, the old URLs should generally be redirected to their corresponding new destinations so that users and search engines can reach the correct pages and relevant signals can be consolidated.

Examples include:

Changing /services/seo/ to /seo-services/
Restructuring product and category folders
Cleaning up complex URLs to create a clearer URL structure

Ecommerce Migration

An ecommerce migration involves moving an online store to a new platform, architecture, or technology environment. Because ecommerce websites can contain thousands of product, category, filter, and other transactional URLs, they require detailed planning to protect organic visibility, conversions, and revenue.

Examples include:

Moving from Magento to Shopify
Moving from WooCommerce to Shopify
Moving from Magento Open Source to Adobe Commerce

Platform Migration

A platform migration involves moving a website to a substantially different technology stack, framework, or application architecture. These changes can affect rendering, crawling, internal linking, page performance, and how search engines access and process content.

Examples include:

Moving from a traditional server-rendered architecture to a JavaScript-heavy application
Moving from a monolithic website to a headless CMS architecture
Migrating from one web framework or application platform to another

Website Consolidation Migration

Many organizations merge multiple websites into a single domain to consolidate content, simplify management, strengthen their overall brand presence, and potentially consolidate relevant organic signals. This requires careful content and URL mapping to prevent valuable pages, rankings, and backlinks from being lost.

Examples include:

Merging several brand websites into one
Combining separate regional websites
Moving standalone microsites back into the main domain

International SEO Migration

International SEO migrations affect multilingual or multi-regional websites. Changes to country or language targeting, URL structures, internal linking, canonicalization, or hreflang implementation can affect international search visibility.

Examples include:

Restructuring country-specific URLs
Moving from subdirectories to country-specific domains
Changing the site’s international URL architecture
Updating hreflang implementation as part of a site restructure

Subdomain Migration

A subdomain migration involves moving content between a subdomain and a subfolder, or vice versa. Because this changes the site’s URL structure and architecture, the migration should be carefully planned so that redirects, internal links, canonicals, sitemaps, and other SEO signals are updated correctly.

Examples include:

Moving from blog.example.com to example.com/blog/
Moving from store.example.com to example.com/store/

Hosting Migration

A hosting migration involves moving a website to a new hosting provider, server environment, or cloud infrastructure. The URLs may remain unchanged, but extended downtime, incorrect server responses, DNS issues, crawling problems, or significant performance degradation can negatively affect users and search visibility.

Examples include:

Moving from shared hosting to cloud hosting
Moving from local servers to AWS, Azure, or Google Cloud

HTTP to HTTPS Migration

Moving from HTTP to HTTPS is standard practice for modern websites. HTTPS encrypts data exchanged between users and the website, improves browser security and user trust, and is also a lightweight Google ranking signal. However, the migration still needs to be implemented carefully to avoid redirect chains, mixed-content issues, incorrect canonicals, or indexing problems.

Key considerations include:

Implementing permanent redirects from HTTP URLs to their HTTPS equivalents
Updating canonical URLs and internal links
Updating XML sitemaps
Checking for mixed-content issues
Verifying HTTPS URLs in Google Search Console
Monitoring crawling, indexing, and organic traffic after launch

Why Website Migrations Can Hurt SEO ?

Search engines build an understanding of your website through its content, URLs, internal links, technical signals, and other signals accumulated over time. When a migration changes these elements without proper planning, search engines may need to recrawl and reprocess large parts of the site, while users can encounter broken pages, missing content, or disrupted journeys.

Common SEO Risks During Website Migration

During migration projects, we frequently see sites affected by the same set of common issues:

Lost keyword rankings caused by changes to URLs, content, internal linking, or other important SEO signals
Drops in organic traffic caused by crawlability, indexation, redirect, content, or technical issues
Broken internal links that disrupt navigation and make important pages harder for users and search engines to discover
Missing, incorrect, or poorly mapped redirects that prevent users and search engines from reaching the correct new URLs and can result in the loss of relevant signals
Accidental indexing blocks, such as incorrect noindex directives, robots.txt restrictions, or canonical signals
Lost or changed content, page titles, metadata, and other on-page SEO elements
Disrupted internal linking that makes important pages harder to discover and weakens the relationships between related content
Incorrect canonical tags that cause search engines to consolidate signals toward the wrong URLs
Rendering or JavaScript issues that prevent important content or links from being properly discovered
Broken analytics, Search Console, tag management, or conversion tracking that makes it difficult to measure the migration’s impact on traffic, leads, sales, and revenue

AI-Powered Search Considerations

AI-powered search experiences build on many of the same technical and content foundations used by traditional search. A migration that removes important content, disrupts internal linking, blocks crawling, or incorrectly implements structured data can therefore affect how content is discovered, understood, and surfaced across search experiences such as Google AI Overviews and AI Mode.

A migration can also affect ongoing efforts to improve visibility across generative and AI-powered search experiences through Generative Engine Optimization.

Key considerations include:

Making important content harder to discover, which can reduce the likelihood of it being surfaced or cited in AI-powered search experiences
Disrupting internal links to related content, making important topical relationships and supporting resources harder for search engines to discover and understand
Removing useful question-and-answer content that previously attracted organic visibility or helped users understand important topics
Breaking relevant structured data, which can reduce the information available to search engines when interpreting pages and determining eligibility for supported search features
Removing author information or other transparency elements that help readers understand who created or reviewed important content
Changing or removing important brand and organization information, including consistent business details, About pages, and relevant Organization structured data

A migration should therefore preserve the underlying technical, content, and trust foundations that support visibility across both traditional and AI-powered search experiences.

The Ultimate SEO Website Migration Checklist

A successful website migration starts weeks or even months before the new website goes live. Use this 2026 SEO website migration checklist throughout every stage of your project to protect organic traffic, rankings, conversions, and search visibility across traditional and AI-powered search experiences.

Pre-Migration SEO Checklist

Much of a migration’s success is determined before launch day. From our experience, projects perform best when teams prioritize thorough planning, auditing, testing, and documentation before development changes reach production.

Conduct a Complete SEO Audit

Before changing the website, establish a clear baseline of its current SEO and business performance. Review:

Organic traffic trends and seasonal patterns
Google Search Console performance
Current keyword rankings
Important indexed and indexable pages
Organic landing pages generating the most traffic
Organic leads, sales, conversions, and revenue
Top-performing pages by traffic and conversions
Backlinks and referring domains
Current redirects and important redirect chains
Canonical tags
Robots.txt and XML sitemaps
404, 3xx, and 5xx URLs
Internal linking and important navigation paths
Core Web Vitals and other key performance metrics
Structured data and hreflang implementation, where applicable

This baseline gives you a reference point for identifying changes after the migration. Review as much historical Search Console and analytics data as available, ideally covering at least 12 months, so you can account for seasonal trends and compare performance before and after launch.

Crawl and Benchmark the Existing Website

Run a comprehensive crawl of your current website to capture as much technical and SEO information as possible before development begins. This benchmark will give you a reliable reference point for comparing the old and new websites after launch.

Capture:

Every existing URL discovered during the crawl
HTTP status codes
Meta titles and descriptions
H1 headings
Indexability and robots directives
Internal links
Canonical tags
Existing redirects
XML sitemap URLs
Hreflang implementation, where applicable
Structured data
Orphan or poorly linked pages

Also document important dynamic elements, widgets, and third-party integrations, including embedded chat tools, payment gateways, booking systems, filters, and other functionality that must be tested on the new platform.

Tools such as Screaming Frog and Sitebulb can help build this technical and SEO inventory.

Build a Complete URL Inventory

Your URL inventory is one of the most important documents you will create during a migration. For every important existing URL, document:

The existing URL
HTTP status code
Indexability status
Canonical URL
Organic traffic
Organic conversions or revenue
Backlinks and referring domains
Page type or template
The exact new destination URL
Redirect status

This inventory becomes the foundation for your content review, URL mapping, redirect strategy, and post-migration validation.

Identify High-Value SEO Assets

Not every URL carries the same business or SEO value. Prioritize the pages that are most important to your organic performance and revenue.

Focus on:

Revenue-generating landing pages
Core service pages
High-converting product and category pages
Pages ranking for valuable commercial keywords
High-traffic blog articles and resources
Pages with strong backlink profiles
Pages generating significant organic leads, sales, or other conversions

Use analytics, Google Search Console, backlink data, and business conversion data to determine which pages deserve the highest level of protection during the migration

Audit Existing Content

Review the existing content before deciding what should move to the new website. Categorize important pages as:

Keep — content that continues to meet user and business needs
Update — content that needs improvement before or during migration
Merge — overlapping pages that can be consolidated
Redirect — pages that have a relevant replacement
Remove — obsolete pages with no useful replacement

Pay particular attention to content that receives organic traffic, generates conversions, ranks for valuable queries, or has strong external backlinks.

Audit Existing Metadata

Do not let your existing on-page optimization get lost during a redesign or platform migration. Capture and review:

Meta titles
Meta descriptions
H1 headings
Meta robots directives
Open Graph tags

Compare these elements against the new templates before launch to ensure important pages retain their relevant SEO and social-sharing information.

Audit Existing Structured Data

Structured data can help search engines understand the content and entities represented on a page and can make eligible pages qualify for supported rich results. During a migration, make sure existing valid implementations are preserved and updated to reflect the new website.

Review relevant implementations, such as:

Organization structured data
Product structured data
Article structured data
Breadcrumb structured data
Review structured data
FAQ structured data, where applicable

Validate the new implementation against the visible content on each page and remove outdated or inaccurate markup rather than carrying it over automatically.

Audit Existing 404 and Broken URLs

Not every broken URL is useless. Some may still have valuable backlinks, organic traffic, or historical business value.

Identify:

404 URLs receiving organic traffic
404 URLs with external backlinks
URLs linked internally but returning 404
Broken pages that previously generated conversions
Broken URLs that have relevant replacement pages

Where an appropriate replacement exists, include the URL in your redirect mapping. Do not automatically redirect every 404 URL to the homepage.

Audit Navigation and Internal Linking

Changes to your navigation can quietly reduce the prominence and discoverability of important pages. Review how users and search engines currently reach your key content.

Audit:

Header navigation
Footer links
Breadcrumbs
Mobile navigation
Contextual internal links
Related-content links
Category and subcategory navigation

If an important page becomes significantly deeper in the site structure or loses relevant internal links, it may become harder for users and search engines to discover and understand its importance. Make sure the new architecture provides clear paths to your most valuable pages.

Audit Backlinks to Important URLs

Identify the pages that have earned valuable external links before changing their URLs.

Review:

High-authority referring domains
Pages with significant backlink profiles
Important URLs receiving external links
Broken URLs that still have valuable backlinks
Backlinks pointing to URLs that will change during the migration

Use this information when prioritising your redirect mapping so valuable backlink destinations are not accidentally abandoned.

Create a Redirect Mapping Document

A well-planned redirect strategy is one of the most important safeguards in a URL migration. Your redirect document should clearly list:

The old URL
The new destination URL
The redirect type, typically a 301 or 308 for permanent URL changes
The priority of the URL
Implementation status

When setting up redirects, avoid chains and loops by pointing each old URL directly to its final destination. Do not use blanket redirects that send multiple unrelated pages to the homepage or another irrelevant URL.

Where possible, update internal links so they point directly to the new URLs rather than relying on redirects.

Before launch, test the redirect map to confirm that important legacy URLs resolve correctly and that no high-value pages have been left without an appropriate destination.

Pre-Migration AI Search Visibility Checklist

Search visibility in 2026 extends beyond traditional organic results. AI-powered search experiences can surface and cite information from websites in different ways, making it important to understand where your brand and content currently appear across these platforms.

In our experience, some pages can be surfaced or cited by AI-powered search experiences even when they are not among the site’s highest-ranking traditional organic results. Understanding and protecting these sources of visibility is now an important part of migration planning.

For businesses that actively monitor and optimize visibility across AI-powered search experiences, a migration should also be coordinated with their AI SEO Services strategy.

Benchmark AI-Powered Search Visibility

Before making significant changes, establish a baseline of your brand’s visibility across relevant AI-powered search experiences, such as Google AI Overviews, ChatGPT, Gemini, Microsoft Copilot, and Perplexity.

Use a consistent set of relevant prompts and record:

Brand mentions
Products or services mentioned
Cited sources and URLs
Competitors appearing in responses
Frequently cited pages
Accuracy of brand and business information
Any outdated or incorrect information

AI platforms do not provide a universal equivalent of traditional keyword rankings, so focus on documenting mentions, citations, sources, and the context in which your brand appears.

Identify AI-Cited Pages

Identify the pages that are already being referenced or cited in AI-powered search experiences. In our experience, a single statistics page, research resource, or authoritative guide can sometimes receive substantial AI citation visibility compared with many traditional commercial landing pages.

Prioritize protecting pages such as:

Original research and statistics
Authoritative guides
Product and service resources
Case studies
Industry reports
Helpful articles and FAQs
Documentation and other reference content

Record the URLs of important cited sources so they can be specifically monitored during and after the migration.

Audit Brand and Entity Information

Review the consistency of your brand, organization, product, and business information across the website and other important digital properties.

During the migration, preserve important information such as:

Organization and brand name
Company description
Contact information
Business locations
Products and services
About Us information
Relevant Organization or Product structured data
Consistent references to important entities and relationships

The goal is to ensure that important brand and business information remains clear, consistent, and accessible after the migration.

Preserve E-E-A-T Elements

Preserve the elements that demonstrate experience, expertise, authoritativeness, and trustworthiness (E-E-A-T). Do not accidentally remove important trust and transparency elements during a redesign, content consolidation, or platform migration.

Review:

About Us pages
Author profiles and credentials
Reviewer information, where relevant
Industry certifications
Contact information
Editorial policies
References and sources
Original research
Case studies
First-hand experience and supporting evidence

Avoid treating E-E-A-T as a single technical ranking score. Instead, focus on preserving the information and content elements that help users and search engines evaluate the reliability and expertise of the website.

Audit Content Relationships and Topic Coverage

Map your content pillars and supporting resources before migration. Ensure the new site’s internal linking preserves clear relationships between related topics and makes important content easy for users and search engines to discover.

Pay particular attention to:

Core topic pages
Supporting articles
Research and statistics
Related guides
Internal links between supporting and primary content
Important contextual links
Content that supports key commercial pages

Preserve Original Research and Valuable Data

Identify original research, statistics, reports, case studies, and other unique resources that contribute to the site’s organic and AI-powered search visibility.

Before migration, confirm that these assets are:

Included in the new website
Accessible to users and search engines
Mapped to the correct new URLs
Supported by relevant internal links
Properly attributed
Still accurate and up to date

Create an AI Visibility Monitoring List

Create a list of important AI-visible URLs and prompts to monitor after launch. For each important source page, record its current URL, new URL, AI platforms where it appears, relevant prompts, and any important citation or brand-visibility observations.

After migration, use this baseline to identify meaningful changes in how your brand and content are surfaced across AI-powered search experiences.

Staging Environment SEO Checklist

The staging environment is your final safety net for identifying SEO, technical, tracking, and functionality issues before they reach the live website. Treat it as a full pre-launch testing environment rather than simply a preview of the new design.

Validate Staging Access and Indexation Controls

Protect the staging environment with authentication or other access controls. You can also use noindex as an additional safeguard, but do not rely on noindex alone to keep staging content out of search results.

Check that:

Staging pages require appropriate authentication
Staging URLs are not included in public XML sitemaps
Staging pages are not linked from the production website
noindex directives are correctly implemented where required
Staging restrictions will not accidentally carry over to production

Validate Canonical Tags

Check that canonical tags are correctly configured throughout the staging environment and will resolve to the intended production URLs when the site goes live.

Look for:

Missing canonical tags
Incorrect canonical URLs
Canonicals pointing to obsolete pages
Canonicals pointing to staging URLs when production URLs are intended
Conflicting canonical signals

Perform a final crawl of the production website after launch to confirm that canonical tags point to the correct live URLs.

Validate Internal Linking

Test the site’s header, footer, breadcrumbs, contextual links, related-content links, and mobile navigation on staging.

Make sure:

Important pages are internally linked
Navigation links point to the correct URLs
No important links return 404 errors
Internal links do not unnecessarily pass through redirects
Mobile navigation provides access to the same important content where appropriate

Validate Structured Data

Validate structured data across key page templates to confirm that the markup is present, valid, and accurately reflects the visible content.

Review:

Required properties
Validation errors
Relevant warnings
Schema types
URLs and entity references
Structured data carried over from the existing website

Resolve issues that could affect eligibility for supported search features before launch.

Validate Analytics and Conversion Tracking

Test GA4, Google Tag Manager, conversion events, ecommerce tracking, forms, and other critical measurement systems using an appropriate staging or test configuration.

Validate:

Page views
Key events
Lead submissions
Ecommerce events
Purchase and checkout tracking
Form interactions
Consent settings
Cross-domain tracking, where applicable
Google Ads or other advertising conversion tracking, where applicable

Make sure production uses the correct measurement IDs, containers, events, and configuration before launch.

Validate JavaScript Rendering

If the new site relies heavily on JavaScript, verify that search engines can discover and render important content, metadata, links, and navigation correctly.

Pay particular attention to:

Main content
Navigation links
Product or service information
Metadata
Internal links
Structured data
Content loaded dynamically
Client-side routing

Where applicable, verify that server-side rendering, static rendering, or client-side rendering behaves as intended.

Validate Robots.txt and XML Sitemaps

Check that staging and production have the correct robots.txt and XML sitemap configurations.

Before launch, confirm that:

Staging restrictions will not be carried into production
Production URLs are not blocked accidentally
The production sitemap contains the correct canonical URLs
Redirected, noindex, or non-canonical URLs are excluded where appropriate
The sitemap is accessible and returns the expected URLs

Validate Forms, Ecommerce, and Third-Party Integrations

Test critical user journeys on staging before launch, including:

Lead-generation forms
Account registration and login
Search functionality
Filters and faceted navigation
Shopping cart and checkout
Payment gateways
Booking systems
Chat tools
APIs and third-party integrations
Email notifications
Confirmation pages

Document any integration that behaves differently between staging and production and assign an owner for final validation.

Validate Performance and HTTPS

Check the new site for technical performance and security issues before launch.

Review:

Core Web Vitals
Server response times
Page loading performance
Image optimization
JavaScript and CSS resources
HTTPS implementation
Mixed-content errors
Redirects from HTTP to HTTPS

The goal is to ensure that the new platform is technically ready before the migration reaches production.

Website Migration Launch Checklist

Launch day is where your planning and testing come together. Use this checklist immediately after deployment to confirm that the new website is accessible, crawlable, trackable, and functioning correctly.

Deploy and Validate Redirects

Deploy your planned permanent redirect map and verify that important legacy URLs resolve directly to their intended new destinations.

Check that:

High-priority URLs redirect to the correct equivalent pages
Redirects use 301 or 308 status codes for permanent URL changes
No redirect loops exist
No unnecessary redirect chains exist
No important URLs return unexpected 404 or 5xx errors
Redirects point to relevant replacement pages rather than unrelated destinations or the homepage

Prioritize testing URLs that previously generated significant organic traffic, conversions, or backlinks.

Validate URL Structure

Review the live site architecture to confirm that URL folders, paths, and hierarchy match the approved migration plan.

Check for:

Unexpected URL changes
Incorrect folder structures
Duplicate URL variations
Trailing-slash inconsistencies, where relevant
Incorrect case sensitivity
Unexpected parameters
Broken or malformed URLs

Update Internal Links

Confirm that navigation menus, contextual links, breadcrumbs, related-content links, and footer links point directly to the new live URLs.

Avoid relying on redirects for internal navigation wherever possible. Update internal links so users and search engines reach the final destination directly.

Validate Metadata Migration

Spot-check and crawl key live pages to confirm that important on-page SEO elements have been carried over correctly.

Check:

Title tags
Meta descriptions
H1 headings
Meta robots directives
Important page content
Open Graph information, where relevant

Pay particular attention to high-value landing pages and important templates.

Validate Canonical Tags

Verify that production pages contain the correct canonical URLs.

Check that:

Canonicals point to the intended live URLs
No canonical references remain to staging or development environments
Canonicals are not pointing to redirected URLs
Important pages do not have conflicting or incorrect canonical signals
Canonical tags accurately reflect the preferred version of each page

Do not assume every page must have a self-referencing canonical; the correct canonical depends on the site’s URL and content architecture.

Validate Navigation and Internal Linking

Test the main header, footer, breadcrumbs, mobile navigation, and important contextual links on the live website.

Confirm that users can reach key pages and that important pages haven’t become unnecessarily difficult to discover after the migration.

Verify Robots.txt

Check the production robots.txt file immediately after launch.

Confirm that:

Important sections are not accidentally blocked
Development or staging restrictions have not been carried over
Critical CSS, JavaScript, or other resources are not unnecessarily blocked
The correct production sitemap is referenced where appropriate

Remove Unintended Noindex and Development Restrictions

Confirm that temporary development restrictions have not been carried into production.

Check for:

noindex meta tags
X-Robots-Tag directives
Authentication requirements
IP restrictions
Staging access controls
Development environment restrictions

This is one of the most important post-launch checks because an accidental noindex directive can prevent important pages from appearing in search results.

Generate and Submit the XML Sitemap

Generate or update the production XML sitemap so that it contains the appropriate canonical, indexable URLs from the new website.

Then:

Validate the sitemap
Confirm it returns a successful HTTP response
Check that URLs use the correct production domain
Remove redirected, blocked, and non-canonical URLs where appropriate
Submit the sitemap through Google Search Console
Submit it through Bing Webmaster Tools where applicable

Validate Structured Data

Validate structured data on key page templates and important migrated pages.

Check that:

Expected schema markup is present
Required properties are populated
URLs reference the correct production pages
Markup accurately represents visible page content
No critical validation errors exist
Important structured data from the previous site has not been unintentionally removed

Remember that valid structured data does not guarantee rich results; Google determines eligibility and display.

Verify HTTPS Configuration

Confirm that the production website is fully accessible over HTTPS.

Check that:

The SSL/TLS certificate is valid
HTTP URLs redirect to HTTPS
There are no mixed-content issues
Canonicals use HTTPS where appropriate
Internal links use the correct HTTPS URLs
XML sitemaps use HTTPS URLs
Important resources load securely

Validate Analytics and Conversion Tracking

Confirm that GA4, Google Tag Manager, advertising pixels, and other measurement systems are working correctly on the live website.

Test:

Page views
Key events
Lead-generation forms
Purchases
Ecommerce events
Conversion events
Phone or WhatsApp interactions, where applicable
Cross-domain tracking, where applicable
Consent configuration

Compare the implementation against your pre-migration tracking baseline to identify unexpected changes.

Validate HTTP Status Codes

Verify HTTP status codes across important migrated URLs immediately after launch.

Confirm that:

New important pages return 200 OK
Permanently moved legacy URLs return 301 or 308
No important pages unexpectedly return 404
No important pages return 5xx server errors
No unexpected 302/307 temporary redirects have replaced permanent redirects
Redirect chains and loops are not present

For large websites, automate this validation with a crawl rather than checking URLs manually.

Test Critical User Journeys

Test the most important customer journeys on the live website.

Depending on the business, this may include:

Contact forms
Lead-generation forms
Account registration
Login
Product search
Filters
Add-to-cart functionality
Checkout
Test purchases
Booking journeys
Confirmation pages
Payment gateways
Third-party integrations

Confirm that both the user experience and associated conversion tracking work correctly.

Verify Google Search Console

Immediately after launch, check Google Search Console for unexpected issues.

Indexing
Page indexing
Sitemaps
Crawl statistics
HTTPS status
Manual actions
Security issues
Search performance
URL Inspection for important pages

For a major domain or URL migration, ensure that the appropriate Change of Address process is followed in Search Console when applicable.

Run a Post-Launch Crawl

Run a fresh crawl of the live website and compare it with your pre-migration crawl.

Look for:

Unexpected 404s
Redirect chains
Redirect loops
Broken internal links
Missing metadata
Canonical changes
Indexability changes
Missing structured data
Orphan pages
Unexpected URL changes
Incorrect robots directives

This comparison is one of the fastest ways to identify migration problems that weren’t caught during staging.

Post-Migration SEO Checklist

The work does not stop once the new website goes live. The weeks following launch are critical for identifying technical, SEO, analytics, and performance issues before they have a significant impact on traffic, conversions, or revenue.

Monitor Indexation

Monitor Google Search Console closely after launch to understand how Google is discovering, crawling, and indexing the new website.

Review:

Indexed pages
Newly discovered URLs
Excluded pages
Indexing errors
Valid and invalid sitemap URLs
Unexpected changes in indexed page counts
Important URLs using URL Inspection

Pay particular attention to high-value pages that should be indexed but remain excluded or are unexpectedly removed from Google’s index.

Validate Redirects

Run post-launch crawls to identify redirect issues that may not have been detected during staging.

Check for:

Missing redirects
Redirect chains
Redirect loops
Incorrect destinations
Unexpected 404 responses
Legacy URLs that were not included in the redirect mapping

Prioritize URLs that previously generated significant organic traffic, conversions, or backlinks.

Monitor Crawl and Server Errors

Review Google Search Console and server monitoring data regularly during the first few weeks after launch.

Look for:

New 404 errors
5xx server errors
Unexpected crawling restrictions
Sudden changes in crawl activity
URLs that Google is repeatedly requesting but cannot access

For large or enterprise websites, combine Search Console data with server-log analysis to identify crawl issues that may not be immediately visible in standard SEO tools

Monitor Organic Traffic and Conversions

Compare organic traffic against your pre-migration baseline across:

Users
Sessions
Landing pages
Leads
Purchases
Conversion rate
Organic revenue

Do not judge the migration based on traffic alone. A small traffic change may be less concerning if qualified leads and revenue remain stable, while a modest traffic decline can be significant if high-value commercial pages are affected.

Monitor Keyword Rankings

Track priority commercial keywords, important landing pages, and other strategically important queries.

Look for:

Significant ranking losses
New ranking opportunities
Pages losing visibility after URL changes
Keywords where the wrong page is now ranking
Changes in branded and non-branded visibility

Ranking fluctuations are not necessarily evidence of a migration failure. Compare ranking changes with traffic, indexing, crawlability, content, and technical signals before drawing conclusions.

Validate Metadata and On-Page SEO

Periodically crawl the live website to make sure CMS changes, template issues, or plugin updates have not overwritten important SEO elements.

Check:

Title tags
Meta descriptions
H1 headings
Meta robots directives
Canonical tags
Important page content

Review Internal Links

Run a fresh internal-link audit after launch to identify:

Broken internal links
Links pointing to old URLs
Links passing through unnecessary redirects
Newly created orphan pages
Important pages that have lost internal links
Changes to contextual linking

Compare the new internal-link structure with your pre-migration benchmark to identify significant changes in how important pages are connected.

Validate Structured Data

Re-crawl important page templates and validate structured data after launch.

Confirm that:

Expected markup is still present
Markup accurately reflects visible content
URLs reference the correct production pages
No critical validation errors have appeared
Important structured data was not lost during deployment

Monitor Core Web Vitals and Performance

Performance can change significantly after a migration, particularly following redesigns, platform changes, infrastructure updates, or changes to JavaScript and third-party integrations.

Monitor:

LCP
INP
CLS
Server response times
Page load performance
Mobile performance

Compare the new site’s performance against your pre-migration baseline and investigate significant regressions.

Monitor Server Logs

For large and enterprise websites, server-log analysis can provide valuable insight into how Googlebot and other crawlers interact with the new website.

Use log data to identify:

Repeated requests to old URLs
Crawl attempts returning errors
Blocked resources
Unexpected crawl patterns
Excessive crawling of low-value URLs
Important pages receiving little or no crawler activity

Compare Against the Pre-Migration Benchmark

Measure post-migration performance against the benchmarks established before launch.

Compare:

Organic traffic
Organic landing pages
Keyword visibility
Indexed pages
Leads
Conversions
Revenue
Backlinks
Core Web Vitals
Crawl and indexing health

A successful migration should not only preserve important SEO performance but also create opportunities for future growth. Comparing post-launch results with pre-migration data helps identify problems, measure the project’s success, and prioritize further optimization.

AI Visibility Monitoring After Migration

AI-powered search experiences add another layer to post-migration monitoring. However, AI visibility should be treated as a complement to traditional SEO monitoring, not as a replacement for rankings, organic traffic, conversions, or indexing data.

A migration can change how content is discovered, interpreted, and cited across AI-powered search experiences, so establish a consistent baseline before launch and compare it with post-migration observations.

Monitor AI-Powered Search Visibility

Re-run the important prompts and queries used during your pre-migration AI visibility benchmark.

Monitor:

Brand mentions
Products and services mentioned
Cited URLs
Sources referenced
Competitor visibility
Accuracy of brand information
Important pages that are no longer being surfaced.

Because AI-generated results can vary between queries, users, platforms, and time periods, focus on trends and recurring observations rather than treating individual responses as definitive rankings.

Monitor AI Referral Traffic

Where referral data is available, monitor traffic arriving from AI platforms such as ChatGPT, Perplexity, Gemini, and Microsoft Copilot.

Compare:

Referral sessions
Landing pages
Engaged sessions
Conversions
Revenue
Referral trends over time

Do not assume that all AI-generated visits will be consistently identifiable in analytics. Referral attribution can vary by platform and implementation, so use available analytics data alongside other visibility measurements.

Validate Brand and Entity Information

Review important brand and organization information after migration to ensure that it remains accurate, consistent, and accessible.

Check:

Organization information
Brand name and descriptions
Products and services
Contact details
Locations
About pages
Relevant structured data
Author and reviewer information where applicable

The objective is to preserve clear and consistent information that helps users and search systems understand the organization and its content.

Review Content Relationships

Check that important content hubs, pillar pages, supporting articles, and contextual internal links remain connected after migration.

Pay particular attention to:

Broken internal links
Removed supporting content
Orphaned pages
Changes to navigation
Lost contextual links
Broken internal links
Removed supporting content
Orphaned pages
Changes to navigation
Lost contextual links
Important research or reference pages that are no longer well connected

Rather than assuming that “topic clusters” directly determine AI visibility, focus on preserving clear relationships between related content and making important resources easy to discover.

Review Citation-Worthy Content

Identify important resources that may be valuable sources for AI-powered search experiences, including:

Original research
Statistics
Industry reports
Case studies
Data-driven resources
Detailed guides
Original insights

Confirm that these pages remain:

Live
Accessible
Indexable where appropriate
Internally linked
Accurate
Properly attributed
Available at the expected URLs

If a frequently cited page has moved, make sure the old URL redirects correctly and that the new page preserves the important content and context.

Conclusion

A successful website migration is much more than moving pages from one platform, domain, or URL structure to another. It is a carefully managed process that protects the SEO value, content, user experience, analytics, conversions, and technical foundations your business has built over time.

The safest migrations start early. By establishing a clear pre-migration baseline, auditing your existing website, mapping URLs and redirects, testing the new environment, validating the launch, and closely monitoring performance after deployment, you can identify and address issues before they become costly problems.

In 2026, migration planning also needs to consider how users discover information through AI-powered search experiences. Preserving valuable content, clear brand information, structured data, internal linking, and other important sources of visibility can help your website remain discoverable as search continues to evolve.A migration should not be viewed simply as a risk to manage. With the right planning and execution, it can be an opportunity to improve your website’s architecture, performance, user experience, conversion paths, and long-term organic growth.

Frequently Asked Questions (FAQs)

Will a website migration automatically disrupt my AI search visibility?

Not necessarily, but a migration can affect how your content is discovered, interpreted, and cited across AI-powered search experiences. Changes to URLs, content, internal linking, structured data, and important brand information can alter the sources available to AI systems. Before and after migration, benchmark important AI search queries, protect frequently cited pages, and make sure key content and brand information remain accessible and accurate.

How long should I expect organic traffic to fluctuate after launch?

There is no fixed recovery period because the impact depends on the size and complexity of the migration, the number of URLs affected, the quality of the redirect implementation, and how quickly search engines recrawl and process the changes. Smaller migrations may stabilize relatively quickly, while large enterprise or ecommerce migrations can experience fluctuations for several weeks or longer. Monitor Google Search Console, analytics, rankings, indexing, and conversions closely during the months and continue comparing performance against your pre-migration baseline.

Can a simple website redesign trigger the same SEO risks as a full domain migration?

Yes. A redesign can create significant SEO risks even when the domain remains unchanged. Changes to URLs, navigation, internal linking, page templates, content, metadata, canonical tags, structured data, or rendering can affect crawling, indexing, and organic visibility. The level of risk depends on what changes as part of the redesign—not simply whether the domain changes.

Do I need to update my internal links if all my old URLs redirect properly?

Yes, wherever practical. Redirects can successfully send users and search engines from old URLs to their new destinations, but internal links should generally point directly to the final URLs. Updating them reduces unnecessary redirect requests, keeps your internal architecture clean, simplifies future maintenance, and helps users and crawlers reach the intended pages directly.

Should I keep the old URLs after a website migration?

Yes. Keep redirects from important old URLs for as long as they continue to provide value, particularly when those URLs have backlinks, traffic, or other external references. Avoid removing redirects immediately after launch simply because the new URLs are live.

Should I launch a website migration all at once or in stages?

The right approach depends on the size and complexity of the website. Smaller websites can often be migrated in a single controlled deployment, while very large websites may benefit from a phased approach. Whatever method you choose, maintain a clear URL mapping, test thoroughly, and monitor each stage before expanding the rollout.

What should I do if organic traffic drops after a migration?

First, determine whether the decline is temporary or caused by a technical issue. Check redirects, indexability, robots.txt, canonical tags, XML sitemaps, server errors, internal links, content changes, analytics tracking, and Google Search Console data. Compare affected URLs with your pre-migration benchmark to identify where the decline began. Fix technical issues first, then investigate content and ranking changes.

Should I migrate SEO and analytics tracking at the same time?

Analytics and SEO should be planned together, but tracking should be tested independently before and immediately after launch. Make sure GA4, Google Tag Manager, conversion events, ecommerce tracking, consent settings, and other measurement systems are correctly configured on the new website. Without reliable tracking, it becomes much harder to determine whether a migration has affected leads, sales, or revenue.

(Visited 1 times, 1 visits today)

gmi-admin