A redesign is the most common moment for a website to lose its search rankings. The new site looks better and runs on a modern platform — and then organic traffic drops for weeks.
The problem is rarely the new design. It is the move itself. A Figma to Webflow migration changes URLs, headings, images, page speed and internal links all at once, and if any of those change without a plan, search engines have to re-learn the site from scratch.
Here is how to move a site from Figma to Webflow and keep the SEO it has already earned.
1. Map every old URL before you build anything
The single biggest cause of lost rankings in a migration is a URL that changes without a redirect. If a page ranked at /services/web-design/ and the new site puts it at /web-design/, every link and every search result pointing at the old address hits a dead end.
Before the build starts, export a full list of the live site’s URLs. For each one, decide its fate: keep the same URL, move it to a new URL with a 301 redirect, or remove it deliberately with a redirect to the closest relevant page.
Keep URLs the same wherever possible. Every URL change is a small risk, so change only the ones that genuinely need it.
Set up the redirects in Webflow before launch, not after, and test each one on the staging site.
2. Keep the content and headings intact
Search engines rank pages for the words on them. If a migration quietly rewrites headings, shortens copy, or drops sections to fit a cleaner design, the page can lose the rankings that copy earned.
During the build, the headings on the new page should match the old page in meaning and order: one H1 that states the page topic, H2s for the main sections, and H3s for sub-points. A design that turns a heading into styled body text, or that uses two H1s on one page, weakens the structure search engines rely on.
The same applies to the body copy. A redesign is not a rewrite. If the design needs shorter text, edit the copy deliberately, with the ranking keywords kept in place, not trimmed away by accident during the Figma to Webflow build.
3. Protect your images and their alt text
Images are easy to lose in a migration. A new design often replaces old images with fresh ones, compresses them differently, and renames the files — and the alt text that described them disappears with the old file names.
Alt text matters twice: it helps search engines understand what an image shows, and it is what screen readers read aloud. When images are replaced, write new alt text for each one that describes the image and, where it fits naturally, includes the page keyword.
File names matter too. A descriptive file name such as figma-to-webflow-homepage-build.jpg is better than a camera or export default like IMG_4821.jpg. Keep image files reasonably small as well — Webflow compresses images, but starting from a huge export still costs loading time.
4. Watch page speed on the new build
A new site should be faster than the old one, but a heavy migration can make it slower instead: large hero images, extra animations, and third-party scripts carried over from the old site all add loading time.
Webflow sites are generally fast out of the box, but the build still decides the result. Keep hero images under a reasonable size, limit animations to the ones the design genuinely needs, and avoid loading scripts that no longer serve a purpose.
Test the staging site with a speed tool before launch, and test the most important pages — the homepage and the top service pages — rather than only the homepage.
5. Rebuild internal links deliberately
Internal links tell search engines which pages matter most on a site. A migration often breaks them quietly: a link to an old URL that now redirects, a service page that no longer links to its related pages, or a footer that points at pages which no longer exist.
After the build, walk through the new site and check the links on the homepage, the main service pages, and the navigation. Each important page should be reachable in a few clicks, and related pages should link to each other — for example, a Figma to Webflow service page linking to the Webflow services page, and the other way round.
Fix any link that points to a removed page, and update links that still use old URLs even if a redirect would catch them.
6. Check the technical basics before launch
A few small technical details decide whether search engines can find and index the new site at all:
- Make sure the staging subdomain is not indexed, and that the live site is not accidentally blocked from search engines after launch.
- Confirm the XML sitemap includes the new pages and excludes pages that were removed.
- Set a title tag and meta description on every page.
- Check that the site has an SSL certificate and that all internal links use the secure version of the address.
These take an hour to check and weeks to recover from if they are wrong, so they belong on the pre-launch list, not the post-launch one.
7. Monitor the first month after launch
No migration is finished on launch day. Rankings usually wobble for a short time while search engines re-crawl the new pages, and the job is to watch for the wobbles that do not settle.
In the first month, check weekly: pages that now return errors, pages that dropped out of the index, redirects that are not working, and traffic to the pages that mattered most before the move. A search console account will show crawl errors and indexing problems directly, so connect it before launch if it is not connected already.
Most small problems show up in the first two weeks. Fix them as they appear, and avoid making further big changes during that first month, so the site has a stable version for search engines to settle on.
FAQ
How long does it take for rankings to recover after a migration?
Small, temporary drops are normal and often settle within two to four weeks if the URLs, headings and content stayed the same. A drop that lasts longer than a month usually means something was missed — a missing redirect, a changed URL, or content cut during the build.
Do I need to redirect every old page?
Every old page that received traffic or links should redirect to the closest matching new page. Pages with no traffic and no links can redirect to a relevant parent page. Redirecting everything to the homepage is a mistake — it sends visitors to a page that does not answer what they were looking for.
Can I change the design and keep my rankings?
Yes. Rankings depend on the URL, the content, the headings, the speed and the links — not on the exact look. A Figma to Webflow migration can change the design completely and keep rankings, as long as those five things are protected during the move.
Final thoughts
A Figma to Webflow migration is a design project and an SEO project at the same time, and the SEO half is mostly discipline: map the URLs, keep the headings and content, protect the images, watch the speed, rebuild the links, and check the technical basics before launch.
And if you would like the move handled for you — from a Figma to Webflow conversion to ongoing Webflow services — get a free quote and we will take it from there.