- Traffic lost in a WordPress to Webflow migration almost always comes from broken URLs and missing redirects, not from Webflow.
- Map every WordPress URL that gets traffic, links or impressions to its new Webflow URL before you build a single template.
- Build the Webflow CMS around how your team publishes today instead of copying WordPress categories, plugins and page builders 1:1.
- Most full migrations take 8 weeks to 4 months, depending on content volume, integrations and how much of the design changes.
- We moved Amigos Ingleses' 280+ blog posts from WordPress to Webflow with no rankings lost and +48% conversion on its course platforms in the first months.
Can you migrate from WordPress to Webflow without losing SEO?
Yes. Rankings drop when URLs break, metadata goes missing or ranking content changes during the move. Webflow itself is not the risk. The process is.
When we look at a migration that lost traffic, the cause is usually one of three things: old URLs that return 404 errors, blog posts that lost their titles and meta descriptions, or redirect chains that send Google through three hops before it reaches the new page. All three are preventable before launch.
From our projects: Amigos Ingleses ran on WordPress for 13 years, and organic search was its main source of leads. We moved 20+ pages and 280+ blog posts to Webflow without losing a single ranking. The site now gets 350K+ views a month, and conversion on its course platforms grew 48% in the first months after launch. Read the case study.
What made it work was treating SEO as the core foundation, not just a launch-week task. If you are still deciding whether to move at all, start with our Webflow vs WordPress comparison. This guide is about how to move.
What should you do before moving anything?
Build a URL map. It's the single most important document in a migration, and it should exist before anyone designs a template.
- Export every URL. Combine a full crawl of the WordPress site, the XML sitemap and the pages report from Google Search Console. Include posts, pages, category and tag archives, author pages and PDFs.
- Add performance data. Next to each URL, note clicks, impressions and backlinks from the last 12 months. This tells you which pages you cannot afford to lose.
- Decide what happens to each URL. Keep it, merge it into another page, redirect it, or retire it. Pages with traffic or links always keep a new home.
- Record the SEO data. Save each page's title tag, meta description, H1, canonical and any structured data, so nothing is rewritten by accident.
Expect blog URLs to change. Webflow places CMS items inside a collection folder, so a WordPress post at “/my-article” or “/2021/05/my-article” becomes “/blog/my-article”. That's fine, as long as every old URL redirects to its new one.
Our tip: Most WordPress sites have hundreds of thin tag and author archive pages that get no traffic. A migration is the right moment to retire them. Redirect them to the main blog or the closest category instead of rebuilding them.
How should you structure the Webflow CMS for WordPress content?
Structure it around how your team publishes now, not around how WordPress stored things. A WordPress site that has run for years usually carries post types, plugins and page-builder layouts nobody uses anymore.
Here is how the main WordPress pieces usually map to Webflow:
Check your Webflow plan's CMS item limit before you import. Posts, categories, tags and authors all count as items.
On Amigos Ingleses, the CMS was half the job. The old site ran on WordPress, Teachable and ThriveCart patched together, so every integration had to be reconnected for checkout to keep working. We also built ready-to-publish templates, and the team now launches campaigns and courses up to 3x faster.
How do you move WordPress content into Webflow?
Export your posts to a CSV file and import them into the Webflow CMS. For very large sites, or content that updates often, push it through the Webflow CMS API instead.
Before the import, clean the content. This step decides how much manual fixing you do afterward:
- Remove shortcodes and page-builder markup. They show up as raw code inside Webflow rich text.
- Strip inline styles. Let Webflow's typography styles do the formatting.
- Keep the original publish dates. Map them to a date field so posts keep their age and order.
- Move images with their alt text. Image URLs will change, so keep the alt text in your export to avoid losing image search visibility.
- Rebuild key pages by hand. The homepage, service pages and top landing pages usually need a real redesign, not an import.
Import a test batch of 10 to 20 posts first. Check the formatting, links and images, fix the export, then run the full import.
How do you set up redirects and SEO settings in Webflow?
Add a 301 redirect for every URL whose address changes, and bind the SEO fields of every CMS template before launch.
- Import redirects in bulk. In Webflow, go to Site settings → Publishing → 301 redirects, and import a CSV with two columns: old path and new path. A new import replaces all existing redirects, so export the current list first and add to it. Webflow's article covers the format.
- Avoid redirect chains. If WordPress already redirects page A to page B, send A straight to the final Webflow URL.
- Update internal links. Links inside old post bodies still point to WordPress URLs. Redirects catch them, but updating them avoids wasted hops.
- Keep titles that rank. For pages with strong rankings, carry over the existing title tag and meta description. Rewrite them later, one page at a time, and measure.
- Re-add structured data. Article, FAQ and Organization schema from WordPress plugins do not move. Add them back through custom code on the relevant templates.
Webflow generates the sitemap and canonical tags automatically, so check them on staging rather than building them by hand.
What should you check on launch day and after?
Test the redirects before the domain switches, then watch Search Console every week for at least a month.
Before launch:
- Run your full redirect list against the staging site and fix every 404 or chain.
- Crawl staging to confirm titles, meta descriptions, H1s and canonicals match the URL map.
- Launch on a low-traffic day and keep a full WordPress backup.
After launch:
- Submit the new sitemap in Google Search Console.
- Check the indexing report and 404 errors daily for the first week.
- Compare impressions and clicks on your top 20 pages week by week.
A short dip while Google recrawls the site is normal. A page that keeps losing impressions after a few weeks usually has a missing redirect or changed content, and that is where to look first.
How long does a WordPress to Webflow migration take?
Our full migrations start at 8 weeks, and most take 3 to 4 months. A small site with a short blog can move faster. A large site with hundreds of posts and several integrations takes longer.
Three things drive the timeline:
- Content volume. 50 posts and 300 posts need very different amounts of cleanup and QA.
- Integrations. Checkout, CRM, course platforms and gated content all need to be reconnected and tested.
- Design scope. A straight move is faster than a redesign, but most teams combine both so they rebuild only once.
What is the safest way to make the move?
Plan SEO first, rebuild the CMS for your team, and launch only when every URL with value has a tested home. If you follow that order, a WordPress to Webflow migration can grow traffic instead of risking it.
If organic search drives a real share of your leads, or you have more than a few dozen posts and several integrations, work with a team that has done it before. Our Transform service covers the full move, from the URL map to the redesign and launch, with content and SEO equity preserved.
