Skip to content
SEO Migration

Website Migration SEO Checklist: Preserving Rankings During Domain or Platform Changes

A comprehensive guide to executing a website migration without losing organic traffic. Learn how to handle 301 redirects, technical audits, and post-launch monitoring to protect your SEO equity.

8 min readSysGenPro Editorial
Website Migration SEO Checklist: Preserving Rankings During Domain or Platform Changes

What Is a Website Migration SEO Checklist and Why Is It Critical?

A website migration SEO checklist is a structured set of technical, content, and strategic steps designed to preserve organic search visibility during a domain change, platform switch, or major site redesign. The primary business risk of a migration is the loss of accumulated SEO equity, including rankings, backlinks, and brand authority. Without a rigorous plan, businesses often experience significant drops in organic traffic that can take months to recover. The practical recommendation is to treat the migration as a technical project with a dedicated SEO workstream, ensuring that every URL, asset, and metadata element is mapped and verified before launch. This approach minimizes downtime, prevents indexation errors, and ensures that search engines can efficiently transfer link equity from the old site to the new one.

Pre-Migration Audit and Planning Phase

Before any code is changed or domains are purchased, a comprehensive audit of the existing website is essential. This phase establishes the baseline for success and identifies potential pitfalls. The goal is to understand the current state of the site's technical health, content inventory, and backlink profile. This data will drive the mapping strategy and help prioritize which pages require the most attention during the transition.

Crawl and Indexation Analysis

Use a crawler to generate a complete list of indexed URLs. Compare this list with the XML sitemap and the robots.txt file to identify discrepancies. Look for pages that are indexed but not in the sitemap, or pages that are blocked by robots.txt but still have backlinks. This step ensures that you are not accidentally dropping valuable pages or ignoring pages that search engines have already discovered. Additionally, check for any existing crawl errors, such as 404s or 500 errors, that need to be resolved before the migration begins.

Analyze the backlink profile to identify the most authoritative referring domains and the specific URLs they link to. High-value backlinks pointing to pages that will be removed or changed require careful handling. Create a content inventory that categorizes pages by their business value, traffic volume, and conversion rate. This inventory helps in deciding which pages should be kept, consolidated, or redirected. Pages with high traffic and high conversion value should be prioritized for one-to-one mapping, while low-value pages may be consolidated into broader category pages.

URL Mapping and Redirect Strategy

The core of a successful migration is the URL mapping document. This document defines how every old URL will behave on the new site. The standard practice is to use 301 redirects for all pages that are moving to a new location or domain. A 301 redirect signals to search engines that the move is permanent and transfers the majority of link equity to the new URL. Avoid using 302 redirects, as these are temporary and do not transfer link equity effectively. The mapping should be exhaustive, covering every indexed URL, not just the top-performing ones.

Old URLNew URLRedirect TypeReason for ChangePriority
/old-product-page/new-product-category301Product line discontinuedHigh
/blog/post-1/blog/post-1301Domain changeMedium
/about-us/company/about301Site structure changeHigh
/contact/contact301Domain changeHigh
/old-promo/404410Promotion expiredLow

When mapping URLs, avoid creating redirect chains, where an old URL redirects to a middle URL, which then redirects to the final URL. Redirect chains dilute link equity and slow down page load times. Each old URL should point directly to its final destination. If a page is being removed entirely, consider using a 410 Gone status code if the content is no longer relevant, or redirect it to the most relevant category page if the topic still exists elsewhere on the site.

Technical Implementation and Configuration

Once the mapping is complete, the technical implementation begins. This involves configuring the new server or platform to handle the redirects and ensuring that all technical SEO elements are correctly set up. This phase requires close collaboration between developers and SEO specialists to ensure that the new site is crawlable and indexable from day one.

Server Configuration and Redirects

Implement the 301 redirects at the server level, such as in the .htaccess file for Apache servers or the Nginx configuration. This is more efficient than using JavaScript or meta tags for redirects, as it happens before the page content is loaded. Test the redirects using a script or a tool to ensure that every old URL returns the correct status code and points to the intended new URL. Pay special attention to case sensitivity and trailing slashes, as these can cause unexpected 404 errors if not handled correctly.

Sitemaps, Robots.txt, and Canonicals

Update the XML sitemap to include only the new URLs and submit it to Google Search Console and Bing Webmaster Tools. Ensure that the robots.txt file does not block any important resources, such as CSS, JavaScript, or the sitemap itself. Verify that canonical tags are correctly implemented on all pages to prevent duplicate content issues. If the site uses multiple domains or subdomains, ensure that the canonical tags point to the preferred version of the URL. This helps search engines understand which version of the page should be indexed.

Content and Metadata Preservation

During the migration, it is crucial to preserve all on-page SEO elements. This includes title tags, meta descriptions, header tags, image alt text, and structured data. Losing these elements can result in a drop in click-through rates and relevance signals. Ensure that the new CMS or platform allows for the easy transfer of this metadata. If the content is being rewritten or restructured, ensure that the core semantic meaning and keywords are retained. Structured data, such as schema markup for products, articles, or local businesses, should be validated using the Rich Results Test to ensure it remains valid after the migration.

Post-Launch Monitoring and Verification

The migration is not complete when the site goes live. The first few weeks are critical for identifying and fixing any issues that may have been missed. Monitor the site closely using Google Search Console, analytics tools, and manual testing. Look for spikes in 404 errors, drops in indexed pages, or changes in average position. If you notice a significant drop in traffic, investigate the cause immediately. Common issues include incorrect redirects, blocked resources, or indexing delays. Be prepared to make quick adjustments to the server configuration or content to resolve these issues.

  • Check Google Search Console for new crawl errors and index coverage issues.
  • Monitor organic traffic and keyword rankings daily for the first two weeks.
  • Test a sample of old URLs to ensure they redirect correctly to the new pages.
  • Verify that the new sitemap is being crawled and indexed.
  • Check for any broken internal links that may have been missed during the mapping process.

Common Pitfalls and How to Avoid Them

Many migrations fail due to avoidable mistakes. One common pitfall is not mapping all URLs, leading to orphaned pages that lose their link equity. Another is using the wrong type of redirect, such as a 302 instead of a 301, which fails to transfer authority. Additionally, failing to update the canonical tags can lead to duplicate content issues, where search engines are unsure which version of the page to index. To avoid these pitfalls, use a systematic approach, double-check your work, and involve multiple stakeholders in the review process.

Measuring Success and Long-Term Impact

Success in a website migration is measured by the retention of organic traffic and rankings over time. While some fluctuation is normal in the first few weeks, a sustained drop in traffic indicates a problem. Track key metrics such as organic sessions, average position, and conversion rate. Compare these metrics to the pre-migration baseline to assess the impact. If the site recovers and continues to grow, the migration was successful. If not, use the data to identify areas for improvement and make necessary adjustments. Long-term monitoring is essential to ensure that the new site continues to perform well and that any new issues are addressed promptly.

Frequently Asked Questions

Here are answers to common questions about website migration SEO.

How long does it take for a migration to affect SEO?

It typically takes 2-4 weeks for search engines to fully process the changes and re-index the new site. However, the full impact on rankings may take longer, depending on the size of the site and the competitiveness of the keywords.

Should I use 301 or 302 redirects?

Written by
SysGenPro Editorial

SysGenPro Editorial

Platform & solutions team

Practical guidance on ERP, AI automation, cloud deployment and enterprise transformation from the SysGenPro team.

Share this article
Continue learning
View all articles
Explore the platform

Where to go next

Browse the knowledge hub

See how SysGenPro fits your business

Discuss your workflows, modules and deployment options with our team.

Back to resources