How Do You Migrate a Multilingual Website to Webflow Without Losing SEO?

Quick Summary

• The short answer: Map every URL in every language, import existing translations, redirect every locale, rebuild hreflang, and monitor each language separately.
• The biggest trap: Webflow 301 redirects don't cover locale subdirectories. Each locale needs its own redirect rules.
• Hreflang: Webflow generates it automatically when you use the auto-generated sitemap and turn on publishing for every locale.
• Imports: CMS content can be imported through the Data API with a locale ID for each language. Static pages and localized images need manual work.
• Agentic Translation: Use it to fill gaps, not to replace translations that already rank.

To migrate a multilingual site to Webflow without losing SEO, map every URL in every language, import the translations you already have, set up redirects for each locale, and track each language on its own after launch.

Most teams get the English site right.

It's the German, French, or Arabic pages that quietly lose rankings.

That's because in Webflow, redirects and SEO settings don't carry over from your main language. Each locale needs its own setup.

Below is the process we follow, in 8 steps.

Want us to handle it? Our Webflow migration service plans every locale before a page moves.

‍

What usually breaks in a multilingual migration?

The same few things go wrong again and again:

• Redirects for other languages. Webflow doesn't cover locale folders automatically.
• Hreflang. Old tags still point to URLs that no longer exist.
• URL changes. Moving from ?lang=, subdomains, or country domains changes every non-English URL.
• Missing content. Some things can't be imported, so pages go live in the wrong language.
• Monitoring. Total traffic looks fine while one language drops.

‍

How does a multilingual Webflow migration work?

We split it into three phases:

1. Map: Record what you have and plan where every URL goes.
2. Match: Rebuild in Webflow Localize and bring every SEO signal across.
3. Monitor: Test before launch, then watch each language after.

‍

Phase 1, Map: what should you do before building in Webflow?

Don't open Webflow yet.

First, write down what the old site has, in every language.

‍

Step 1, benchmark and crawl every locale:

Pull traffic, rankings, and top pages for each language from Search Console and your analytics.

Keep them separate. A drop in German traffic is easy to miss inside a healthy global number.

Next, crawl the whole site and export every indexable URL by language.

For each one, save the title, meta description, canonical, hreflang tags, and schema.

Mark the URLs that have backlinks. Those need the most care.

Pro Tip

Add a URL-prefix property in Search Console for each locale folder, like example.com/de/, before you migrate. You get clean per-language data from day one, instead of digging through filters later.

‍

Step 2, map every URL, locale by locale:

Most multilingual sites use one of four URL patterns.

Webflow Localize puts each locale in a subdirectory, like /de/. If you're on anything else, every non-English URL will change.

Now build a simple sheet. Old URL in one column, new URL in the next, one row per page.

A few rules while you fill it in:

• Keep ranking URLs the same if you can. No change, no risk.
• Redirect German to German. Not to the English page.
• Only switch languages if you have to. That means the page no longer exists in its original language.
• Don't send everything to the homepage. Pick the closest match for each URL.

Keep this sheet handy. You'll come back to it for redirects, QA, and monitoring.

Using country domains and want to keep them? Read Should You Use One Webflow Site or Multiple Sites for Global Markets? first.

We did this for ZingHR's website. URL mapping, redirects, schema, and metadata were sorted before migration started, and we shipped 22+ pages in 4 weeks.

‍

Phase 2, Match: how do you rebuild the site in Webflow?

Now you rebuild.

The goal is simple: same pages, same languages, clear URLs.

‍

Step 3, set up locales and import your translations:

Add a locale for each language and region you support today.

Check your plan first. Localization Essential covers up to 3 locales, and Advanced covers up to 10.

Every new locale starts with your primary locale's content, so nothing goes live empty.

Then bring in the translations you already have. That's the content Google is ranking right now.

CMS content can come in through the Webflow Data API, which can create and manage CMS items in primary and secondary locales.

A few things won't come across on their own:

• Locale IDs. Each import request needs a CMS locale ID for every language. Skip one, and that version won't exist.
• Static pages. The Data API can't create them, which is why tools like PowerImporter only move CMS content. Rebuild these in the Designer.
• Main-language page content. API updates to page and component content only work for secondary locales.
• Localized images. They can't be updated through the localization API. Swap them in the Designer.

‍

Step 4, fill gaps with Agentic Translation:

Webflow's Agentic Translation is great for missing content.

Don't use it to redo translations you already have.

One-time translation does a whole language for your team to review. Continuous translation keeps a locale in sync as your main content changes.

Why not just re-translate everything?

• Your translations already rank. Swapping them for new AI text changes what Google has indexed.
• It uses up words. Translated words count toward your plan's word limits, shared across locales.
• You can protect them. Exclusion rules keep chosen pages, components, CMS fields, and component props out of AI translation.

Planning to turn on continuous translation later? Our guide to Webflow Agentic Translation covers the setup.

‍

Step 5, recreate slugs, metadata, hreflang, and canonicals:

Each locale needs its own SEO title, meta description, and Open Graph settings.

Pull them from your Step 1 export. Don't copy the English ones across.

Want translated slugs, like /de/preise instead of /de/pricing? Collection slug translation needs an Advanced or Enterprise Localize plan.

If your current translated slugs rank, keep them exactly as they are. A new slug is a new URL.

Hreflang is mostly handled for you. Webflow adds it to pages, the sitemap, or both, and updates it every time you publish.

The exception is a custom sitemap. Then you'll need to add hreflang yourself.

For pages that repeat the same content in the same language, Google suggests picking one preferred version. For everything else, run this check:

‍

Step 6, add 301 redirects for every locale:

Pay close attention here.

Webflow's 301 redirects are relative to your root domain and don't apply to locale folders.

So a redirect from /old-page to /new-page does nothing for /de/old-page. You need rules for each locale.

Wildcards save time. A rule like /de/blog/(.*) covers a whole folder.

Pro Tip

Add specific redirect rules before broad wildcards, because Webflow redirects run in the order they were added. Wildcards aren't full regex, so you can't exclude a single page from one. Test on the live domain in a private browser window, since browsers cache redirects.

More on how ordering works in Webflow's redirects guide.

Moving a multilingual site to Webflow?

Book a short call

Check case studies

‍

Phase 3, Monitor: what should you check before and after launch?

Test every locale on staging first.

After launch, watch each language on its own until Google catches up.

‍

Step 7, QA every locale before launch:

Go back to your Step 2 sheet and test from it.

• Redirects: Try a few from every locale, including old ?lang= and subdomain URLs.
• Hreflang: Spot-check your key pages in each language.
• Metadata: Make sure titles and descriptions are translated, not copied from English.
• Language switcher: It should open the same page in the other language, not the homepage.
• Internal links: German pages should link to German pages.
• Indexing blocks: Remove any noindex tags or robots.txt rules left over from staging.

‍

Step 8, monitor rankings and AI visibility by locale:

Google moves a site one URL at a time.

It has to visit every old and new URL at least once, so expect some movement for a few weeks.

• Compare each locale with your Step 1 numbers.
• Check the indexing report for each language.
• Look for 404s on old non-English URLs, and add redirects as they show up.
• Ask ChatGPT, Perplexity, and Google AI Overviews the questions your pages used to answer, in each language. See if you're still cited.

‍

What does a well-built multilingual Webflow site look like?

It helps to know where you're heading before you start mapping URLs.

Here's a live example: Amazon Signage, which we built on Webflow. It's one site serving 8 markets, and it shows the end state a multilingual migration should land on.

The use cases: one product, six industries, eight markets

Amazon Signage sells the Signage Stick to very different buyers. So the site has a page for each industry it serves.

Each of those pages then exists in every locale:

This is where multilingual sites get big fast.

Six industry pages plus the home, search, and blog pages make 9 page types. Multiply by 8 locales, and that's 72 URLs.

That's why the structure matters so much.

Because every locale follows the same /locale/industries/slug pattern, one wildcard rule per locale can cover a whole section. A rule like /de-de/industries/(.*) handles all six German industry pages at once.

And because the sitemap is auto-generated, every new page shows up with all 8 language versions linked. Nobody has to maintain hreflang by hand.

We shipped 20+ pages in 5 weeks, on a CMS the Amazon team can update on its own.

‍

Can a Webflow migration affect AI search visibility?

Yes. AI engines can only cite pages they can find and understand.

A missing redirect means the page can't be found. A rewritten page might lose the answer an AI engine used to quote.

• Keep the direct answers. If a section opened with a clear answer before, keep it near the top.
• Keep names consistent. Brand and product names should match in every language. Webflow's glossary helps.
• Don't launch half-translated locales. They give AI engines less to work with.
• Bring your schema across. Recreate FAQ, article, and organization schema on every locale.

Our SEO and AEO team checks rankings and AI visibility on every migration we run.

‍

What can't Webflow migrate automatically?

Webflow does a lot for you, but these always need manual work:

• Static pages. Rebuild them in the Designer.
• Localized images. Swap them per locale in the Designer.
• Main-language page content. The API can only update secondary locales.
• Redirects for other languages. Each locale needs its own rules.
• Country domains. Webflow Localize uses subdirectories, not separate domains.
• Custom sitemaps. Hreflang has to be added by hand.

Adding Arabic as part of the move? Read How Do You Build an Arabic and English (RTL) Website in Webflow?

‍

Key takeaways

Treat every language like your main one, and a multilingual migration doesn't have to cost you rankings.

Webflow takes care of hreflang, lang tags, and localized sitemaps. Redirects, imports, and QA are on you.

Moving from a specific platform? We've written guides for Sitecore, Drupal, Contentful, Next.js, and WordPress. Or start with our SEO-safe Webflow migration checklist.

Planning a multilingual move? Talk to Flowtrix. Our migration team maps every locale before launch.

Migrate every language without losing rankings

Book a short call

Check case studies