How to Prevent SEO Problems During a Webflow Website Migration

Most SEO losses after a move to Webflow come from a short list of causes: changed URLs without redirects, missing metadata, content that was cut, and a staging site that got indexed. You prevent them by mapping every URL that matters before you build, setting 301 redirects before launch, and checking Search Console in the first weeks after.

Why migrations lose traffic

Search engines tie years of signals to your old URLs. Links point to them and rankings are attached to them. When they return a 404 on launch day, those signals have nowhere to go. A redesign is also when pages get shortened or dropped, and some of them were quietly bringing in search traffic.

Step 1: Build a URL inventory

Start with a spreadsheet, one row per URL on the current site. No single source has all of them, so I pull from several:

• The current XML sitemap
• A crawl of the live site
• Search Console pages with clicks or impressions
• GA4 landing pages for the last 12 months
• URLs with external backlinks

For each URL, record organic clicks, whether it has links, and the planned new URL.

Example: a 300-page SaaS site where the blog moves from /resources/blog/post-name to /blog/post-name. Every post needs a row, even if the change follows a pattern.

Step 2: Keep URLs where you can

If an old URL is clean and descriptive, keep it. Every changed URL adds a redirect and some risk. Webflow puts CMS items under the Collection's URL prefix, such as /blog/, so choose Collection slugs early to match your old structure.

When a URL must change, map it to the closest matching page. Redirecting everything to the homepage is treated much like a 404 by Google.

Step 3: Set up 301 redirects

Add redirects in Site settings > Publishing > 301 redirects. They go live when you publish.

Old path:  /services/web-design
New path:  /web-design

Old path:  /resources/blog/(.*)
New path:  /blog/%1

The second rule uses a capture group, so one line covers a whole folder. Test pattern rules carefully.

• Point each old URL straight to its final destination. No chains.
• Never create loops or redirect a path that is still a live page.
• Keep the redirect list in your spreadsheet for later audits.

Changing domains too? Redirect the old domain as well and use the Change of Address tool in Search Console.

Step 4: Carry over on-page SEO

Each Webflow page has its own title, meta description and Open Graph settings. On Collection templates you build these from CMS fields. Before launch, check that:

• Important pages keep a unique title and description
• Each page has one H1
• Image alt text was migrated, including CMS images
• Links in rich text point to new URLs
• Old structured data is rebuilt as JSON-LD

Compare old and new versions of your top 20 organic landing pages. If a section answered a search query, keep it.

Step 5: Handle staging and noindex

Webflow has a setting in the SEO area of Site settings to stop the webflow.io staging domain from being indexed. Turn it on early. Then make sure no blocking rule or noindex tag survives onto the production domain.

User-agent: *
Disallow: /

That robots.txt rule blocks the whole site. Fine on a test project, a disaster on launch day.

Launch day checklist

• Custom domain and HTTPS working, one preferred host (www or non-www)
• All 301 redirects saved and the site published
• 20 to 30 old URLs spot-checked: one 301, then a 200
• Sitemap reachable at /sitemap.xml and submitted in Search Console
• GA4 and GTM firing, conversions recording
• No noindex on pages that should rank

Step 6: Monitor the first weeks

Some ranking movement is normal while Google recrawls. Watch for errors that stay:

1. New "Not found (404)" URLs in the Search Console Pages report. Redirect any that had value.
2. Clicks by page compared with the pre-launch period.
3. A fresh crawl for broken links, redirect chains and missing titles.
4. Views of your 404 page in GA4, with the requested path, if you track them.

Keep the old site's crawl export. When a page drops, you can see exactly what changed.

Google's guide to site moves with URL changes is worth reading once before you start.

FAQ

How long should I keep 301 redirects?

At least a year, and longer if you can. Old external links may never be updated.

Can I add redirects in bulk?

Pattern rules cover whole folders. For very large lists, check the current options in Webflow's help docs before you plan the work, and group URLs by pattern where you can.

Will rankings drop after moving to Webflow?

Short-term movement is common. A lasting drop usually points to missing redirects, removed content or indexing settings, which you can find and fix.

Dealing with this on a live Webflow site? It is the kind of work I do in Webflow SEO and AEO. Send me your site and I will tell you what I would fix first.