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

Menu and footer texts remain in French on Webflow with Localize: why and how to fix it

Identify the cause and apply the appropriate solution.

Key points:

  • Menus and footers are often static or loaded via Webflow symbols, which can prevent them from being detected by Localize.
  • Localize only translates text present in published and publicly accessible code.
  • A simple reconfiguration or a "rescan" is often enough to unlock the translation.

It's common, when setting up a multilingual site on Webflow with Localize, for the main content to be translated correctly, but for the navigation menu and footer to remain in the original language (often French). This isn't a bug, but a consequence of how Webflow and Localize handle static elements.

Step 1: Check that the menu and footer are included in the post

Webflow symbols (or reusable components) such as the header and footer can be saved without being “published” on the active page.

  1. Open your site in Webflow Designer.
  2. Select the menu or the footer.
  3. Verify that they are properly integrated into the page and not just contained within an unpublished symbol.
  4. Click Publish to republish the entire site.

💡 Tip: Localize only scans published content that is visible in the final HTML code.

Step 2: Relaunch a scan in Localize

Localize detects text strings during the site scan. If your menus have been modified since the initial integration, they are not yet translated.

  1. Log in to your Localize account.
  2. Go to Settings → Languages.
  3. Click on “Rescan Website”.
  4. Please wait a few minutes for Localize to detect the new text in the menu and footer.

💡 Tip: After a rescan, you will find the new texts in “Translations → Untranslated”.

Step 3: Manually translate the static text in the menu and footer

  1. Open Translations → Untranslated in your Localize dashboard.
  2. Search for the exact words from the menu or footer (e.g., “Book Now”, “Contact”, “Legal Notice”).
  3. Enter the corresponding translations for each language.
  4. Save: the update is automatic on your Webflow site.

💡 Tip: Use the “Search” function in Localize to quickly target missing texts.

Step 4: Check for hidden or dynamic elements

Some Webflow structures may prevent Localize from "seeing" the text:

  • Mobile menus (Burger Menu) are hidden behind an interaction.
  • Dynamic elements of the CMS (e.g., a footer link pulled from a Collection).
  • The menus are loaded after rendering via JavaScript.

💡 Solution: Open the published site, open the mobile menu or scroll down to the footer, then run a “Rescan”. This forces Localize to detect the text visible on the screen.

Step 5: Check the custom styles

In some cases, the texts may appear “untranslated” when they are actually translated, but hidden or superimposed.

  1. Check the style of your elements (color, size, z-index).
  2. Test it in another language and look at the code (right-click → Inspect).
  3. If the translated text is present in the DOM, it's a CSS style issue, not a translation problem.

💡 Tip: Add a slight appearance delay to the Localize script if the content loads too quickly to be replaced.

Step 6: Translate the texts from the CMS

If your footer or menu links use CMS elements (for example, blog posts or offers):

  • Localize only translates what is rendered in the HTML.
  • Verify that the text fields are visible and not hidden in scripts or logical conditions.

💡 Solution: Go to “Translations → Dynamic Content” and manually add the CMS fields to be translated.

Step 7: Force the display in the code (as a last resort)

If Localize still doesn't detect your text despite everything:

Add them manually to a data-localize attribute in Webflow: <a data-localize="link-contact">Contact</a>

  2. In Localize → Custom Translations, add the corresponding translation:
    • link-contact: Contact → Contacto / Contact / Kontakt.

  3. Republish your site.

💡 Tip: this “manual” method is very reliable for items not detected automatically.

Best practices for hotels

  • Re-run a Localize rescan after each navigation or footer update.
  • Opt for short, universal names for multilingual menus (“Rooms”, “Offers”, “Book”).
  • Test your translations on mobile and tablet devices, as mobile menus may behave differently.
  • Keep a saved version of your menu in each language for quick access in case of an update.

Conclusion

Menu or footer text that remains in French doesn't necessarily indicate a bug; it's often simply undetected or unpublished during the Localize scan. By rerunning the scan, manually translating the missing strings, and checking your Webflow symbols, you can fix the problem in minutes and ensure a smooth multilingual experience for your international visitors.