SEO Website Migration Checklist & Project Plan (2026): How to Replatform or Rebrand Without Losing Traffic

Whether you are rebranding your startup onto a new .com domain, consolidating subdomains into subfolders, or replatforming a legacy WordPress site onto Webflow, Framer, or Next.js, a website migration is one of the highest-risk technical operations in digital marketing.

When organic visibility drops after a site launch, it is rarely because Google "penalized" the redesign. Traffic losses almost always trace back to preventable engineering oversights: staging noindex tags left on production pages, legacy URLs redirected en masse to the homepage instead of matching equivalents, broken internal link graphs, or stripped structured data.

A flat bulleted list is not enough to manage those dependencies across developers, designers, and stakeholders. Below is a complete SEO website migration project plan—complete with a risk assessment matrix, a copy-pasteable URL redirect mapping spreadsheet template, a launch-day runbook, and a 90-day post-migration monitoring protocol.

How to Migrate a Website Without Losing SEO Traffic

To execute an SEO website migration without losing organic traffic, benchmark all existing ranking URLs and backlink targets before touching code, map every changing URL to its exact semantic equivalent using permanent 301 redirects, and verify metadata, internal links, and rendering parity on a password-protected staging site. On launch day, remove staging blocks, test live redirects with a crawler, and submit both legacy and new XML sitemaps in Google Search Console to accelerate indexation and signal consolidation.

1. Benchmark Legacy Performance (Weeks -4 to -3): Crawl your current site and merge URL data with Google Search Console clicks, impressions, and external backlink counts.

2. Build a 1:1 301 Redirect Map (Weeks -3 to -2): Map every retiring URL directly to its closest matching new URL—never redirect inner content pages to the homepage.

3. Audit the Staging Environment (Weeks -2 to -1): Crawl the staging build to confirm title tags, headings, canonicals, schema markup, and Core Web Vitals match or improve upon the old site.

4. Execute Launch-Day Verification (Day 0): Deploy DNS/redirect rules, verify live HTTP 200 and 301 status codes, and submit the Google Search Console Change of Address form (for domain moves).

5. Monitor Reprocessing in GSC (Days 1 to 90): Track index coverage, 404 spikes, and page-level query recovery weekly until search signals stabilize.

Understanding Migration Scope: 4 Types of Website Migrations & Their SEO Risk

Not every migration carries the same level of ranking volatility. The time it takes Google to reprocess your site—and the potential for temporary traffic fluctuation—depends heavily on whether you are changing your underlying URLs, your HTML content/DOM structure, or both.

Engineering Best Practice: If your leadership team wants to change your domain name, switch from WordPress to Framer/Webflow, and rewrite 50 landing pages at the same time, push back. Separate the domain move from the content/architecture overhaul by at least 60 days so Google can process 1:1 URL forwarding cleanly before evaluating new page layouts.

Complete SEO Website Migration Project Plan (6-Week RACI Timeline)

Successful migrations treat SEO as an engineering workstream prior to writing code, not a last-minute QA check the afternoon before launch. Use this 6-week project schedule to assign clear ownership across your team:

Phase 1: Pre-Migration Audit & Baseline Benchmarking (Weeks -4 to -3)

Before any page is deleted or any slug is altered, you must build a complete snapshot of how search engines and users currently interact with your website. If something breaks after launch, this baseline is the only way to diagnose what was lost.

1. Crawl the Legacy Site & Export Full URL Inventory

Use a desktop crawler like Screaming Frog SEO Spider (or Ahrefs Webmaster Tools / Semrush Site Audit—see our guide on How to Get Semrush for Free & Run a Trial Audit Sprint) to crawl 100% of your existing website:

• Export all internal HTML URLs returning an HTTP 200 status code.

• Record existing Title Tags, Meta Descriptions, H1 headings, Canonical URLs, word counts, and internal inlink counts.

• Export all existing HTTP 301 redirect rules currently active on your server or .htaccess / Cloudflare configuration so legacy redirects are not accidentally wiped out when switching hosts.

2. Export 16 Months of Google Search Console & Analytics Data

A common mistake is only redirecting pages that appear in your current XML sitemap. Often, older blog posts or forgotten landing pages sit outside the main navigation while still driving organic traffic or holding valuable backlinks.

• Open Google Search Console → Performance → Search Results, set the date range to Last 16 months, and export all Pages with at least 1 click or 50 impressions.

• Open Google Search Console → Indexing → Pages and export all indexed URLs.

• Export your top landing pages by organic sessions and conversions from GA4 (or your product analytics tool) over the past 12 months.

3. Audit High-Authority Backlink Target URLs

Using Ahrefs Webmaster Tools (free for verified site owners) or Semrush Backlink Analytics, export every URL on your domain that has at least one external referring domain—including broken (404) legacy pages that still have external links pointing to them. Migrating is the single best opportunity to reclaim lost link equity by redirecting historically linked 404 URLs to relevant live pages.

Phase 2: The URL Redirect Mapping Spreadsheet (Template & Rules)

Whenever a URL changes—even by a single character, trailing slash, or subfolder name (such as /services/seo-audit changing to /blogs/technical-seo-audit-services-guide)—you must implement a permanent HTTP 301 redirect (or HTTP 308 permanent redirect).

Copy-Paste URL Redirect Mapping Spreadsheet Template

Create a master Google Sheet or Excel workbook using these exact 9 columns to merge your crawl, traffic, and backlink data into an engineering-ready redirect map:

4 Non-Negotiable 301 Redirect Rules (Avoiding Soft 404s & Chains)

1. Never Redirect Retired Inner Pages to the Homepage: When you redirect a specific blog post or product page to your root homepage (/), Google's algorithms detect that the destination page bears no semantic relationship to the original URL. Google Search Console will flag this as a Soft 404, dropping all ranking signals and backlink equity associated with the old page. Always redirect to the closest topically related category, parent guide, or alternative feature page.

2. Eliminate Redirect Chains (URL A → URL B → URL C): Every additional hop in a redirect chain adds server latency and wastes crawl budget. If URL A previously redirected to URL B, and URL B is now moving to URL C, update both rules so URL A → URL C and URL B → URL C resolve in a single hop.

3. Standardize Protocol, www, and Trailing Slashes in One Rule: Ensure http:// to https://, non-www to www (or vice versa), and trailing slash normalization (/page/ vs. /page) resolve in a single global edge/server rule rather than chaining three separate redirects.

4. Watch CMS Folder Prefix Constraints (Webflow, Framer & Shopify): If you are migrating from WordPress (where blog posts lived at the root domain.com/post-slug/) to Webflow or Shopify (where CMS items require a collection folder like domain.com/blogs/post-slug), use wildcard regex rules where supported—but always test individual top-traffic URLs manually. (Comparing modern CMS capabilities? See our engineering breakdown of Webflow vs. Framer vs. WordPress).

Phase 3: Staging Environment & Technical Parity Audit (Weeks -2 to -1)

Once your development team has built the new site on a staging environment (e.g., staging.yourdomain.com or a .webflow.io / .framer.website preview domain), conduct a full technical parity audit at least 7 days before launch.

Securing Staging Without Accidental Production noindex Leaks

The single most destructive launch-day mistake occurs when developers place <meta name="robots" content="noindex, nofollow"> across the staging site to keep it out of Google, and then push that exact code to production on launch day.

• Best Practice: Protect your staging environment using HTTP Basic Authentication (password protection) or IP whitelisting rather than HTML meta noindex tags or robots.txt blocks. That way, your staging HTML templates remain 100% identical to production, and nothing can accidentally block Googlebot when DNS switches over.

Verifying Content, Metadata, Schema & Internal Link Parity

Crawl your staging site using Screaming Frog (entering your staging HTTP password in Spider Configuration) and verify:

• Metadata & Heading Parity: Did every migrated Tier-1 page retain its optimized <title>, <meta name="description">, and <h1>? Designers frequently overwrite SEO-optimized H1 headings with vague marketing taglines during redesigns.

• Internal Link Graph Depth: Compare internal link counts per page between the old crawl and the staging crawl. Often, sleek new mega-menus or simplified footers strip out links to key commercial pages, pushing them from click-depth 1 to click-depth 4+.

• Structured Data (JSON-LD) Validation: Confirm that Organization, SoftwareApplication, Article, BreadcrumbList, and FAQPage schema markup were carried over cleanly without syntax errors.

• JavaScript Rendering & Mobile Parity: Because Google uses mobile-first indexing, verify that mobile accordion menus, tabs, and lazy-loaded sections exist in the rendered DOM and are not hidden behind user-click events. (Need a deeper diagnostic checklist? Reference our complete Technical SEO Audit Services & Enterprise Checklist).

Phase 4: Launch-Day Runbook (Go-Live Execution Checklist)

Schedule your migration launch during your lowest-traffic business hours (typically Tuesday or Wednesday morning, never Friday afternoon) so your engineering and SEO teams are online to resolve immediate edge cases.

Run through this exact sequence on Launch Day (Hour 0 to Hour 4):

1. Lower DNS TTL 24–48 Hours Prior: Set your DNS Time-to-Live (TTL) down to 300 seconds (5 minutes) two days before launch so DNS cutover propagates globally within minutes.

2. Flip DNS & Deploy Edge/Server Redirects: Point production traffic to the new server/CMS and activate your 301 redirect rules.

3. Immediate robots.txt & Meta Robots Check (Minute 5): Manually inspect [https://yourdomain.com/robots.txt](https://yourdomain.com/robots.txt) and view the page source of your homepage, top 5 commercial pages, and top 5 blog posts to confirm:

   • robots.txt is NOT set to Disallow: /.

   • Meta robots tag says index, follow (no noindex tags).

   • Self-referencing <link rel="canonical"> tags point to the live production domain (NOT the staging. URL!).

4. Crawl the Redirect Mapping Sheet in List Mode (Minute 15): Upload Column A (Legacy URLs) from your Redirect Mapping Spreadsheet into Screaming Frog → Mode: List (with "Always Follow Redirects" enabled in Configuration). Verify that:

   • Every legacy URL returns an initial 301 status code and resolves to a final 200 OK destination.

   • Zero URLs resolve to a 404, 500, or redirect loop.

5. Verify Analytics & Conversion Tracking (Minute 45): Test live form submissions, trial signup buttons, and GA4 / CRM attribution tags to ensure lead tracking did not break during the cutover.

Phase 5: Post-Migration Monitoring & GSC Diagnostics (Days 1 to 90)

Your job does not end when the site goes live. The first 30 to 90 days determine how quickly Google transfers historical ranking signals to your new URLs or domain.

Submitting Both Old and New Sitemaps in Google Search Console

• Submit Your New XML Sitemap: Upload your clean sitemap.xml (containing only canonical HTTP 200 new URLs) in Google Search Console.

• Temporarily Submit a "Legacy Redirect Sitemap": Generate a temporary XML sitemap containing your old retired URLs and submit it in GSC alongside your new sitemap for the first 30 to 45 days. This forces Googlebot to rapidly recrawl the old URLs, discover the 301 redirects immediately, and consolidate ranking equity faster. Once GSC shows those old URLs as "Page with redirect", remove the temporary legacy sitemap.

• For Full Domain Moves Only: Use the Change of Address Tool inside Google Search Console (Settings → Change of Address) on the old domain property to officially notify Google that your domain has permanently moved to the new property.

• Keep Legacy Domain Registration & Redirects Active for at Least 1 Year: Google Search Central explicitly recommends maintaining control of the old domain and keeping 301 redirects live for a minimum of 1 year (and indefinitely if high-authority backlinks point to the old domain).

What to Expect During Google's Reprocessing Window

According to official Google Search Central Site Move Documentation, temporary fluctuations in rankings and organic impressions are normal during any migration that changes URLs:

• Days 1 to 14 (Crawl Surge & Index Swap): You will see a sharp spike in crawl requests inside GSC → Settings → Crawl Stats as Googlebot processes 301 redirects. In the Page Indexing report, indexed count on old URLs will drop while new URLs climb.

• Days 15 to 45 (Signal Consolidation): Page-level rankings may fluctuate by a few positions while Google re-evaluates canonical targets and page rendering. Use the GSC Page-Level Filter workflow to verify that your Tier-1 commercial pages are regaining their pre-migration average positions.

• Update High-Value External Backlinks Directly: While 301 redirects pass link equity, reaching out to your top 20 to 30 referring domains (partners, directories, and high-authority publications) to update their links directly to your new URLs eliminates redirect latency for human visitors and crawlers alike.

Downloadable & Copy-Paste Migration Sign-Off Tracker

Copy this sign-off table into your Notion workspace, Jira epic, or Google Sheet to track final QA approval across every phase:

Transparent Callout — Need a Pre-Migration Audit or Webflow/Framer Replatforming Review?

Planning to migrate your B2B SaaS or business website from WordPress or HubSpot to Webflow or Framer? The engineering and technical SEO team at 8Spark helps startups validate staging architecture, build 1:1 redirect maps, and protect organic search equity during CMS transitions. Explore our SaaS SEO Strategy & Software Stack guide or contact our team for a technical review.