Strategy
WordPress to Webflow Migration: SEO Checklist and Real-World QA
Move from WordPress to Webflow without overlooking CMS exports, URL mapping, image assets, 301 redirects, canonicals, forms and Search Console checks.
Moving a WordPress business website to Webflow can simplify some editorial workflows and enable a new visual system. It is not a guaranteed SEO upgrade. The risk comes from changing content and URLs without a migration plan.
This platform-specific guide complements our website redesign SEO checklist. Keep that guide for the broad migration decisions; use this one for WordPress exports, Webflow collections and redirect implementation.
Confirm which WordPress features need replacing before you choose Webflow: multilingual paths, forms, search, membership and e-commerce workflows may require a different architecture.
- Export and audit WordPress content before changing the website.
- Map old URLs to equivalent new Webflow pages and test direct 301 redirects.
- Test the content, enquiry forms and indexability after launch; do not assume a platform switch improves rankings.
Step 1: inventory content and old URLs
| Old WordPress path | New Webflow path | Action |
|---|---|---|
| /services/web-design/ | /services/web-design | Permanent 301 if the content matches |
| /2025/09/example-post/ | /blog/example-post | 301 to the article with equivalent content |
| /old-discontinued-offer/ | No equivalent page | Return 404/410 rather than redirect to home |
Export WordPress posts, pages and relevant metadata; WordPress documents its Tools > Export XML workflow. That export is not a full visual website or media backup, so retain your theme assets, plugins, uploads and a complete database backup separately.
Crawl existing public URLs. Use Search Console to identify landing pages receiving clicks or links, and record titles, canonical tags, important images and contact form routes before redesign.
Create a mapping sheet with one row per old URL and columns for the new destination, redirect rule, test result and owner.
Step 2: rebuild CMS structure before import
Decide which content becomes Webflow CMS collections: posts, room types, case studies and authors can have different fields. Export and clean WordPress data to CSV for the structure you actually need, and verify SEO-relevant fields after import.
Check image names, image alt text, internal references, excerpt consistency and draft versus published status. Never assume an imported WordPress XML file automatically maps to a new CMS schema.
For multilingual sites, list each translated URL and plan language switching and reciprocal hreflang where a real equivalent exists.
Step 3: publish correct permanent redirects
Webflow documents CSV-based 301 import and export for redirects. Important: importing a new CSV can replace existing Webflow redirect entries, so export the current rules first and merge the entire mapping before uploading.
Test old URLs with an HTTP request: the server must send one permanent redirect to the relevant live page. Avoid redirecting all legacy pages to the homepage; that confuses users and search engines.
Keep the domain, host redirects and canonical targets aligned. If only the design changes and all URLs stay stable, there is no reason to manufacture redirects.
Step 4: run mobile and content acceptance tests
- HTTP status and redirect list verified from every valuable old URL.
- No stale links to the WordPress staging domain.
- All priority articles and media present and readable.
- Forms send real notifications; errors are understandable.
- Sitemap contains final canonical URLs, not redirected legacy paths.
- Search Console property and GA4 consent behavior are verified.
Open the new site on mobile and desktop: navigation, forms, cookie choices, CMS collections, image loading, links to downloadable resources, and every important conversion path.
Check the production HTML for a correct self-canonical, one descriptive H1, relevant title and description, crawlable content and no accidental staging noindex. Validate structured data only where it describes true facts.
Do not let a smooth-looking Webflow preview replace real testing on the production domain.
Step 5: monitor Search Console and users after launch
Compare important pages by search query and landing URL for several weeks. Google notes that ranking fluctuations can occur during major site moves; avoid judging the redesign after 24 hours.
Keep a record of actual qualified enquiries and any booking confirmations. A redesign can improve clarity without an immediate jump in organic sessions.
For a broader platform decision, see Webflow vs WordPress vs Framer.
FAQ
Common questions
Does WordPress export include every plugin setting and media?
No. The Tools > Export XML is a content export, not a full backup or automated copy of plugin functionality. Verify uploads and workflows separately.
Do I need 301 redirects if URLs stay the same?
Not just because you changed CMS. Redirect old paths only where the address actually changes.
Can a migration preserve rankings perfectly?
No one can guarantee that. Proper planning reduces avoidable loss but search engines still recrawl and reevaluate pages.
How long should I keep redirects?
Google recommends keeping permanent redirects in place at least one year, and longer when practical.
Sources
Primary sources for the claims above, last checked on 2026-10-19.
- WordPress Tools > Export — WordPress.org
- Import/export 301 redirects — Webflow Help
- Site moves with URL changes — Google Search Central
- Google Search SEO Starter Guide — Google Search Central
Have a project in mind?
Plan a website that supports real enquiries
Share your current funnel, content and requirements. Futura can review the scope and prepare a specific implementation plan.
Discuss your project
