The Pre-Migration SEO Audit: 7 Things to Do Before You Switch Platforms

A pre-migration SEO audit is a critical process for safeguarding your website's search engine rankings before switching platforms. It involves benchmarking your current performance, mapping all URLs, preserving valuable content, and preparing for technical changes to prevent traffic loss and ensure a smooth transition. This audit identifies risks and creates a data-driven plan for your move.

Why a Pre-Migration Audit Is Non-Negotiable

Website migrations are one of the riskiest activities in digital marketing. When you move your site, you change the underlying code, URL structures, and server configurations that search engines like Google use to understand and rank your content. Without a proper plan, it’s easy to lose years of accumulated SEO value overnight.

Think of it like moving a retail store to a new location. You wouldn't just pack up and go without telling your customers the new address, forwarding your mail, or making sure the new layout is easy to navigate. A pre-migration audit is the digital equivalent of that careful planning. It ensures your "customers" (search engine bots and users) can find you at your new address without any confusion.

The core goal is to preserve, and ideally improve, your existing search visibility. This means keeping the pages that rank well, maintaining the link equity you've built, and ensuring the new site is technically sound and user-friendly. A rushed migration without this step often leads to weeks or months of frantic damage control, trying to recover lost rankings and traffic. Our seven-step checklist below gives you a structured way to avoid this scenario.

The 7-Step SEO Migration Checklist

Follow these seven steps to create a comprehensive pre-migration plan. This process will form the backbone of your website migration checklist, ensuring no critical SEO element is overlooked.

1. Benchmark Everything: Capture Your "Before" Picture

Before you touch a single line of code, you need a complete and accurate snapshot of your current site's performance. This data is your baseline. It's the only way to know if your migration was a success and provides the information needed to diagnose any post-launch issues.

What to document:

• Keyword Rankings: Use a tool like Semrush or Ahrefs to export your current rankings for all tracked keywords. Pay special attention to keywords that rank on page one (positions 1–10) and those driving the most traffic.
• Organic Traffic and Conversions: In Google Analytics 4 (GA4), document your average daily, weekly, and monthly organic traffic. Record conversion rates for key goals, like form submissions or product purchases. Look at data for the last 30, 90, and 365 days to understand seasonality.
• Top Performing Pages: Identify your most valuable pages. This isn't just about traffic. Look for pages with high conversion rates, the most backlinks, or the highest number of ranking keywords. You can find this data in Google Search Console (GSC) and your analytics platform.
• Crawl Data: Run a full crawl of your live site using a tool like Screaming Frog or Sitebulb. This crawl will capture all your URLs, title tags, meta descriptions, H1 tags, status codes (200, 404, etc.), and more. Save this crawl file: it is your single source of truth for the old site.
• Backlink Profile: Export a complete list of all backlinks pointing to your site from a tool like Ahrefs, Majestic, or Moz. This tells you which pages have the most authority, which you absolutely cannot afford to break.

This benchmarking phase gives you a clear set of KPIs to measure against after the migration. If your traffic for a top page drops by 50% post-launch, you'll know immediately and can use this "before" data to investigate why.

2. Create a Comprehensive URL Map

This is the most critical and time-consuming part of the audit, but it's the foundation of a successful migration. You need to create a master spreadsheet that maps every single URL from your old site to a corresponding URL on the new site. This map will be used to implement 301 redirects.

A 301 redirect is a permanent redirect that tells search engines and browsers that a page has moved. It passes most of the link equity (ranking power) from the old URL to the new one.

How to build your URL map:

1. Start with your crawl file: Use the list of URLs you gathered in step one as your starting point. This ensures you account for every indexed page.
2. Create two columns: "Old URL" and "New URL".
3. Map one-to-one where possible: If your blog post at `oldsite.com/blog/my-post` is moving to `newsite.com/articles/my-post`, that's a simple mapping. Your goal is to keep URL structures as similar as possible.
4. Handle structural changes: Often, a migration involves changing the URL structure. For example, you might be moving from WordPress (`/YYYY/MM/DD/post-name/`) to a cleaner structure (`/blog/post-name/`). Map these systematically.
5. Decide what to cut: You will likely find old, low-quality, or irrelevant pages during this process. This is your chance to prune them. If a page has no traffic, no backlinks, and no business value, you can let it go. Redirect it to a relevant parent category page or the homepage instead of a direct equivalent. Do not leave it as a 404 error.

Your finished map is the blueprint for your developer. It removes all guesswork and ensures every valuable old page forwards users and search bots to the correct new page.

3. Perform a Content Audit and Archive

Not all content is worth migrating. A platform switch is the perfect opportunity to evaluate your content and decide what to keep, what to improve, and what to discard.

Categorize your content:

• Keep and Migrate As-Is: These are your high-performing assets. They get good traffic, have strong backlinks, and generate leads or sales. These pages should be migrated with minimal changes.
• Improve and Migrate: These pages show potential. They might rank on page two or three, get some traffic, or cover an important topic but are outdated. Tag these for a content refresh after the migration. You might update statistics, add new sections, or improve the on-page SEO.
• Consolidate and Migrate: You may have multiple posts or pages competing for the same keyword (keyword cannibalization). For example, three different blog posts about "small business accounting tips." Combine the best elements of each into a single, comprehensive guide on a new URL. Then, 301 redirect the old, weaker pages to the new pillar page.
• Archive and Redirect: These are pages with little to no traffic, no backlinks, and no strategic value. There's no need to move them to the new platform. Redirect their URLs to a relevant category page or the homepage using your URL map.

For all content you plan to keep, make sure you have a full backup. Use a tool to download the text, images, and other media assets. This protects you against data loss during the transition.

4. Analyze Technical SEO Elements

Different platforms handle technical SEO in different ways. What worked on your old WordPress site with Yoast SEO might not translate directly to a new Webflow or Squarespace site. You need to audit the technical foundation of both the old and new sites.

Key technical items to check:

• Robots.txt: This file tells search engines which pages they can and cannot crawl. Compare the `robots.txt` file on your old site to the one on the new staging site. Ensure you aren't accidentally blocking important sections of your new site. A common mistake is leaving a `Disallow: /` command from the development phase in the live file, which tells search engines to ignore the entire site.
• XML Sitemaps: Your new site needs an accurate XML sitemap that lists all the pages you want Google to index. Check that the new sitemap is generated correctly, is free of errors, and is submitted to Google Search Console upon launch.
• Canonical Tags: Canonical tags (`rel="canonical"`) tell search engines which version of a URL is the "master" copy when duplicate content exists. Check that your new platform implements these correctly, especially on pages with parameters or print versions.
• Schema Markup (Structured Data): If you use schema for things like product reviews, events, or FAQs, ensure it is correctly implemented on the new site. Use Google's Rich Results Test tool to validate the markup on your staging site before you go live.
• Page Speed: Performance is a critical ranking factor. Use Google's PageSpeed Insights to test the speed of key templates on your new staging site (homepage, blog post, product page). A migration should ideally result in a faster website, not a slower one.

5. Review On-Page SEO Factors

This step involves ensuring that your core on-page optimization elements are transferred correctly to the new platform. Your initial site crawl gives you the data you need for this comparison.

Compare these elements between the old site and the staging site:

• Title Tags and Meta Descriptions: These are critical for click-through rates from search results. Ensure that every migrated page has its title tag and meta description carried over. Many platforms auto-generate these, which can overwrite your carefully crafted originals. Your URL map spreadsheet should have columns for these elements so you can verify them.
• Headings (H1, H2, H3): Headings provide structure and context for both users and search engines. Verify that your new site's templates use headings correctly. There should be only one H1 per page, which typically matches the page's main topic. Subheadings (H2, H3) should be used to organize the content logically.
• Image Alt Text: Alt text describes an image for visually impaired users and for search engines. It's an important accessibility and SEO feature. Check that your alt text from the old site has been migrated with your images.
• Internal Linking: Your internal links help distribute page authority and help Google understand your site structure. When you change URL structures, internal links can break. Use your staging site crawl to check for any broken (404) internal links and fix them before launch.

Platforms like WorkspaceCMS provide built-in SEO tools that make managing these elements simple. You can edit titles, metas, and alt text directly from one dashboard, ensuring consistency without needing separate plugins.

6. Prepare Your Go-Live Technical Plan

The actual launch day can be stressful. A detailed plan ensures a smooth process and minimizes downtime.

Your launch day checklist should include:

1. Choose a low-traffic period: Plan the launch for a time when your site receives the least amount of traffic, like late at night or over a weekend. This minimizes the impact on users if issues arise.
2. Implement the 301 redirects: This is step one after the new site is live. Take your URL map and implement every redirect. This is often done via a server configuration file (`.htaccess` on Apache) or through a platform's built-in redirect manager.
3. Update DNS settings: This is the technical step that points your domain name to the new server. It can take anywhere from a few minutes to 48 hours to propagate fully.
4. Unblock search engines: Remove any blocks from the staging environment. This means ensuring the live `robots.txt` file allows crawling and removing any "noindex" meta tags from the site's header.
5. Submit the new XML sitemap: In Google Search Console, submit your new sitemap to prompt Google to crawl your new URLs quickly.
6. Set up analytics and tracking: Make sure your Google Analytics 4 tag, Google Tag Manager container, and any other tracking scripts (like a Meta Pixel) are installed and working correctly on the new site.

7. Plan for Post-Migration Monitoring

The work isn't over once the new site is live. For the first few weeks, you need to monitor your site closely to catch and fix any issues before they cause significant SEO damage.

Key monitoring tasks:

• Crawl the new live site: Run a new crawl with Screaming Frog immediately after launch. Look for 404 errors (broken links), 302 redirects (which should be 301s), and redirect chains.
• Watch Google Search Console: Pay close attention to the "Indexing" report in GSC. Look for spikes in "Not Found (404)" errors or other crawl anomalies. Use the URL Inspection tool to check the status of key pages.
• Monitor keyword rankings: Keep a close eye on your rankings. Some fluctuation is normal in the first one to three weeks, but you should not see a catastrophic drop. If you do, use your benchmark data to investigate which pages were affected.
• Check organic traffic: Compare your post-launch organic traffic in GA4 to the benchmark data you collected. Are there any major drops on specific pages or sections of the site?

A thorough pre-migration audit makes this post-launch phase much easier. When a problem appears, you have all the "before" data needed to understand what changed and how to fix it.

Pre-Migration Audit FAQ

What is a website migration?

A website migration is any significant change to a site's location, platform, structure, content, or design. Common examples include switching hosting providers, moving from HTTP to HTTPS, changing content management systems (like migrating from Wix to Squarespace), or redesigning the site with major URL changes.

How long does it take for Google to recognize a site migration?

Google can begin recognizing changes within hours of crawling the new site, but it can take several weeks for rankings to fully stabilize. During this period, some ranking fluctuations are normal as Google processes the 301 redirects and re-evaluates the new site structure and content. A well-executed migration minimizes this period of volatility.

What is the biggest mistake to avoid during a website migration?

The single biggest mistake is failing to implement a comprehensive 301 redirect map. Forgetting to redirect old URLs to their new equivalents tells Google the old pages are gone (404 errors), effectively deleting their search equity. This can cause a catastrophic and immediate loss of organic traffic.

Can I migrate my website without losing SEO?

Yes, it is possible to migrate a website with minimal to no long-term loss in SEO value. Some temporary fluctuation is expected, but a thorough pre-migration audit and a careful technical launch will preserve your rankings, backlinks, and traffic. In many cases, moving to a better, faster platform can even improve your SEO over time.

Do I need a developer to help with a website migration?

For most migrations, especially those involving a platform change or complex redirect mapping, working with an experienced developer is highly recommended. They can handle the technical implementation of redirects, manage DNS changes, and troubleshoot server-side issues that are often beyond the scope of a marketing team.