Migrating from WordPress to Webflow without losing SEO

Everything starts before touching anything: you need to know what you own. Inventory URLs, titles, content, traffic, backlinks and lead-generating pages. The tools: a full crawl (Screaming Frog or similar), 12 months of Search Console data, analytics to see where enquiries come from.

From that inventory comes the single most important document of the migration: the URL map. For every current address, a destination on the new site or an explicit decision. A typical company site has 40–150 indexable URLs: less enormous than it sounds, but it has to be done URL by URL, not by category.

And here the migration becomes an opportunity: not every page deserves to survive. Some move, some merge, some are removed deliberately — a page with no traffic, backlinks or commercial role can go, redirected to the closest relevant page. Without a map, though, redirects remain guesses.

With the map in hand, go-live stops being a leap in the dark. Every important URL has its destination; 301 redirects are loaded in Webflow's publishing settings and tested before launch, not after. The practical test: export all old URLs and bulk-check their status codes as soon as the new site is on staging.

Watch out, though, for the redesign's sneakiest risk: the new template that is prettier but poorer. Content shortened, H1s turned into slogans, text moved into images. Check canonicals, headings, internal links, alt text and sitemap: the design must not erase what made you findable.

One last point almost everyone misses: the content WordPress generates on its own and Webflow does not — category pages, tags, author archives, attachment pages. If they were indexed and drove traffic, they need destinations; if they were noise, redirects clean them up for good.

The site is live — the migration is not over. The first week is the critical one: status codes, indexable pages, the sitemap submitted to Search Console, 404s, redirect chains. Errors fixed within days leave no trace; errors found after a month do.

Don't panic over a dip in impressions during the first two or three weeks: it can happen while Google recrawls the new structure. Watch the trend, not the daily number — core pages should recover their queries within a few weeks.

For the systematic sign-off of the new site, use our technical SEO checklist for Webflow: it covers the checks template by template, in the order to run them.

Let's close with the three mistakes that, on their own, explain almost every “we migrated and lost our traffic” we hear. First: changing slugs without reason. If a ranking article lives at /blog/risorse-x, moving it to /resources/risorse-x brings no upside — only risk.

Second: launching with staging indexable, or the mirror image — a global noindex forgotten on the new site. Symmetrical damage, same check: thirty seconds.

Third, the most expensive: treating the migration as finished at go-live. The first four weeks of monitoring are part of the project — if whoever proposes the migration does not include them, the risk stays entirely with you. Now you know what to demand: that was this guide's promise.