Site migration without losing SEO in 2026: 30-point checklist

SEO migration: one wrong move, six months of lost traffic

Across 24 site migrations supported by Kolonell (platform redesign, domain change, internationalization), the correlation is clear: teams that follow a disciplined checklist lose 0-8% of SEO traffic in the first 30 days (recovered within 60 days). Those who improvise lose 35-60% and take 9-14 months to return to baseline. The difference lives in three places: URL mapping, technical integrity (sitemap, hreflang, structured data) and post-launch monitoring.

This article condenses the 30-point checklist we apply to every migration in 2026.

Phase 1 — Audit BEFORE migration (days -30 to -7)

• Full crawl of the old site with Screaming Frog or Sitebulb: export every HTTP 200 URL, status codes, titles, meta descriptions.
• 16-month GSC export: top 1000 URLs by clicks + impressions + position. This is the protected list.
• GA4 export: top 200 URLs by organic sessions + conversions. Cross-reference with GSC.
• Backlink audit via Ahrefs / SE Ranking: top 100 URLs receiving external backlinks. These MUST be redirected.
• Structured data inventory: log existing JSON-LD (Article, FAQ, Product, Organization, BreadcrumbList) to reproduce.
• Hreflang audit for multilingual sites: export every current hreflang tag.
• List active sitemaps + latest GSC submission.
• Baseline speed: LCP, INP, CLS on 20 key URLs via PageSpeed Insights API (kept for post-migration comparison).

Phase 2 — Preparation (days -7 to -1)

• Old → new mapping in CSV: 1 row per old URL, 1 new URL column, 1 status code column (301 or 410).
• Mapping validation on 100% trafficked URLs GSC + GA4 + top backlinks.
• Automatic redirect generation in next.config.js, vercel.json, .htaccess or _redirects (Netlify) according to target stack.
• Redirect tests on staging: curl/Playwright script verifying 100% of URLs → 301 → correct destination + final 200.
• Dynamic sitemap generation on the new site (/sitemap.xml) with proper lastmod.
• Hreflang reproduction, identical or improved (never degraded).
• Structured data reproduction JSON-LD for every template (article, product, FAQ, etc.).
• Robots.txt check: no accidental blocking of important sections.
• Canonical check: 1 canonical per page, no duplicates, no cross-language canonical mix-up.

Phase 3 — Cut-over (D-day)

• DNS switch + 301 redirects active.
• Test 50 random URLs within 30 min: confirm 301 → 200, correct content, performance.
• Submit new sitemap to GSC (and Bing Webmaster Tools if relevant).
• Priority indexing request for top-20 traffic URLs.
• Update Google Business Profile if local presence, plus strategic Wikipedia / institutional links.
• Internal communication: notify sales and support of the new URLs.

Phase 4 — 90-day monitoring

• D+1 to D+7: monitor GSC > Coverage > 404 errors, soft 404s, exclusions. Target: zero 404 on traffic URLs.
• D+1 to D+7: monitor GSC > Enhancements > Core Web Vitals + Mobile Usability + Structured Data.
• D+7 to D+30: analyse GSC > Performance: positions, clicks, impressions vs pre-migration baseline.
• D+15: full Screaming Frog crawl to spot orphan URLs, broken redirects, missing tags.
• D+30: GA4 review — sessions, conversions, bounce rate by template.
• D+60: backlink audit — confirm redirects pass PageRank, manually contact major referring sites to refresh links.
• D+90: decide on the end of the watch period + retire temporary redirects and unused monitors.

Fatal mistakes and their symptoms

Netlify `_redirects` example

`

/blog/2024/* /blog/:splat 301

/produit/:slug /products/:slug 301

/contact-us /contact 301

/*.php / 410

`

Apache `.htaccess` example

`

RewriteEngine On

RewriteRule ^blog/2024/(.*)$ /blog/$1 [R=301,L]

RewriteRule ^produit/(.*)$ /products/$1 [R=301,L]

`

Field case — 4-star Saly hotel (April 2026)

Migration from hotel-X.sn (WordPress) to hotel-X.com (Next.js + new design). 220 URLs, including 40 tourism blog posts. 301 mapping at 100% coverage, FR/EN/ES multilingual sitemap submitted on D-day. 404 spike fixed in 48h. Organic traffic: -6% at D+14, +12% at D+45, +31% at D+90. Zero loss on direct bookings.

FAQ

How long until I recover SEO traffic after a 2026 migration?

With a clean migration: 4-8 weeks back to baseline, 8-12 weeks to exceed it. Without proper 301 mapping: 6-14 months and often never 100% back.

Should I keep the old domain after a migration?

Yes, at least 12 months for 301 redirects to pass SEO equity. After that you can keep the old domain on permanent redirect for another 3-5 years to capture aging backlinks.

How do you mass-test 301 redirects?

Playwright script or simple curl loop on the mapping CSV: each old URL must return 301 → correct destination → final 200. Best: bake this test into the new site CI/CD.

Why does my traffic drop in the first month even though everything looks fine?

Three usual causes: (1) Googlebot needs to re-crawl the whole site (15-30 days), (2) SERP features (FAQ, sitelinks) must rebuild, (3) natural seasonality is often ignored. Patience + daily monitoring.

Do I need a Change of Address request in GSC?

Yes, mandatory if changing domains. Settings > Change of Address in GSC. Effect: tell Google domain A is replaced by domain B. Not for internal migrations (just URL changes).

Let us talk about your migration

Kolonell runs secure SEO migrations using the 30-point checklist. If you are preparing a site change, we can audit your setup and quote the migration in 48h. WhatsApp +221 77 596 93 33.