A website migration SEO checklist is a structured sequence of technical tasks designed to move a website to a new domain, platform, or structure while preserving its existing organic search visibility. This process involves auditing every current URL, creating a detailed redirect map, and testing the new environment to ensure that search engines can continue to index the site correctly. By following a clear plan, marketing teams can prevent the sudden loss of traffic and keyword rankings that often occurs when site changes are made without technical oversight.
What are the common types of website migrations?
A site migration can take several forms depending on the business goals. The most common type is a domain migration, where a company changes its web address, such as moving from a .net to a .com extension or rebranding entirely. Another frequent scenario involves moving from one Content Management System (CMS) to another, such as migrating from a legacy custom-built platform to a modern system like Shopify or WordPress. This often changes the underlying URL structure, which requires careful attention to avoid broken links and lost rankings.
Protocol migrations are also standard, specifically moving from HTTP to HTTPS for security reasons. While most sites have already made this change, new security standards sometimes require further updates to SSL certificates or server configurations. Structural migrations occur when a site stays on the same domain but changes its internal hierarchy, such as moving subfolders or changing how categories are organized. Each of these types carries different risks, but they all require a central checklist to manage the technical transition and communicate changes effectively to search engines.
Step 1: Pre-migration planning and site auditing
Before any files are moved or DNS settings are changed, a complete audit of the existing site is required. This means using a crawling tool to create a record of every page currently indexed by search engines. You should export a list of all URLs, their meta tags, and their current performance metrics from Google Search Console. This data serves as a baseline to measure the success of the migration later. If you do not have a clear picture of which pages are driving traffic now, you cannot ensure those pages will continue to perform after the move.
During this phase, it is also useful to identify pages that are no longer needed. A migration is a good time to prune low-quality content that does not contribute to your business goals. However, any page that has external backlinks must be accounted for in the redirect plan. Identifying these high-authority pages early allows you to prioritize them during the testing phase. A typical account will have a mix of high-traffic blog posts and essential product pages that need to be monitored most closely during the transition.
How do you map URLs for 301 redirects effectively?
Google advises thorough mapping of old URLs to new URLs and implementing 301 redirects to preserve search equity during migrations. This is perhaps the most technical part of the entire process. You must create a spreadsheet where every old URL is matched with its most relevant new equivalent. For example, if you are moving a page about ‘blue running shoes’ from your old site, it should point directly to the ‘blue running shoes’ page on the new site. Avoid the mistake of redirecting all old pages to the new homepage, as this loses the context of the content and can lead to a significant drop in keyword rankings.
When the mapping is complete, these redirects must be implemented at the server level using the .htaccess file or a server-side redirect manager. Permanent 301 redirects tell search engine crawlers that the content has moved permanently, prompting them to pass the ranking power from the old URL to the new one. If you use temporary 302 redirects by mistake, search engines may keep the old URL in their index, causing confusion and potentially leading to duplicate content issues. A detailed mapping document ensures that no page is left behind and that the user journey remains functional.
Technical SEO checks for the staging environment
The staging site is where you test the new website before it goes live to the public. It is essential to keep this environment hidden from search engines to prevent them from indexing a work-in-progress version of your site. Use a robots.txt file with a ‘Disallow: /’ command or password protection to keep crawlers out. While in staging, you should verify that all internal links are pointing to the new domain rather than the old one. This is a common error where developers accidentally leave links that point back to the staging URL or the old production site.
- Verify that all canonical tags are updated to reflect the new URL structure.
- Check that robots.txt is not accidentally blocking essential pages on the new site.
- Ensure that the mobile version of the site is fully functional and passes speed tests.
- Test the loading speed of key landing pages to maintain a strong user experience.
- Check that all structured data and schema markup are correctly implemented on the new pages.
- Confirm that XML sitemaps are generated correctly and contain only the new URLs.
How Alien Road manages complex site migrations
Alien Road approaches website migrations using a data-first methodology to minimize downtime and ranking fluctuations. Our process starts with a deep discovery phase where we use multiple data sources to identify every single URL that has ever received a backlink or a click. We do not just look at the current sitemap; we examine historical data to ensure that old pages forgotten by the current team are still redirected correctly. This prevents the loss of legacy link equity that often happens during manual migrations.
In a typical engagement, Alien Road sets up a parallel monitoring system. We use automated scripts to crawl the staging site and compare it against the production site, flagging any missing tags or broken links instantly. Once the site goes live, we provide a 30-day intensive monitoring period. During this time, we analyze server logs and Google Search Console data daily to catch any 404 errors that might have slipped through. This systematic approach allows our clients to focus on their business while we handle the technical complexities of the search engine transition.
Post-launch monitoring and troubleshooting
Once the new site is live, the work is not finished. The first task is to remove any ‘noindex’ tags or robots.txt blocks that were used in the staging environment. You must then submit the new XML sitemap to Google Search Console to alert the search engine that the site is ready to be crawled. If you have changed your domain name, you should use the ‘Change of Address’ tool in Google Search Console. This tool helps Google understand the relationship between the old and new domains and speeds up the process of updating the index.
Monitoring the ‘Indexing’ report in Google Search Console is the best way to track progress. You will likely see a decrease in indexed pages on the old domain and a corresponding increase on the new domain. If the old domain stays indexed for several weeks without a drop, there may be an issue with your redirects. You should also check for a spike in 404 errors. These errors indicate that users or crawlers are trying to reach pages that were not included in your redirect map. Fixing these quickly is essential to maintaining a high-quality search profile.
What are the common risks of a poor migration?
The primary risk of a poorly managed migration is a total loss of organic traffic. If search engines cannot find the new versions of your high-ranking pages, they will simply remove them from the results. This can lead to a loss of revenue that takes months or even years to recover. Another risk is a degraded user experience. When users click on a link from a search result or a social media post and land on a 404 error page, they are likely to leave your site immediately and visit a competitor instead.
- Loss of keyword rankings for high-value commercial terms.
- Broken internal links that prevent users from completing a purchase or lead form.
- Duplicate content issues if both the old and new sites remain accessible.
- Loss of referral traffic from external sites pointing to dead links.
- Slow site performance if the new server is not properly configured for the traffic load.
Where to start this week
If you are planning a migration, start this week by performing a full crawl of your current website using a tool like Screaming Frog. Export this list into a spreadsheet and categorize your pages by their traffic volume. This will give you a clear map of what needs to be protected. Once you have this list, identify any pages that can be deleted and those that must be moved. Establishing this baseline early is the best way to ensure your migration remains organized and successful from start to finish.
Keep reading: SEO (Search Engine Optimization) · SEO