Why are browser translation tools not working with Weglot?

In this article, you’ll learn why Weglot disables browser-based translation tools and how this helps prevent translation conflicts.

1. How Weglot disables browser translation

Regardless of the integration method you use (WordPress, JavaScript, subdomains, or subdirectories), Weglot automatically prevents browsers from translating your website.

To do this, Weglot adds the following attribute to the <html>   tag in your website’s source code: translate="no"  

This tells browsers and translation tools that the page should not be translated automatically.

Weglot also adds the following meta tag for Google Chrome: <meta name="google" content="notranslate">  

This prevents Chrome’s built-in translation feature from generating another translation on top of Weglot’s version.

2. Why do we disable browser translation?

Browser translation tools use their own translation systems and modify the content displayed on the page. If they run alongside Weglot, the two systems may interfere with each other and cause issues such as:

• Weglot translations being overwritten: The browser may replace Weglot’s translations directly on the live website.
• Unnecessary translations being generated: Content modified by another translation tool may be detected and added to your Weglot project.
• Display or functionality issues: Multiple translation systems modifying the same page can lead to inconsistent content or technical conflicts.

Disabling browser translation tools ensures that Weglot remains the only system managing your website’s translations, providing visitors with a consistent and reliable multilingual experience.