The Google Translate Website Widget in 2026: Is It Still Available, and Does It Help SEO?

🔎 SEO · Updated October 2026 · 9 min read · by Jacob Campbell

No, the Google Translate website widget is no longer available: Google stopped offering it to new commercial sites in 2019, and in an update to its Search Central blog it said the Website Translator widget would no longer be supported from October 1, 2026. It also never helped SEO, because the translation happens in the visitor’s browser after the page loads, so search engines only ever index your original language. This guide explains how the widget works, why it adds nothing for search or AI assistants, the privacy and layout costs, the legacy embed code (so you can recognise it, or load it only on click while you replace it), and what to use instead.

Key facts

• 2019 — Widget closed to new commercial websites
• Oct 1, 2026 — Date Google said support for the widget ends
• 0 — Translated pages it creates for search engines to index
• element.js — The script at translate.google.com/translate_a/ to look for

Is the widget still available in October 2026?

The Google Website Translator widget is not available to new sites and, from October 1, 2026, is no longer supported by Google. The history, in order:

• 2019: Google stopped offering the widget for new commercial websites. Existing installations kept loading.
• May 2020: Google’s Search Central blog announced the widget was available again, but only for government, non-profit and non-commercial websites (for example academic institutions) focused on COVID-19 response.
• September 2026: that same blog post was updated to say the Website Translator widget would no longer be supported from October 1, 2026, with site owners pointed to the paid Cloud Translation API instead.

“No longer supported” is not the same as a promise that the script will disappear on a set day, and Google has not said exactly what happens to existing embeds. You should not plan on it: an unsupported third-party script on a public page can stop working, change behaviour or leave an empty box at any time. If you find the widget on a site you manage, schedule its removal now rather than waiting to see whether it breaks.

The widget is separate from Google Translate itself, from the translation built into Chrome, and from the Cloud Translation API, none of which are affected.

How the widget works

The widget is a client-side script: it loads element.js from translate.google.com, draws a language dropdown, and when a visitor picks a language it sends the page text to Google for translation and rewrites the text in the visitor’s browser. Nothing changes on your server. The URL stays the same, the HTML your server sends stays in the original language, and the chosen language is remembered in a browser cookie (named googtrans), not in the address.

That design is what made it easy to install, and it is also why it does nothing for search.

Does it help SEO? No.

The Google Translate widget does not help SEO because it never produces a translated page that a search engine can fetch. Search engines index what a URL returns. With the widget, every URL returns the original language; the Spanish or French text exists only inside one visitor’s browser, after they chose it from a menu that a crawler does not use. Specifically:

• There is no translated URL to index, so there is nothing for hreflang to point to.
• Your title, meta description and structured data stay in the original language in search results.
• AI assistants and agents that fetch your page (see how AI assistants read pages) receive the original HTML too.

Google also already offers searchers machine translation of its own. Its translated results feature can show the title and snippet of a result in another language translated into the searcher’s language, then open a machine-translated view of the page. For a searcher, the widget adds nothing that Google Search and Chrome do not already provide. If you want to be found in another language, you need real pages in that language, at their own URLs: see multilingual websites for search and AI.

The costs: privacy, speed, layout and accessibility

Even when it worked, the widget carried costs that are easy to miss:

• Privacy. The script loads from Google servers on every page view, so every visitor’s browser contacts Google whether or not they ever translate anything, and translated text is sent to Google. Depending on where your visitors are and what your privacy policy says, that may need disclosure or consent. Loading the script only when a visitor asks for it (below) avoids most of this.
• Speed. It is extra third-party JavaScript and CSS on every page. Loaded synchronously, it can delay rendering; loaded on every page by default, it adds work for visitors who never use it. See INP and Core Web Vitals.
• Layout. When a translation is active, the widget inserts a toolbar frame at the top of the page and shifts the page down by setting a top offset on <body>. That commonly breaks sticky headers and fixed-position elements, and sites end up with CSS overrides to hide the bar.
• Markup changes. Translated text is wrapped in <font> elements inserted into the DOM. JavaScript frameworks that manage the DOM themselves, React being the best-known example, can throw errors when text nodes they expect have been replaced.
• Accessibility. The dropdown is another control for keyboard and screen-reader users to deal with, and the machine translation is unreviewed. For anything a visitor relies on, such as prices, medical or legal information, or instructions, an unreviewed translation can mislead.

The legacy embed code (and a click-to-load version)

This is the standard snippet the widget used, shown so you can recognise it in a theme or template and remove it. Search your code for translate_a/element.js and google_translate_element.

<div id="google_translate_element"></div>
<script>
function googleTranslateElementInit() {
  new google.translate.TranslateElement({pageLanguage: "en"}, "google_translate_element");
}
</script>
<script src="https://translate.google.com/translate_a/element.js?cb=googleTranslateElementInit"></script>

If you must keep it for a short time while you replace it, at least stop it loading for everyone. This version contacts Google only after a visitor clicks, and shows a fallback message if the script fails to load, which is the likely outcome now that it is unsupported:

<button type="button" id="gt-load">Translate this page</button>
<div id="google_translate_element"></div>
<p id="gt-fallback" hidden>Translation is not available here. Use your browser’s built-in translate option instead.</p>
<script>
function googleTranslateElementInit() {
  new google.translate.TranslateElement({pageLanguage: "en"}, "google_translate_element");
}
document.getElementById("gt-load").addEventListener("click", function () {
  var btn = this;
  btn.disabled = true;
  var s = document.createElement("script");
  s.src = "https://translate.google.com/translate_a/element.js?cb=googleTranslateElementInit";
  s.onload = function () { btn.hidden = true; };
  s.onerror = function () {
    btn.hidden = true;
    document.getElementById("gt-fallback").hidden = false;
  };
  document.body.appendChild(s);
}, { once: true });
</script>

Set pageLanguage to your page’s language code. Do not add this to new pages. It is a stopgap for pages that already rely on the widget, not a recommendation.

Alternatives that work

There are three realistic replacements, depending on whether the page needs to be found in search.

1. Browser translation (free, nothing to install). Chrome, Edge, Safari and Firefox all have page translation built in, and they offer it automatically when a page’s language differs from the user’s. Help them by declaring the language correctly with <html lang="en">, and mark anything that must not be translated (brand names, product codes, addresses) with translate="no":

<span translate="no">Built2WinWeb</span>

A short line near your footer or language menu, such as “Need another language? Use your browser’s translate option”, replaces the widget for most visitors.

2. Real translated pages (for anything you want found). Publish each language at its own URL, with translations reviewed by a fluent speaker, linked with hreflang. This is the only option that gives you indexable pages in other languages. The full method is in multilingual websites for search and AI.

3. Translation plugins and services. For WordPress there are plugins that manage translated versions, and for any platform there are hosted translation services, several of which use machine translation from Google or others with an editor for review. Before choosing one, check three things: does it publish each language at its own URL in the HTML the server returns (not only in JavaScript); does it output hreflang; and can a person review and edit the translations. A tool that only translates in the browser has the same SEO limits as the old widget.

What we recommend

Use browser translation for convenience, and real translations for the pages you want found. In practice:

• App and tool pages (logged-in dashboards, calculators, booking flows): rely on browser translation, declare lang correctly, and protect fields and codes with translate="no". Test the page with Chrome translation switched on, because translated labels can be longer and break tight layouts.
• Marketing and information pages (home, services, pricing, contact, guides): if a language matters to your business, publish reviewed translations at their own URLs with hreflang.
• Existing widget installs: remove the script, remove any CSS written to hide its banner, and replace the dropdown with a browser-translation note or links to your translated pages.

A removal checklist: search templates for element.js; delete the init function and the container div; remove .goog-te- CSS overrides; update your privacy policy if it lists Google Translate; and check the page still lays out correctly at the top, where the old banner offset was.

Limits of this advice

• We cannot tell you exactly when existing embeds will stop working. Google said support ends on October 1, 2026; it has not published a shutdown schedule for the script itself. Test your own pages.
• Browser translation is not reviewed translation. It is fine for convenience, and wrong for legal terms, medical instructions or prices where a mistake matters.
• Some audiences may rely on the widget. If you serve people who are less comfortable with browser menus, a visible link to a translated page, or a phone number answered in their language, is more helpful than a dropdown.
• Cloud Translation API is a developer tool, not a widget. It can power a translation workflow on your server, but it charges per character and you still need review and hreflang.

Product facts: the AI Indexing Pack

Stated plainly, so it can be checked against the product page:

• What it is: the AI Indexing Pack is a set of files you upload to your own website. It is sold by Built2WinWeb as a one-time purchase, with no subscription.
• What it ships: (1) a working MCP server using the Streamable HTTP transport, with typed output schemas and tool annotations; (2) Markdown content negotiation, so agents can request a clean text version of each page; (3) llms.txt, agents.txt and agent cards; (4) the full /.well-known/ discovery tree; (5) OAuth protected-resource metadata; (6) bot access control that verifies crawler identity; (7) a README with a verification checklist.
• Requirements: PHP 7.4 or newer, Apache or LiteSpeed with .htaccess support, FTP access, and a domain you control. Installation takes about 30 minutes.
• What it is not: it is not a WordPress plugin (that is the separate WordPress edition, which needs WordPress 6.0+ and PHP 8.0+), it does not write content for you, it does not guarantee rankings or citations, and it is not a managed service.
• Free routes in: sites built on AIWebBuilding get the core built in, and a 50-day streak on FreeAIBoost unlocks the pack for one domain. Current prices are on the product pages.

Related reading

• Multilingual websites for search and AI — Separate URLs, hreflang, the lang attribute and reviewed translation.
• How AI assistants read pages — What an assistant receives when it fetches your URL.
• INP and Core Web Vitals — Why third-party scripts slow down interactions.
• Accessibility is agent-readiness — Why accessible pages work better for AI agents too.
• Technical SEO checklist — 12 factors that move rankings.
• Make a WordPress site readable by AI — Practical changes for WordPress sites.

Frequently asked questions

Can I still add the Google Translate widget to a new website?

No. Google stopped offering the Website Translator widget to new commercial sites in 2019, and said support for the widget ends on October 1, 2026.

Does the Google Translate widget help SEO?

No. The widget translates text in the visitor browser after the page loads, so no translated URL exists for search engines or AI assistants to index. Only real translated pages at their own URLs can rank in other languages.

Will existing Google Translate widgets stop working?

Google has said the widget is no longer supported from October 1, 2026, but has not published an exact shutdown schedule for the script. Treat it as unsupported and plan to remove it.

What is the best free replacement for the Google Translate widget?

The translation built into Chrome, Edge, Safari and Firefox. Declare your page language with the lang attribute so browsers offer translation, and add a short note telling visitors to use it.

How do I stop a browser from translating a brand name?

Wrap it in an element with the HTML translate="no" attribute, for example a span. Browser translators skip text marked this way.