Add to Preferred Sources
An SEO site migration checklist is the structured set of tasks that protects your organic rankings when you move your website — whether you are changing domains, platforms, CMS, or URL structures. If you are running an SEO strategy for a South African business, a poorly executed migration is one of the fastest ways to erase months of search progress.
A SALT.agency analysis of 1,052 domain migrations found that only 22.8% recovered their organic traffic within 90 days, with a median recovery time of 304 days and 13.9% still not fully recovered after three years.
Those numbers are for domain migrations specifically — the highest-risk migration type. Platform migrations on the same domain (for example, moving from WooCommerce to Shopify without changing your URLs) carry lower risk but are not risk-free. Either way, most of the damage is caused by a handful of specific, preventable mistakes made in the 72 hours before and after launch. This SEO migration checklist is structured by phase so you know what to do and, critically, what each step prevents.
Quick Answer
An SEO site migration checklist runs across four phases: pre-migration audit (crawl and baseline), redirect mapping and staging, launch day, and 30-day post-launch monitoring. The steps that prevent permanent ranking loss — exporting all indexed URLs, building a 1:1 redirect map, and verifying tracking before launch — must be completed before your new site goes live. Google's documentation recommends maintaining 301 redirects for at least one year and submitting the Change of Address tool for domain-to-domain moves. Skipping pre-migration work is the primary cause of traffic losses that never recover.
Not sure if your migration plan covers the high-risk steps?
Send us your current migration brief and we will identify the gaps before your launch date — not after.
Get a Free Migration ReviewWhat Does an SEO Site Migration Checklist Actually Cover?
A complete SEO site migration checklist covers every action needed to preserve — and ideally improve — a site's organic search performance across four phases: discovery and audit before work begins, staging and redirect preparation, the launch window itself, and structured post-launch monitoring. Experienced migration teams report a distinct failure mode for each phase: missing the pre-migration audit leaves you without a baseline to diagnose problems; missing the redirect map means old URLs have no mechanism to pass their accumulated ranking signals to new destinations; a failed launch day means you bleed rankings in real time; and missing post-launch monitoring means small problems compound into permanent losses.
This website migration checklist applies whether you are moving from one hosting provider to another (no URL changes), migrating to a new CMS on the same domain, switching domain names, or restructuring your entire URL architecture. The level of risk scales with the number of changes you are making simultaneously — changing domain, platform, and content structure at the same time is the highest-risk scenario.
Migration types ranked by SEO risk
| Migration type | URL change? | Domain change? | Risk level |
|---|---|---|---|
| Hosting provider change only | No | No | Low |
| Platform change (same domain + URLs) | No | No | Low–Medium |
| CMS change with URL restructure | Yes | No | Medium–High |
| Domain name change | Yes | Yes | High |
| Domain + platform + URL structure | Yes | Yes | Very High |
Phase 1 — Pre-Migration Audit (Start 2–4 Weeks Before Launch)
The pre-migration audit creates the baseline you will use to diagnose problems after launch — without it, you cannot tell whether a traffic dip is a seasonal shift or a migration error. This phase should start at least two weeks before your planned launch date, and four weeks is better for sites with more than a few hundred indexed pages.
The following SEO checklist for site migration begins with the audit phase — work through these tasks in order:
- Export all indexed URLs from Google Search Console. Go to Index Coverage and export the full list of indexed pages. This is your definitive source — not your sitemap, which misses orphaned pages, old blog posts, and legacy landing pages that still carry backlinks. Any URL in this export that disappears without a redirect forfeits the ranking signals it had accumulated — with no path to transfer them to the new site.
- Run a full crawl with Screaming Frog or a comparable tool. Crawl the current live site and flag every URL, including those returning 301 redirects already in place. Export the full list for comparison after launch. If you need a broader review of crawl health before migrating, see our guide on improving crawlability.
- Record your rankings and traffic baseline. Export your top 100 ranking keywords and their positions from Search Console. Screenshot the 90-day organic traffic trend in GA4. You need a documented before-state to measure recovery against.
- Audit your inbound backlinks. Use Ahrefs, SEMrush or Moz to identify the pages on your current domain that attract the most external links. These are your highest-priority redirect targets — removing them without a 301 redirect means those URLs' accumulated ranking signals have no path to the new site.
- Flag high-value pages: rankings, traffic, and backlinks. Compile a short list of pages that rank well, drive conversions, or hold meaningful backlink profiles. These pages require explicit 1:1 redirect mapping; they cannot be left to chance or catch-all redirects.
Pre-migration audit checklist
Before your development team touches the new site: export indexed URLs from Search Console, run a full crawl of the live site, document the top-100 keyword rankings, export backlink profiles for high-equity pages, and compile your high-value page shortlist. Every item you miss here becomes a blind spot in post-launch diagnosis.
Phase 2 — Redirect Map and Staging Environment
The redirect map is the single most important deliverable in any migration that changes URLs — it is the document that routes every old URL to its new destination, preserving user experience and telling search engines where ranking signals should be transferred. Building it from a spreadsheet template is faster than building it from production errors.
Building the redirect map
Take your exported list of indexed URLs (from Phase 1) and match each one to its new destination URL. This is the core of any site migration SEO guide: without a verified redirect map, every old URL becomes an uncontrolled variable. For detailed guidance on this process, see our dedicated resource on building a redirect map. The redirect map rules that practitioners most often learn the hard way:
- Every redirect must point to a genuinely relevant page. Redirecting an old product page to the new homepage — because you cannot find an equivalent — may be treated by Google as a soft 404, signalling that the content is gone rather than moved, and ranking signals are not reliably transferred. Redirect to the closest relevant page, or let the old URL return a genuine 404 and accept the link equity loss.
- Avoid redirect chains. If URL A redirected to URL B in your old site, and URL B now redirects to URL C in your new site, Googlebot may stop following after a few hops. Consolidate so old URL A points directly to the final destination. For a full reference on implementing these correctly, see our 301 redirect checklist.
- Use 301 (permanent) redirects for moved content. A 302 (temporary) redirect does not transfer ranking signals in the same way. Your server-side redirect implementation should use 301 or 308 responses.
Staging environment hygiene
Your staging site must be blocked from search engine indexing throughout development. Use HTTP basic authentication, IP restriction, or server-level noindex directives — never rely on a CMS toggle alone, as plugins can fail silently. If Googlebot indexes your staging site before you remove the noindex on your live site, you can end up with competing indexed copies or an empty index at launch. This is one of the more devastating and avoidable migration failures.
Phase 3 — Launch Day (The First 12 Hours)
Launch day is not the time for discovery — every item on this list should have been verified on the staging environment before the domain switches over. Work through these in order, and have someone else cross-check each step:
| Task | Why it matters | Verified? |
|---|---|---|
| Remove noindex tags from new site | Staging noindex left in place = invisible site | ☐ |
| Activate all 301 redirects | Ranking signals transfer from old to new URLs | ☐ |
| Confirm SSL certificate is active | HTTP → HTTPS without SSL certificate = browser warnings | ☐ |
| Submit updated XML sitemap in Search Console | Accelerates Googlebot discovery of new URL structure | ☐ |
| Submit Change of Address tool (domain moves only) | Signals domain migration to Google, supports signal transfer | ☐ |
| Verify GA4 tracking is firing correctly | Without working analytics, diagnosing post-launch issues becomes significantly harder | ☐ |
| Test conversion tracking events | Migration frequently breaks goal/event firing via GTM | ☐ |
| Run immediate post-launch crawl | Identifies 404s, redirect chains, and missing tags before Google does | ☐ |
| Spot-check top 20 high-value pages manually | Confirm content, canonicals, and meta tags migrated correctly | ☐ |
For SA businesses on shared hosting with providers such as Afrihost, Web Africa, or Hetzner SA: confirm with your host how 301 redirects are implemented (typically via .htaccess for Apache, nginx config for Nginx, or a control panel redirect manager). Misconfigured server redirects are a common source of launch-day failures that do not show up in pre-launch testing when the development environment uses a different server type. If you are using a managed hosting environment, test server-level redirects before you switch DNS. For a migration you cannot afford to get wrong, our technical SEO support can plan and check the move under a flat monthly retainer agreed before work starts.
One SA-specific timing note: schedule your migration launch during a known load-shedding off period if your hosting infrastructure is locally dependent. A server restart mid-migration on shared hosting can corrupt your redirect configuration or break your SSL handshake. Most enterprise SA hosting (Hetzner SA, AWS Cape Town region, Microsoft Azure South Africa) maintains UPS backup, but check your specific plan.
The Change of Address tool is for domain migrations only
Google's Change of Address tool in Search Console signals a domain-to-domain move and helps accelerate the transfer of search signals. It applies only when your hostname changes — it is not required for platform or URL-structure migrations on the same domain. Submit it in Search Console as soon as your 301 redirects are live and your new domain is verified. It works alongside your redirects; it does not replace them.
Phase 4 — 30-Day Post-Launch Monitoring
Post-launch monitoring is where recoverable problems become permanent ones if you are not watching. Most migration errors surface within the first two weeks — the sites that never recover are typically the ones that did not have monitoring in place to detect early signals.
What to check and when
| Timeframe | Check | Tool |
|---|---|---|
| Days 1–3 daily | Crawl errors and 404s | Google Search Console (Coverage report) |
| Days 1–7 daily | Indexing progress of new URLs | Search Console URL Inspection tool |
| Week 1–2 daily | Organic traffic vs pre-migration baseline | GA4 channel report |
| Week 1 once | Sitemap submission confirmed and processed | Search Console Sitemaps report |
| Week 2 weekly | Ranking positions for top keywords | Search Console Performance report |
| Week 2 once | Core Web Vitals — field data | Search Console Core Web Vitals report |
| Day 30 | Full comparison: traffic, rankings, indexed URLs | Search Console + GA4 |
A temporary dip in rankings during the first two weeks is normal as Googlebot recrawls and re-evaluates the new site structure. A dip that continues past week three, or that does not align with your redirect map coverage, suggests a structural problem rather than normal recrawl lag. If you are seeing unexplained traffic loss, our guide on prioritising SEO fixes and our resource on improving website indexation cover the diagnostic steps for common post-migration indexing failures.
For Core Web Vitals specifically: field data in Search Console takes 28 days to accumulate after launch, so you will not have a complete picture until day 28 at the earliest. Run lab tests immediately post-launch with Chrome DevTools → Performance. For a full breakdown of what to measure, see our guide on Core Web Vitals in South Africa.
Redirect maintenance: Google's own site migration documentation recommends maintaining 301 redirects for at least one year. Removing redirects early — even if traffic to the old URLs has dropped — is the most common cause of post-migration ranking losses that appear months after launch, because external links pointing to old URLs still pass through those redirects.
Seeing a traffic drop after your recent launch?
Share your Search Console data and we will diagnose whether the drop is normal recrawl lag or a structural migration error that needs correcting now.
Get a Migration DiagnosisFive Migration Mistakes That Turn a Temporary Dip Into a Permanent Loss
Most permanent ranking losses after a site migration are caused by the same five errors. Use this SEO site migration checklist as your launch-week reference — these are not obscure technical failures, but shortcuts taken under deadline pressure.
Why South African Businesses Work With Growth Pulse Media on Migrations
Growth Pulse Media handles every layer of a site migration in-house — pre-launch crawl analysis, redirect map validation, launch-day monitoring, and 30-day post-launch tracking — so South African businesses do not lose organic rankings to preventable execution errors. Dirk van Greuning manages each migration directly, because the decisions made in a 48-hour launch window carry consequences that can take 12–18 months to recover from.
If you are planning a migration and want a senior review of your redirect map, staging setup, and launch-day sequence before you go live, our SEO service for South African businesses includes pre-launch migration audits as part of ongoing engagements. We work with a deliberately limited client load so that every migration receives full pre-migration crawl analysis, redirect map validation, launch-day monitoring, and 30-day post-launch tracking — all executed in-house.
Who This Migration Checklist Is NOT For
This checklist is designed for sites with established organic rankings, inbound backlinks, and indexed pages. If any of the following describes your situation, the full process does not apply.
Planning a migration in the next 60 days?
Tell us your timeline and current setup — we will give you an honest assessment of what preparation is realistic before your launch date.
Book a Pre-Migration AssessmentFrequently Asked Questions
How long does it take to recover rankings after a site migration?
Recovery time depends heavily on migration type and execution quality. SALT.agency's analysis of 1,052 domain migrations found a median recovery time of 304 days, with only 22.8% recovering within 90 days. Platform or CMS migrations on the same domain with well-executed redirects typically stabilise faster — often within four to eight weeks — because Google does not need to process a domain change. The primary driver of longer recovery is incomplete redirect maps, not the migration type itself.
Do I need to use Google's Change of Address tool for every migration?
No — Google's Change of Address tool in Search Console is only for domain-to-domain migrations (when your hostname changes). If you are migrating platforms, restructuring URLs, or changing hosting providers on the same domain, the Change of Address tool does not apply. For domain migrations, submit it in Search Console once 301 redirects are live and the new domain is verified. It complements your redirects; it does not replace them.
How long should I keep 301 redirects active after a migration?
Google's own site migration documentation recommends maintaining 301 redirects for at least one year. External sites, business directories, and aggregators continue pointing links at your old URLs for months or years after your migration — remove the redirects and those inbound signals have no destination. Check Search Console for traffic through old URLs before decommissioning any redirect, even after a year.
What is a soft 404 and why does it matter in a migration?
A soft 404 occurs when a URL returns a 200 OK response (meaning the server says "page found") but the content signals to Google that the page does not exist — the most common example is redirecting old URLs to the homepage. Google recognises homepage redirects as a signal that the original content is gone, not moved, and does not transfer ranking signals from the old URL. Use a genuine 404 or 410 response for deleted pages, and 301 redirects only for pages that have a legitimate new destination.
Can I migrate my website and redesign the content at the same time?
You can, but doing both simultaneously significantly increases risk and complicates post-migration diagnosis. If your rankings drop after a combined migration and redesign, you cannot easily determine whether the cause is the URL changes, the content changes, or a technical migration error. Where your timeline allows, separate the structural migration (URL changes, platform move) from the content changes by at least four to six weeks. Complete the migration first, stabilise, then iterate on content.
Ready to migrate without losing your rankings?
Growth Pulse Media reviews migration plans for South African businesses before launch — redirect map validation, staging audit, and launch-day monitoring included. All work is handled in-house by senior practitioners, not subcontracted. No obligation — we will get back to you within 24 hours.
Request a Free Migration Audit