WordPress to Webflow Migration Checklist (Keep Your Rankings)

To move from WordPress to Webflow without losing rankings, list every old URL first, keep the ones that rank, and set a 301 redirect for every URL that changes. Move titles, descriptions, headings and content with care. Then publish, submit your sitemap and watch Search Console for several weeks. Missed redirects cause most lost rankings.

Key takeaways

• Your URL list is the most important file in the whole move. Build it before anyone designs a thing.
• Webflow imports WordPress content through CSV. WordPress exports XML, so you convert it first, then map fields into a CMS collection.
• Each WordPress plugin does a job. List those jobs, then decide how Webflow will do each one.
• Google says to keep redirects for at least a year, and that rankings on a medium site can take a few weeks or more to settle.

Why do sites lose rankings after a migration?

Most ranking drops come from a few fixable mistakes: old URLs that now show a 404, redirects that all point to the homepage, pages that lost their titles and descriptions, content that got cut or thinned, and internal links that still point to old addresses. A planned move avoids all of these.

Search engines have learned your old URLs over years. Each one carries links, history and trust. When a URL changes with no redirect, that value has nowhere to go. Google sees a dead page and a new page it knows nothing about.

Other common causes:

• Thinner pages. A redesign trims text to look clean, and the words that ranked are gone.
• Lost metadata. SEO titles and descriptions lived in a WordPress plugin and never got moved.
• Staging left open. A test copy of the new site gets indexed and competes with the real one.
• Tracking gaps. Analytics or call tracking is not installed on launch day, so nobody can see what changed.

What should you do before you start the move?

Before any design work, take inventory. Crawl the old site to list every URL. Export your top pages and search queries from Google Search Console. Back up the WordPress files and database. List every plugin and what it does. Note every form, tracking code and outside tool. This list becomes your plan and your test sheet.

Your pre-move checklist:

1. Crawl the site. Use a crawler to list every page, post, category, tag and image URL. Save it as a spreadsheet.
2. Pull Search Console data. Export the pages and queries with clicks over the last 12 months. These pages must keep their content and get exact redirects.
3. Save SEO fields. Export each page's SEO title, meta description and H1. Many SEO plugins can export these.
4. Back up everything. Keep a full copy of the WordPress files and database, even after launch.
5. List plugins. Write down every active plugin and the job it does.
6. List forms and tracking. Every form, where its emails go, plus GA4, Google Ads tags, call tracking and chat.
7. Decide what to keep. Mark each URL keep, merge or remove. Pages with no traffic and no links may not need to move.

If you want a second set of eyes on the plan, our Webflow audit can review it before you start.

How do you map old WordPress URLs to new Webflow URLs?

Put every old URL in one column and its new Webflow URL in the next. Keep URLs the same wherever you can. Where they must change, point each old URL to the closest matching new page, never to the homepage by default. Webflow CMS pages live under a collection path, such as /blog/post-name, so plan for that.

WordPress sites often use URL patterns Webflow does not copy exactly. Here is how common patterns usually map:

Your new site's collection names set the folder in the URL. Choose them before you import, because changing a collection slug later changes every URL inside it.

How do you move WordPress content into the Webflow CMS?

WordPress exports content as XML. Convert that file to CSV, create a collection in Webflow with the fields you need, then import the CSV and map each column to a field. Move images through the Assets panel. Before you import, check your plan's CMS item limit. Webflow's Premium plan holds 20,000 items.

That process comes straight from Webflow's WordPress migration guide. In practice, the work is in the details:

• Plan the fields. Title, slug, body, summary, featured image, author, category, date, SEO title and meta description. Add the SEO fields so the values you exported have a home.
• Keep slugs. Import the old post slug into the slug field so the last part of each URL stays the same.
• Clean the body. WordPress posts often hold shortcodes and page builder code. Those do not work in Webflow, so clean them out or rebuild those parts.
• Fix images. Images in the post body still point to the old WordPress address. Move them, or they will break when the old host shuts down.
• Spot-check. Open 10 or 20 imported posts and compare them with the old ones, line by line.

Check the plan too. As of October 21, 2026, Webflow's pricing page lists Basic with no CMS and Premium with 20,000 CMS items at $25 a month billed yearly. A blog migration needs Premium. Our Webflow CMS development team builds the collections and templates for this step.

How do you replace WordPress plugins in Webflow?

List each plugin's job, then pick how Webflow handles it. Many jobs, like SEO fields, sitemaps, redirects, caching, backups and SSL, are built into Webflow. Others, like booking, reviews or members-only content, need an outside tool or an embed. A few may not have a clean match, and you should know that before you commit.

Member areas need a special note. Webflow shut down its own User Accounts feature on January 29, 2026, and points customers to tools like Outseta and Memberstack. If your WordPress site has a members area, plan that piece early.

Security is one of the biggest reasons owners move. Patchstack found 11,334 new WordPress security flaws in 2025, and 91% were in plugins. Every plugin you retire is one less thing to patch.

How do you set up 301 redirects in Webflow?

In Webflow, go to Site settings, then Publishing, then 301 redirects. Add redirects one by one, or import a CSV with two columns: old path and new path. A new import overwrites every existing redirect, so export first. Any invalid row fails the whole import. Publish the site after importing so the redirects go live.

From Webflow's redirect import guide, the CSV can be up to 16 MB. That fits thousands of rows. Tips that save headaches:

• Use paths, not full addresses, in the old-path column, such as /2024/05/how-to-spot-roof-damage.
• Remove duplicates and loops, where A points to B and B points back to A.
• Avoid chains. Point old URLs straight to the final page.
• Keep the redirect file with your project records. You will need it again.

Google's site move guide recommends permanent redirects like 301s and says to keep them as long as possible, generally at least one year. In practice, leave them in place for good.

What should you check on launch day?

On launch day, connect the domain, publish, then test. Click a sample of old URLs and confirm each redirect lands on the right page. Check that staging indexing is off, the global canonical URL is set, and the sitemap is on. Test every form and phone link. Confirm analytics and call tracking are firing. Then submit the sitemap.

Launch-day checklist:

1. Domain connected and SSL working on both www and non-www versions.
2. All redirects imported, and the site published.
3. Your top 50 old URLs tested by hand. They should land on the right new page.
4. Staging indexing off, under Site settings, SEO, Indexing.
5. Global canonical tag URL set to your main domain, with no trailing slash.
6. Auto-generate sitemap on, and no stray blocks in robots.txt.
7. Each page has one H1 and its old SEO title and description.
8. Every form sends to the right inbox or CRM. Every phone number is tappable.
9. GA4, ad conversion tags and call tracking installed and tested.
10. Internal links updated to the new URLs, not pointing through redirects.
11. Sitemap submitted in Google Search Console and Bing Webmaster Tools.

Google's site move guide also says to update internal links to the new URLs and to submit the new sitemap once redirects are live.

What should you watch in the weeks after launch?

For the first month, check Google Search Console weekly. Look for new 404 errors, pages dropped from the index, and big changes in clicks on your top pages. Fix any missing redirect the day you find it. Google says rankings on a medium-sized site can take a few weeks or more to settle after a move.

What to watch, week by week:

• 404 errors. Every new one is a missing redirect. Add it.
• Top pages. Compare clicks on your top 20 pages with the same weeks before launch.
• Indexing. Check that new URLs are being indexed and old ones are dropping out.
• Leads. Calls and form fills are the real test. Compare them with the month before.

If you also changed your domain name, Google says to submit a Change of Address in Search Console for the old site. If the domain stayed the same, you do not need to.

Keep the old WordPress backup for a while. If something is missing, you can pull it from there instead of rebuilding it from memory.

Should you do the migration yourself or hire help?

A small site with a handful of pages and few blog posts is a fair do-it-yourself project if you follow a checklist. A site with hundreds of posts, many rankings, forms tied to a CRM, or a members area is worth handing to a team that has done it before. The cost of lost rankings can outweigh the project fee.

Our WordPress to Webflow service handles the full move: inventory, URL mapping, CMS import, redirects, launch checks and follow-up in Search Console. We have been building brands and websites since 2010, and every site our team builds today is built in Webflow. After launch, our Webflow maintenance plan and Webflow SEO service keep the site in shape.

Frequently asked questions

Will I lose my Google rankings if I move from WordPress to Webflow?

You should not lose them for good if the move is planned well. Keep the URLs you can, set a 301 redirect for every URL that changes, and move your titles, descriptions and content. Expect some ups and downs for a few weeks while Google catches up. Missed redirects are the most common cause of lasting drops.

Can Webflow import my WordPress blog posts?

Yes. WordPress exports content as an XML file. You convert that to CSV, create a Webflow CMS collection with matching fields, and import the CSV. Then you map each column to a field. Shortcodes and images inside posts need cleanup, so check a sample of posts by hand after the import.

How long should I keep 301 redirects after a migration?

Google recommends keeping redirects for as long as possible, and generally at least one year. In practice, leave them in place for good. Old links on other websites, in emails and in bookmarks keep sending people to your old URLs for years, and the redirects make sure those visitors still land on the right page.

What happens to my WordPress plugins when I move to Webflow?

They do not come with you. List what each plugin does, then decide how Webflow handles that job. Many jobs, like SEO fields, sitemaps, redirects, backups and SSL, are built into Webflow. Others, such as booking, reviews or member logins, need an embedded tool or a third-party app.

Which Webflow plan do I need for a WordPress migration?

If you are moving a blog or many service pages, you need a plan with the CMS. As of October 21, 2026, that is Webflow's Premium site plan at $25 a month billed yearly, with 20,000 CMS items. The Basic plan has no CMS, so it only works for a small site with a few static pages.

The bottom line

A WordPress to Webflow move is safe when you treat it as an SEO project, not just a design project. Build the URL list first, redirect every changed URL to its closest match, carry over your titles and content, and watch Search Console after launch. Do those things and your rankings have a clear path to follow you. To plan your move, Book a free call with Mike, or See every Webflow service.

Sources

• Webflow Help Center: Migrate your site from WordPress to Webflow
• Webflow Help Center: Import/export 301 redirects
• Webflow Help Center: User Accounts sunset
• Webflow: Pricing (checked October 21, 2026)
• Google Search Central: Site moves with URL changes
• Patchstack: State of WordPress Security in 2026

Keep reading

• The Webflow SEO checklist
• Webflow vs WordPress for a service business
• How much does a Webflow website cost in 2026?