Webflow Migration Checklist: The SEO-Safe Guide for 2026

Table of Contents

1. Pre-Migration: The Audit Phase
2. URL Strategy & Redirect Mapping
3. Content Migration: What Moves, What Changes
4. SEO Metadata Preservation
5. Structured Data & Schema Migration
6. Technical SEO Setup on the New Webflow Site
7. Pre-Launch Testing
8. Launch Day: The Cutover Process
9. Post-Launch Monitoring & Recovery
10. Platform-Specific Migration Guides
11. Frequently Asked Questions

Pre-Migration: The Audit Phase

Before touching Webflow, you need a complete inventory of what exists on your current site. Every URL, every meta tag, every ranking position. Skip this phase and you're flying blind.

1. Crawl Your Current Site

Run a full crawl with Screaming Frog, Sitebulb, or a similar tool. Export every URL with its:

• Status code (200, 301, 404)
• Title tag and meta description
• H1 and H2 tags
• Canonical URL
• Indexability status (index/noindex)
• Word count
• Incoming internal links

2. Export Search Console Data

From Google Search Console, export:

• All pages receiving organic clicks in the last 16 months (the maximum GSC window)
• Average position and click-through rate for each URL
• Top queries driving traffic to each URL
• Any pages with manual actions or security issues

3. Audit Current Backlinks

Use Ahrefs, SEMrush, or Moz to export your entire backlink profile. Flag:

• Pages with the most referring domains (these are your highest-risk URLs — losing them costs the most authority)
• Backlinks pointing to URLs that will change structure
• Toxic backlinks that should be disavowed after migration

4. Benchmark Current Performance

Record baseline metrics you'll compare against post-migration:

• Total indexed pages in Google
• Organic traffic (last 30 days, GA4)
• Core Web Vitals scores (LCP, INP, CLS) for top 20 pages
• PageSpeed Insights scores for key landing pages
• Current domain rating/authority

URL Strategy & Redirect Mapping

URL structure decisions during migration can't be undone without another migration. Get this right once.

Decision: Keep or Change URLs?

• Keep URLs identical: Lowest risk. If your current URL structure is clean and logical (e.g., /services/web-design/), mirror it exactly in Webflow. This eliminates redirect risk entirely
• Improve URLs: Medium risk. If your current URLs are messy (e.g., /?page_id=47 or /2023/03/15/blog-post-title/), migration is the right time to improve them. Create clean, keyword-rich Webflow URLs. Every changed URL needs a precise 301 redirect
• Completely restructure: High risk. Only do this if your current information architecture is fundamentally broken. Requires thorough redirect mapping and carries the highest traffic risk

Building the Redirect Map

Your redirect map is a spreadsheet with three columns and zero gaps:

• Column A — Old URL: Every URL from your crawl (excluding 404s). Use relative paths: /old-page/, not https://oldsite.com/old-page/
• Column B — New URL: The exact Webflow URL it maps to. Must exist in Webflow's page structure
• Column C — Redirect type: 301 (permanent) for most. Use 302 only if the move is temporary

Critical rules:

• Every old URL must redirect somewhere — even deleted pages should go to the most relevant existing page, not a generic homepage
• One-to-one redirects: /old-page/ → /new-page/. Not one-to-many
• Preserve trailing slashes: If old URLs have them, Webflow URLs should too (or redirect the slash variant)
• Test every redirect before launch — a spreadsheet typo is a 404 in production

Content Migration: What Moves, What Changes

Not everything should move as-is. Migration is your chance to improve.

Content Audit: Keep, Improve, Remove

• Keep as-is: High-performing pages (top 20 by organic traffic), cornerstone content, pages with strong backlinks. Preserve URL, content structure, and heading hierarchy exactly
• Improve during migration: Pages with decent rankings (positions 4-15) but thin content. Add 500-1000 words, update statistics to 2026, add FAQ sections, improve internal linking. Keep the URL
• Remove and redirect: Pages with zero traffic, zero backlinks, and no strategic value. Redirect to the most relevant existing page
• Consolidate: Multiple thin pages on the same topic → one comprehensive pillar page. Redirect all old URLs to the new pillar

CMS Content Migration

If moving from WordPress CMS to Webflow CMS:

• Export WordPress posts/pages as CSV
• Map WordPress fields to Webflow CMS fields. Blog title → Name. Post content → Rich Text. Featured image → Image field. Categories/tags → Multi-reference or option fields
• Import via Webflow's CSV import (max 200 items per import — batch larger sites)
• For sites with 500+ posts, consider using the Webflow API with a migration script instead of manual CSV imports

SEO Metadata Preservation

Every page's SEO metadata must survive the migration intact — or be deliberately improved.

Fields to Preserve or Upgrade

• Title tags: Match existing titles for high-performing pages. For improved pages, write new titles targeting 2026 keywords. 50-60 characters, primary keyword near the front
• Meta descriptions: 150-160 characters. For CMS-driven pages, build dynamic meta descriptions from CMS fields
• H1 tags: Match existing H1s for pages keeping their content. For improved pages, write H1s that include the primary keyword naturally
• Image alt text: Import all existing alt text. For new images, write descriptive alt text — every image needs it
• Canonical URLs: Set self-referencing canonicals on every page. Webflow does this automatically, but verify
• Open Graph tags: Set og:title, og:description, og:image (1200x630px), og:image:width, og:image:height. Without explicit width/height, Facebook and LinkedIn drop image previews
• Robots meta tags: Preserve any existing noindex/nofollow directives. If a page was noindexed on the old site, keep it noindexed on Webflow until you're ready to change the strategy

Structured Data & Schema Migration

Schema markup doesn't automatically transfer. You need to rebuild it in Webflow — and this is an opportunity to upgrade.

Schema Audit & Migration

• Audit existing schema: Use Google's Rich Results Test on 10-15 key pages of the old site. Record every schema type in use
• Rebuild in Webflow: Add JSON-LD schema to page-level custom code or CMS template code. For programmatic pages, build dynamic schema that pulls from CMS fields
• Upgrade schema: If the old site had only basic Organization schema, add Article, FAQ, LocalBusiness, BreadcrumbList, and HowTo schema where relevant
• Test before launch: Run every new schema through the Rich Results Test and Schema Markup Validator

Technical SEO Setup on the New Webflow Site

Before launch, configure these in Webflow's project settings:

Webflow SEO Settings Checklist

• Global canonical URL: Set to https://yourdomain.com
• Auto-generate sitemap: Enabled. Verify it generates correctly at /sitemap.xml
• SSL: Enabled. Webflow provides free SSL — verify it's active on your custom domain
• 301 Redirects: Import your entire redirect map into Webflow's redirect manager. Import in batches if the list is large
• Custom robots.txt: Add disallow rules for staging subdomains, Webflow's CDN paths, and any utility pages. Add your sitemap reference
• Favicon and Web App Manifest: Upload favicon (32x32px) and configure PWA manifest if applicable
• Custom 404 page: Design a helpful 404 page with navigation links and a search function

Pre-Launch Testing

Test everything on the Webflow staging subdomain before switching DNS.

Pre-Launch Test Checklist

• Crawl the staging site: Use Screaming Frog. Confirm: all expected pages return 200, no unexpected 404s, no redirect chains, all meta titles and descriptions are populated and unique
• Validate redirects: Test a random sample of 50 redirects from your map. Use a tool like curl -I or redirect-checker to verify each returns 301 to the correct destination
• Check mobile responsiveness: Test every page template on real mobile viewports — not just Webflow's preview
• Validate schema: Run 15-20 key pages through Google's Rich Results Test
• Test forms: Submit every form on the site. Verify emails arrive, CRM entries are created, and thank-you pages load
• Check Core Web Vitals: Run PageSpeed Insights on the top 10 pages. Compare to your pre-migration benchmarks
• Verify analytics: Confirm GA4 is firing on all pages. Check Google Search Console is configured for the new domain
• Internal link check: Confirm no internal links point to the old domain. All links should be relative or point to the new domain

Launch Day: The Cutover Process

The cutover itself — switching DNS to point to Webflow — should be methodical, not rushed.

Launch Day Sequence

1. Submit old sitemap one final time in Google Search Console — this helps Google discover redirects faster
2. Switch DNS: Point your domain's A records and CNAME to Webflow. For most registrars, DNS propagation takes 5-30 minutes but can take up to 48 hours in rare cases
3. Verify SSL: Once DNS propagates, Webflow auto-provisions SSL. Confirm the site loads on https://
4. Submit new sitemap: Submit https://yourdomain.com/sitemap.xml to Google Search Console
5. Request indexing: Use the URL Inspection tool in GSC to request indexing for your homepage and top 10 landing pages
6. Submit change of address: If you're moving domains (e.g., oldsite.com → newsite.com), use GSC's Change of Address tool
7. Monitor for 24 hours: Keep a close eye on GSC, analytics, and server logs for any errors

Post-Launch Monitoring & Recovery

The 90 days after migration are when most traffic loss happens — and when most recovery occurs if you're vigilant.

Post-Launch Monitoring Schedule

• Day 1-7 (hourly checks): Monitor GSC for crawl errors. Watch for 404 spikes, redirect failures, and pages dropping from the index. Check that forms and critical user flows work
• Week 2-4 (daily checks): Track organic traffic against your baseline. Monitor average position for top 20 keywords. Check for any new crawl errors. Review Core Web Vitals in CrUX
• Month 2-3 (weekly checks): Compare organic traffic to pre-migration levels. Most sites recover to 80-95% of previous traffic by month 3 if migration was executed correctly. Audit backlinks — reach out to sites linking to old URLs that aren't redirecting properly
• Month 4-6 (monthly checks): If traffic hasn't recovered to pre-migration levels by month 4, investigate: missing redirects, lost backlinks, content quality degradation, or technical issues on the new Webflow site

Common Post-Migration Issues and Fixes

• Traffic drop >30%: Check redirect map for missing entries. Check if Google has discovered the new sitemap. Verify no pages are accidentally noindexed
• 404 spike: Identify the 404 URLs in GSC. Add redirects for high-value pages. For low-value ones, ensure they return a proper 410 (Gone) if permanently removed
• Core Web Vitals regression: Audit the new site's performance. Heavy Webflow interactions, unoptimised images, or bloated custom code are common causes
• Index bloat: If Webflow is indexing staging URLs, CSS files, or other non-content pages, tighten robots.txt immediately

Platform-Specific Migration Guides

WordPress to Webflow

The most common migration path. Export WordPress content via Tools → Export → All Content. Map posts, pages, and custom post types to Webflow CMS collections. Pay special attention to: permalink structure (WordPress often uses /blog/post-name/ — match this in Webflow), Yoast/RankMath SEO metadata (export and map to Webflow SEO fields), and WooCommerce data (Webflow Ecommerce has different schema — plan the product data mapping carefully).

Squarespace to Webflow

Squarespace exports are limited. You'll likely need to manually copy content or use a scraping tool. Squarespace URLs often use clean slugs — these can usually be preserved in Webflow. Blog posts export via WordPress format (Squarespace uses a WordPress-compatible export).

Wix to Webflow

Wix doesn't provide a clean export. Content migration for Wix sites with more than 50 pages typically requires a scraping approach. Wix URLs often contain hash fragments (/#!page/c1v7m) — these won't redirect cleanly. Budget extra time for Wix migrations.

Custom Build to Webflow

The most complex migration type. You need to reverse-engineer the existing URL structure, content model, and any dynamic functionality before building the Webflow equivalent. For large custom builds (500+ pages), a phased migration — moving section by section — is often safer than a single cutover.

Frequently Asked Questions

How long does a Webflow migration typically take?

A standard migration (50-100 pages, including a CMS blog) takes 4-8 weeks from audit to launch. Larger sites (200+ pages) typically take 8-16 weeks. The content migration itself is 60% of the work; SEO preservation and testing account for the other 40%. Rushing either phase means traffic loss.

Will I lose SEO rankings during a Webflow migration?

If the migration is executed correctly — all redirects in place, metadata preserved, content kept or improved, schema rebuilt, and post-launch monitored — you should not lose rankings. Most well-executed migrations see a temporary 5-15% dip that recovers within 4-8 weeks. Some actually improve rankings because Webflow's cleaner code and faster performance boost Core Web Vitals.

Can I migrate my WordPress blog to Webflow CMS?

Yes. Export WordPress posts as CSV, map the fields to Webflow CMS, and import. For blogs under 200 posts, CSV import works well. For larger blogs, use the Webflow API with a migration script. Note that Webflow CMS has a 100-field-per-collection limit — complex blogs with many custom fields may need restructured data models.

What's the biggest risk in a Webflow migration?

The biggest risk is missing redirects. One missed redirect on a page with backlinks from 20 referring domains can permanently lose that link equity. The second biggest risk is changing URLs unnecessarily. If your current URLs are clean and ranking well, keep them — the SEO benefit of a "better" URL structure rarely outweighs the ranking risk of 301 redirects.

How do I handle a domain change during Webflow migration?

If you're changing domains, use Google Search Console's Change of Address tool. Implement site-wide 301 redirects from every page on the old domain to its equivalent on the new domain. Update all social profiles, directory listings, and external citations to the new domain. This is a 6-12 month process for full authority transfer.

Can I keep my Webflow staging site hidden from Google?

Yes. In Webflow project settings, disable indexing for the webflow.io staging domain. Also password-protect the staging site during development. Add the staging domain to your robots.txt disallow list as a belt-and-suspenders measure. Never point real backlinks at your staging domain.

How does a London Webflow migration differ from a general migration?

London businesses face specific migration challenges: (1) Local SEO signals — Google Business Profile, local citations, and review signals need to survive the migration intact. (2) Competitive market — London rankings are harder to recover if lost, so the margin for error is smaller. (3) Location-specific URLs — if you have neighbourhood-level landing pages, every one needs its redirect preserved. (4) UK-specific structured data — ensure LocalBusiness schema includes UK-formatted addresses and phone numbers.