How to Migrate WordPress to Webflow Without Losing SEO

Plenty of businesses want to migrate WordPress to Webflow without losing SEO, and with good reason. Moving platforms is the moment most sites accidentally throw away years of rankings. Usually it isn't Webflow's fault. It's the details: URLs that change without redirects, missing meta data, broken internal links, images that lose their alt text. This guide walks through the process we use at Asctro, step by step, so your new Webflow site keeps the traffic your old WordPress site earned.

If you're still deciding whether to switch at all, read our Webflow vs WordPress comparison first. This article assumes you've decided to move.

Why migrations lose rankings (and how to avoid it)

Search engines rank URLs, not websites. When a URL disappears, every link, ranking signal and bookmark pointing at it goes nowhere unless you tell search engines where the content has moved. Google's own guidance on site moves with URL changes recommends mapping old URLs to new ones and using server-side permanent (301) redirects.

The most common causes of lost traffic after a migration are:

• No redirect map, or an incomplete one
• Blog posts moving from /post-name/ to /blog/post-name/ with no redirects
• Page titles and meta descriptions not carried over
• Thin or merged pages that drop content Google was ranking
• Internal links still pointing at old URLs
• Images re-uploaded without alt text
• The new site launched with search engine indexing still disabled

Every step below is designed to stop one of these.

Step 1: Benchmark before you touch anything

You can't protect what you haven't measured. Before planning the new site, record:

Traffic and rankings

Export the last 12 months of pages and queries from Google Search Console, and landing-page sessions from your analytics. Note which pages bring in the most organic traffic and conversions. These are your protected pages.

Backlinks

Export the pages that have external links pointing at them (Search Console's Links report is a free starting point). Every one of these URLs needs a redirect.

A full crawl

Crawl the live WordPress site with a crawler such as Screaming Frog. Save every URL, status code, title, meta description, H1, canonical and image alt text. This becomes your master spreadsheet.

Step 2: Build your URL map

This is the most important deliverable in the whole migration.

Keep URLs the same where you can

The safest redirect is the one you don't need. Webflow lets you set slugs for static pages and CMS items, so many URLs can stay exactly the same.

Plan for Webflow's CMS structure

Webflow CMS items live under a collection path. For example, blog posts sit under a folder such as /blog/ or /blogs/. WordPress posts often live at the root (/my-post/), so they usually need redirects to the new collection path. Map each one in your spreadsheet.

Decide what to keep, merge or retire

A migration is a good moment to clean up. For each URL, choose:

• Keep: migrate as-is, same or new URL
• Merge: combine thin, overlapping posts into one stronger page, then redirect the old URLs to it
• Retire: remove content that's outdated or gets no traffic or links, then redirect it to the closest relevant page

Don't retire pages that get traffic or have backlinks unless they have a genuinely relevant redirect target.

Remember the WordPress leftovers

WordPress creates URLs you may never have noticed: category and tag archives, author pages, /page/2/ pagination, attachment pages and feed URLs. Decide what happens to each.

Step 3: Design the Webflow site around your content

Build the new structure from what's working, not from a blank template.

• Create CMS collections that match your content types: posts, case studies, services, team, locations.
• Add fields for SEO title, meta description, Open Graph image and alt text so editors can manage them per item.
• Keep heading structure clean: one H1 per page, logical H2s and H3s.
• Plan internal links between related services and articles.

This is where design and SEO meet. A website redesign done alongside a migration should improve how the content is organised, not just how it looks.

Step 4: Migrate the content

Export from WordPress

Export posts and pages to CSV. Several tools and plugins can convert WordPress content into a CSV that matches your Webflow collection fields.

Import into Webflow CMS

Webflow supports CSV import into CMS collections. Map each column to the right field: name, slug, body, SEO title, meta description, featured image, category, author.

Clean the content

WordPress content often carries shortcodes, inline styles, page-builder markup and broken embeds. Check imported rich text carefully, especially:

• Shortcodes rendering as raw text
• Images still loading from the old WordPress /wp-content/ URLs
• Missing image alt text
• Links still pointing at old URLs

Carry over every SEO field

Titles, meta descriptions, canonicals and Open Graph data should come across exactly, or be improved on purpose. Don't let them fall back to defaults.

Step 5: Set up 301 redirects in Webflow

Webflow lets you add 301 redirects in Site settings → Publishing → 301 redirects. You can add rules one at a time, and Webflow supports pattern-based rules for whole folders.

Best practice:

• Redirect old URL → final new URL directly, with no chains (A → B → C)
• Redirect to the most relevant equivalent page, not the homepage
• Include trailing-slash and non-trailing-slash variants if your old site used both
• Test every redirect from your spreadsheet before and after launch

Step 6: Technical SEO checks before launch

Run through this list on the Webflow staging site:

• Indexing: staging should be hidden from search, and indexing must be switched on for the live domain
• Sitemap: Webflow can auto-generate your sitemap. Check that it includes the right pages and excludes utility pages
• Canonical tags: set the global canonical URL in Webflow's SEO settings
• Page speed: compress images, use modern formats such as WebP, and limit heavy third-party scripts
• Schema: carry over any structured data you relied on (such as FAQ or Organization), making sure it matches the visible text
• Forms and tracking: test forms, analytics and conversion tracking
• 404 page: create a helpful custom 404

Google's guidance is that there's no special trick for appearing in AI Overviews or AI Mode. Normal SEO fundamentals apply: crawlability, internal links and clear text content. A clean migration protects both your classic rankings and your chances of being cited in AI answers. Our AEO service builds on that foundation.

Step 7: Launch, then monitor closely

Launch day

• Point DNS to Webflow and confirm SSL is active
• Submit the new sitemap in Google Search Console
• Spot-check your protected pages and their redirects
• Crawl the live site and fix any 404s or redirect chains

The first 4–8 weeks

Some ranking movement is normal while Google processes the change. Track:

• Search Console coverage and the "Not found (404)" report
• Clicks and impressions for your protected pages
• Rankings for your most valuable queries
• Conversions from organic traffic

If a key page drops sharply, check its redirect, content and internal links first. Those are the usual causes.

How long does a WordPress to Webflow migration take?

It depends on content volume and how much redesign is involved. A small site with a few dozen URLs can move within a normal project timeline. Sites with hundreds of posts, complex taxonomies or custom post types need more planning, cleanup and QA. The URL mapping and content cleanup usually take longer than the build itself.

What does it cost?

Migration is usually priced as part of a Webflow build, or as an addition to it. In an October 2026 review of Webflow agency pricing by Octo Agency, one provider estimated migration at 20–40% on top of a comparable new build. Our guide to Webflow website cost in the UK covers budgeting in more detail.

Get migration help from Asctro

Asctro is a London studio founded in 2016 that builds on both Webflow and WordPress, so we know both sides of a migration. Our Webflow development and WordPress development teams handle the build. Our SEO team handles redirect mapping, technical checks and post-launch monitoring.

Planning a move to Webflow?

We'll audit your WordPress site and send you a migration plan, including the URL map. Talk to Asctro.