WORDPRESS TO WEBFLOW MIGRATION PLANNED AROUND YOUR SEO

Usually not, as long as the redirect map is complete before launch. A short dip can occur while Google replaces the old URLs with the new ones, which is why we monitor Search Console after launch. In our experience, traffic improves within about a week of launch. The redirect map is what keeps rankings in place: every page with rankings or backlinks needs an equivalent page on the new website and a 301 redirect to it. Rankings are lost when old URLs return a 404, when redirects go to the home page instead of the right page, when the new website launches with noindex still switched on, or when the copy is shortened during the move.

That is why we build the redirect map from a crawl, Google Search Console and your backlink profile, so that nothing of value is missed, and test it in a staging environment before the domain is pointed at the new website. The steps we follow are described in the step-by-step guide to migrating without losing rankings.

In our experience, traffic improves within about a week of launch when we have rebuilt a website. A rebuild is more than a move: the pages load faster, the structure is cleaner and the metadata and internal links are put in order, and that shows quickly in Search Console. This assumes that the domain stays the same and the redirect map is complete.

You get the most out of the move if an SEO audit is done before we start. Then we build the improvements into the new structure from the start, instead of fixing them afterwards. The audit in step one of our process is always included and protects what you already have. A full SEO audit is a separate add-on that shows what can be improved.

Google's own guidance is more cautious. Most pages on a small to medium-sized website move in the index within a few weeks, and larger websites take longer. Source: Google Search Central on site moves. While the old URLs are replaced by the new ones in the search results, you may see a short dip in Search Console.

After launch we monitor Search Console and compare the pages that mattered most before the move with how they perform on the new website. If a page has not recovered, we find the cause (a missing redirect, a changed title, thinner copy or a slower page) and fix it. Changing domain at the same time is a separate project and takes longer to settle; the section on how long it takes for the traffic to come back explains why we keep the two separate.

Yes, most of them. Static pages keep their slugs. Blog posts follow Webflow's collection structure: every collection page sits under the collection's URL slug, so a WordPress address such as /2024/05/post-name/ becomes /blog/post-name and gets a 301 redirect; date-based URLs cannot be reproduced. Source: Webflow Help on Collection URLs.

Webflow's redirects are set under Site settings → Publishing → 301 redirects and require a paid Site plan. Wildcard rules with capture groups are supported, for example /2024/(.*)/(.*) → /blog/%2, so a whole year of date-based URLs can be redirected with a single rule. Rules run in the order they were created, so specific rules go in before wildcards, and the list can be imported and exported as CSV. Webflow recommends no more than 1,000 rules; for larger websites we consolidate with wildcards rather than writing one rule per URL. Two more things to know. Redirects do not apply automatically to localised slugs, so a multilingual website needs one set per language. An existing page also has to be unpublished or renamed before a redirect from its address will work. Source: Webflow Help on 301 redirects.

The size of the move and the design option you choose. Four things drive the price: how many pages and posts have to be moved and cleaned, how many URLs change structure, whether you keep the existing design or the website gets a unique one, and which forms, integrations and languages have to be rebuilt. The four price bands in the price section are the same as for every website we build: SEK 25,000–45,000 (about €2,200–4,000) for a landing page or a small website, SEK 50,000–85,000 (about €4,500–7,600), SEK 90,000–135,000 (about €8,000–12,000), and from SEK 140,000 (about €12,500) for large, multilingual builds. A 1:1 move of a smaller marketing website falls in the lower bands. A rebuild with new copy, several languages and integrations falls in the upper ones.

The price is set after a call. Reasonable adjustments that come up along the way are included; larger additions are priced separately before we build them. Webflow's platform fee and any support after launch are not part of the build price. The price section shows how to compare the move with staying on WordPress over three years.

Normally 4–6 weeks from brief to launch, whichever option you choose. With the first option you keep the existing design: we rebuild the layouts as components and migrate the content and metadata, so the website looks the same but runs on Webflow. This is the faster and cheaper option. With the second option the website gets a unique design in the same project. That adds design rounds but saves you a second project later. It is also a good time to improve the forms, the calls to action and the pages buyers land on from search, as described on our website redesign and conversion rate optimisation pages. A straight 1:1 move of a smaller website can be quicker.

What sets the pace is how quickly decisions are made: approving the redirect map in the first week, and deciding what is merged or rewritten. If you need to go live faster, we can do a fast-track launch in 2–3 weeks with a defined scope. If you have a fixed deadline, we launch on that date with a clear plan for version 2.0.

Admin access to WordPress or an export of posts and pages, read access to Google Search Console and your analytics, the plugin list, your brand assets, and one person who can approve the redirect map and the CMS model. That is enough for the audit and a fixed price. You keep publishing in WordPress as usual during the project; anything published after the content export is synced on launch day.

Plugins cannot be moved. What each plugin does is either built into Webflow, replaced by a specialised tool or, where the logic is complex, a reason to consider a different platform. We go through the plugin list in the audit and tell you which of the three applies.

• SEO plugins (Yoast, Rank Math): title tags and meta descriptions are exported and mapped to SEO fields in the CMS; existing schema markup is carried over; redirects stored in the plugin go into the redirect map.
• Forms (Gravity Forms, Contact Form 7): rebuilt as Webflow forms with submissions routed to your email or CRM, e.g. HubSpot or Salesforce. Stored form entries stay in WordPress, so export them before the move.
• Page-builder layouts (Elementor, Divi): the layouts are plugin markup and cannot be imported. The sections are rebuilt as reusable components. This is also where you choose between keeping the existing design and giving the website a unique one.
• Plugins with their own logic (membership, booking, gated content): replaced by a specialised third-party tool, or a sign that a coded website with a headless CMS is the better choice.
• WooCommerce: the shop is rebuilt, not moved. Webflow Commerce is a real option for a smaller shop, and especially for digital products. Its limits are in order logistics, not in what the shopper sees. For a larger shop, or one with demanding order handling, we recommend Shopify.

Content is imported into the Webflow CMS as CSV, one file per collection. WordPress exports are typically already in a compatible structure, which is why a WordPress migration is more predictable than most migrations. Reference fields such as categories and authors are matched by slug, and existing items can be updated by Item ID, so a second import can correct the first without duplicates.

Five limitations affect how we work. The import file may be at most 4 MB, so large blogs are split into batches. Rich text is imported as HTML, and Webflow may strip embeds, so posts with embedded video, tables or scripts are checked by hand. Images imported from a direct URL get no responsive variants, so we upload media into Webflow instead. File fields, such as PDFs and downloads, cannot be imported at all and are re-uploaded manually. And the number of CMS items a website can hold depends on the Webflow Site plan, which we check against your archive in the audit. Source: Webflow Help on CMS import.

They are moved first, not last. Your tag manager, analytics and consent banner are installed on the new website before the staging test, and every form is tested with a real submission so that the conversion events in your analytics and in Google Ads work on launch day. Campaign landing pages keep their URLs where the structure allows, so paid traffic does not go through a redirect; where a URL has to change, the final URLs in Google Ads are updated on launch day. If you run campaigns through us, our Google Ads agency team makes that update as part of the launch.

Each language becomes a locale in Webflow Localize, which is a paid add-on on top of the Site plan: at the time of writing, Localize Essential is USD 9 a month per locale and Localize Advanced, which is the tier that supports localised URLs, USD 29 a month per locale; the Team plan includes Localize. Source: Webflow pricing. The redirect map is built per language, because Webflow's redirects do not apply to localised slugs automatically, and hreflang is set at launch. For Learnifier we run four languages in one Webflow CMS, so this is a setup we already work with every day.

When a larger shop is the core of the business, when logged-in flows or complex logic are central, or when the archive is very large with many categories and relations. Webflow is often the right choice for a marketing website that a marketing team will own and publish on. A smaller shop, or one that sells digital products, can run on Webflow Commerce. A larger shop with demanding order logistics is better served by Shopify. Member areas, bookings, gated content or tens of thousands of posts with complex relations often point towards a coded website with a headless CMS in Next.js or Astro. It handles that logic well and is often cheaper to build than a Webflow website of the same scope. That option is described on our headless CMS agency page. Sometimes the right recommendation is to stay on WordPress and clean up: fewer plugins, better hosting, a tidier theme. The cases where staying makes sense are described in the section on when to stay on WordPress. The choice is yours. We give a recommendation once we have heard more about your needs.

At the time of writing (checked November 2026), Webflow's Site plans are USD 15 a month for Basic, which has no CMS, and USD 25 a month for Premium with the Webflow CMS included, both billed annually and paid directly to Webflow. Team, a platform plan for organisations that want Localize, publishing workflows and governance, is USD 2,500 a month on an annual contract, and Enterprise is priced on request. Source: Webflow pricing. Most marketing websites we migrate run on the plan that includes the CMS. WordPress has no licence fee for the software itself, but the running cost is spread across hosting, premium licences for plugins and the theme, and the hours someone spends on updates, testing and security every month, a cost that is rarely counted. Compare the two over three years before you decide; the section on Webflow vs WordPress for SEO explains where the maintenance difference shows up.

Ask us, and any other agency you talk to, five questions. Ask to see the redirect map from a previous migration. Ask where redirects and index settings are tested before launch. Ask who owns the Webflow project after launch and who pays Webflow. Ask what happens to the redirects already stored in Yoast or Rank Math. And ask how the weeks after launch are monitored, and what the agency does if a page has not recovered. The answers tell you whether the migration is treated as an SEO project or as a copy-and-paste job. With us you talk directly to the people doing the work, and the full checklist is in the section on what to demand from an agency that handles the migration.