WordPress to Webflow SEO Migration: How to Keep Your Rankings

A WordPress to Webflow SEO migration is mostly about one promise: every page Google already knows about must still lead somewhere useful on launch day. Rankings rarely drop because of the platform. They drop because URLs changed without redirects, titles were lost or pages quietly disappeared. This guide is the SEO deep dive that sits beside our WordPress to Webflow migration guide.

Work through it in order. The early steps feel like admin, but they are where rankings are protected.

Why rankings drop in a WordPress to Webflow SEO migration

Search engines rank individual URLs. When a URL stops working, the ranking attached to it has nowhere to go. The usual causes are:

• Old URLs returning a 404 page because no redirect was set.
• Redirects pointing everything to the home page instead of the matching page.
• Page titles, meta descriptions and headings rewritten during the move.
• Content trimmed or merged without a plan.
• The staging site being indexed alongside the real one.

Every one of these is preventable.

Step 1: Build a complete URL inventory

Gather every URL that matters before you change anything. Do not rely on a single source, because each one misses something.

• Your XML sitemap from WordPress, usually generated by Yoast or Rank Math.
• Google Search Console, the Pages report and the Performance report, for URLs Google indexes and shows.
• Your analytics landing pages for the last year, so seasonal pages are not missed.
• A backlink report for URLs other sites link to, including old ones you forgot.
• A site crawl to catch pages that are linked internally but missing from the sitemap.

Put them in one spreadsheet with columns for the old URL, monthly clicks, backlinks, the decision (keep, merge or retire) and the new URL.

Step 2: Understand Webflow's URL structure

Static pages in Webflow can live at almost any path you choose, including inside folders. CMS items work differently. Every item in a collection sits under that collection's path, so a blog post becomes something like /blog/post-slug. You set the collection path in the collection settings, and you cannot place CMS items at the root of the site.

That matters because many WordPress sites put posts at the root, under dates or under category folders. Those patterns will change. WordPress also creates pages that may not exist in Webflow at all: tag archives, author archives, date archives, attachment pages and paginated lists.

Here is how typical addresses map across.

Step 3: Set up 301 redirects in Webflow

Webflow has a redirect manager in the site settings, under the publishing section. Each rule has an old path and a new destination, and it returns a permanent 301 redirect once the site is published.

One to one where it counts

For pages with traffic or backlinks, write a single rule per URL pointing to the closest matching page. Never send everything to the home page. Search engines treat that like a missing page.

Pattern rules for whole groups

Webflow also supports pattern redirects with capture groups. In plain terms, a rule can match a whole family of old URLs, such as every dated post address, capture the slug part, and insert it into the new path. This saves writing hundreds of rules when your slugs stay the same. The exact syntax has changed over time, so check Webflow's current redirect documentation before writing patterns, and test each pattern against several real old URLs.

Things to test

• Old URLs with and without a trailing slash.
• No redirect chains, where one redirect leads to another.
• No rule that accidentally captures a live page.
• Your top fifty URLs by traffic, clicked one by one.

Step 4: Titles, meta and Open Graph

Every static page in Webflow has its own SEO settings for the title tag and meta description, plus Open Graph settings for the title, description and image shown when the page is shared. Copy these from your SEO plugin for every page that already ranks.

For CMS content, you set the SEO settings once on the collection template and fill them from fields. That is why the SEO title and meta description belong in the CMS import as their own fields. If the import is still ahead of you, see importing WordPress posts into the Webflow CMS.

Step 5: Canonicals, alt text and headings

Webflow lets you set a global canonical URL in the SEO settings, which tells search engines which version of your domain is the real one. Check what per-page canonical options your plan offers if you need them for specific pages. Also make sure the staging subdomain is not indexed, using the setting Webflow provides for that.

Carry over image alt text, both on static images and on CMS image fields. Keep the heading structure of ranking pages: one h1, then logical h2 and h3 sections. A redesign is a common moment for headings to be swapped for styled paragraphs without anyone noticing.

Step 6: Sitemap and robots

Webflow can generate your XML sitemap automatically and update it whenever you publish. Pages you exclude from search are left out. You can also edit the robots.txt file in the SEO settings. Before launch, check that robots.txt does not block the whole site, which is a surprisingly common leftover from development.

Step 7: Schema through custom code

WordPress SEO plugins often add structured data automatically. In Webflow, you add it yourself as JSON-LD in the custom code area of a page or template. On the blog template, the code can pull values like the title, date and image from CMS fields. Typical types are Organization on the home page, Article on posts and FAQPage where a page has real questions and answers. Validate everything with Google's Rich Results Test.

Step 8: Search Console on launch day

1. Confirm the domain property is verified, which carries over if the domain stays the same.
2. Submit the new Webflow sitemap.
3. Inspect your most important URLs and request indexing.
4. Spot check a handful of old URLs to confirm they redirect.

Step 9: Monitor for a few weeks

Check the Pages report in Search Console every day for the first two weeks, looking for new 404 errors and redirect problems. Compare clicks and impressions on your top pages against the weeks before launch. Small movement is normal while Google recrawls. A clear drop on one page usually points to a missing redirect or a lost title, which is quick to fix once found.

Getting help

If you want a second pair of eyes, an SEO audit before launch catches redirect gaps and indexing problems early. A basic SEO setup covers titles, meta, sitemap and Search Console on the new site. Or let our WordPress to Webflow migration service handle the URL inventory and redirects as part of the whole move. Still deciding whether to move at all? Read the pros and cons of switching.

Frequently asked questions

Will my rankings drop after moving to Webflow?

Some movement in the first few weeks is normal. With full redirects and the same content and titles, rankings usually settle back where they were.

Can I keep my exact WordPress URLs?

Static pages, yes. Blog posts usually gain a collection folder such as /blog, because Webflow places CMS items under their collection path, so those need redirects.

How many redirects can Webflow handle?

Limits can change, so check Webflow's current documentation. Pattern redirects keep the number of rules small when your slugs stay the same.

Does Webflow add schema automatically?

Not in the way SEO plugins do. You add JSON-LD through custom code, and CMS templates can fill it from collection fields.

How long should I keep the redirects?

Keep them for good. They cost nothing to leave in place and protect backlinks pointing at old addresses.