Free website translation widget

Your site,
in 27 languages.

No resource files, no rebuild, no second site. Switch training on and the snippet reports back the copy it finds. You translate it once, publish, and visitors get their own language on the next page load.

27 locales|RTL ready|No rebuild
Choose a language
🇬🇧 English English
🇩🇪 Deutsch German
🇪🇸 Español Spanish
🇯🇵 日本語 Japanese
🇸🇦 العربية Arabic
1,284 / 5,000 strings published
Google Translate widget alternative

The Google Translate widget is gone.
Here is what replaces it.

Google stopped supporting its Website Translator widget on 1 October 2026, and since 2020 it had only been offered to non-commercial sites anyway. If your pages still carry that language dropdown, Translations takes its place with one script tag, and this time you get to read every translation before a visitor does.

How to find the old snippet on your site, the alternatives compared and the move step by step: the guide to replacing the Google Translate widget.

Google Website Translator Builderify Translations
No longer supported from 1 October 2026. A maintained module, supported by the people who build it.
Offered only to non-commercial sites since 2020. Any site, shops and businesses included, free to start.
Machine output shown to visitors as it came. Every string approved by you in a workbench before it goes live.
Brand names and product codes translated along with the rest. Ignore anything that should stay exactly as it is.
How it works

It reads your site
so you do not have to.

Train

Switch training on. As people browse, the snippet reports the text it finds back in small batches.

Collect

Chunks are deduplicated by content hash and stored once, with the page they came from for context.

Translate

Work through the queue in the workbench, per language, drafting and publishing as you go.

Serve

Published strings become a cached dictionary the snippet applies on the visitor's next page.

The dictionary is keyed by the source text itself rather than a hash, so the snippet does a plain object lookup per text node — no hashing work on the visitor's device.

Catalogue

Twenty-seven locales.
Deliberately not two hundred.

A list you can actually scan — the languages people ship in, with native names and flags in the switcher.

🇬🇧 English English
🇪🇸 Español Spanish
🇫🇷 Français French
🇩🇪 Deutsch German
🇮🇹 Italiano Italian
🇵🇹 Português Portuguese
🇳🇱 Nederlands Dutch
🇵🇱 Polski Polish
🇷🇴 Română Romanian
🇸🇪 Svenska Swedish
🇩🇰 Dansk Danish
🇳🇴 Norsk Norwegian
🇫🇮 Suomi Finnish
🇨🇿 Čeština Czech
🇬🇷 Ελληνικά Greek
🇹🇷 Türkçe Turkish
🇷🇺 Русский Russian
🇺🇦 Українська Ukrainian
🇸🇦 العربية Arabic
🇮🇱 עברית Hebrew
🇮🇳 हिन्दी Hindi
🇯🇵 日本語 Japanese
🇰🇷 한국어 Korean
🇨🇳 中文 Chinese
🇮🇩 Bahasa Indonesia Indonesian
🇻🇳 Tiếng Việt Vietnamese
🇹🇭 ไทย Thai

Right-to-left is handled, not bolted on

Arabic and Hebrew are marked as RTL in the catalogue, and the snippet flips the document direction for them automatically. You do not maintain a second stylesheet.

Workbench

One screen
per language.

Pick a locale, filter to what still needs doing, and work down the list. Nothing reaches a visitor while it is still a draft.

Draft and published

Save work in progress without exposing it, then publish when it reads right.

Needs review

Flag a translation you are not sure about so somebody else looks at it.

Ignore a string

Brand names, product codes and anything that should stay in English.

Delete a string

Clear out copy that no longer exists on the site.

Search and filter

Jump to a phrase, or show only what is still outstanding.

Controls

You decide what
gets collected.

Source locale

The language your site is written in today.

Chunk length

Minimum and maximum characters worth translating.

Attributes

Also translate placeholders, titles and alt text.

Language switcher

Show it or hide it, with your own label.

Exclude paths

Keep admin and checkout routes out of the queue.

String cap

Up to 5,000 strings per website before pruning.

Config and dictionaries are cached and served to the snippet asynchronously, so adding languages does not cost you page speed.

Questions

Translations, before you ask.

Translations run on the 250 free Usage Credits every account gets each month, and each translation row, meaning one string translated into one language, costs 0.1 credits. If you need more, one-time packs start at $9, purchased credits never expire and there is no monthly fee.

Add the Builderify script tag to the head of your site and switch training on, with no resource files, no rebuild and no second site. It works the same on Wix, Webflow, WordPress, Shopify, Squarespace, Framer and plain HTML, with 27 languages available, including right-to-left Arabic and Hebrew.

Google ended support for its Website Translator widget on October 1, 2026, and Builderify Translations is a replacement you control. Training mode collects your copy as people browse, you approve the translations in a workbench, and published strings are served to visitors from a cached dictionary on their next page load.

With training on, the snippet reports the text it finds back in small batches, stored once with the page it came from for context. You then work through the queue per language in the workbench, saving drafts, flagging anything that needs review and ignoring brand names or product codes. Nothing reaches a visitor while it is still a draft.

Stop losing the visitors
you already paid for.

More leads from the traffic you already have, and follow-up that sends itself. Free to start. No card, no monthly fee.