Migrating to Webflow without losing your search equity

Every replatform conversation eventually reaches the same fear: "will we lose our rankings?" It is a reasonable fear. Sites do lose traffic in migrations, sometimes badly and sometimes permanently.

But in almost every post-mortem I have read or run, the cause was not the new platform. It was a handful of URLs nobody mapped, a sitemap nobody resubmitted, and a two-week window where nobody was watching the graph.

Search equity is not fragile. It is just unforgiving about paperwork. Here is the paperwork.

Before: freeze a baseline you can argue with

You cannot tell whether a migration hurt you if you do not know what "before" looked like. Do this while the old site is still live:

• Full crawl of the existing site. Every URL, status code, title, meta description, H1, canonical, and word count. Export it. This is your source of truth for the URL map.
• Search Console export. 16 months of queries, pages, clicks and impressions. Once the old property changes, that history gets harder to reconstruct.
• Top pages by clicks and by backlinks. Usually 80% of the value sits in under 30 URLs. Those 30 get individual attention. The long tail gets rules.
• Analytics snapshot. Organic sessions and conversions by landing page, monthly, for the last year — so seasonality does not get blamed on you or credit you unfairly.

The URL map is the whole job

Everything else is detail. Build a spreadsheet with one row per old URL and one target on the new site. Rules that keep this honest:

1. Map to the closest equivalent page, not to the homepage. Bulk-redirecting to the homepage is the classic way to throw away link equity — search engines increasingly treat it as a soft 404.
2. If there is genuinely no equivalent, say so. Either write the replacement page or let the URL 410. A deliberate 410 is healthier than a lie.
3. 301, never 302. Temporary redirects do not pass equity the way permanent ones do, and "temporary" always becomes permanent.
4. No chains. Old URL to final URL, one hop. If the old site already redirects A to B and B is dying, map A directly to C.
5. Watch trailing slashes, case, and query strings. These generate the duplicate rows that get skipped, and they are always the ones that break.

What has to survive the move

Beyond the URLs, these carry ranking signals and are easy to lose in a rebuild:

• Title tags and meta descriptions, page by page — not regenerated from a template.
• One H1 per page, carrying the same intent as before.
• Structured data: Organization, Article, Product, FAQ, Breadcrumbs — whatever you had, plus what you should have had.
• Image alt text and, where possible, image filenames.
• The internal link graph. Rebuilds routinely orphan pages that used to be linked from a sidebar or an old nav.
• Canonical tags pointing at the new canonical, not a staging domain.

Webflow-specific things that bite

• Staging domains get indexed. Keep Disable subdomain indexing on until launch, and confirm the live site's robots.txt is not still blocking after you flip.
• The 301 panel has limits and no chaining logic. Do a final pass through it and test a sample with a redirect checker, not by clicking around.
• CMS slugs are generated from names. Rename a collection item after launch and the URL changes silently. Lock slugs on anything that ranks.
• The auto-sitemap only includes what you let it. Check that no template or collection page is excluded by accident.
• SSL and the www / non-www choice must match what you told Search Console. Pick one host, redirect the other, be consistent in canonicals.

Launch day and the two weeks after

1. Crawl the new site immediately and diff it against the baseline. Every 404 in that diff is a lost page.
2. Test the top 30 old URLs by hand. Not a sample — all thirty.
3. Submit the new sitemap in Search Console and remove the old one.
4. Request indexing on the top pages rather than waiting to be discovered.
5. Check Core Web Vitals on the new templates before traffic teaches you the hard way.
6. Watch Search Console coverage daily for two weeks. New 404s and "crawled, not indexed" spikes are the early warning.

The part nobody budgets for

The migration is not finished at launch. It is finished when the graph is back where it was and the client's team can ship a page without calling anyone. That second half is why we hand over a component system rather than a set of pages — it is the difference between a site that ages and a site that compounds.

That was the actual deliverable on our OCR Solutions project: a redesign and a Webflow migration, and then an internal team that has not needed agency hours since.

Written by Luka. Two years running projects at a Premium Webflow Enterprise Partner in New York, and every migration since.