How to migrate to Webflow without losing SEO: a technical checklist

A migration doesn't lose rankings on its own. What loses them is URLs left without redirects, metadata that disappears and content that gets dropped along the way. This guide is the technical checklist we use in our Webflow migrations, including the WordPress-specific details that usually get missed.

If you're still deciding whether to migrate, what it costs or how long it takes, start with our guide on WordPress to Webflow migration: timeline, cost and process. This article is for when the decision is made.

‍

1. Before touching anything: the URL inventory

Everything else depends on this step. You need a spreadsheet with every URL that exists today and how valuable each one is. Pull it from three sources, because none is complete on its own:

• A full crawl with Screaming Frog (or similar): every indexable URL with its title, meta description, H1 and canonical.
• Google Search Console → Pages, last 12–16 months: URLs with clicks and impressions. This is where old URLs show up that are no longer linked but still get traffic.
• Backlinks (Ahrefs, Semrush or Search Console's Links report): URLs with external links. Losing them means losing authority.

Add one column with the new URL and another with the action: keep, redirect or remove (410). That sheet is your redirect map.

‍

2. What changes when moving from WordPress to Webflow

This is where most migrations break. WordPress and Webflow structure URLs differently:

• Posts need a prefix. In WordPress a post can live at /post-name/. In Webflow, every CMS item lives under its collection slug: /blog/post-name. Every post needs its redirect.
• Trailing slash. WordPress usually uses /page/ and Webflow /page. Google treats them as different URLs. Check that trailing-slash URLs redirect correctly.
• Date or category permalinks (/2023/05/post/, /category/post/): these can be redirected in bulk with patterns instead of one by one.
• Category, tag, author and pagination archives (/category/, /tag/, /author/, /page/2/): decide whether to recreate them in Webflow or redirect them to the closest page. Don't leave them as 404s.
• Images. /wp-content/uploads/ URLs disappear. If you get Google Images traffic, expect those positions to drop and recover with the new URLs.
• Feeds and technical URLs (/feed/, ?p=123): redirect the feed if newsletters or aggregators used it.

‍

3. Setting up 301 redirects in Webflow

Redirects are created in Site settings → Publishing → 301 redirects. They work in two ways:

• One by one: old path → new path. For static pages and posts with traffic.
• With patterns: Webflow supports capture groups. For example, /2023/(.*) → /blog/%1 redirects every post from that year while keeping the slug.

Three rules that prevent problems:

• No chains. If a URL was already redirecting in WordPress, point the redirect straight to the final destination, not to the intermediate URL.
• Redirect to the equivalent page, not the homepage. Google treats mass redirects to the homepage as soft 404s.
• Redirects are set up before publishing, not the day after.

‍

4. Metadata, content and structure

• Titles and meta descriptions: in the Webflow CMS, create them as collection fields and bind them in the template's SEO settings. Import the ones that already worked instead of rewriting them all.
• H1 and content: if a page ranks, don't rewrite it completely during the migration. Improve it later, once you know the migration went well.
• Image alt text: add an alt text field to the collection. A CSV import won't bring it over on its own.
• Internal links: links inside posts still point to the old URLs. They work thanks to the redirect, but it's worth updating them to the new ones.
• Canonical and schema: set the global canonical URL in Webflow and the schema on your templates (Article or BlogPosting for the blog).
• Languages: on multilingual sites, Webflow Localization generates hreflang tags automatically. Check that each language's URLs match the old ones or have their redirect.

‍

5. Launch day

• Publish, connect the domain and check that the SSL certificate is active.
• Crawl the list of old URLs in Screaming Frog's list mode. Every one should return a 301 followed by a 200. Any 404 or redirect chain gets fixed that same day.
• Submit Webflow's sitemap (/sitemap.xml) in Search Console.
• Request indexing for your 10–20 most important pages.
• If the domain stays the same, you don't need Search Console's Change of Address tool. It's only for domain changes.

‍

6. Monitoring: what to check in weeks 1, 2, 4 and 8

‍

The mistakes that cost the most rankings

• Redirecting everything to the homepage.
• Forgetting old posts that are no longer linked but still get traffic from Google.
• Changing URLs, content and structure all at once, so you can't tell afterwards what caused a drop.
• Launching without redirects and "adding them later".
• Leaving the old site accessible on another domain or subdomain where Google can index it.

‍

Frequently asked questions

How long does traffic take to recover after migrating to Webflow?

With correct redirects, expect fluctuations for 4–8 weeks and a return to previous levels within that window. If a page is still clearly below after 8 weeks, there's a specific problem to look at.

‍

Does Webflow support pattern or regex redirects?

Yes. In the 301 redirect settings you can use capture groups, for example /old-blog/(.*) → /blog/%1, to redirect whole sections with a single rule.

‍

Can I keep the same WordPress URLs in Webflow?

For static pages, yes. For blog posts, not entirely: Webflow adds the collection slug (/blog/). If your posts already lived under /blog/ in WordPress, you can keep identical URLs.

‍

Will I lose my backlinks when migrating?

No, as long as every URL with external links has a 301 redirect to its equivalent page. Authority passes through the redirect.

‍

If you'd rather we handle it, our Webflow migration service covers the mapping, the redirects and the post-launch monitoring.