Migrating WordPress to Webflow without losing your rankings
Replatforming is where SEO goes to die. A field-tested checklist for moving a site to Webflow and keeping every position you earned.
A replatform is the highest-risk thing you can do to an organic channel. Done carelessly, six years of accumulated authority evaporates in a fortnight. Done properly, nothing happens at all — which is exactly the goal.
Before you design anything: crawl the old site
Full crawl, exported. Every URL, its status code, its title, its meta description, its canonical, its inbound internal links. This export is your contract with the new site. You cannot map redirects for pages you didn't know existed.
Build the redirect map before the build, not after
- Every old URL maps to exactly one new URL, or is a deliberate, documented 410.
- 301, never 302. Never chain more than one hop.
- Watch trailing slashes and case sensitivity — Webflow and WordPress disagree, and that disagreement is a redirect loop.
- Preserve query-string handling for any paid campaign landing pages.
Match the content model, not just the pages
WordPress custom post types become Webflow CMS collections. Get the field-level mapping right — including the fields the old theme rendered but nobody remembers, like schema data hiding in a custom field.
Launch day sequence
- 01Publish to the staging domain and crawl it. Fix everything before DNS changes.
- 02Verify the redirect map against the old crawl export, URL by URL, automated.
- 03Cut DNS at a low-traffic hour. Keep the old host live and reachable for at least 30 days.
- 04Submit the new sitemap in Search Console immediately, and request indexing on the top 20 revenue pages.
- 05Watch Search Console coverage daily for two weeks. Most problems surface on day three, not day one.
The measure of a successful migration is that nobody outside the project ever notices it happened.
Rajat Bharti
Senior Web Developer in Bengaluru, IN. Writes about performance, automation and the parts of client work nobody documents.
