Blog

How to move from WordPress to Webflow and protect organic traffic

Map your URLs, test a CMS collection and check the pages that bring in leads before committing to a migration budget.

Before you price the move, identify the WordPress pages that already bring you customers. Decide where each will live in Webflow, what information it needs to retain and how you will test the contact journey. That inventory captures work a quote for “twenty pages” can easily miss.

Which URLs are worth keeping?

Combine the current sitemap, the pages earning clicks in Search Console and the landing pages generating enquiries in your analytics. Add destinations used in ads, sales emails and downloadable brochures. A low-traffic specification sheet may be the link your best distributor sends buyers every week.

Imagine you sell industrial filtration systems. Your food-processing page earns enquiries because buyers can check materials and capacities before requesting a sample. Keeping its address and its specifications table may be the most valuable decision in the redesign. If you move it to an industry page, check that buyers can still answer those questions there.

Make a URL map an agency can test

Use six columns: current URL, destination, action, content to retain, acceptance test and owner. Three rows illustrate different decisions:

  • Keep. The filtration page keeps its address. Start at that URL on mobile, read the capacity table and submit a sample request.
  • Move. An article moves from /2022/cleaning-filters/ to /guides/cleaning-filters/. The old URL should permanently redirect straight to the new article. Update the links inside the site as well.
  • Retire. A discontinued unit has no replacement. If customers still need its manual, keep a support page. If the content goes away, remove obsolete links and record the expected response, such as a 404.

Webflow supports permanent 301 redirects and CSV imports. Google recommends mapping changed addresses to relevant destinations and advises that visibility can fluctuate during a move. Webflow redirect documentation · Google’s site migration guide

Migrate one collection before estimating the rest

Pick three real entries: a typical item, one with a table or download and one with categories or an author. Request a sample import into Webflow CMS. Check images, alternative text, internal links and the fields marketing will edit. Record which fields import cleanly and which need manual work. Webflow documents the WordPress migration process and CSV imports for collections. Moving from WordPress to Webflow

Give the imported item to its future editor. Can they change a capacity, replace the PDF and publish a translation with the intended permissions? If each edit requires a designer, the estimate still needs to cover that work.

What to check at launch and in the following weeks

Save baseline clicks and enquiries for your important pages. At launch, open the old addresses and verify the final destination, canonical URL and indexing settings. Submit a mobile enquiry and have sales confirm the right product arrived. Name an owner for broken routes and another for failed enquiries.

Compare results by page and query over the following weeks. If clicks are steady but enquiries drop, try the form first. If one product family loses visibility, check its template, redirects and incoming links. Looking at the whole domain alone can hide both problems.

When requesting a Webflow estimate from MANUBRIO, send your domain, three commercial URLs and an example your team finds difficult to update. That gives us a complete journey to review. Discuss a Webflow project

← Back to the blog

Start a project

Let's build
what's next.

Tell us about your business and what you want to achieve. We'll recommend the right stack and a clear plan, no strings attached.