A website migration keeps its rankings when three things are done right: every old URL is redirected to its closest new equivalent with a 301, nothing from staging (noindex, blocked robots.txt, wrong canonicals) goes live, and Search Console and analytics are checked week by week after launch. Most traffic drops after a redesign, platform change or domain move come from skipping one of those. This checklist walks you through what to do before launch, on launch day and in the weeks after. If your traffic has already dropped, our website traffic recovery service finds what broke and fixes it.
Why migrations lose traffic
Google ranks URLs, not businesses. When URLs change, Google has to discover the new ones, understand that they replace the old ones, and transfer the signals the old pages earned. Anything that interrupts that process costs traffic:
- Old URLs return 404 instead of redirecting.
- Redirects point to the homepage or to unrelated pages.
- Content that ranked was removed or cut down during the redesign.
- Staging settings went live: a sitewide noindex, a blocked robots.txt, canonicals pointing to the staging domain.
- Internal links still point to old URLs, creating redirect chains.
- Tracking broke, so it looks like traffic dropped when measurement did.
Types of migration (and how risky each is)
| Migration | What changes | Risk |
|---|---|---|
| Design-only refresh | Look and feel; same URLs and content | Low |
| Redesign with new structure | URLs, navigation, content | Medium to high |
| Platform change (e.g., Wix to WordPress) | URL patterns, templates, technical setup | High |
| Domain change | Every URL | High |
| HTTP to HTTPS, or adding/removing www | Protocol or hostname | Low if redirected correctly |
The more things change at once, the harder it is to diagnose problems. If you can, avoid changing the domain, the platform and the content in a single launch.
Before launch
1. Benchmark your current performance
- Export the last 12 months of clicks and impressions by page and by query from Google Search Console.
- Export landing-page sessions and conversions from GA4.
- Note your top 20–50 pages by organic traffic and by leads. These are the pages you cannot afford to lose.
2. Build a complete URL inventory
- Crawl the current site with a crawler such as Screaming Frog.
- Add URLs from your XML sitemap, Search Console's page reports and analytics.
- Include PDFs, images that get search traffic, and old URLs that still have backlinks.
3. Create the redirect map
- Map every old URL to the most relevant new URL, one to one where possible.
- Use 301 (permanent) redirects.
- Only redirect to the homepage when there is truly no equivalent page.
- Avoid chains (A → B → C): every old URL should go straight to its final destination.
4. Protect the content that ranks
- Keep the text, headings and FAQs of your top pages, or improve them. Don't cut them for the sake of a cleaner design.
- Carry over title tags and meta descriptions that perform well.
- Keep structured data (schema) for services, FAQs, reviews and business details.
5. Audit the staging site
- Keep staging blocked from Google with password protection or noindex. Write down every setting you will need to switch off at launch.
- Check page speed and Core Web Vitals on mobile.
- Check hreflang on bilingual sites.
- Test every form, phone link and WhatsApp button.
Launch day
- Remove the staging noindex and confirm that robots.txt allows crawling.
- Deploy the redirects, then test a sample of old URLs, including your top pages. Each should return a single 301 to the right page.
- Check canonical tags: they should point to the live URLs on the live domain.
- Submit the new XML sitemap in Search Console.
- Update internal links so they point directly to the new URLs.
- Verify tracking: GA4, Google Tag Manager and conversion events (forms, calls, WhatsApp) all fire on the new site.
- For a domain change: verify the new domain in Search Console and use Google's Change of Address tool.
After launch: what to check, week by week
| When | What to check |
|---|---|
| Days 1–3 | Crawl the new site for 404s, redirect chains and noindex pages. Check that forms and tracking work. |
| Week 1 | Search Console: page indexing report, crawl errors, sitemap status. Inspect your top 10 URLs. |
| Weeks 2–4 | Compare clicks and impressions by page against the benchmark. Fix the pages that lost the most first. |
| Months 2–3 | Confirm traffic and leads have recovered. Keep the redirects live; don't remove them. |
A short dip in the first weeks is common while Google recrawls the site. A drop that keeps growing after a month usually means something is broken and needs a diagnosis.
Bilingual and multilingual migrations
Sites with more than one language have extra ways to break during a migration:
- Each language needs its own redirect map. Spanish URLs should redirect to Spanish pages, never to the English homepage.
- Hreflang tags must be updated to the new URLs on every page, in both directions. A page that points to an alternate that no longer exists sends Google mixed signals.
- Language detection should not hide pages from Google. Automatic redirects based on browser language can stop Googlebot from crawling one of the versions.
- Check Search Console by language. A drop in one language can be masked by stable traffic in the other.
Who should be involved
Most migration problems happen in the gaps between teams. Before launch, agree on who owns each part:
| Role | Owns |
|---|---|
| SEO | Benchmark, URL inventory, redirect map, post-launch monitoring |
| Developer | Implementing redirects, removing staging settings, canonicals, sitemap, page speed |
| Content | Making sure ranking content, titles and FAQs survive the redesign |
| Analytics | GA4, Tag Manager and conversion tracking on the new site |
| Business owner | Approving the launch date and the pages that cannot be removed |
Avoid launching on a Friday or right before a busy season. If something breaks, you want the team available to fix it the same day.
What to do if traffic already dropped
- Confirm it's real. Compare Search Console clicks, which don't depend on your tracking code, with GA4 sessions. If Search Console looks fine and GA4 dropped, the problem is measurement.
- Find where you lost it. Compare before and after by page and by query.
- Check the old URLs of the pages that lost the most. Do they return a 404, redirect to the homepage, or redirect through a chain?
- Check indexing: noindex tags, robots.txt and canonicals.
- Check the content: was text, an FAQ or a section removed from those pages?
For a deeper walk-through, read why traffic drops after a website redesign and how to redesign a website without losing SEO.
The checklist, in short
- ☐ Benchmark exported from Search Console and GA4
- ☐ Full URL inventory (crawl, sitemap, Search Console, backlinks)
- ☐ One-to-one 301 redirect map, with no chains
- ☐ Top-ranking content preserved or improved
- ☐ Titles, meta descriptions and schema carried over
- ☐ Staging noindex removed and robots.txt checked
- ☐ Canonicals and hreflang point to live URLs
- ☐ New sitemap submitted
- ☐ Internal links updated
- ☐ GA4, GTM and conversions tested
- ☐ Search Console reviewed weekly for the first month
Protect your traffic, or get it back
Whether you're planning a migration or already lost traffic, we use your own Search Console data to find what's at risk, or what broke, and fix it in priority order. Learn about our website traffic recovery service or contact us.