How to Handle Redirects When Migrating From Webflow to WordPress

Knowing how to handle redirects when migrating from Webflow to WordPress is the difference between keeping your rankings and watching six years of link equity evaporate in a weekend. Webflow and WordPress build URLs differently, so almost every page on your site will change address unless you plan for it. This guide covers the URL inventory, the redirect map, where to run the rules, and how long to watch your 404 logs afterward.

Why Redirects Are the Riskiest Part of a Webflow to WordPress Move

Moving content is mechanical. You export what you can, rebuild the templates, and re-upload the media. Redirects are different because they depend on decisions Webflow made for you years ago, decisions you may not remember making.

Webflow CMS collections force a path prefix. A blog collection often publishes to /blog/post-slug, but plenty of sites end up with /post/, /posts/, or a custom collection slug like /insights/. WordPress, meanwhile, defaults to /%postname%/ with no prefix at all. That single mismatch can orphan every article you’ve ever published.

Google treats a missing page as a signal to drop it. According to Google Search Central’s guidance on site moves, a permanent 301 redirect is how you pass ranking signals from an old URL to a new one, and it should stay in place for at least a year.

Step 1: Build a Complete Inventory of Your Webflow URLs

You cannot redirect what you haven’t listed. Before you touch WordPress, pull every URL Webflow has ever served from at least four sources, because no single source is complete.

• Your Webflow sitemap.xml: visit yourdomain.com/sitemap.xml and copy every entry. This gives you current, published pages only.
• Google Search Console: export the Pages report and the last 16 months of Performance data by page. This catches URLs that still earn clicks but fell out of your sitemap.
• A crawler: run Screaming Frog or Sitebulb against the live Webflow site to catch pages nobody linked in the nav.
• Webflow’s existing redirect list: under Site Settings, Publishing, you’ll find 301 redirects somebody already created. Those old paths still receive traffic and need to be carried over.
• Analytics: export landing pages from GA4 for two years, sorted by sessions.

Deduplicate everything into one spreadsheet. A 60-page marketing site with a blog usually produces 200 to 600 unique URLs once you include old redirects and paginated archives.

Step 2: Map Webflow Paths to Their WordPress Equivalents

Now decide what the new structure looks like. You have two honest options, and the second one is usually better.

Option A: match Webflow exactly. Set your WordPress permalink structure to mirror the old prefix, for example /blog/%postname%/, and rebuild static pages at identical paths. Fewer redirects, less risk, less cleanup.

Option B: redesign the structure. Sensible if your Webflow slugs were messy, but every changed URL now needs a 301. Do this once, at migration time, rather than twice.

Whichever route you pick, watch these details as you import content:

• Trailing slashes: Webflow serves URLs without them by default; WordPress adds them to posts and pages. Pick one convention and redirect the other.
• Case sensitivity: Webflow slugs are lowercase, but old external links may contain capitals. Add a lowercase rule server-side.
• Collection prefixes: /blog/ versus /posts/ versus nothing. Decide before you import a single post.
• Asset URLs: images hosted on uploads-ssl.webflow.com or assets.website-files.com break when you cancel the Webflow plan. Download and re-upload them to the WordPress media library, then find-and-replace the old domain in post content.

Step 3: Build the Redirect Map

Your spreadsheet needs four columns: old path, new path, redirect type, and status. Keep the rule simple: every old URL points to its closest single equivalent, not to the homepage and not to a category archive.

Redirecting dozens of retired pages to the homepage is the most common mistake we see. Google frequently treats those as soft 404s, which means the link equity goes nowhere. If a page genuinely has no successor, redirect to the most relevant parent section instead.

Use 301 (permanent) for anything moving as part of the migration. Reserve 302 for temporary situations only, since a 302 tells crawlers the old URL is still the canonical one. MDN’s reference on the 301 status code spells out the behavioral difference clearly.

Step 4: Decide Where the Redirects Actually Run

You have three places to put the rules, and they perform very differently at volume.

1. Server level (.htaccess on Apache, or an Nginx config block): fastest, because the request never touches PHP or the database. Best for large rule sets and wildcard patterns like moving an entire /post/ directory to /blog/.
2. Hosting control panel or edge rules: many managed hosts, including our own WordPress migration service, let you load a redirect list at the platform layer without editing config files.
3. A WordPress plugin such as Redirection or Rank Math: convenient, supports CSV import of your map, and logs 404s. The tradeoff is that each redirected request boots WordPress first, which adds latency.

A practical hybrid: put your broad pattern rules at the server or edge, and manage one-off exceptions in a plugin where your content team can see them. If you’re running LiteSpeed Cache, purge the cache after any redirect change so stale responses don’t confuse your testing.

Step 5: Deploy the Redirects Before the DNS Cutover

Sequence matters more than speed. The redirect rules must already be live on the WordPress server at the moment DNS records start resolving to it.

• Load the full rule set on staging and test with the staging hostname or a hosts-file override.
• Lower your DNS TTL to 300 seconds roughly 24 to 48 hours before the switch, so propagation is measured in minutes, not days.
• Keep the Webflow site published during cutover. If something breaks, you can point DNS records back.
• Publish a fresh XML sitemap of the new URLs and submit it in Search Console the same day.
• Leave the old Webflow project active for 30 days minimum before cancelling, mostly so you can still reach original assets.

Step 6: Test, Then Monitor for 90 Days

Testing a redirect map by clicking links is how errors survive. Verify programmatically instead.

Run curl -I against every old URL, or feed the list into Screaming Frog in list mode, and confirm each returns a single 301 to a 200. Two things to hunt for: redirect chains (old URL to intermediate to final, which wastes crawl budget) and loops, usually caused by conflicting trailing-slash rules.

After launch, check the Pages report in Search Console weekly for the first month, then biweekly through day 90. Watch your 404 log too, since real users and old backlinks surface paths your inventory missed. Most migrations we handle produce 10 to 40 unmapped URLs in the first fortnight, and each one is a quick fix.

Expect a modest ranking wobble regardless. A clean 1:1 redirect migration typically shows a 5 to 15 percent organic dip that recovers within two to six weeks. If traffic drops 40 percent or more, you have a redirect or indexing problem, not a Google mood swing.

Don’t Forget These Easy Misses

• Webflow’s own old redirects: re-create them on WordPress or you’ll break links that already worked.
• RSS and feed paths: /blog/rss.xml on Webflow versus /feed/ on WordPress.
• Form endpoints and thank-you pages: paid ads often point directly at these.
• www versus non-www and HTTP versus HTTPS: all four variants should resolve to one canonical version with a valid SSL certificate in place from day one.
• Internal links inside content: update them in the database rather than relying on redirects forever.

If you’re also changing hosts later, our walkthrough on moving a WordPress site to a new host covers the DNS and database side in more detail.

Frequently Asked Questions

How long should I keep 301 redirects after migrating from Webflow?

Keep them for at least 12 months, and ideally permanently. Google says a year is the minimum for signals to consolidate, but old backlinks and bookmarks keep sending traffic for years, so there’s no real benefit to deleting working rules.

Can I set up the redirects inside Webflow instead of WordPress?

No, Webflow redirects only apply while Webflow is serving your domain. Once DNS points at your WordPress host, Webflow never sees the request, so every rule has to live on the new server, at the edge, or in a WordPress plugin.

Does Webflow have an export that includes my URLs?

Webflow exports CMS collections as CSV, and each row includes the item slug, which you can combine with the collection prefix to rebuild full paths. Static page URLs are not included in that export, so pull those from your sitemap.xml and Search Console.

How many redirects is too many for a WordPress site?

A few thousand server-level rules add no measurable latency, while 500 or more plugin-managed redirects can add 20 to 80 milliseconds per redirected request. Convert repetitive patterns into a single wildcard rule wherever the old and new paths share a structure.

Should I redirect Webflow subdomain URLs too?

Yes, if yoursite.webflow.io was ever indexed or linked. You can’t redirect that subdomain after cancelling the project, so add a canonical tag and check whether any of those URLs earn impressions in Search Console before you shut it down.

Planning a Webflow to WordPress Move This Year?

Our migration team builds and tests the redirect map with you, deploys it at the server level, and watches your 404 logs through the first 90 days. Start with our managed WordPress hosting plans or compare pricing to see what fits your site’s traffic.