To handle redirects when migrating from Webflow to WordPress, build a URL map of every old Webflow URL and its new WordPress destination, then create 301 redirects inside WordPress (not Webflow) using the Redirection plugin, your SEO plugin, or .htaccess rules. Match trailing slashes, avoid redirect chains, and keep the redirects live permanently.
I have handled this exact migration, and the redirect step is where it is won or lost. Your content will move fine; content always moves. What decides whether your rankings and traffic survive is whether every URL that existed on Webflow still resolves somewhere sensible on WordPress.
This guide covers the part most migration tutorials rush past: where the redirects actually live after you leave Webflow, the URL differences between the two platforms that catch people, and the mistakes (like trailing slash mismatches) that quietly create redirect chains.
Why redirects decide whether your migration succeeds
Redirects preserve the three things you spent years earning: rankings, backlinks, and referral traffic. When Google and other sites link to your Webflow URLs, those links point at specific addresses. If those addresses die after migration, the equity dies with them.
The data on this is stark. Research from Moz shows sites that maintain their URL structure preserve about 97% of their rankings at 90 days post-migration, while sites with significant URL changes and imperfect redirects keep only around 60% without aggressive recovery work.
A 301 redirect is how you stay in the first group when URLs must change: it tells search engines “this page moved permanently, transfer the authority to the new address.”
One more 2026-specific reason this matters: AI search engines including ChatGPT, Perplexity, and Google AI Overviews also crawl and cite URLs, and they respect 301 redirects the same way Google does.
The same redirect map that protects your rankings protects your AI citations, provided the new page stays substantially the same as the old one.
Where do redirects live after you leave Webflow?
This is the conceptual point that confuses almost everyone: after the migration, your 301 redirects live in WordPress, not in Webflow. Webflow has a native redirect manager in its site settings, but it only works while Webflow hosts your domain.
The moment your DNS points at your WordPress host, Webflow is out of the picture, and every request (including requests for old Webflow URLs) lands on your WordPress server.
So the sequence is: build your redirect rules in WordPress before the DNS switch, and they take effect the instant traffic arrives. Anything you set up in Webflow’s redirect panel becomes irrelevant the moment you leave.
This also answers a common question early: you do not need to keep paying for Webflow hosting to keep redirects working. Once DNS points at WordPress and your redirects are in place there, the Webflow subscription can end.
Step 1: Export every URL from Webflow (build the URL map)
The URL map is the document that drives everything: a spreadsheet with every old Webflow URL in column A and its new WordPress destination in column B. Without it, you are guessing, and guessing creates gaps that show up later as 404s in Search Console.
Collect the URLs from three places. First, your Webflow CMS Collections: open each collection and export it as a CSV, which gives you every item slug (blog posts, projects, case studies). Second, static pages: go through Webflow’s Pages panel and note each one manually.
Third, the real-world check most people skip: crawl your live Webflow site with a tool like Screaming Frog, and pull the “Pages” report from Google Search Console. These catch URLs you forgot exist, and the pages Google actually has indexed are the ones that most need redirects.
Include every URL, even low-traffic ones. You will decide what to do with each later; the map’s job is completeness.
Step 2: Know the URL differences between Webflow and WordPress
Webflow and WordPress structure URLs differently in predictable ways, and knowing the patterns lets you plan most of the map in minutes.
The big ones:
- CMS collection prefixes. Webflow CMS items live under their collection slug, like /posts/my-article or /work/project-name. WordPress default permalinks put posts at /my-article/ or under /blog/. If you keep slugs identical and only the prefix changes, one pattern rule handles the whole collection (Step 4).
- Trailing slashes. Webflow URLs typically have no trailing slash (/about), while WordPress defaults to trailing slashes (/about/). This looks trivial and is the single most common source of hidden redirect chains after this migration. Decide your WordPress format, then write redirects that point directly at the final format.
- Category and tag pages. Webflow collection template pages and WordPress category/tag archives rarely match one-to-one. Map each Webflow category page to its closest WordPress archive, or to the blog index if no equivalent exists.
- Case sensitivity and cleanup. Webflow slugs are lowercase by convention, but any manually created mixed-case URLs need explicit rules, since some servers treat /About and /about as different pages.
Before importing any content into WordPress, set Settings, Permalinks to “Post name”. Doing this first means content imports with clean, final URLs, and your map does not have to change midway.
Step 3: Keep the same slugs wherever you can
The best redirect is the one you never need. Wherever possible, keep the exact same slug on WordPress that the page had on Webflow, because an unchanged URL preserves rankings with zero redirect risk.
This is worth real effort. If your Webflow blog lived at /blog/post-name and WordPress can serve /blog/post-name, you have eliminated the entire redirect question for your most valuable section. Reserve URL changes for cases with a genuine reason: consolidating thin pages, fixing a bad old structure, or renaming a section deliberately. Every changed URL is a small SEO risk; do not spend that risk for cosmetic preferences.
Step 4: Create the redirects in WordPress
With the map ready, implement the rules. You have three good options, and which one fits depends on your hosting and comfort level.
Option A: The Redirection plugin (easiest, works everywhere). Install Redirection (free), go to Tools, Redirection, and add each rule: source path from column A, target URL from column B. It supports CSV import, so you can upload your whole map at once, and it logs 404s so you can catch anything you missed after launch.
Option B: Your SEO plugin. Rank Math and Yoast Premium both include redirect managers. If you already run one, adding rules there keeps everything in one place.
Option C: Server rules (fastest performance, technical). On Apache hosts, .htaccess handles redirects before WordPress even loads. A single pattern rule can cover a whole collection when slugs stayed identical:
RedirectMatch 301 ^/posts/(.*)$ https://yourdomain.com/blog/$1That one line sends every /posts/ URL to its /blog/ twin. Use patterns only when the slug is unchanged; changed slugs need individual rules. One caveat: managed WordPress hosts running Nginx (Kinsta, WP Engine, Cloudways) have no .htaccess, and server rules require going through the host. On those platforms, the Redirection plugin is the practical choice.
Whichever option you pick, redirect to the exact final URL, including the trailing slash format you chose. A redirect that lands on a URL that itself redirects (old URL to /about to /about/) is a chain, and chains leak both speed and link equity.
Step 5: Decide deliberately what gets no redirect
Not every old URL deserves a redirect, and pretending otherwise creates a different problem: redirecting everything to the homepage, which search engines treat as a soft 404 and which frustrates visitors who landed expecting a specific page.
The honest triage: high-traffic pages and any page with backlinks get precise, one-to-one redirects (check your backlinks in Search Console or a tool like Ahrefs; those URLs carry the equity that is most expensive to lose). Mid-value pages get redirected to the closest relevant equivalent, not the homepage.
Genuinely obsolete pages with no traffic and no links can be allowed to 404, which tells search engines cleanly that the page is gone. A deliberate 404 is healthier than a lazy homepage redirect.
One prioritization rule from practitioners who do this repeatedly: spend most of your validation effort on the small share of URLs that hold most of your backlink value. A redirect mistake on a page with fifty referring domains costs more than mistakes on fifty pages with none.
Step 6: Test before and after the DNS switch
Redirects fail quietly, so test them twice: once on the new site before DNS moves, and once against your full URL map after launch.
Before the switch, with WordPress on a staging or temporary URL, spot-check your redirect rules resolve to the right destinations. After DNS points at WordPress, run the real test: paste your entire column A (all old Webflow URLs) into Screaming Frog’s list mode and crawl it.
Every URL should return exactly one 301 hop to the correct final page, no 404s, no chains, no 302s (temporary redirects do not pass authority the way 301s do; migrations use 301s only).
Then watch Google Search Console: submit your new sitemap, and check the Pages report at one month and again at three months.
Expect minor ranking wobble for two to four weeks while Google recrawls; most sites return to baseline within about 30 days and settle fully by 60 to 90 days when redirects and metadata were handled correctly. The reviews catch the stragglers: 404s from URLs you missed, or chains that crept in.
How long should the redirects stay up?
Permanently, or as close to it as practical. Backlinks on other sites will keep pointing at your old Webflow URLs for years, and every one of those links only passes value while the redirect exists.
Google has suggested keeping migration redirects for at least a year; in practice, since the redirects live in your WordPress setup and cost nothing to maintain, there is no reason to ever remove the ones that receive traffic.
This is also why redirects belong in your WordPress site rather than any external service tied to a subscription: they survive as long as the site does, with no renewal to forget.
Conclusion
Redirects are the part of a Webflow to WordPress migration that decides whether your rankings survive, and they live in WordPress after the switch, since Webflow’s own redirect manager stops mattering the moment DNS moves.
Build a complete URL map from Webflow’s CMS exports, the Pages panel, a crawl, and Search Console. Keep slugs identical wherever possible so most pages need no redirect at all. Implement the rest with the Redirection plugin or server rules, matching trailing slashes exactly to avoid chains, giving backlink-heavy pages the most careful one-to-one mapping, and letting genuinely dead pages 404 deliberately.
Test the full old-URL list after launch, watch Search Console at one and three months, and leave the redirects up permanently. Do that, and the platform change stays invisible to Google, your visitors, and the AI engines citing your pages.
Frequently Asked Questions
Will I lose SEO migrating from Webflow to WordPress?
Not if redirects and metadata are handled correctly. Sites that keep their URL structure preserve about 97% of rankings at 90 days, per Moz research. Expect minor fluctuations for two to four weeks while Google recrawls; a correctly redirected migration typically returns to baseline within about 30 days.
Where do I set up redirects after leaving Webflow?
In WordPress. Once your DNS points at your WordPress host, every request (including old Webflow URLs) reaches WordPress, so the 301 rules must live there: in the Redirection plugin, your SEO plugin’s redirect manager, or your server’s .htaccess. Webflow’s own redirect settings stop working when you leave.
Do I need to keep paying for Webflow after migrating?
No. Once DNS points at your WordPress host and your redirects are set up in WordPress, Webflow no longer serves any traffic, so the subscription can end. Keep your Webflow account only long enough to export all content and confirm the new site and redirects work.
What happens to my backlinks when I migrate?
Backlinks point at URLs, not platforms. Links to URLs that stay identical keep working unchanged, and links to URLs that changed pass their value through the 301 redirects. Give pages with the most referring domains the most careful one-to-one redirect mapping, since their equity is the costliest to lose.
Should I redirect every old Webflow URL to my new homepage?
No. Bulk-redirecting everything to the homepage is treated as a soft 404 by search engines and loses the page-level relevance that passes ranking value. Redirect each URL to its closest equivalent page, and let genuinely obsolete pages return a clean 404 instead.
Should I use 301 or 302 redirects for the migration?
301 (permanent) redirects only. A 301 tells search engines the move is permanent and transfers ranking authority to the new URL. A 302 signals a temporary move and does not consolidate authority the same way, which makes it the wrong tool for a platform migration.
