Website Migration Checklist: Step-by-Step SEO Guide for Risk-Free Site Moves

A website migration is one of the highest-risk projects an SEO or marketing team can run. Handled well, it preserves rankings and can improve them. Handled poorly, it can wipe out organic traffic for months.

This checklist is built as a complete operational system. Copy the master table below into your project management tool, assign owners, and work through each phase.

Jump to master checklist ↓

Master Website Migration Checklist

Use this as your migration control document. Copy the table into Asana, Jira, Notion, or a Google Sheet. Assign owners, set due dates, and track status through launch and the first month after.

What Is a Website Migration? (and Why It's Risky)

A website migration is any major change to how your site is structured, accessed, or delivered that significantly affects how users and search engines experience it. Common examples:

• Moving from one domain to another (rebrand, merger)
• Switching CMS or platform
• Overhauling information architecture or URL structure
• Moving from HTTP to HTTPS
• Changing hosting infrastructure

These changes alter URLs, internal links, and sometimes the underlying technology — which is why they put rankings, crawlability, and revenue at risk. A simple copy edit doesn't disrupt indexing; a migration can.

Why migrations fail:

• Critical URLs change without proper 301 redirects, breaking link equity
• Key pages become harder to find or disappear from navigation
• Tracking, tags, or integrations aren't correctly reimplemented

Real-world example: An ecommerce brand rebrands and changes domains but forgets to redirect old product URLs. Search traffic plummets, customers hit 404 pages, and backlinks stop passing value to the new domain.

Types of Website Migrations (and When You Need One)

Different migration types carry different SEO risks. If you're doing more than one at once, treat each as its own mini-project and combine the strictest requirements from each.

Each type shifts the checklist's emphasis. Domain changes demand exhaustive redirect mapping and close monitoring of external link equity. CMS replatforming focuses on template parity — matching metadata handling, structured data, and indexation rules silently carried by the old system. IA changes prioritize precise 1:1 redirects and internal link updates. Content consolidation requires careful canonical destination choices to avoid diluting ranking signals.

For deeper coverage of URL mapping patterns, see our guide to [redirect strategies for SEO migrations].

How Website Migration Affects SEO

Every migration causes SEO turbulence. The question is how much, for how long, and whether what you're seeing is normal.

Short term (2–8 weeks): Expect ranking and traffic volatility as search engines recrawl, process redirects, and rebuild their index of your site.

• Small site (≤1,000 URLs): 2–4 weeks of volatility
• Mid-size site (~10,000 URLs): 4–8 weeks
• Large, complex sites: several months

A well-managed migration typically results in a temporary 5–20% organic dip for a few weeks, followed by stabilization. A catastrophic outcome — sustained 40–70% losses — almost always traces back to a specific technical or strategic error.

Long term (3–12 months): A well-planned migration can return traffic to baseline and exceed it, especially if the new site improves structure, speed, and content relevance.

Main SEO risks during migration:

• Lost link equity — missing or misconfigured redirects break backlink value
• Crawl errors — 404s, redirect loops, and broken links waste crawl budget
• Indexation issues — stale sitemaps, bad noindex tags, or blocked resources delay recovery
• Duplicate content — running old and new URLs in parallel dilutes ranking signals

Post-Migration Performance Expectations

Use this table to interpret your traffic data and decide whether to act.

Who Should Use This Checklist (and When)

This checklist is built for the core roles that own or influence a migration: marketing managers responsible for organic performance, SEO leads safeguarding rankings, project managers coordinating timelines, and development leads overseeing implementation.

Start using it as soon as a migration moves from vague idea to active planning. It remains relevant through specification, build, and testing; becomes a launch-day control sheet at go-live; and serves as a post-launch review tool in the first weeks after launch.

Phase 1: Pre-Migration Planning Checklist

Phase 1 Summary

Define objectives and SEO KPIs

Clarify why you're migrating and how success will be measured before any technical work starts. Translate each objective into measurable SEO KPIs so you can compare pre- and post-migration performance:

• Organic sessions (overall and by key section)
• Rankings for priority keywords
• Indexed pages count and index coverage
• Conversion rate from organic traffic
• Core Web Vitals (LCP, INP, CLS)
• Crawl errors and Search Console coverage

Document baseline values and define acceptable variance (e.g., "no more than 10% drop in organic sessions after 4 weeks"). Mark each KPI as "must protect" or "nice to improve" so trade-offs are clear under time pressure.

Map stakeholders and responsibilities

Assign clear ownership using RACI:

• Executive sponsor — approves scope, budget, go/no-go
• Project owner — coordinates tasks and risk management
• SEO lead — responsible for redirects, URL strategy, rankings
• Development lead — implements technical changes
• Content lead — oversees content audit and approvals
• Analytics owner — manages tracking and reporting

Name a backup for each critical decision so launch and rollback aren't gated on one person's availability.

Crawl and inventory the existing site

Run a full crawl to capture the true scope of what you're migrating and surface orphaned or hidden URLs. Build a master inventory with:

• All indexable URLs and status codes
• Canonical tags
• Title tags, meta descriptions, H1s
• Indexation signals (noindex, robots directives)
• Non-HTML assets (PDFs, feeds, key images)

This inventory feeds redirect mapping, the content audit, and technical checks. Include legacy subdomains or microsites that need to be in scope.

Content audit: keep, merge, or remove

Evaluate every significant URL using performance data — organic sessions, backlinks, conversions, and engagement.

Decision Framework: Keep, Merge, or Remove a Page

• High traffic or conversions → Keep and improve
• Strong backlinks but low traffic → Keep or merge (preserve link equity via redirects)
• No traffic, no backlinks, no conversions → Remove or noindex
• Multiple pages targeting same intent → Merge into one primary page
• Legally or operationally required → Keep regardless of performance

Record every decision in a spreadsheet so it feeds directly into redirect and build plans.

Content Audit Template:

Benchmark current performance

Capture a detailed snapshot so you can detect and diagnose changes after launch:

• Rankings for a defined set of priority keywords
• Organic sessions by section and landing page
• Conversion rate and total conversions from organic
• Core Web Vitals on mobile and desktop
• Indexed pages count and CTR from search

Use identical data sources and segments post-launch so comparisons are valid.

Define technical requirements and constraints

Specify what the new environment must support — platform features, URL structure rules, redirect capabilities, hosting/CDN, security and compliance, analytics requirements. Document hard constraints (e.g., no server-side redirects, limited DNS access) so the plan accounts for them early rather than at launch.

Plan rollback and backups

Decision Framework: Rollback vs. Fix Forward

• Site down or widespread critical errors → Rollback
• Tracking completely broken → Rollback
• >40% traffic drop with unclear cause → Consider rollback
• Issues are localized, understood, and fixable in hours → Fix forward

Required backups: full codebase, database, DNS records, server configs, analytics settings. Verify the restore process in staging before launch. Document a step-by-step rollback procedure with assigned owners and an approval chain.

Enterprise note: For large sites with many stakeholders, run a rollback tabletop exercise before launch. The procedure should be executable in under 30 minutes without senior approval if triggered by a pre-agreed threshold.

Phase 2: Pre-Launch SEO & Technical Checklist

Phase 2 Summary

Set up and secure the staging environment

Staging must mirror production but be invisible to search engines.

• Restrict access with password protection or IP allowlisting
• Add global noindex, nofollow via meta robots on every page
• Add X-Robots-Tag: noindex, nofollow HTTP header as a secondary layer
• Use robots.txt with Disallow: / — but never rely on this alone

Verify: crawl staging and confirm every HTML page is flagged noindex, canonicals are self-referential (not pointing to production), and robots.txt returns 200 with the disallow rule.

Design new site architecture and navigation

Group related content into intuitive categories. Keep important pages within 3 clicks of the homepage to preserve crawl depth and ranking potential. Decide URL patterns per content type (e.g., /category/, /blog/post-slug/) and apply consistently. Every significant legacy page needs a clear place in the new structure or a defined retirement plan.

Create a 301 redirect map

A robust redirect map is the single most important asset for preserving rankings and link equity.

Redirect mapping process:

1. Export all existing URLs from analytics, server logs, and XML sitemaps
2. Flag high-traffic, high-conversion, and high-backlink URLs as critical
3. Match each old URL to its most relevant new URL (aim for 1:1)
4. For retired pages with no equivalent, redirect to the nearest relevant higher-level page; for obsolete, low-value pages, consider 410 (Gone)
5. For consolidations, map many-to-one — ensure the destination addresses all merged intents
6. Every redirect must be one hop — no chains, no loops

Example redirect map:

Validation: implement on staging, crawl the old URL list against it, and confirm every URL returns a 301 to the intended destination with no chains, 302s, or 404s. Spot-check high-value URLs manually.

Migrate on-page SEO

Preserve or improve every critical on-page element that affects rankings:

• Titles and meta descriptions — export current, recreate on staging, check uniqueness and length
• Headings — one descriptive H1 per page aligned with primary keyword; logical H2/H3 structure
• Canonical tags — self-referencing for standard pages; correct variants for filtered/paginated pages; never pointing to staging
• Schema markup — implement structured data for relevant content types (organization, product, article, breadcrumb); validate with a testing tool

Canonical verification: crawl staging, extract all canonical tags, and confirm no loops, no non-200 targets, and no accidental cross-environment references.

Configure internal linking

Internal links guide crawlers and users to priority content, and they shape how ranking signals flow through the site:

• Top-level categories and revenue drivers linked from main navigation
• Contextual in-content links with descriptive anchor text (not "click here")
• Breadcrumbs marked up with structured data
• No orphaned pages (0 internal links)
• All internal links use final canonical URLs — not old or redirected paths

Technical SEO checks

Run a structured technical review on staging to catch issues before launch.

Pre-Launch Technical Checks:

Configure analytics and tracking (GA4, GTM, pixels)

Set up tracking on staging so data flows correctly from the moment of launch:

• Implement GA4 via GTM or direct script
• Add marketing pixels (ads, social, remarketing) with consent mechanisms
• Configure key events: form submissions, add-to-cart, checkout, purchases, lead actions
• Verify events fire in debug and real-time views
• Confirm production tracking IDs — not staging or test IDs — will ship

Audit for duplicate tags and missing events on key templates. Document the event schema so it can be validated immediately post-launch.

Performance and Core Web Vitals checks

Slow pages hurt rankings directly via Core Web Vitals and indirectly via engagement signals. Test each key template on staging:

• LCP (Largest Contentful Paint) — target under 2.5 seconds on mobile. Check hero images, fonts, and render-blocking resources.
• INP (Interaction to Next Paint) — target under 200ms. Audit heavy JavaScript and third-party scripts.
• CLS (Cumulative Layout Shift) — target under 0.1. Reserve space for images, ads, and embeds to prevent shift.
• TTFB (Time to First Byte) — target under 800ms. Validate server response, caching, and CDN configuration.

Run tests on home, category, product/article, and checkout templates using PageSpeed Insights, Lighthouse, and a real-device test. Compare against the pre-migration benchmark — any regression on a high-traffic template is a launch blocker.

Accessibility and UX checks

Accessibility directly affects rankings where it overlaps with UX signals (mobile usability, readability) and is a legal requirement in many jurisdictions:

• Keyboard navigation — every interactive element reachable and operable
• Color contrast — 4.5:1 for body text, 3:1 for large text
• Alt text — descriptive alt on meaningful images; empty alt for decorative
• Form labels — every input has an associated <label> or aria-label
• Heading hierarchy — no skipped levels (H1 → H2 → H3)
• Mobile usability — tap targets ≥48×48px; no horizontal scroll; readable without zoom

Run an automated audit (axe, Lighthouse) and supplement with keyboard-only and screen-reader spot-checks on key templates.

Phase 3: Launch-Day Checklist

Phase 3 Summary

Final pre-launch checks

1. Freeze content, design, and plugin changes
2. Confirm full backup of old site and new environment
3. Verify staging is in sync with final code and content
4. Confirm SSL certificate installed and valid on new host
5. Double-check robots.txt, XML sitemaps, canonicals for the new domain
6. Export list of top 20–50 pages to monitor (by traffic, revenue, backlinks)
7. Ready monitoring: uptime alerts, log access, analytics, GTM preview

Top pages to check first: homepage, top 10 organic landing pages, top 5 revenue pages, top 3 lead-gen pages, key blog hubs and category pages.

DNS / hosting switch and go-live

1. Lower DNS TTL several hours before launch
2. Update DNS records (A, AAAA, CNAME) to the new host
3. Confirm HTTPS redirects work with no mixed-content warnings
4. Verify site loads from multiple networks and regions
5. Start real-time uptime and response-time monitoring

Deploy 301 redirects

1. Enable redirect rules at the moment of DNS cutover
2. Test sample URLs: old homepage, top landing pages, product/category URLs, blog posts with known backlinks
3. Confirm all redirects are 301 (not 302 or meta refresh), one hop, pointing to the correct destination

Remove staging blocks

1. Remove global noindex directives
2. Remove HTTP auth and IP allowlists
3. Verify: no noindex on key templates; canonicals point to live URLs; robots.txt doesn't block key sections

Submit updated XML sitemaps

1. Confirm sitemaps are accessible at the new location
2. Update sitemap location in robots.txt if needed
3. In Search Console: submit new sitemaps; use URL Inspection to request indexing of homepage, top 10 landing pages, and key category/product pages

Validate key pages

1. Manually review the top N:

1. Confirm forms, search, login, and checkout work end-to-end
2. Check page speed on key templates

Check for critical errors

1. Run a focused crawl for 5xx, 404s on important URLs, redirect loops
2. Check server logs for error spikes
3. Verify analytics, ads, and pixels fire on homepage, top 5 landing pages, and conversion confirmation pages
4. Confirm goals and conversions are recording

Phase 4: Post-Launch Monitoring & Optimization

Phase 4 Summary

First 24 hours

Focus: stability, data integrity, critical errors.

1. Confirm 200 status on key URLs (home, top categories, top products, blog hub, forms, checkout)
2. Verify analytics, GTM, and conversion pixels fire correctly in real-time reports
3. Run a limited crawl (500–2,000 URLs) for 4xx/5xx clusters and unexpected noindex tags
4. Check Search Console: property verified, sitemaps submitted, no immediate server error spikes
5. Validate redirects for a sample of high-value legacy URLs
6. Page speed spot-checks on mobile and desktop for key pages

Red flags: widespread 5xx or timeouts; key templates returning 404/302 instead of 200/301; analytics showing near-zero traffic; large Search Console error spikes.

First week

Focus: confirm search engines are crawling and indexing correctly.

1. Daily traffic, organic trend, and conversion checks vs. pre-launch baseline
2. Expanded crawl across the full site — identify 4xx/5xx clusters, redirect loops, orphaned pages, stray noindex
3. Search Console: coverage report, sitemap processing, URL Inspection on high-value pages
4. Compare organic trend to baseline — a 10–20% dip for 1–2 weeks can be normal; >40% sustained is a red flag
5. Validate internal linking — no links to legacy or redirected URLs

First month and beyond

Shift from firefighting to optimization:

1. Weekly, then bi-weekly, checks on traffic, rankings, conversions, index coverage
2. Identify high-impression, low-CTR pages — adjust titles and meta descriptions
3. Monitor Core Web Vitals on templates that changed significantly
4. Reduce remaining redirect chains; update internal links to final URLs
5. By 4–6 weeks, organic should trend back toward baseline. If >25–30% below baseline after 6–8 weeks, treat as a structural issue and re-audit.

For help recovering from a sustained drop, see our guide to [diagnosing traffic loss after migration].

Fixing missed redirects and broken links

When 404s spike:

1. Find top 404 URLs in analytics and Search Console; group by pattern
2. Classify: legacy URLs needing redirects vs. spam/junk that can stay 404
3. Add 301s for legitimate legacy URLs; update internal links, sitemaps, and canonicals
4. Re-crawl affected sections to confirm 404 counts drop

Post-Launch Monitoring Schedule

Common Website Migration Mistakes to Avoid

1. Launching without complete redirect mapping — inventory every URL, map to destinations, test on staging.
2. Blocking staging and forgetting to unblock — add "remove noindex" to the launch checklist; verify live robots.txt immediately.
3. Launching without analytics tracking — configure and validate in staging; confirm firing on the live site.
4. Changing domain, CMS, and IA all at once — phase changes where possible to isolate variables and diagnosis.
5. Not benchmarking before migration — record traffic, rankings, speed, conversions; without this you're guessing.
6. Ignoring mobile and Core Web Vitals — test on real devices; include in pre-launch QA.
7. Overlooking internal link updates — crawl and update all internal links to final URLs.
8. Forgetting to update and submit XML sitemaps — regenerate, validate 200 status only, submit.
9. Skipping load and error monitoring at launch — run load tests, monitor logs in real time.
10. No rollback plan — backups, documented procedure, pre-agreed trigger thresholds.

Top 3 mistakes that kill SEO: incomplete redirects, leaving crawl blocks in place, launching without tracking. Treat these as non-negotiable items on every migration.

Website Migration Tools & Workflow

Rather than listing tools in isolation, here's how each fits into the migration workflow:

Pre-migration (planning and inventory):

• Crawlers (Screaming Frog, Sitebulb) — full URL inventory, metadata, status codes, internal links
• Rank trackers — baseline keyword rankings for priority terms
• Analytics — export traffic, conversion, and engagement baselines

Pre-launch (validation on staging):

• Crawlers — validate redirects, canonical tags, status codes, noindex rules
• Structured data validators — Rich Results Test, Schema Markup Validator
• Performance tools — PageSpeed Insights, Lighthouse, WebPageTest
• Accessibility auditors — axe, Lighthouse accessibility panel

Launch day and post-launch (monitoring and debugging):

• Uptime monitors — alert on downtime or key-page outages
• Log analyzers — see how bots crawl the new structure; spot redirect and error patterns
• Search Console — coverage, sitemap status, URL inspection, Core Web Vitals
• Rank trackers — compare movement against baseline

Use this article as your migration control document. Copy the master checklist at the top into Asana, Jira, Notion, or a Google Sheet. Assign owners, set due dates, and track status through launch and the first month after.

For platform-specific guidance, see our dedicated Shopify migration SEO guide or WordPress migration SEO guide.

Website Migration FAQ

What is a website migration? A website migration is a significant change to your site's platform, structure, design, domain, or hosting that affects how users and search engines access it. It typically involves URL changes, technical configuration updates, and content or template shifts that must be carefully planned and tested. For the full process, see the master checklist at the top.

Does website migration affect SEO? Yes. Migration can temporarily disrupt rankings, crawlability, and indexation if redirects, internal links, and technical settings aren't handled correctly. Done well, it preserves or improves visibility; done poorly, it causes major traffic loss that's difficult to recover. See the SEO impact section for typical ranges and recovery timelines.

How long does a website migration take? Small sites can complete in a few weeks; complex sites often need several months. Search engines can take days to weeks to fully process redirects and new URLs, so performance should be monitored over that period. See the pre-migration planning section for timing guidance.

How much traffic loss is normal after migration? A small, temporary dip of 5–15% in organic traffic for a few weeks is common. Larger or prolonged drops usually signal issues with redirects, internal links, indexing rules, or content — trigger a structured audit. See the post-migration performance table above for thresholds.

Do I need an SEO expert for migration? Strongly recommended for any site that relies on search traffic. SEO experts design redirect maps, protect key pages, validate technical settings, and interpret post-launch data. Smaller sites can follow checklists, but expert oversight reduces risk and speeds recovery. See the roles section in Phase 1.

Can I migrate my site without downtime? Yes, near-zero downtime is achievable with staging environments, DNS cutovers with low TTL, pre-warmed servers, and launching during low-traffic windows. Users may see brief cache-related inconsistencies, but a well-executed migration should avoid noticeable outages. See Phase 3 for launch-day execution.

What's the difference between SEO migration and website migration? A website migration is the overall move or change to your site's platform, structure, or domain. An SEO migration focuses specifically on preserving and improving organic visibility during that change — covering redirects, metadata, internal links, structured data, and indexation controls. Both should be planned together.

How do I know if my migration was successful? Success means stable or improving organic traffic and rankings, correct redirects, no major crawl errors, and key pages indexed under their new URLs. Analytics, Search Console, and crawl reports should show healthy engagement and no unexpected drops or error spikes. See the Phase 4 monitoring schedule for specific thresholds.

About the Author

Shakur Abdirahman

Technical SEO Specialist

Shakur is a Technical SEO Specialist with expertise in large-scale website migrations, redirect management, and technical SEO optimization. He helps businesses preserve search rankings and maintain crawl efficiency during complex site changes.

More about the author →

LinkedIn