By Mehdi HassanHow do you do a WordPress to Webflow migration without losing rankings?
You do a WordPress to Webflow migration without losing rankings by treating URLs as the main risk. Keep every slug identical where Webflow allows it, redirect every URL that must change with a single permanent redirect, and carry over titles, descriptions and structured data before launch.
Design and build get most of the attention in a migration, but they rarely cost traffic. Broken or missing redirects do. WordPress lets you shape permalinks almost any way you like, and Webflow has a more fixed structure, so the gap between the two is where rankings leak. If you haven't chosen Webflow yet, our guide to where to move when you migrate from WordPress compares the options first.
Why is URL mapping the main risk?
URL mapping is the main risk because every WordPress URL that changes in Webflow loses its rankings and backlinks unless it redirects correctly. Search engines treat a new URL as a new page until a permanent redirect tells them otherwise.
Three WordPress patterns cause most problems: posts at the root of the domain, category prefixes in post URLs and date-based paths. Webflow places CMS items under their collection's path, so a post at /my-post on WordPress becomes something like /blog/my-post on Webflow. That's fine, as long as the redirect exists and works.
WordPress URL pattern | Can Webflow match it? | What to do |
|---|---|---|
/blog/post-name/ | Yes, with a collection slug of blog | Keep it identical; check trailing-slash behavior |
/post-name/ (root) | Not for CMS items | Redirect to /blog/post-name |
/2024/05/post-name/ | No | Pattern redirect to /blog/post-name |
/category/news/post-name/ | No for posts | Redirect posts; recreate category pages under /category/ |
/category/news/ | Yes, with a categories collection slug of category | Keep it identical |
/services/design/ (static page) | Yes, with folders | Recreate the folder structure |
/wp-content/uploads/file.pdf | No | Re-upload and redirect high-value files |
How do you keep WordPress slugs identical in Webflow?
Keep WordPress slugs identical in Webflow by matching collection URL slugs to your existing paths and importing each item's slug exactly as WordPress had it. Every URL you keep the same is a redirect you don't need and a risk you don't take.
- Name collection slugs to match. If posts live at /blog/ on WordPress, set the Webflow blog collection slug to blog. If you have /resources/ or /case-studies/, do the same.
- Import the slug field, don't regenerate it. Webflow creates slugs from names by default. Map the WordPress slug column to the Webflow slug field so nothing changes.
- Rebuild static pages in folders. Webflow folders let you recreate nested static paths like /solutions/fintech.
- Keep taxonomy paths where it helps. A categories collection with the slug category reproduces /category/name archives, which matters if those pages rank or earn links.
How do you redirect category and date URLs?
Redirect category and date URLs with Webflow's 301 redirect settings, using pattern rules for predictable structures and one-to-one rules for everything else. Patterns save time on large blogs; one-to-one rules handle merged and renamed pages.
Export every old URL
Combine your WordPress sitemap, a full crawl and a Search Console export so you catch posts, pages, archives, attachments and old URLs with backlinks.
Group URLs by pattern
Sort them into posts, pages, categories, tags, authors, date archives and files. Each group gets a rule.
Write pattern redirects
Webflow's redirect settings support capture groups, so a rule can send /2024/05/post-name to /blog/post-name. Check Webflow's current documentation on 301 redirects for the exact syntax.
Add one-to-one redirects
Merged, renamed or retired pages get individual rules pointing to the most relevant live page, never the homepage by default.
Avoid chains
If an old URL already redirects on WordPress, point it straight to the final Webflow URL. Export your redirect plugin's rules so none are lost.
Test before and after launch
Test the full list against staging if possible, then again on the live domain right after the switch.
Tag and author archives rarely rank well. Many teams redirect them to the closest category or the blog index instead of rebuilding them. Decide per archive using traffic and backlink data.
What content do you move, and how?
Move pages by rebuilding them in the Webflow designer, and move posts and other structured content by importing them into CMS collections. The import route matters for SEO because it decides whether rich text, images and metadata arrive intact.
Export WordPress content first; our guide to exporting a WordPress site's content covers XML, the REST API and plugins. Webflow's CSV import is the standard path for posts, and our research found that CSV import turns images inside rich text into placeholders, so inline images usually need re-uploading or an API-based import. The full flow for posts, authors and categories is in how to migrate a WordPress blog to Webflow CMS.
Custom post types, ACF fields and translated content
Custom post types map to their own Webflow collections, and Advanced Custom Fields map to collection fields. Plan the field types before importing: plain text, rich text, image, reference, multi-reference, option and switch fields each behave differently.
Relationships, such as a case study linked to an industry and a service, need reference fields, and those references must be imported after the target items exist. That's why a careful import runs in order: categories and authors first, then posts.
Translated sites built with WPML or Polylang add another layer, because locale URLs and hreflang need mapping too. Read moving WPML or Polylang sites before you set up Webflow localization.
What SEO data do you need to carry over?
Carry over titles, meta descriptions, canonical URLs, open graph images, structured data, alt text and internal links. Most of this lives in a WordPress SEO plugin, not in the post content, so it won't come across unless you export it.
- Titles and descriptions: export them from your SEO plugin and map them to Webflow's SEO fields for static pages and collection templates.
- Structured data: recreate Article, Organization or FAQ schema with custom code on templates, filling values from CMS fields. Schema.org documents each type.
- Internal links: update links inside post bodies to the new URLs instead of relying on redirects for your own links.
- Images: carry alt text across and re-host images inside Webflow.
- Sitemap and robots: check the new sitemap and submit it in Search Console after launch.
If you're restructuring content into pillar pages at the same time, plan it with our guide to topic clusters on a marketing site. And if you'll replace plugins like forms and popups, list them first with WordPress plugins to replace.
What should you check after launch?
After launch, check that every old URL redirects once to the right page, that Search Console shows no new wave of 404s, that forms reach your CRM and that rankings for your top pages hold. Check daily for the first week, then weekly.
- Run the full old URL list through a redirect checker on the live domain.
- Submit the new sitemap and watch coverage and page indexing reports in Search Console.
- Submit every form and confirm the lead arrives where it should.
- Compare organic traffic and rankings for your top pages against the weeks before launch.
- Check analytics and conversion tracking fire on the new templates.
If WordPress was only one part of your problem, compare destinations again before you commit: WordPress to Framer suits page-led sites, and WordPress to Next.js suits sites with product logic. For budgeting, see WordPress to Webflow migration cost.
