WordPress to Webflow Migration: A Checklist to Keep Your SEO
A WordPress to Webflow migration keeps its SEO when nothing search engines rely on goes missing. Every old URL gets a 301 redirect to its new equivalent. Every page keeps its title, meta description and structured data. The new site is tested on staging before the domain switches. According to Google’s guide to site moves with URL changes, 301 redirects don’t cause a loss in PageRank, but rankings will move up and down for a while as Google recrawls. This checklist is for the person hiring the team: what to check and ask at each step.
What moves on its own and what doesn’t
Webflow’s own integration page says the platform has no built-in way to pull existing content from a WordPress site. A free Marketplace app, WP to Webflow (built by Eclipse SRL), reads a live public WordPress URL and builds the CMS Collection structure for you. It needs a Premium plan (from $25/mo) or higher. It is useful, but its scope is narrow.
| Element | Moved by the WP to Webflow app | What needs planning |
|---|---|---|
| Blog posts | Yes | Check formatting and internal links |
| Featured images | Yes | Review alt text and file size |
| Tags and categories | Yes | Confirm their URLs in the redirect map |
| Static pages | No | Rebuilt in Webflow |
| Custom fields (ACF, Pods, Meta Box) and custom post types | No | Mapped to CMS Collection fields |
| SEO titles and meta descriptions | Not in its listed scope | Carried over page by page |
| Plugin functions and site design | No | Rebuilt or replaced |
| WooCommerce data | No | Planned as a separate project |
The gap sits where rankings live: titles, descriptions, URLs and page structure. Ask your migration partner about that work first.
The checklist in ten steps
- Record a baseline and agree on goals.
- Decide what changes, and in what order.
- Sort every piece of content into pages or CMS Collections.
- Choose a Webflow plan that supports redirects and the CMS.
- Build a full redirect map.
- Rebuild the SEO layer page by page.
- Test everything on staging.
- Check accessibility before launch.
- Launch, then watch Search Console.
- Train the team to run the site.
1. Record a baseline and agree on goals
Webflow’s WordPress to Webflow migration checklist starts with KPIs, goals and success criteria, plus a functionality audit of every content type, plugin, theme customization and integration. Ask for that audit in writing. Export your current traffic and top pages from Search Console too, so you can compare after launch.
2. Decide what changes, and in what order
Google advises changing one thing at a time. Its example: if you are moving domain, changing CMS and changing layout, do them one after another. Many owners want a redesign with the move. That works when it is planned on purpose. Keep URLs where you can, and agree up front which pages will change structure and why.
3. Sort every piece of content
Each piece of content is either a static page or an item in a CMS Collection. WordPress taxonomies move over as Collections too. Webflow’s checklist names WP All Export as a popular export tool and recommends one CSV file per post type. Plan a second CMS import close to the switchover to catch posts edited after the first export.
4. Choose a plan that supports the move
Webflow site plans as listed on its pricing page in October 2026 (USD, per site, taxes added at checkout):
| Plan | Price | CMS | 301 redirects |
|---|---|---|---|
| Starter | Free | 50 CMS items | Not included |
| Basic | $15/mo, billed yearly | No CMS | Included |
| Premium | $25/mo, billed yearly | 20,000 CMS items | Included |
A WordPress site with a blog needs the CMS, which rules out Basic. The free plan has no redirects, which rules out a live migration. The pricing page has no line item for migration, so budget the migration work separately.
5. Build a full redirect map
List every URL that changes and point each one to its closest new page. Google warns against sending many old URLs to one unrelated page such as the homepage: it can confuse users and might be treated as a soft 404. Include images and downloads such as PDFs. Keep the redirects for as long as possible, generally at least one year.
6. Rebuild the SEO layer page by page
Each page needs its title, meta description, alt text and Open Graph data (the preview shown when a link is shared) restored. Every new URL should carry a self-referencing canonical tag. Turn on Webflow’s autogenerated sitemap unless you use a custom one. Then update internal links so they point to new URLs directly instead of through redirects. Webflow’s plans include schema markup support (code that tells engines what a page is about) and controls for robots.txt and llms.txt. A professional uses them to make the site readable for AI engines (ChatGPT, Perplexity, Gemini) as well as Google: structured data, AI crawlers allowed, and text machines can read without JavaScript.
7. Test everything on staging
Test on Webflow’s staging link or a subdomain, with version control so you can roll back. Check text formatting, page functions, image rendering, links, SEO elements and structured data. The integration page notes that Webflow staging sites are capped at 50 CMS items on every plan, so a larger blog may need a separate test project.
8. Check accessibility before launch
Webflow’s checklist includes making sure the site works with screen readers and for users with visual or motor impairments. At Pixerry we build every project accessible from the start, so clients don’t pay later to rebuild for compliance. Our accessibility statement for Grand Bains, Martin Belaysoud group, shows this in practice.
9. Launch, then watch Search Console
Add the custom domain and verify ownership, publish from staging to production, then point the DNS from WordPress to Webflow. Submit the new sitemap. Use Search Console’s Index Status and Sitemaps reports. Google counts a move complete only once Googlebot has visited every old and new URL at least once. For medium-sized sites, it can take a few weeks or more before Google shows the new URLs, and longer for large sites.
10. Train the team to run the site
The last step on Webflow’s checklist is training, and it matters more than it looks. A website is not a project you launch and forget: it is a growth system your team runs every week. In Webflow, your team edits pages visually, without waiting for a developer. We compare the two platforms for small teams in WordPress vs Webflow for Small Business and B2B Websites.
What a rebuild without ranking loss looks like in practice
Pixerry has redesigned and rebuilt established websites while keeping their search visibility. One project, our SEO-powered, UX-driven website rebuild, was not a WordPress migration. It raised the same challenge: rebuilding and restructuring a site without losing the rankings built up over years.
“[Olga’s] technical skills enabled the quick implementation of a functional solution and, above all, her SEO expertise ensured a smooth transition with no disruptions and a fast indexing of the new URLs.”
Guillaume Dardenne, Digital Project Lead, Grandbains (Martin Belaysoud group). Translated from French. Read the case
We have also delivered a complex, multi-location site for a well-known brand with more than 70 stores across France. Sites like that carry hundreds of location pages, and each one is a URL to map, test and keep indexed. A migration partner earns their fee in the redirect map, the SEO layer and the weeks of monitoring after launch, far more than in the export itself.
Our Design & Development service covers the full move, from audit to team training. Before you start, you can see how your current WordPress site looks to search and AI engines with our free site check.
