SEO audit for migrations is a structured process of evaluating a website before, during, and after a move to ensure that search engine visibility remains stable. This procedure involves mapping old URLs to new destinations, verifying technical configurations, and monitoring indexing status to prevent significant traffic loss. By identifying potential roadblocks in a staging environment, you can address crawl errors or redirect loops before they impact your live audience. A successful migration depends on how well you communicate these changes to search engines while maintaining the user experience for your visitors.
Why is a pre-migration SEO audit necessary?
A pre-migration audit serves as the essential baseline for your entire transition strategy. When you change a site’s structure, domain, or protocol, you are essentially asking search engines to relearn your digital footprint. Without a detailed audit of your current state, you have no way to measure the impact of the move or identify which pages were lost in the process. This phase focuses on gathering data from Google Search Console, analytics platforms, and crawling tools to build a master list of every active URL. This list ensures that no high-value page is left behind or forgotten during the site launch.
During this phase, it is vital to identify your top-performing content. In a typical account, about 20% of the pages often drive 80% of the organic traffic. If these pages are not correctly mapped or if their technical health declines during the move, the financial impact can be severe. A pre-migration audit allows you to document existing metadata, header tags, and internal linking structures. This documentation acts as a reference point to ensure that the new site meets or exceeds the SEO standards of the old one. It also helps in setting realistic expectations for stakeholders regarding temporary fluctuations in rankings.
How to map URLs for a successful transition?
URL mapping is the core of any SEO audit for migrations. It involves creating a direct link between every old URL and its most relevant counterpart on the new site. Google Search Central documentation recommends planning URL mappings and setting up 301 redirects before launching a site migration to preserve search presence. This means you should not wait until the site is live to decide where old traffic should go. A common pattern is to use a spreadsheet where column A lists the legacy URLs and column B lists the destination URLs. This map serves as the instruction set for your server-side redirects.
When mapping URLs, avoid the temptation to redirect all old pages to the homepage. This is often treated as a soft 404 by search engines, which means the link equity from the old page will not transfer to the new site. Instead, find the closest topical match for each page. If a specific product page is being removed, redirect it to the parent category page. If a blog post is being updated with a new URL slug, ensure the 301 redirect is a 1-to-1 match. This level of detail helps search engines understand that the content has moved rather than disappeared, which is critical for maintaining your authority.
What are the essential technical checks for staging?
The staging environment is where you test the new site’s architecture before the public sees it. Your audit here must focus on technical integrity. Check the robots.txt file to ensure it is not accidentally blocking essential resources. While it is standard practice to use a noindex tag on staging to prevent duplicate content issues, you must have a plan to remove these tags exactly at the moment of launch. An overlooked noindex tag on a live production site can de-index an entire domain within days, leading to a total loss of search visibility that takes weeks to recover from.
You should also audit the internal linking structure on the staging site. Ensure that all links point to the new domain or the new URL structure rather than the old one or the staging URL. For example, if your staging site is at dev.example.com, all internal links should be updated to example.com before going live. Check the canonical tags as well; they should be self-referential to the new URLs. If the canonical tags still point to the old site or the staging environment, search engines will be confused about which version is the authoritative one, leading to indexing delays and ranking drops.
How Alien Road manages site migrations
Alien Road handles complex migrations through a rigorous technical framework designed to minimize downtime and ranking volatility. The process begins with a deep discovery phase where every URL is crawled and cross-referenced with performance data from the last 12 months. This allows the team to prioritize redirects based on actual business value. For instance, a Shopify store moving to a custom headless setup would require specific attention to product variants and collection filters. Alien Road uses proprietary scripts to automate the mapping of thousands of URLs, which are then manually reviewed by senior practitioners to ensure accuracy.
Once the mapping is complete, Alien Road performs a series of ‘smoke tests’ on the staging environment. These tests check for redirect chains, which can slow down crawl speed and degrade the user experience. The agency also verifies that the new site meets modern performance standards, such as a Largest Contentful Paint (LCP) of under 2.5 seconds. After the launch, the team monitors the Google Search Console API around the clock. This allows for the immediate detection of any 404 errors or indexing issues, enabling fixes to be deployed in hours rather than days. This proactive approach ensures that the migration is a growth opportunity rather than a recovery project.
Critical items for your migration checklist
- Create a full crawl of the existing site to capture all URLs, page titles, and meta descriptions.
- Identify high-traffic and high-backlink pages that require priority 1-to-1 redirects.
- Configure 301 redirects at the server level (e.g., .htaccess or Nginx config) rather than using plugins.
- Update all internal links to point directly to the new URLs without going through a redirect.
- Update XML sitemaps to include only the new URLs and submit them to Google Search Console.
- Verify that canonical tags are updated to reflect the new site structure.
- Check that robots.txt is correctly configured for the new environment.
- Monitor the ‘Change of Address’ tool in Google Search Console if moving to a new domain.
How to monitor performance after the migration?
Monitoring starts the minute the DNS changes take effect. Your primary tool will be Google Search Console. Look at the ‘Index Coverage’ report to see how quickly the old URLs are being removed and the new ones are being added. It is normal to see a temporary increase in ‘Valid with warnings’ or ‘Excluded’ pages during the first few weeks. However, a sharp rise in ‘Server error (5xx)’ or ‘Not found (404)’ for your high-priority pages indicates a problem with your redirect implementation. You should also monitor your server logs to verify that Googlebot is successfully following the 301 redirects.
Ranking tracking is another vital component of post-migration monitoring. Track your top 50-100 keywords daily for at least a month after the move. Small fluctuations are expected as Google re-evaluates the site, but a steady decline over two weeks suggests that the new site may have technical or content-related issues. Check the site speed of your most important pages using PageSpeed Insights. If the new site is significantly slower than the old one, it may struggle to maintain its previous rankings, even if the redirects are perfect. Performance is a key factor in how search engines perceive the quality of a migration.
Common mistakes that lead to traffic loss
One of the most frequent errors is leaving the staging site’s robots.txt file in place. If the staging file blocks all crawlers, and you copy it to the live site, your entire domain will disappear from search results. Another common mistake is creating redirect chains. This happens when URL A redirects to URL B, which then redirects to URL C. Search engines may stop following the chain if it becomes too long, and each jump can cause a slight loss in link equity. Always aim for a single-hop redirect from the old URL directly to the final destination.
Neglecting to update external links is another missed opportunity. While you cannot change every link on the internet that points to your site, you should reach out to your most important partners or directory listings to have them update their links to your new URLs. This reduces the reliance on redirects and provides a faster experience for users. Furthermore, failing to update your Google Business Profile, social media bios, and email signatures can lead to fragmented brand signals. Consistency across all platforms helps search engines verify the new site’s identity and authority more quickly.
Steps to audit your redirects
- Run a crawl of the old URL list and check the status code for each; it should return a 301.
- Check the destination URL for each redirect to ensure it is the correct, intended page.
- Identify any 404 errors for pages that were supposed to be redirected.
- Ensure that redirects are not pointing to other redirects (chains).
- Verify that the redirects work for both the www and non-www versions of the site.
- Check that both HTTP and HTTPS versions redirect correctly to the final secure URL.
Where to start this week
Begin by performing a comprehensive crawl of your current live website to create a master list of all URLs. Export this data into a spreadsheet and include columns for organic sessions and backlink counts. This will allow you to see exactly which pages are your ‘crown jewels’ that must be protected at all costs. Once you have this list, share it with your development team to start the mapping process. If you are within two weeks of a launch, double-check your staging environment for any ‘noindex’ tags or robots.txt restrictions that could interfere with the transition. Establishing this baseline today is the only way to ensure a controlled and successful migration.
Keep reading: SEO (Search Engine Optimization) · SEO