Webflow Agency

WordPress to Webflow: How to Migrate Without Losing Rankings

The short answer

Rankings survive a migration if every old URL 301-redirects to its match. Google states plainly that "301 and other permanent redirects don't cause a loss in PageRank", and advises keeping those redirects for at least a year. Expect a few weeks of movement while Googlebot re-crawls, because the move is only complete once it has visited every URL on both the old and new site at least once.

What Google says
Does a 301 lose ranking powerNo loss in PageRank
How long to keep redirectsAt least 1 year
How long the move takesA few weeks for most pages on a small to medium site
What to expect meanwhileTemporary fluctuation, settling over time

Most migration guides are a list of steps for moving content. Content is the easy part. Webflow will import your posts.

What actually decides whether traffic survives is the redirect map, and whether Webflow does what you assume it does when you build one. It has four specific behaviours that will quietly break a migration, and all four are documented by Webflow itself in a page most people skim.

This covers those, plus what Google says to expect, plus what to check once it is live.

The rankings question, answered by Google

Start here because it removes the main fear.

Google's guidance on site moves with URL changes says that "301 and other permanent redirects don't cause a loss in PageRank." It recommends HTTP permanent redirects "if possible, such as 301 and 308."

So a correctly redirected URL keeps its ranking power. Migration does not inherently cost you anything. Losing rankings in a migration is not a tax on moving platform, it is a redirect map with holes in it.

Two further points from the same guidance.

Keep the redirects "for as long as possible, generally at least 1 year." Many teams tear them out after a few months because the new site is settled. The old links in other people's articles are not.

And the move is finished only when "Googlebot will have to visit every URL on your old and new site at least once." That is why it takes time rather than effect on publish day.

The redirect map is the migration

Everything else is a redesign. The map is the part that carries your traffic across.

Build it before you build the site, as a two-column list of every indexed URL on the old site and its destination on the new one. Pull the old URLs from your existing sitemap, from Search Console's Pages report, and from your server logs if you have them. A sitemap alone will miss URLs that still earn traffic but dropped out of it.

Every old URL needs one of three outcomes: a direct match, a sensible parent, or a deliberate 410 if the content is genuinely gone and not coming back. What it must not have is no row.

Webflow supports bulk import and export of redirects via CSV, so the map can live in a spreadsheet and be loaded in one go rather than typed in one at a time.

Four Webflow behaviours that break migrations

All four come from Webflow's own documentation.

Redirects need a paid plan. Webflow is explicit: "To add 301 redirects, your site needs a paid Site plan, or it must be part of a Workspace with a paid Workspace plan." If you are testing a migration on a free staging site, your redirects are not being tested. Plan for this before launch day rather than discovering it during it.

A redirect will not fire while the old path still exists. This is the one that catches people. Webflow says that to redirect an existing static page "you'll need to delete or save the page as a draft, or change its slug before setting the redirect." The same applies to CMS Collection items, which must be archived, deleted, unpublished, drafted or re-slugged first.

So a redirect rule pointing at a live page does nothing at all, silently, and the rule sits in your settings looking correct. If a redirect is not working, check whether the source page still exists before you check anything else.

Why your redirect does nothingthe rule looks correct and still never fires301 rule added in settingsDoes the old page still existon the Webflow site?yesnothe rule is ignored,silentlythe redirect worksDelete the page, draft it, or change its slug first.Same for CMS Collection items.

Localised URLs need their own rules. "301 redirects are relative to your root domain and won't apply to localized slugs or subdirectories." If you want both /old-url and /es/old-url to land on /new-url, that is two rules, not one. Multilingual sites should expect their redirect count to multiply by the number of locales.

Redirects have a weight cost. This is the one nobody mentions. Webflow recommends "1,000 maximum as best practice", and explains why: "Each redirect rule is uploaded to a site's manifest.json file, which provides site information to visitors' browsers. As the manifest file grows, there's more data for browsers to download."

There is no hard cap. But every rule you add is shipped to every visitor's browser. A redirect map is not a free, invisible lookup table on this platform.

Which is why wildcards matter more here than elsewhere

Webflow's own advice is to "use wildcard redirects where possible, which minimizes the total number of redirect rules."

A capture group (.*) in the old path, and %1 in the destination, collapses a whole folder into one rule.

Old path:         /blog/(.*)
Redirect to path: /articles/%1

Multiple groups work too, so /blogs/(.*)/(.*) can map to /articles/%1/%2.

One rule, or one rule per postevery rule ships to every visitor in manifest.jsonwritten one at a timehundreds of ruleswith a capture group/blog/(.*) to /articles/%1one ruleWebflow recommends a maximum of 1,000 rules.There is no hard cap, but the file is downloaded.

For a WordPress site this is usually the difference between a workable map and an unworkable one. A dated permalink structure like /2019/07/post-name is hundreds of rules written one at a time, or one rule written with a capture group.

One convenience worth knowing: if you change a page's slug in Page settings and tick "Permanently redirect the old URL to this new one", Webflow writes the 301 for you.

What to expect after you publish

Google's guidance is that on a small to medium site "it can take a few weeks for most pages to move", with larger sites taking longer. During that window expect "temporary fluctuation in site ranking", settling over time.

Which means the week-two panic is not evidence of a failed migration. Judge it at six to eight weeks, not six to eight days.

One practical note: your old sitemap will start throwing redirect warnings in Search Console. Google says these can be ignored.

What migrated sites actually land without

We audited 53 verified Webflow sites earlier this month and ran the same technical checks across every homepage. The platform handles its own defaults well. Three things it leaves to you were missed repeatedly.

CheckSites passing
Width and height on every image1 of 53
Exactly one H143 of 53
Any structured data40 of 53

Image dimensions were present on only 19% of the 4,771 images we counted, which is a direct Cumulative Layout Shift risk. If you are rebuilding every template anyway, this is the cheapest moment in the project to set those as a build rule. The full method and findings are in our audit of 53 Webflow sites.

If you are coming from Wix rather than WordPress

The redirect rules above are identical, because they are Webflow's behaviour rather than WordPress's.

The difference is on the way out. WordPress gives you database access, an export file and plugins that will generate a full URL list for you. Wix gives you considerably less, so budget more time for building the URL inventory by crawling the live site rather than exporting it.

The destination work does not change at all.

We handle both on Webflow development projects, and the redirect map is the first thing we build, not the last.

The bottom line

A 301 does not cost you ranking power. Google says so directly. What costs you is an old URL with no row in the map.

Build the map first, from the sitemap, Search Console and your logs together. Use wildcards wherever a folder maps cleanly, because on Webflow every rule is shipped to every visitor in manifest.json. Remember that a redirect does nothing while its source page still exists, that localised URLs need their own rules, and that none of it works at all without a paid plan.

Then wait properly. A few weeks, not a few days.

Every figure and quotation here comes from Google Search Central, Webflow's own redirect documentation, or our own audit of 53 Webflow sites.

What next

Let’s get you started!

Tell us what your brand has to hold together. We will show you which of the three surfaces to build first.

Start

Takes 4 minutes