How to Migrate Your Site from Webflow to WordPress — Without Losing Rankings or Traffic

1. Why Businesses Move from Webflow to WordPress

Webflow is genuinely impressive software. Its visual editor, responsive design tools, and CMS have won over thousands of designers who wanted more control than Squarespace without the complexity of a developer workflow. For early-stage startups and design studios, it makes a lot of sense.

But Webflow has ceilings — and when you hit them, they hurt. Here is why businesses consistently make the move to WordPress.

Cost Scaling Is Brutal

Webflow’s pricing model is built around a per-site, per-CMS-item structure. A small brochure site is affordable. Add a blog with hundreds of posts, a team of content contributors, advanced CMS collections, and e-commerce functionality, and you can quickly find yourself paying $500–$1,000+ per month. WordPress hosting with equivalent functionality typically costs a fraction of that.

Plugin Ecosystem: No Contest

WordPress has over 60,000 plugins in its official repository alone. Need a specific membership gate? Done. A complex affiliate tracking system? Done. A multilingual setup with hreflang management? Done. Webflow’s integrations are limited by design — the platform controls what integrates and what doesn’t, and if your use case isn’t covered, you’re often stuck with workarounds.

Content Team Limitations

Non-technical content editors often struggle with Webflow’s CMS interface. It is designed with developers and designers in mind, not marketing managers who need to publish quickly. WordPress’s block editor (Gutenberg) or classic editor are far more familiar to most content teams, reducing training time and friction in everyday publishing workflows.

SEO Tooling

Webflow has improved its native SEO features significantly, but it still falls short of what you get with a well-configured WordPress site running a full SEO plugin like Rank Math or Yoast. Schema markup customisation, redirect management, breadcrumb control, canonical tag handling, and advanced sitemap configuration are all far more flexible on WordPress. For sites investing heavily in technical SEO and organic growth, this matters enormously.

Developer Freedom

WordPress is open source. You can modify anything, host it anywhere, integrate with any API, build custom post types, and extend functionality without waiting for a platform update or paying for a higher tier. That freedom is worth a lot for teams building complex, custom digital experiences.

2. Before You Start: Pre-Migration Checklist

The biggest migration mistakes happen in the first hour — specifically, when someone opens WordPress, starts clicking around, and begins “just trying things.” A migration is a surgical operation. You prepare before you cut.

Run through every item in this checklist before you touch a single file.

Audit Your Existing Webflow Site

Use Screaming Frog or a similar crawler to map every URL currently on your Webflow site. Export the list as a spreadsheet. This becomes your master redirect map and your post-migration QA checklist. Record:

• All page URLs (including paginated pages if applicable)
• Current page titles and meta descriptions
• Canonical tags in use
• Which pages have custom Open Graph metadata
• Pages with structured data/schema markup
• All image alt attributes
• Current H1 tags on each page

Back Up Your Google Search Console Data

Export your top-performing pages by clicks and impressions from Google Search Console for the past 12 months. This baseline tells you which pages matter most for organic traffic and should receive extra attention during migration. If traffic drops post-migration, this data lets you pinpoint exactly which pages lost traction.

Benchmark Core Web Vitals

Run PageSpeed Insights on your top 10 pages and record the LCP, FID/INP, and CLS scores. You want to beat these benchmarks with your WordPress build, not fall below them. Understanding your Core Web Vitals baseline before the migration gives you a clear performance target to hit.

Inventory All Third-Party Integrations

List every third-party tool connected to your Webflow site — analytics, CRM, chatbots, form handlers, heatmap tools, payment processors, email marketing platforms. Every single one needs to be reconnected in WordPress. Missing one can mean broken lead capture forms, missing analytics data, or disconnected customer journeys.

Check Your Webflow CMS Collections

If you use Webflow’s CMS (for blog posts, team members, case studies, etc.), catalogue every collection, every field within it, and the total number of items. This tells you how much content you need to export and how to structure the equivalent in WordPress (custom post types, custom fields, taxonomies).

3. Choosing the Right WordPress Hosting for a Post-Migration Site

One of the most consequential decisions you will make in this entire process is where to host your WordPress site. Webflow handles hosting as part of its service, so many teams have never had to think about this. Now you do.

Bad hosting will undo even the most careful migration. Slow response times hurt your Core Web Vitals. Unreliable uptime creates crawl gaps that damage rankings. Poor security leads to malware injections that get your site penalised. This is not a place to cut corners.

Managed WordPress Hosting

Managed WordPress hosts (WP Engine, Kinsta, Flywheel, Cloudways) handle server configuration, automatic updates, daily backups, and performance optimisation for you. They cost more than shared hosting but are worth every penny for a site with existing traffic and SEO value. Kinsta and WP Engine both run on Google Cloud Platform infrastructure, which means excellent global latency.

What to Look For

• PHP 8.2+ — Modern PHP versions are significantly faster. Avoid hosts still defaulting to PHP 7.x.
• Server-side caching — Full-page cache at the server level dramatically reduces TTFB (Time to First Byte).
• CDN included — A bundled CDN ensures assets are delivered from a node close to your visitor.
• Staging environments — You need a staging site to build and test your migration before going live.
• Daily automated backups — Non-negotiable. You must be able to roll back if something goes wrong at launch.
• Free SSL — Ensure HTTPS is enabled and working before launch. A migration that accidentally drops SSL will cause an instant ranking penalty.

For most migrating sites, Kinsta or WP Engine is the right choice. If budget is a concern, Cloudways on a DigitalOcean or Vultr instance delivers strong performance at a lower price point. Avoid generic shared hosting — the performance difference is stark and directly impacts your SEO outcomes.

4. Exporting Your Content from Webflow

Content migration is often where projects get stuck. Webflow’s export capabilities are more limited than most people expect, and understanding exactly what you can and cannot export automatically will save you hours of confusion.

What Webflow Lets You Export

• Static HTML/CSS/JS — Webflow allows you to export your site’s code as a ZIP file. This gives you the HTML structure of each page, which you can reference when rebuilding in WordPress.
• CMS Collection Items (CSV) — Any CMS collection can be exported as a CSV file. This includes your blog posts, products, team members, and any other custom collections. Each row represents one item; each column is a field.
• Images — Images must be downloaded manually or scraped. Webflow’s CDN URLs are not permanent once you cancel your Webflow plan, so download all images before you switch off your Webflow subscription.

What You Cannot Export Automatically

• Webflow interactions and animations (these need to be rebuilt using JavaScript or animation plugins in WordPress)
• Webflow’s native form submissions and form data
• Membership site data if using Webflow Memberships
• E-commerce order history

Step-by-Step: Exporting CMS Content

1. Open Webflow Designer → CMS Navigate to your Webflow dashboard, open the project, and go to the CMS panel in the left sidebar.
2. Select a Collection Click on the collection you want to export (e.g., “Blog Posts”). You’ll see a list of all items in the collection.
3. Click “Export Items (CSV)” In the top-right of the collection view, you’ll find the export button. Download the CSV file and save it.
4. Repeat for all collections Export every CMS collection that contains content you need to migrate. If you have a blog, case studies, team members, and testimonials as separate collections, export all four.
5. Download all images separately Use the Webflow exported HTML to identify all image URLs, then download them. You can use tools like HTTrack or a custom download script to batch-download images.

Static Pages Without CMS

For pages built directly in the Webflow Designer without a CMS template (your homepage, about page, services pages, etc.), export the site as HTML/CSS and use those files as your reference when manually recreating or importing these pages into WordPress. There is no automated import for these — they will need to be rebuilt.

5. Setting Up Your WordPress Environment

Your WordPress site should be built and tested in a staging environment before it ever touches your live domain. This is non-negotiable. Building on a staging URL means your Webflow site stays live and indexed the whole time, protecting your rankings during the build.

Install WordPress on Staging

Most managed hosts provide one-click WordPress installation. Set this up on a staging subdomain (e.g., staging.yourdomain.com) or a temporary URL provided by your host. Never build your migration on the live domain.

Configure Permalink Structure First

This is critically important: set your permalink structure in WordPress before importing any content. Go to Settings → Permalinks and choose a structure that matches your Webflow URLs as closely as possible.

If your Webflow blog posts used the URL pattern /blog/post-title, set your WordPress permalink to /blog/%postname%/. If you import 200 posts and then change the permalink structure, every URL changes and you have a redirect nightmare on your hands.

Essential Plugins to Install Before Content Import

Choose Your Theme Carefully

The theme you choose sets the foundation for your site’s performance. Avoid bloated multipurpose themes that load dozens of scripts regardless of whether you use those features. Instead, choose a lightweight base theme:

• Astra — Extremely fast, highly compatible with page builders, excellent out-of-the-box performance scores.
• GeneratePress — Minimal codebase, fantastic for developers who want full control.
• Kadence — A strong middle ground between design flexibility and performance.
• Hello Elementor — Minimal theme designed to be used with Elementor, if you prefer that page builder.

If you want a design experience closest to Webflow’s visual builder, Bricks Builder or Oxygen Builder give you component-level control over every element without a bloated theme. These are developer-friendly tools that produce clean, semantic HTML output.

For more details on optimising your WordPress setup from a technical SEO perspective, see our guide on WordPress technical SEO best practices.

6. Migrating Pages, Posts, and Media to WordPress

With your WordPress environment set up, permalink structure configured, and essential plugins installed, you are ready to begin the actual content migration. Work in a deliberate sequence: structure first, content second, media third.

Importing Blog Posts and CMS Content

If you exported your Webflow CMS collections as CSV files, you can import them into WordPress using WP All Import Pro. This plugin gives you a visual drag-and-drop interface to map your Webflow CSV columns to WordPress fields.

1. Install and activate WP All Import Pro Purchase and install the plugin. The free version handles basic imports but lacks the field-mapping flexibility you need for Webflow CSVs.
2. Upload your CSV Go to All Import → New Import → Upload a file. Select the CSV exported from Webflow.
3. Select the import type Choose Posts, Pages, or Custom Post Type depending on where you want the content to land.
4. Map your fields Drag your CSV column names (Title, Body, Slug, Publish Date, Featured Image URL, SEO Title, Meta Description) to the appropriate WordPress fields.
5. Run the import Click Run Import. For large datasets, this may take several minutes. Check for errors in the import log.
6. Review imported content Spot-check 10–20 randomly selected posts to verify formatting, images, and metadata imported correctly.

Migrating Static Pages

Static pages (homepage, about, services, contact, landing pages) cannot be bulk-imported from a CSV because their structure varies. These need to be rebuilt manually in your WordPress page builder. Use the full-page screenshots you took from Webflow as your design reference.

Work through pages in order of importance: homepage first, then high-traffic landing pages, then secondary pages. Do not launch until every indexed page has a WordPress equivalent.

Migrating Images and Media

This is the most time-consuming part of the migration, and skipping it properly is the most common cause of broken post-migration sites. Images hosted on Webflow’s CDN will stop working once you cancel your Webflow plan.

Your approach depends on volume:

• Under 50 images: Download manually and upload to WordPress Media Library one by one.
• 50–500 images: Use the Auto Upload Images plugin. It scans your imported content for image URLs and automatically downloads them into your WordPress Media Library.
• 500+ images: Use a script to batch download images from Webflow’s CDN URLs (you’ll find these in your exported HTML or CSV), then use WP CLI to bulk upload them to WordPress.

7. Preserving SEO: Redirects, Metadata, and Schema

This section is the heart of the entire migration. Get this wrong and you will spend the next six months recovering traffic you lost unnecessarily. Get it right and your rankings will transfer with minimal disruption.

The Redirect Map: Your Most Important Spreadsheet

Remember that spreadsheet of all your Webflow URLs you created in Section 2? Now it becomes your redirect map. For every Webflow URL, you need a corresponding WordPress URL. Create a three-column spreadsheet:

• Column A: Old Webflow URL (e.g., /blog/how-to-design-a-landing-page)
• Column B: New WordPress URL (ideally identical to Column A)
• Column C: Redirect status (301, same URL, or not yet live)

If you kept your URL structure identical between Webflow and WordPress — which you should have done by matching your permalink settings — many rows will be identical in Column A and B. But check every single one. Even slight differences (trailing slash, case sensitivity, www vs non-www) can cause missed redirects.

Implementing 301 Redirects in WordPress

Use Rank Math’s redirect manager (Rank Math → Redirections) or the standalone Redirection plugin to implement your redirect map. Both allow CSV import, which means you can paste your entire redirect map and import it in one action.

Important rules for redirects:

• Always use 301 (Permanent) redirects, never 302 (Temporary). Google does not fully pass ranking signals through 302s.
• Avoid redirect chains. If Page A redirects to Page B which redirects to Page C, fix it so Page A redirects directly to Page C.
• Do not redirect everything to your homepage. That is a signal to Google that those pages no longer exist — you lose all their individual ranking value.
• Include redirects for both the www and non-www versions of URLs.

Migrating Meta Titles and Descriptions

If you mapped SEO title and meta description fields in WP All Import Pro, these should already be populated in your posts. Verify them by going to a post and checking the Rank Math or Yoast SEO panel at the bottom of the editor.

For static pages rebuilt manually, you will need to re-enter meta titles and descriptions manually in the SEO plugin panel for each page.

Schema Markup

Any structured data you had in Webflow needs to be recreated in WordPress. Rank Math handles most common schema types automatically: Article, FAQ, How-To, BreadcrumbList, and more. Review each page type and ensure the correct schema type is assigned.

Canonical Tags

WordPress SEO plugins (Rank Math, Yoast) automatically add canonical tags to all pages, pointing to themselves by default. Check that no canonicals are pointing to Webflow URLs post-migration — this is rare but can happen if you have manually set canonical URLs in your Webflow metadata fields and they carried over in the CSV import.

XML Sitemap

Generate a fresh XML sitemap in WordPress (Rank Math does this automatically) and submit it to Google Search Console immediately after launch. Do not leave the old Webflow sitemap in Google Search Console — remove it or let it 404, and replace it with the new WordPress sitemap URL.

Understanding how to handle indexing and crawling after a major site migration is one of the most important factors in recovering your organic visibility quickly.

8. Rebuilding Your Design in WordPress

Webflow’s greatest strength is its design tooling. Recreating that level of visual polish in WordPress requires the right builder and a methodical approach. The good news: modern WordPress builders are far more capable than they were even two years ago.

Choosing a Page Builder

Your choice of page builder will define your design workflow for the foreseeable future. Here is a comparison of the most popular options:

For designers transitioning from Webflow, Bricks Builder offers the most familiar experience: component-based design, CSS class management, and direct control over spacing, typography, and layout on a visual canvas. Oxygen Builder is even more powerful but has a steeper learning curve.

Global Design System Setup

Before designing a single page, set up your global design tokens in WordPress. In Bricks or Elementor, this means defining:

• Colour palette: Brand primaries, secondaries, neutrals, semantic colours
• Typography scale: H1–H6 sizes, body font, line heights, font families
• Spacing system: Base spacing unit and scale
• Global CSS variables: For consistent spacing and colour usage across all templates

Setting these globally means you change them once and they update everywhere — exactly how Webflow’s global styles work.

Building Templates vs. Building Pages

One of the most valuable concepts to understand when rebuilding in WordPress is the template hierarchy. Rather than building every post individually, you create a single blog post template that all posts inherit. All case studies inherit from a case study template. This is how WordPress is designed to work, and leveraging it will save you enormous amounts of time.

Recreating Webflow Animations

Webflow’s interactions engine is one of its most celebrated features. Scroll-triggered animations, hover effects, and multi-step interactions that are effortless in Webflow require JavaScript in WordPress. Options include:

• Motion.page or AOS (Animate On Scroll) — For scroll-triggered entrance animations
• GSAP (GreenSock) — For complex, precise animations (requires custom development)
• CSS transitions — For hover effects and simple transitions directly in your theme’s CSS

Be pragmatic here. Not every Webflow animation needs to be recreated in WordPress. Many animations are decorative rather than functional. Rebuild the ones that reinforce your brand experience; skip the ones that were added because they looked good in Webflow’s preview.

9. Optimising WordPress Performance After Migration

Performance is where many Webflow-to-WordPress migrations fall down. Webflow’s managed infrastructure handles performance automatically. WordPress does not. If you install a heavy theme, 30 plugins, and unoptimised images without addressing performance, you will go live with a site that is slower than what you left.

Here is how to ensure your WordPress site is as fast or faster than your Webflow site at launch.

Caching

Install a caching plugin as a priority. For sites on managed hosts like Kinsta or WP Engine, the host provides server-level full-page caching — do not install an additional caching plugin on top of these or you will create conflicts. For other hosts, WP Rocket is the industry standard for WordPress caching: it handles page cache, browser cache, database cleanup, lazy loading, and CSS/JS minification in one plugin. See our in-depth comparison of the best caching plugins for Core Web Vitals.

Image Optimisation

Images are the single largest contributor to page weight on most sites. Set up an image optimisation workflow:

• Use WebP format for all images where possible (most modern browsers support it)
• Set maximum upload dimensions in WordPress (Settings → Media) to prevent full-resolution originals being served
• Install ShortPixel, Imagify, or Smush to automatically compress images on upload
• Add lazy loading to all images below the fold (WordPress 5.5+ does this natively)

Minify CSS and JavaScript

Use WP Rocket or Asset CleanUp to minify and combine CSS and JavaScript files. Reduce the number of HTTP requests by deferring non-critical JavaScript. Remove scripts loaded globally that are only needed on specific pages.

Database Optimisation

After importing a large amount of content, your WordPress database may contain post revisions, orphaned metadata, and transients that slow query performance. Run a database clean-up before launch using WP-Optimize or directly via phpMyAdmin. Learn more about cleaning up your WordPress database for SEO purposes.

Hosting and Server Configuration

Confirm your hosting is running PHP 8.2 or higher, has OPcache enabled (PHP bytecode caching), and uses HTTP/2 or HTTP/3. These server-level configurations can halve your TTFB without any changes to your site’s code.

Core Web Vitals Benchmarks to Target

10. DNS Cutover: Going Live Without Downtime

The DNS cutover is the moment your domain stops pointing to Webflow and starts pointing to WordPress. If you do this well, your visitors notice nothing. If you do it poorly, you can have hours of downtime, mixed content errors, and confused crawlers seeing both versions of your site.

Pre-Cutover Checks

Before touching your DNS, complete this checklist without exception:

• Every page from your Webflow URL list has a corresponding WordPress page or redirect
• All images load correctly on the WordPress staging site
• All forms work and submit correctly
• SSL certificate is installed and working on your new host
• Google Analytics and Search Console tracking codes are installed
• Your XML sitemap is accessible at /sitemap.xml
• Robots.txt is correctly configured (not blocking Google)
• The staging site is either password-protected or has a noindex meta tag to prevent premature indexing
• Full backup of the WordPress staging site is complete

Lowering DNS TTL in Advance

Before your planned cutover date, log into your domain registrar and lower your DNS TTL (Time to Live) to 300 seconds (5 minutes). Do this 24–48 hours before you plan to cut over. This means that when you change your DNS records, the change propagates globally in 5 minutes rather than up to 48 hours.

Executing the Cutover

1. Update your WordPress site URL settings In WordPress Settings → General, update both the WordPress Address and Site Address from your staging URL to your live domain.
2. Update the A record (or CNAME) In your domain registrar, update the A record for your domain to point to your new WordPress host’s IP address. If using Cloudflare, update the proxied A record.
3. Verify SSL is active Within minutes of DNS propagating, visit your domain and confirm the padlock shows in the browser. If there is a certificate error, check your host’s SSL settings.
4. Check for mixed content Look for any HTTP (non-secure) references in your pages using a browser console or tools like Why No Padlock. Webflow CDN URLs that are still referenced in your content can trigger mixed content warnings.
5. Remove the noindex from WordPress Go to WordPress Settings → Reading and uncheck “Discourage search engines from indexing this site.” This is the most commonly forgotten step — leaving it checked means Google will not index your new site.
6. Submit your sitemap in Search Console Add your new WordPress sitemap URL in Google Search Console under Sitemaps.

11. Post-Migration SEO Audit: The 90-Day Monitoring Plan

The migration does not end when you go live. It ends when you have 90 days of stable or improving organic traffic data and Google has fully recrawled and reindexed your new site. Until that point, you are in a monitoring window that requires active attention.

Week 1: Technical Checks

• Crawl your entire live WordPress site with Screaming Frog. Export all URLs and compare against your Webflow URL list. Every Webflow URL should either exist as-is in WordPress or have a 301 redirect in place.
• Check Google Search Console → Coverage for 404 errors. Any 404s that appear within the first week are likely pages you missed in your redirect map.
• Verify your XML sitemap in Search Console is submitted and showing no errors.
• Run PageSpeed Insights on your 5 most important pages. Compare scores to your pre-migration benchmarks.
• Test all forms, checkout flows, and conversion points manually.

Week 2–4: Crawl and Index Monitoring

• Monitor Google Search Console daily. Watch for spikes in 404 errors, drops in indexed pages, or crawl errors.
• Use the URL Inspection tool in Search Console to check how Google is rendering key pages. Look for content loading issues or blocked resources.
• Request indexing for your most important pages using the URL Inspection tool.
• Check your robots.txt (yourdomain.com/robots.txt) is not accidentally blocking any important directories.

Month 2–3: Traffic and Ranking Recovery

In months two and three, you should see organic traffic stabilising and beginning to recover. It is normal for there to be a short-term dip immediately post-migration as Google recrawls and reassesses your site. This typically lasts 2–6 weeks. If the dip extends beyond 8 weeks or you see major ranking losses on key pages, investigate immediately.

Common causes of prolonged post-migration ranking drops include:

• Missing or incorrect redirects causing 404 errors that Google logged
• Canonical tags pointing to wrong URLs
• Significantly slower Core Web Vitals on the new WordPress site
• Robots.txt or noindex meta tags blocking sections of the site
• Thin or reformatted content that no longer matches the original’s depth

If you experience an unexpected traffic drop post-migration, treat it as a diagnostic project. Our resource on diagnosing traffic drops and algorithm penalties covers the systematic approach to identifying whether you’re dealing with a migration issue, a technical problem, or an algorithm update.

Post-Migration Quick Reference Checklist

12. Common Webflow-to-WordPress Migration Mistakes to Avoid

Having helped numerous sites through platform migrations, certain mistakes come up again and again. Each of the following has cost at least one website months of ranking recovery. Avoid every single one.

Mistake 1: Redirecting Everything to the Homepage

This is the most catastrophic redirect error you can make. When you point all your old URLs to the homepage, Google treats it as if every individual page disappeared — they all lose their individual ranking equity. Redirects must be page-to-equivalent-page. There are no shortcuts here.

Mistake 2: Launching Before the Site Is Fully Built

The pressure to “just get it live” leads teams to launch with incomplete pages, placeholder content, or missing sections. Google will crawl your site within days of launch. What it finds in those first crawls forms the initial impression it uses to assess your content quality. Launch only when every page is complete.

Mistake 3: Forgetting to Remove the Staging Noindex

The most embarrassing and unfortunately common mistake. WordPress has a checkbox in Settings → Reading that discourages search engine indexing. It is enabled by default on many hosts to prevent staging sites from being indexed. If you forget to uncheck it after launch, Google will quietly ignore your entire site. Check it immediately after go-live.

Mistake 4: Cancelling Webflow Before Verifying the Migration

Keep your Webflow plan active for at least 30 days after your WordPress site goes live. This keeps your Webflow site accessible as a reference, and more importantly, keeps all your Webflow CDN-hosted images accessible while you verify every image has been migrated to WordPress. Cancelling early breaks image URLs you may not have caught yet.

Mistake 5: Ignoring Page Speed

Moving from a managed platform to WordPress and neglecting performance is extremely common. A WordPress site running a heavy theme, multiple page builders, 40 plugins, and no caching can easily score 20–40 on PageSpeed Insights. That is not just bad for user experience — it directly impacts your rankings in competitive SERPs. Performance is not optional post-migration.

Mistake 6: Not Monitoring Search Console Immediately After Launch

Most migration problems surface within the first 2 weeks. If you are not watching Search Console daily during this period, you may miss a wave of 404 errors that Google is logging — and by the time you notice a ranking drop weeks later, the crawl damage is already done.

Mistake 7: Changing URL Structure Unnecessarily

Some teams use a migration as an opportunity to “clean up” their URL structure, changing /blog/post-title to /articles/post-title across hundreds of pages. Every URL change requires a redirect, and every redirect introduces a small amount of link equity loss. Change URLs only when there is a compelling structural or SEO reason to do so. Never change URLs just for aesthetics.

Mistake 8: Not Testing Across Devices and Browsers

Your rebuilt WordPress site needs to be tested on iOS Safari, Chrome on Android, Firefox, and Edge — not just Chrome on a desktop. Mobile overflow issues, font loading problems, and layout shifts are common on specific browsers and can crater your mobile Core Web Vitals scores. Test on real devices, not just browser dev tools.