Website Migration SEO Checklist: How to Switch Platforms Without Losing Rankings
Switching your website platform should be an upgrade, not a disaster. Yet countless small businesses have watched their organic traffic plummet by 50% or more after a migration because they overlooked critical SEO steps. The frustrating part is that most of these losses are entirely preventable. A website migration done correctly preserves your search rankings, maintains your traffic, and positions you for growth on a better platform. A migration done carelessly can undo years of SEO progress in a single afternoon.
Whether you are moving from Wix to WordPress, upgrading from an outdated CMS to a modern platform, switching hosting providers, or redesigning your site from scratch, this checklist covers every step you need to protect your search visibility. Bookmark this page and work through it methodically. Skipping steps here has real financial consequences.
Understanding Website Migration Types
Not all migrations carry the same SEO risk. Understanding which type you are doing helps you prioritize the right precautions.
Platform migration. Moving your website from one CMS or website builder to another (Wix to WordPress, Squarespace to Shopify, custom code to a new framework). This typically changes your URL structure, page templates, and sometimes your hosting environment. SEO risk: moderate to high.
Domain migration. Changing your website's domain name (oldbusiness.com to newbusiness.com). This is the highest-risk migration type because search engines treat the new domain as a completely different entity until they process your redirects and signals. SEO risk: high.
Hosting migration. Moving your website to a different hosting provider while keeping the same platform, domain, and content. If done correctly, search engines should not notice any change. SEO risk: low.
Redesign migration. Rebuilding your website with new templates, layouts, and possibly restructured content while staying on the same platform and domain. The risk depends on how much the URL structure and content organization change. SEO risk: low to moderate.
Protocol migration. Switching from HTTP to HTTPS. While this is technically a migration (URLs change from http:// to https://), it is well-supported by search engines and carries minimal risk when done correctly. SEO risk: low.
Structural migration. Reorganizing your URL structure, combining or splitting pages, or restructuring your site's information architecture. This can be done alongside any other migration type and adds complexity to the redirect mapping. SEO risk: moderate.
For a comprehensive understanding of SEO principles that inform every step of this checklist, see our SEO guide for small businesses.
Phase 1: Pre-Migration Audit (Two to Four Weeks Before)
The work you do before the migration determines whether the migration succeeds. Rush this phase and you will pay for it in lost rankings.
Document Your Current SEO Baseline
Record your current organic traffic. Take screenshots or export reports from Google Analytics and Google Search Console for the past twelve months. Document monthly organic sessions, top landing pages by organic traffic, and your overall trend line. You will use this data to measure whether the migration succeeded.
Export your keyword rankings. Use a rank tracking tool (Ahrefs, SEMrush, Moz, or even a free tool like Google Search Console) to document your current keyword rankings. Focus on the keywords that drive actual traffic rather than vanity keywords you rank for but that generate no clicks.
List your top-performing pages. Identify the twenty to fifty pages that generate the most organic traffic. These pages are your highest priority during the migration. Any disruption to these pages has the biggest impact on your business.
Document your backlink profile. Use Ahrefs, Moz, or a similar tool to export a list of pages on your site that have inbound backlinks. These pages must maintain their URLs or have proper redirects in place. Losing backlinks by changing URLs without redirects is one of the most common and costly migration mistakes.
Crawl Your Current Website
Run a full site crawl. Use a tool like Screaming Frog, Sitebulb, or Ahrefs Site Audit to crawl your entire current website. Export the results, paying special attention to the full list of URLs, their HTTP status codes, canonical tags, meta titles, meta descriptions, heading structure, and internal link relationships.
Identify existing redirects. Document any redirects already in place on your current site. These need to be carried over to the new platform. If page A redirects to page B on your current site, the new site must maintain that redirect. Losing existing redirects during migration is a common oversight.
Check for broken links. Identify and document any existing 404 errors or broken internal links. The migration is an opportunity to fix these issues rather than carrying them over to the new platform.
Map your XML sitemap. Download your current XML sitemap and verify that it lists all important pages. Compare the sitemap against your crawl results to identify any discrepancies.
Create a URL Mapping Document
This is the single most important pre-migration document. Create a spreadsheet with two columns: old URL and new URL.
Map every URL. For each page on your current site, document the exact new URL it will have on the new platform. If a page will not exist on the new site, note where its traffic should be redirected (usually a closely related page or a category page).
Pay attention to URL structure changes. Different platforms use different URL conventions. WordPress uses /category/post-name/ by default, Shopify uses /blogs/news/post-name, and static site generators might use /blog/post-name/. Ensure every old URL has a corresponding new destination.
Account for pagination. If your current site has paginated archive pages (/blog/page/2/, /blog/page/3/), decide how these will be handled on the new platform.
Account for parameter URLs. Some platforms generate URLs with query parameters (?sort=price, ?page=2). Decide whether these need redirects or can be handled by robots.txt and canonical tags.
Phase 2: Build and Test the New Site (One to Two Weeks Before)
Build the new site in a staging or development environment where search engines cannot access it. Never build the new version on the live domain with search engines watching.
Staging Environment Setup
Block search engine access. Your staging environment should be inaccessible to search engine crawlers. Use password protection, robots.txt disallow rules, or noindex meta tags on the staging domain. If search engines index your staging site, you create duplicate content issues that can harm your live site's rankings.
Use a separate domain or subdomain. Build the new site on a staging URL like staging.yourbusiness.com or a completely different domain. Do not build it on your live domain until you are ready to launch.
SEO Configuration on the New Platform
Implement proper title tags. Transfer your existing meta titles to the new platform. If the new CMS generates titles differently, configure it to match your existing format. Do not let the migration change your page titles unless you are intentionally improving them.
Transfer meta descriptions. Copy all meta descriptions from the old site to the new site. Missing meta descriptions will not directly hurt rankings, but they affect click-through rates from search results.
Maintain heading structure. Ensure each page on the new site uses H1 and H2 tags in the same logical structure as the old site. The new design template should not change the content's heading hierarchy.
Configure canonical tags. Every page on the new site should have a self-referencing canonical tag. This tells search engines which version of each URL is the authoritative one.
Set up XML sitemap generation. Configure the new platform to generate an XML sitemap automatically. Verify that the sitemap includes all important pages and excludes utility pages (like thank-you pages, login pages, and admin pages).
Configure robots.txt. Prepare a robots.txt file for the new site that allows search engine access to all important content. Review the default robots.txt that your new platform generates, as some platforms block CSS, JavaScript, or media files by default.
For a deeper dive into technical SEO requirements, our technical SEO guide for small businesses covers the details that matter most.
Content Transfer Verification
Compare content page by page. For your top twenty to fifty pages, manually compare the content on the old site with the content on the new site. Look for missing paragraphs, broken formatting, stripped images, and altered internal links.
Verify image alt text. Image alt text often gets lost during content migration. Check that all images on the new site retain their descriptive alt attributes.
Check internal links. Every internal link on the new site should point to valid new URLs. If your URL structure changed, internal links need to be updated to reflect the new paths. Leaving internal links pointing to old URLs means they will rely on redirects, which is less efficient than direct links.
Test forms and interactive elements. Every contact form, search function, email signup, and interactive feature on the new site must work correctly before launch.
Pre-Launch Testing Checklist
Crawl the staging site. Run a site audit tool against your staging environment. Look for broken links, missing meta tags, duplicate content, orphan pages, and redirect chains.
Test page load speed. Use Google PageSpeed Insights or GTmetrix to test key pages on the staging site. The new site should load as fast as or faster than the old site. If it is significantly slower, address performance issues before launch.
Verify mobile responsiveness. Test the new site on multiple devices and screen sizes. Google uses mobile-first indexing, so the mobile version of your site is what search engines evaluate.
Check structured data. If your current site uses schema markup (Organization, Article, Product, FAQ, etc.), verify that the same structured data is present on the new site. Test with Google's Rich Results Test tool.
Use our SEO audit checklist to systematically verify that nothing has been missed before going live.
Phase 3: Migration Day
The actual migration should be quick and well-coordinated. Every minute your site spends in a partially migrated state is a minute where visitors and search engines might encounter errors.
Redirect Implementation
Implement 301 redirects for every changed URL. This is the most critical step of the entire migration. Every old URL that has changed must return a 301 (permanent) redirect to its new location. Use the URL mapping document you created in Phase 1.
Where to implement redirects. Depending on your platform, redirects can be configured in your web server (Apache .htaccess or Nginx config), in your CMS settings, in your hosting provider's control panel, or in your CDN configuration.
Test redirects thoroughly. Spot-check at least twenty to thirty redirects by entering old URLs in your browser and verifying they land on the correct new pages. Test redirects for your top traffic pages, pages with the most backlinks, and pages from different sections of your site.
Avoid redirect chains. If old URL A already redirected to old URL B, the new redirect should go directly from A to the final new URL, not from A to B to the new URL. Redirect chains slow down both visitors and search engine crawlers.
Handle non-mapped URLs. For any old URLs that do not have a direct equivalent on the new site, redirect them to the most relevant existing page. As a last resort, redirect them to the homepage, though this is less effective than redirecting to a topically relevant page.
DNS and Hosting Changes
Reduce TTL in advance. If you are changing DNS records, reduce the Time-To-Live (TTL) value to 300 seconds (five minutes) a day or two before the migration. This ensures that DNS changes propagate quickly.
Make DNS changes during low-traffic hours. Check your analytics to identify when your site receives the least traffic (often late night or early morning in your primary audience's timezone) and schedule DNS changes for that window.
Verify SSL certificate. Ensure your SSL certificate is active and correctly configured on the new hosting. An HTTPS site that suddenly serves HTTP or shows certificate errors will alarm both visitors and search engines.
Immediate Post-Launch Checks
Verify the site loads correctly. Check the homepage, key landing pages, and a sample of interior pages from different sections.
Verify redirects are working. Test your critical redirects again on the live site.
Submit your new sitemap to Google Search Console. Go to Google Search Console, navigate to Sitemaps, and submit the URL of your new XML sitemap. This prompts Google to recrawl your site.
Request indexing for key pages. In Google Search Console, use the URL Inspection tool to request indexing for your top five to ten pages. This is not mandatory, but it accelerates the process.
Phase 4: Post-Migration Monitoring (First Four Weeks)
The work does not end on launch day. The first four weeks after migration are critical for catching and fixing issues before they cause lasting damage.
Week One Monitoring
Check Google Search Console daily. Look for crawl errors, indexing issues, and any manual actions. The Coverage report shows how many pages Google has indexed and whether it is finding errors.
Monitor organic traffic daily. Compare daily organic traffic to the same day in the previous week and month. A temporary dip of 10% to 20% is normal during the first few days as search engines process the migration. A drop of more than 30% signals a problem that needs immediate investigation.
Check for 404 errors. Review your server logs or Google Search Console for pages returning 404 errors. Each 404 is a missed redirect. Fix them as they appear.
Monitor page load speed. Verify that real-world page load times on the new platform match or exceed your pre-migration benchmarks.
Weeks Two Through Four
Track keyword rankings. Compare your current rankings to the pre-migration baseline. Most keywords should stabilize within two to four weeks. Keywords that have not recovered after four weeks may indicate a redirect issue, content change, or technical problem on the specific page.
Review crawl stats. In Google Search Console, check the Crawl Stats report to see how frequently Googlebot is visiting your site and whether it is encountering errors. A healthy migration shows steady or increasing crawl activity.
Monitor backlink preservation. Check that your most important backlinks are still passing value. If a referring site links to an old URL and your redirect is working, the link value should transfer to the new URL. Use a backlink checker to verify.
Fix emerging issues promptly. Every day that a broken redirect, missing page, or technical error persists is a day of lost traffic. Treat post-migration issues with urgency.
Common Migration Mistakes and How to Avoid Them
Learning from other businesses' mistakes is cheaper than making your own.
Forgetting to redirect. The single most common migration failure. Every changed URL needs a 301 redirect. No exceptions. Automate this with a script if you have hundreds or thousands of pages.
Changing content during migration. Resist the temptation to rewrite page content at the same time as migrating. If search engines see new URLs and new content simultaneously, they have no way to understand the relationship between the old and new pages. Migrate first, then update content after rankings stabilize.
Ignoring internal links. Updating external-facing URLs is obvious, but many migrations forget to update internal links. If your internal links still point to old URLs, every internal navigation relies on redirects, which slows down your site and wastes crawl budget.
Removing pages without redirects. If you decide that certain pages from the old site will not exist on the new site, you still need to redirect them somewhere relevant. Simply removing a page that had traffic and backlinks throws away accumulated SEO value.
Blocking search engines accidentally. A leftover noindex tag, a misconfigured robots.txt, or a staging environment's access restrictions accidentally applied to the live site can prevent search engines from crawling your new site entirely. Triple-check these settings on launch day.
Not testing on mobile. Google uses mobile-first indexing. If your new site looks great on desktop but has issues on mobile, your rankings will suffer. Test every page template on actual mobile devices before launching.
Launching on a Friday. If something goes wrong, you want a full working week to address it. Launching on a Friday means problems may go unfixed over the weekend. Aim for a Tuesday or Wednesday launch.
Tools You Will Need
Having the right tools ready before migration day saves time and stress.
Screaming Frog or Sitebulb. For crawling both the old and new sites. Essential for generating URL lists, finding broken links, and verifying technical SEO elements.
Google Search Console. For monitoring indexing, submitting sitemaps, and identifying crawl errors. Free and indispensable.
Google Analytics or your analytics tool. For tracking traffic changes. Have pre-migration benchmarks documented for comparison.
A rank tracking tool. Ahrefs, SEMrush, Moz, or a dedicated rank tracker. For monitoring keyword positions before, during, and after migration.
A redirect testing tool. Tools like httpstatus.io or the Redirect Checker extension for Chrome let you test individual redirects quickly.
A spreadsheet. For your URL mapping document. Google Sheets works well because multiple team members can collaborate on the mapping.
When to Seek Professional Help
Some migrations are simple enough for a technical business owner to handle. Others warrant professional assistance.
Consider hiring an SEO professional if: your site has more than 500 pages, you are changing domain names, your site generates significant revenue from organic search, you lack experience with server configuration and redirects, or the migration involves merging multiple websites.
You can likely handle it yourself if: your site has fewer than 100 pages, you are staying on the same domain, you are comfortable editing server configurations or using your platform's redirect tools, and you have time to follow this checklist methodically.
A well-executed migration protects the SEO equity you have built over months or years. A poorly executed one can erase it in hours. Take the time to plan thoroughly, test rigorously, and monitor closely. Your future organic traffic depends on it.