A website migration — whether changing your domain name, moving to a new CMS, or restructuring your URL architecture — is one of the highest-risk SEO activities a business can undertake. A poorly executed migration can lose 30-50% of organic traffic. This checklist covers every step needed to protect your search rankings, preserve link equity, and maintain user experience throughout the process.
What Types of Website Migrations Carry SEO Risk?
Not all migrations are equal. The level of SEO risk depends on what changes:
- Domain change: Moving from olddomain.com to newdomain.com. Highest risk — you are essentially transferring all authority to a new identity.
- HTTP to HTTPS: Lower risk but still requires 301 redirects for every URL. Most sites should already have completed this.
- CMS platform change: Moving from one platform to another (e.g., Wix to WordPress). Risk depends on URL structure changes.
- URL restructure: Changing /blog/post-title/ to /insights/post-title/. Requires 301 redirects for every changed URL.
- Design/template change: Changing the visual design without altering URLs. Lowest SEO risk but can still affect Core Web Vitals and content hierarchy.
What Should You Do Before Starting the Migration?
- Crawl your current site completely: Use Screaming Frog, Sitebulb, or a similar crawler to capture every URL, its status code, title tag, meta description, canonical tag, and internal links. Export this as your baseline.
- Document current performance: Record organic traffic, keyword rankings for your top 50-100 keywords, top landing pages, and conversion rates from Google Analytics and Search Console.
- Export all 301 redirects already in place: These must be migrated to the new site. Losing existing redirects breaks link chains.
- Map all URL changes: Create a spreadsheet mapping every old URL to its new equivalent. This is the foundation of your redirect plan.
- Identify high-value pages: Pages with the most organic traffic, backlinks, and conversions deserve extra attention during redirect mapping.
- Back up everything: Full site backup including database, files, and media. Test that you can restore from this backup before proceeding.
How Do You Build a Redirect Strategy That Preserves SEO?
The redirect map is the most critical element of any migration:
- Use 301 redirects exclusively: 301 signals a permanent move and passes link equity. Never use 302 (temporary) for permanent URL changes.
- Redirect every URL: Not just your top pages — every indexed URL, including blog posts, images, PDFs, and pagination pages.
- Map to equivalent content: Redirect each old URL to the most relevant new page. If the content no longer exists, redirect to the closest parent category — never to the homepage unless there is no alternative.
- Avoid redirect chains: If A redirected to B on the old site, and B now moves to C, create a direct redirect from A to C.
- Implement server-side: Configure redirects at the server level (.htaccess for Apache, nginx config, or your WordPress redirect plugin) rather than client-side JavaScript redirects.
What Is the Migration Day Checklist?
| Step | Action | Verification |
|---|---|---|
| 1 | Deploy new site to production | Visual review on desktop and mobile |
| 2 | Activate all 301 redirects | Test sample of 50+ redirects manually |
| 3 | Update canonical tags | Verify canonical points to new URL on every page |
| 4 | Update XML sitemap | Sitemap contains only new URLs, no 301s or 404s |
| 5 | Submit new sitemap in Search Console | Confirm submission in both old and new properties |
| 6 | Update robots.txt | No accidental noindex or disallow rules on new site |
| 7 | Update internal links | No internal links pointing to old URLs (causes unnecessary redirect hops) |
| 8 | Update hreflang tags (if multilingual) | All hreflang annotations point to new URLs |
| 9 | Update schema markup | All URLs in schema reflect new domain/paths |
| 10 | Verify analytics tracking | Real-time analytics shows data from new site |
What Should You Monitor After Migration?
The first 4 to 8 weeks after migration are critical. Monitor daily:
- Search Console coverage report: Watch for spikes in excluded pages, crawl errors, or new 404s.
- Organic traffic: A temporary dip of 10-20% is normal. If traffic drops more than 30%, investigate redirect issues immediately.
- Indexation: Track how quickly Google indexes new URLs by searching site:yourdomain.com and monitoring the Index Coverage report.
- 404 errors: Monitor 404 logs daily and add redirects for any missed URLs.
- Keyword rankings: Track your top 50-100 keywords. Expect fluctuations for 2-4 weeks before stabilization.
- Backlink profile: Check that major backlinks are following redirects correctly. Contact high-value linking sites to update their links to your new URLs.
Frequently Asked Questions
How long should I keep old redirects active?
Keep 301 redirects active permanently if possible, or for a minimum of one year. Google has confirmed that they continue to process and pass link equity through 301 redirects. Removing them prematurely causes 404 errors for any remaining external links and can result in traffic loss. Server-level redirects add negligible performance overhead.
Will I lose traffic during a website migration?
A temporary traffic dip is normal even with a perfect migration. Expect 10-20% fluctuation for 2-6 weeks as Google recrawls and reindexes your site. Traffic should recover within 2-3 months. If you see a sustained drop beyond 30%, check for redirect errors, missing pages, or technical issues on the new site. For Indian businesses, migrations during low-traffic periods (avoiding festive seasons like Diwali, Navratri) minimize business impact.
Should I change my domain and redesign at the same time?
Ideally, no. Combining a domain change with a major redesign and URL restructure makes it impossible to diagnose problems — you will not know whether traffic changes are caused by the domain move, the new content structure, or the redesign. If possible, complete the domain move first, wait for rankings to stabilize (6-8 weeks), then proceed with design and structural changes.
How do I handle a migration for a WordPress site with WooCommerce?
WooCommerce migrations require additional attention: redirect product URLs, category and tag archives, and dynamic pages (cart, checkout, my-account). Verify that product schema markup is intact, payment gateway configurations work on the new domain, and SSL certificates cover the new domain. Test the complete purchase flow — from product page to order confirmation email — before going live. Update payment gateway webhook URLs and any third-party integrations that reference your old domain.
