Skip to content
English - United States
  • There are no suggestions because the search field is empty.

Is it possible to have specific URLs (e.g., /en, /fr) with Localize on Webflow?

Understanding language and URL management in Localize

Key points:

  • No, Localize does not create multilingual subfolders or subdomains.
  • The translations are displayed at the same URL, via JavaScript.
  • To have separate URLs for each language (e.g., /en, /fr), a different approach or a complementary tool is required.

Localize is designed primarily to offer a seamless and instant multilingual experience, without page reloads or complex configurations. However, this simplicity has a limitation: URLs do not change according to language, which restricts the site's SEO capabilities.

How does Localize work with Webflow?

  1. A single URL for all languages. Example:
    • Your homepage remains https://www.monsitehotel.com, whether it is displayed in French, English, or Spanish.
    • The content is dynamically replaced according to the language detected by the browser or selected via the language selector.
  2. No /en, /fr, or /es subdirectories are created. Localize does not add language directories or alternative URL tags. Visitors do not change their address when they change languages.
  3. Client-side translation (JavaScript). This means that the translated content does not physically exist on the server — it is simply injected for display.

💡 Tip: This approach offers ideal display speed and fluidity, but it is not designed for advanced international SEO.

Why doesn't Localize use URLs per language?

  • Easy integration: no need to recreate the site structure for each language.
  • Reduced maintenance: only one version of the site to manage and update.
  • Universal compatibility: works with any Webflow site, without redirection logic.

But this has a direct impact on SEO:

  • Google can only index one version of the site.
  • The translated versions do not have separate URLs or indexing.
  • Translated keywords (e.g., “luxury hotel in Paris”) cannot be targeted individually.

Alternatives for having multilingual URLs

1. Use Weglot instead of Localize

Weglot automatically creates a clear and indexable URL structure:

  • monsitehotel.com → FR version

  • monsitehotel.com/en/ → EN version
  • myhotelsite.com/es/ → ES version 💡 Weglot also manages hreflang tags and international SEO without additional development.

2. Create your manually translated pages in Webflow

For complete control, you can duplicate your Webflow pages and define:

  • /fr/accueil
  • /en/home
  • /es/inicio Next, you can:
  • Add a language selector that redirects to the corresponding version.
  • Manage SEO separately (meta title, description, hreflang tags).

💡 This is the best option if you are targeting 2 to 3 main languages ​​and want complete SEO control.

3. Use an external multilingual proxy (advanced)

Some solutions, such as Bablic or CDN proxies, can generate translated URLs from a single website. 💡 However, this approach requires technical skills and a paid subscription.

Best practices for hotels

  • If your priority is conversion and not international SEO, Localize remains an excellent solution.
  • If your strategy focuses on visibility in foreign markets, opt for Weglot or manual page management.
  • Remember to harmonize your SEO tags and page titles for each language, even without a specific URL.

Conclusion

No, Localize doesn't allow you to create specific URLs like /en or /fr. All languages ​​are displayed on the same address thanks to dynamic rendering. If your main goal is multilingual SEO and international visibility, it's better to use a solution like Weglot or build your translated pages directly in Webflow.