Google Translate widget alternatives: replace the website translator

What changed

What happened to the Google Translate website widget?

Google's Website Translator was a free script that added a language dropdown to any page. Google stopped offering it to new sites in 2019. In May 2020 it reopened sign-ups only for government, non-profit, and non-commercial sites focused on COVID-19 response, and recommended the Cloud Translation API for every other website. Several translation vendors now report that Google ended support for remaining installations on 1 October 2026; Google's original announcement does not state that date, so test whether your widget still loads and plan a replacement either way.

• 2019: no new sign-ups for the Website Translator.
• 2020: limited access for government, non-profit, and non-commercial COVID-19 sites only.
• Google's recommendation for other sites: the Cloud Translation API.
• Google Translate itself, and translation built into browsers, are unaffected.

SEO

Why the widget never helped SEO

The widget translated text in the visitor's browser after the page loaded, on the same URL as the original. Search engines saw only the source language, so the translations could not rank, and every language shared one URL with no hreflang. A replacement that keeps this model keeps the same limitation.

• No separate URL per language, so nothing for search engines to index.
• Translated text existed only in the visitor's browser.
• No translated titles, descriptions, or hreflang tags.
• No control over quality, terminology, or which content was translated.

Alternatives

Google Translate widget alternatives

Choose by how your site is built. The useful alternatives all publish translated pages at their own URLs, which the widget never did.

• Altified, for Next.js applications: an SDK that renders translated pages, metadata, and hreflang from your own app at URLs such as /es/pricing, with a configurable language switcher. Needs a developer; no CMS plugins.
• Hosted website translators, for CMS and site builders: GTranslate, ConveyThis, Weglot, and Linguise add a language switcher and serve translations on subdirectories or subdomains. Check that the plan you choose includes indexable URLs; free widget tiers usually do not.
• CMS translation plugins: WordPress and Shopify plugins that store translations inside the platform.
• Cloud Translation API: Google's recommended path, but it is an API, not a widget. You build storage, routing, and the switcher yourself.
• Browser translation: Chrome, Edge, and Safari can translate any page for the visitor. Free and zero work, but it does nothing for SEO.

Migration

How to replace the Google Translate widget

Remove the old script and its placeholder element, then publish real language versions. Most sites can switch without changing their design: the new language switcher goes where the Google dropdown was.

• Find and remove the google_translate_element div and the translate_a/element.js script.
• Pick your target languages from your analytics, not the full list of 100+ languages.
• Choose a URL structure such as /es/ subdirectories.
• Install the replacement and translate titles, descriptions, and slugs as well as page text.
• Add a language switcher that links to each language URL.
• Add hreflang, then check it with an hreflang validator and submit your sitemap.

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

Language switcher

Keep the dropdown, change what it links to

Visitors liked the widget's dropdown because it was easy to find. Keep a switcher in the same place, but make each option a link to a real language URL. That gives visitors the same experience and gives search engines pages to index.

• Show languages in their own names: Español, Deutsch, Français.
• Link to the equivalent page, not the home page.
• Remember the visitor's choice instead of redirecting by browser language.