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
Why this is necessary

1. Behavior on all websites

For all Weglot integrations (WordPress, JavaScript snippet, Subdomains, or Subdirectories), Weglot automatically disables browser-based translation tools.

This is achieved by adding the attribute translate="no" in the <html> tag of your website’s source code. This prevents external translation tools from interfering with Weglot’s translations.

Additionally, for Google Chrome users, Weglot inserts the meta tag <meta name="google" content="notranslate" /> . This ensures Chrome (and any installed translation extensions) do not generate competing translations.

2. Why this is necessary

Browser translation tools rely on their own APIs, which can conflict with Weglot’s system. Without these protections, you may encounter the following issues:

Overwritten translations: Browser tools may replace Weglot’s translations directly on your live website.
Unwanted translations in your project: They can trigger the creation of unnecessary translations inside your Weglot dashboard.
Code conflicts: Using multiple translation engines often leads to display or functionality problems.

By blocking these tools, Weglot ensures that your website content is consistently and reliably translated, without interference.