WordPress to Webflow: A 30-Day Migration Roadmap for Marketing Teams (2026)

Before touching Webflow, export every URL on your WordPress site using a crawler (Screaming Frog, Ahrefs, or Google Search Console export). For each URL, capture: full URL, HTTP status code, title tag, meta description, H1, canonical URL, inbound internal links, and inbound backlinks. This is your migration master document — the basis for every redirect and every piece of metadata you'll transfer.

Also export: all existing 301 and 302 redirects from `.htaccess` or your WordPress redirect plugin, the XML sitemap from `yourdomain.com/sitemap.xml`, and all images via a Media Library bulk export. If you have WooCommerce, export product data separately — Webflow's ecommerce structure differs significantly from WooCommerce.

Categorize your content by type: static pages (keep or consolidate), blog posts (migrate or cut), landing pages (rebuild in Webflow designer), and archive/tag/category pages (decide whether to mirror or redirect to category equivalents). Cutting content you don't intend to maintain is the right call — thin, unmaintained content hurts rankings more than 404s with proper redirects.

Build page templates before migrating content. Webflow's CMS is most efficient when you define the collection schema first and then import content — not the reverse. Set up the CMS collection for blog posts, define all custom fields (including a Meta Description field that will bind to SEO settings), and configure the collection template page before importing any posts.

The WordPress-to-Webflow blog importer handles most post imports: export WordPress posts as XML (WordPress Admin → Tools → Export), then import to Webflow. Images and basic formatting transfer; custom blocks and shortcodes need manual cleanup. Non-blog pages must be rebuilt manually in Webflow's designer — there's no automated page importer.

Build your redirect mapping table in parallel: every old WordPress URL maps to either a Webflow equivalent URL or a relevant redirect destination. Add all redirects to Webflow before launch (Project Settings → SEO → 301 Redirects). Missing even one high-traffic URL means a 404 that Google will discover — and that URL's accumulated ranking signals are lost.

Launch sequence: (1) Verify all redirects are in Webflow before going live. (2) Point DNS to Webflow — propagation typically takes 30 minutes to 2 hours. (3) Submit new sitemap to Google Search Console within 24 hours of launch. (4) Verify `yourdomain.webflow.io` staging subdomain is either deleted or set to noindex. (5) Run a post-launch crawl with Screaming Frog to verify no unexpected 404s.

Transfer all metadata from your WordPress audit document to Webflow before launch. Title tags and meta descriptions are the highest-priority transfer. Canonical URLs should be set on all CMS collection pages. Internal links pointing to old WordPress URLs that weren't changed in Webflow will be broken — audit internal links during QA.

A well-executed migration maintains rankings within 2–4 weeks. Expect a brief fluctuation in the first 7–14 days as Google re-crawls and processes the new sitemap — this is normal. Monitor Google Search Console daily for the first 30 days: watch for 404 errors (fix any you missed), coverage issues, and crawl rate changes.

Performance improvements are typically immediate and measurable. Most WordPress sites with a typical plugin stack have Core Web Vitals scores of 40–65 on mobile. Webflow sites commonly hit 75–90 on mobile without additional optimization. If paid traffic is a significant channel, you may see conversion rate improvements within the first week from faster load times.

If rankings drop after 4 weeks and don't recover, the most common causes are: missed redirects (high-value URLs returning 404), metadata not transferred (pages ranking with old title tags that are now missing), or canonical errors (Webflow serving duplicate content via collection page filters).