What is a WordPress to Webflow migration?
A WordPress to Webflow migration is moving your website's pages, posts, media and SEO settings from WordPress into Webflow, then redirecting every old URL to the new one with a 301. The goal is simple: same content, same or better rankings, far less upkeep.
It is not a copy and paste job. WordPress stores content in a database and renders it through a theme. Webflow stores pages visually and long-form content in CMS collections. So we rebuild the design in Webflow, then import the content into collections that match how your team actually publishes.
Most teams move because of maintenance. Plugin updates, hosting issues and security warnings eat time. Webflow removes that layer, and editors can change pages without calling a developer.
Step one: the URL inventory
Every migration starts with a list of every URL your site has, not only the ones in the menu. Missing a URL is the most common reason traffic drops after a move.
We build the list from four sources and merge them:
- A full crawl of the live site
- Your XML sitemaps, including post, page, category and tag sitemaps
- Landing pages from Google Analytics for the last 12 months
- Indexed pages and top pages from Google Search Console
WordPress creates many URLs you may not know about: /?p=123 short links, /category/ and /tag/ archives, /author/ pages, /page/2/ pagination, attachment pages and files in /wp-content/uploads/. Each one gets a decision: keep, redirect or retire.
Building the 301 redirect map
A 301 redirect tells browsers and search engines that a page has moved for good. Google passes the old page's signals to the new one, which is why the redirect map matters more than anything else in a migration.
Our rules for the map:
- Redirect to the closest match, never to the home page by default
- One hop only. No chains like A to B to C
- Use pattern rules for repeated shapes, like dated post URLs, and single rules for everything else
- Retire thin archives on purpose, and redirect them to the parent page
Webflow has a built-in 301 redirect manager in site settings, and it supports pattern rules with wildcards. We load the map there, then test every row against the staging and live site before we call it done.
Moving content into the Webflow CMS
Pages that rarely change, like home, pricing and about, are rebuilt as static Webflow pages. Anything that grows, like blog posts, case studies, team members or jobs, becomes a CMS collection.
We export posts from WordPress, clean the HTML and import them into Webflow with matching fields: title, slug, date, author, category, summary, cover image and body. Page builder markup and shortcodes are cleaned out along the way, so your rich text stays tidy.
Slugs are kept the same wherever the URL structure allows. When they cannot be, the redirect map covers the gap. Internal links inside posts are rewritten to the new URLs, so readers and crawlers never bounce through a redirect.
SEO parity: titles, metas, canonicals and schema
SEO parity means the new site sends search engines at least the same signals as the old one. Plugins like Yoast or Rank Math held a lot of this, so we export it page by page before anything moves.
- Titles and meta descriptions are carried over exactly, then improved only where you agree
- Canonical tags point to the new Webflow URLs
- Open Graph titles and images are set for every page and CMS template
- Schema such as Organization, Article, FAQPage and BreadcrumbList is added with custom code, using CMS fields on templates
- Headings keep the same H1 and structure on pages that rank
We also keep noindex settings where you had them, so thin pages do not suddenly enter the index.
Images, media, forms and integrations
Images are moved into Webflow and served from its CDN, so nothing still loads from the old WordPress server after you cancel it. We compress them, set sizes and fill in missing alt text. PDFs and downloads get new homes and redirects from their old /wp-content/uploads/ paths when they have links or traffic.
Forms are rebuilt as Webflow forms. They can send email notifications, or feed HubSpot, Mailchimp, a Google Sheet or your CRM through a native integration, Zapier or a webhook. We test every form end to end before launch.
Tracking comes across too: Google Analytics 4, Tag Manager, ad pixels and cookie consent. We check that events still fire, so your reports do not show a fake drop the day after launch.
Launch day: DNS step by step
Launch day is calm when the work is done before it. Here is how we run it:
- A day before, we lower the TTL on your DNS records so the switch spreads quickly.
- We publish the final Webflow site to the staging domain and run the checklist one last time.
- On a call with you, we add your custom domain in Webflow and update the A and CNAME records at your DNS provider to the values Webflow shows.
- We leave MX and other email records alone. Email keeps working.
- Once SSL is issued, we publish to the live domain and test redirects, forms and tracking.
- We submit the new sitemap in Google Search Console.
We keep the old WordPress host running for a few weeks. If anything needs checking, the old site is still there.
After launch: Search Console and what can go wrong
We watch Google Search Console daily for the first two weeks, then weekly until our 30 days of support end. We look at the Pages report for new 404s and excluded pages, the Performance report for clicks and positions on your top pages, and use URL Inspection on key pages to confirm Google sees the new version.
The things that usually go wrong, and how we prevent them:
- Missed URLs. Four-source inventory, so nothing ranking is left out.
- Redirect chains. Every rule points straight to the final URL.
- Lost metadata. Exported before the move and checked after it.
- Broken images in posts. Media re-hosted and links rewritten on import.
- Tracking gaps. Events tested on staging and on the live site.
- Email outage. MX records are never touched.
A small wobble in rankings for a week or two can happen with any move. Steady signals and clean redirects are what bring them back.







