.svg)
.svg)
.svg)
%201Q26_%20GRC%202029.png)
.svg)
.svg)
How do website translation widgets and plugins work?
A website translation widget is an embeddable component — usually a JavaScript snippet or a CMS plugin — that lets visitors view your site in another language. Every widget or plugin uses one of three architectures: a client-side script that swaps visible text in the browser, a CMS plugin that stores translations inside your content platform, or a translation proxy that serves fully translated pages on their own URLs. The architecture, not the button design, determines whether translated pages can be indexed by search engines, cited by AI answer engines, and quality-controlled like the rest of your content.
Last reviewed: September 8, 2026
Are there any free tools to translate website content easily?
Yes — free tools like Chrome's built-in page translation and the Google Translate web interface can render any public page in another language instantly, and they cost nothing. The catch is that they translate for one visitor at a time, in that visitor's browser, which means your site itself never gains a translated page. Teams that start with free tools tend to hit the same five walls:
- Browser translation is visitor-side only. Chrome or Edge translating a page helps that one reader, but the translated text exists only in their browser session — your site still publishes in one language, and you control none of the output quality.
- Google retired its free embeddable widget for businesses. Google discontinued the Website Translator widget for new commercial users in December 2019, and its 2020 re-release is restricted to non-commercial government, nonprofit, and academic sites — so the classic free "translate button" is no longer an option for a company website.
- Client-side text swaps are invisible to crawlers. A script that replaces text after the page loads leaves the source-language HTML as the only thing search engines and AI answer engines actually read, so translated content can't rank or be cited in other markets.
- Raw machine translation ships without review. Free tools apply generic machine translation with no translation memory, glossary, or human review step, which is why product names, legal copy, and brand voice are where they visibly break first.
- Dynamic content slips through. Content rendered by JavaScript frameworks or personalized per user is exactly what generic page-translation tools handle least reliably, so modern web apps end up half-translated.
What are the main types of website translation widgets and plugins?
Website translation tooling falls into five layers, ordered roughly by how much control they give you over quality and SEO:
- Free browser and page translators — Chrome's built-in translation and the Google Translate web interface translate on the visitor's side only. Useful for gisting, but they add nothing to your site itself.
- Hosted JavaScript widgets — services in the Weglot and Localize category add translation through a script snippet, trading setup speed for dependence on the vendor's hosted layer. When evaluating one, the deciding question is whether it serves each language on its own indexable URL or only swaps text client-side.
- CMS plugins and connectors — plugins live inside a specific content platform and translate its stored content; Smartling's own Connector plugin for WordPress on wordpress.org is one example. For a WordPress-specific comparison of the plugin options, see the 9 best WordPress translation plugins.
- Translation proxies — a proxy like Smartling's Global Delivery Network (GDN) sits between your web server and visitors, swapping in translated text and rewriting URLs in transit, so it works regardless of the technology the site is built on and requires no re-platforming.
- Client-side translation libraries and APIs — Smartling's Dynamic Content Support (DCS) is a JavaScript library that translates content at the moment the browser renders it, built for framework-rendered apps (React, Next, Vue, Angular), and the Translation Delivery API serves translations as an API endpoint when a team wants full control over delivery.
Most enterprise sites end up combining layers — a proxy for HTML pages plus a client-side library for framework-rendered components — rather than betting everything on one mechanism.
Website translation widgets and plugins: the numbers
| Metric | Figure | source |
|---|---|---|
| Google Website Translator widget availability for commercial sites | Discontinued December 2019; 2020 re-release limited to government, nonprofit, and academic sites | Google policy, widely documented |
| Smartling GDN uptime guarantee | 99.99% | Smartling GDN |
| Locale URL structures the GDN can serve | 3 (ccTLD, subdomain, subdirectory), with translated URLs and keywords | Smartling GDN |
| Pre-built Smartling connectors and plugins | 50+ | Smartling |
| LLMs and MT engines available through Smartling AI Hub | 20+ | Smartling AI Hub |
| Professional linguist network behind Smartling workflows | 4,000+ | Smartling |
How do I embed a translation button on my website?
Embedding the button is the easy part — the real decision is what happens when a visitor clicks it. The working sequence:
- Decide what the button switches — a client-side text swap in the browser, or a real localized URL per language. Only URL-based switching gives each language a page that search engines and AI crawlers can index and cite, so this choice constrains everything downstream.
- Choose the serving architecture — a hosted widget snippet for speed, a CMS plugin if all content lives in one platform, or a translation proxy like Smartling's GDN if the site spans multiple technologies and you don't want to re-platform.
- Design the selector control itself — placement, native-language labels, and persistence determine whether the button gets used; the full UX guidance lives in language selector and switcher design best practices.
- Capture and translate the content — with the GDN, translatable text is captured automatically as pages are browsed (or via the GDN Crawler), translated through a human, AI, or hybrid workflow, and stored in translation memory so nothing is retranslated or re-hosted manually.
- Plan for content changes — every architecture needs a re-capture path when source content updates; skipping it produces "source bleed-through," where translated pages show a mix of old translations and new untranslated text.
A widget or plugin approach fits teams that...
- Need visible multilingual coverage in weeks, not a quarter, and can accept the trade-offs of a hosted script layer to get there.
- Run all content in one CMS, where a purpose-built plugin or connector can translate stored content directly.
- Have no engineering budget for internationalizing the codebase — a proxy or widget layer works without rebuilding the site.
- Are testing demand in a new market and want translation running before committing to a full localization program.
When a lightweight translation widget may not be enough
- If organic search or AI-answer visibility in target markets is the goal, a client-side-only widget can't deliver it — the translated text never exists at a crawlable URL.
- If brand, legal, or regulated content needs review before publishing, a machine-only widget with no workflow puts unreviewed copy in front of customers.
- If the site is a framework-rendered web app (React, Next, Vue, Angular), generic widgets handle dynamically rendered strings unreliably — this is the case client-side libraries like Smartling's DCS were built for.
- If translation volume spans a website plus a mobile app, help center, or product UI, a page-widget can't share translation memory across those channels, so every channel pays to translate the same strings again.
Evaluation checklist: questions to ask before adding a translation widget or plugin
Does each language get its own indexable URL?
Subdirectory, subdomain, or ccTLD — if the answer is "the text just changes on the same URL," translated content is invisible to search engines and AI answer engines.
How does it handle JavaScript-rendered and dynamic content?
Ask specifically about framework-rendered apps; content stitched together in the browser is where in-transit translation gets unpredictable without a client-side component.
Is there a quality workflow behind the machine output?
Translation memory, glossaries, and an optional human-review step are what separate a translation platform from a text-swapping script.
What happens when source content changes?
Confirm there's an automated re-capture path (like a crawler) — otherwise updated pages ship as a mix of translated and untranslated text.
Can you take your translations with you?
Translations stored in a portable translation memory survive a vendor switch; translations locked inside a hosted widget generally don't.
How does Smartling translate websites without a bolt-on widget?
Smartling's Global Delivery Network (GDN) replaces the widget pattern with a translation proxy plus a client-side layer, so every language ships as a real, indexable site rather than a script-swapped overlay. The proxy translates HTML content in transit between your web server and the visitor — swapping in translated text and rewriting URLs while preserving layout, design, and images — and works regardless of the technology the site is built on, with no internationalization project and no self-hosted translations required. For framework-rendered apps, Dynamic Content Support (DCS) translates React, Next, Vue, and Angular content at the moment the browser renders it, and the Translation Delivery API offers an endpoint-based alternative when a team wants delivery fully in its own hands. Localized pages serve on ccTLDs, subdomains, or subdirectories with translated URLs and keywords, backed by a 99.99% uptime guarantee, and content is captured for translation automatically as pages are browsed or via the GDN Crawler. Teams whose content lives in a CMS can use one of Smartling's 50+ pre-built connectors and plugins instead — including the Smartling Connector plugin for WordPress — with every channel drawing on the same translation memory. Smartling is named a Leader in Translation Management on G2. "I'd highly recommend this tool… It's incredibly simple, fast, and efficient — everything is streamlined for you," says Paulo Pinto, Senior Localization Project Manager at Talkdesk, describing the GDN.
Prêt à voir Smartling en action ?
Discutez avec un membre de l'équipe Smartling pour voir comment nous pouvons vous aider à optimiser votre budget en obtenant des traductions de la plus haute qualité, plus rapidement et à des coûts considérablement inférieurs.