What a multilingual website is, and when to bother
A multilingual website is a site that offers the same content in two or more language versions — each on its own URL, with its own metadata and its own content that search engines won't confuse for duplication. It is not a translation widget bolted onto an existing site. It is a full language version that you maintain the same way you maintain the original.
That distinction matters, because most problems with multilingual sites start right here. Someone bolts on an automatic translator that runs in JavaScript, the translated content only ever exists in the browser, and search engines never see it. The site looks multilingual, but from an SEO point of view it still has exactly one version.
In Webflow you have three realistic ways to do it properly. They differ in cost, in how much control you keep, and in how much work lands on you every time the content changes.
Your options in Webflow
Native localization (Webflow Localization) is built into the platform. You switch to another locale, rewrite the copy, and Webflow handles the URL structure, hreflang tags and sitemap for you. Nothing to code. The catch is pricing — localization sits on the higher-tier plans and you pay per language. For a two-language site it usually pays for itself; at five languages it noticeably moves your monthly bill.
External services like Weglot or Lokalise get you live far faster. Weglot crawls your site, generates machine translations, and lets you correct them by hand afterwards. The upside is speed; the downside is that your content now lives outside your CMS and you depend on someone else's service and price list. Lokalise adds a translation workflow that makes more sense for a team than for one person.
The manual approach means building the language versions yourself — your own pages, your own CMS items, your own switcher. It's free, it gives you full control, and the content stays entirely yours. You pay for it in labour: every change has to be carried into every version by hand.
My practical take: for two languages, with a client who wants to manage the content inside Webflow, native localization earns its keep — it handles hreflang, the sitemap and the URL structure for you, and there's nothing to code. Once the language count climbs or the budget is tight, the manual route makes more sense: you pay once in labour instead of monthly per language. I'd reach for Weglot where a site needs to be multilingual fast and the translations will be polished in production.
How to structure your URLs
I recommend language subfolders: /cs/, /en/, /de/. It's the simplest to manage, it keeps every language on one domain so the versions reinforce each other's authority, and it's how Webflow does it natively.
The alternatives exist but come with strings attached. Subdomains (en.yourdomain.com) are often treated as separate sites, so authority doesn't flow between them. Separate country domains (yourdomain.de) make sense when you genuinely operate in that market and want the local signal — otherwise you've just given yourself several websites to maintain.
One rule holds either way: one language version, one URL. Never serve different languages at the same address based on the visitor's IP. The search engine will lock onto whichever language its crawler happens to get, and never see the rest.
A workflow for managing the content
This is the part people underestimate. Setting a multilingual site up is a one-off job. Keeping it alive is a weekly one.
- When you add an article, create it in every language at once — not "later, when there's time". Language versions that drift apart are painful to reconcile.
- Track what's translated and what isn't. A spreadsheet listing your articles with a column per language is enough. Without it, six months in you have no idea what's missing.
- When you update content, walk through every version. The classic failure is a corrected price in Czech and the old price still sitting in English.
- Agree up front who translates. When nobody owns it, it doesn't happen.
SEO for multilingual sites
A multilingual site has three SEO obligations. Skip them and the whole thing underperforms.
Hreflang tags tell search engines which version belongs to which audience. Without them Google may serve your English page to Czech searchers, or treat the versions as duplicates of each other. Webflow Localization generates them for you; with a manual build you add them as custom code in the head. Note that every version must reference all the others including itself — that's the part people forget.
Unique metadata per version. Translated titles and descriptions, not the Czech text copied across. It sounds obvious, and it's skipped systematically on CMS items.
A sitemap covering every language. When a version is missing from it, search engines only reach it through links, which takes considerably longer.
For more on the technical side, see my article on llms.txt in Webflow, which covers similar ground for AI search engines.
The language switcher
The switcher looks like a detail, and it's where multilingual sites break most often.
The core rule: the switcher must lead to the corresponding page in the target language, not to the homepage. If someone is reading your pricing article and switches to English, they want the English version of that article. Dumping them on the homepage is the fastest way to lose them.
Beyond that: highlight the current language so people can see where they are. Use language names rather than flags — a flag denotes a country, not a language, and German isn't only spoken in Germany. And when a page genuinely doesn't exist in a language, say so instead of sending people to a 404.
Common mistakes
- The switcher goes to the homepage. The most common and the most irritating.
- Missing or incomplete hreflang tags. Especially the self-reference.
- Half-finished translation. Translated pages, untranslated CMS items, or the reverse. Visitors fall into a language hole.
- Automatic IP-based redirects. With no way to override, they frustrate users and blind crawlers.
- A forgotten sitemap and robots.txt. The new language version exists, but nobody knows about it.
What to take away
You can build a multilingual site in Webflow without writing code — and the decision that actually shapes the outcome is made right at the start: native localization, an external service, or manual management. Each is paid for in a different currency, and switching six months later means rebuilding a large part of the site.
After that it comes down to discipline: keeping every version current, getting hreflang right, and having a switcher that goes where it should.
If you're planning a multilingual site and aren't sure which route pays off for you, get in touch — we'll go through the scope and I'll tell you straight whether paying for localization makes sense in your case or whether you're better off doing it manually.
