Why browser translation tools are not working with Weglot?

In this article, you will learn more about why browser translation tools are not working with Weglot

Behavior on all websites
Potential issues with browser translation tools

1. Behavior on all websites

For all the Weglot integrations, that is to say, our WordPress, Javascript, Subdomains, or Subdirectories integrations, Weglot automatically blocks browser translation tools.

More precisely, Weglot is adding a " translate="no" " attribute in the <html> tag of your source code to prevent the other translation tools from interfering with Weglot.

On Google Chrome, Weglot is also adding a meta tag <meta name="google" content="notranslate" /> so that no translations are generated from other translation tools that can be installed on Google Chrome.

2. Potential issues with browser translation tools

Other translation tools use their own translation API, which can lead to code and translation conflicts.

If Weglot wasn't blocking these tools, their translations could erase the Weglot ones on your live website. It could also lead to the generation of undesired translations in your Weglot project.