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

Why are some parts not automatically translated on Webflow?

Fix machine translation problems for your hotel website

Key points:

  • Some areas do not translate automatically because they originate from dynamic elements, external integrations, or image text.
  • Webflow and tools like Weglot only translate the text accessible within the HTML code.
  • A few simple adjustments are all that's needed to guarantee a complete translation.

When creating a multilingual site on Webflow, some sections may remain in the original language after integrating Weglot or after manual translation. This is a common occurrence and is due to the way the text is integrated into the site.

1. Text embedded in images or videos

Machine translators cannot read "drawn" text within an image, logo, or video. Solution:

  • Replace this text with Webflow text elements (H1, H2, paragraphs).
  • If you need to keep an image containing text (e.g., a promotional image), create a translated version of the image and display it only in the corresponding language.

💡 Tip: for each language, you can duplicate the block and make it visible only on the corresponding language version (Display: None on the others).

2. Dynamic content management systems (CMS)

Fields from the Webflow CMS will not be automatically translated if you have not enabled multilingual support or if Weglot does not detect them. Solution:

  • Verify that your CMS fields (title, summary, text, button) are set to Plain Text or Rich Text, and not to code or custom fields.
  • With Weglot, ensure you have enabled CMS Collections translation in the dashboard (Settings > Translations > Dynamic Content).

3. Content injected via custom code

Texts generated by code (JavaScript, external forms, booking widgets, iframes, etc.) are not visible to automatic translation tools. Solution:

  • If possible, integrate the content directly into Webflow as native text.
  • For external booking modules, choose a multilingual version provided by the vendor (e.g., a translatable hotel booking engine).

💡 Tip: Add language attributes to your integrations (e.g., lang="en" or lang="fr") to help Google and Weglot better identify them.

4. Hidden or conditional content

Some hidden blocks (Display: None) or blocks loaded via Webflow interactions may be ignored by Weglot because they are not present in the DOM at the time of translation. Solution:

  • Verify that the text is clearly visible in the Designer when Weglot scans the site.
  • If you are using interactions, temporarily enable hidden content during initial detection.

5. The cache or synchronization delay

Weglot can sometimes take a few minutes to detect and translate new sections added to Webflow. Solution:

  • Refresh the Weglot cache from the dashboard.
  • Click on "Re-scan website" to force the detection of missing content.

Best practices to avoid oversights

  • Use only native Webflow text elements (Heading, Paragraph, Text Block).
  • Avoid including phrases in alt text or class names.
  • Check the translations regularly after publication.
  • If you manage languages ​​manually, make sure that each block of text has a translated version.

💡 Pro tip: for repetitive texts (e.g., “Book Now”, “See More”), centralize them in a Symbol (global component): this allows you to duplicate and translate them more easily on all pages.

Conclusion

If parts of your Webflow site aren't translating automatically, it's often because they're embedded in an unreadable format (image, script, hidden content). By following these steps, you'll ensure a complete and seamless translation for your hotel website, regardless of the tool used.