Download websites that use GTranslate

About GTranslate

A translation widget is a statement about audience. Whoever runs the site concluded that visitors were arriving who did not read the language the site was written in, and chose to answer that with a script rather than with a localisation project.

GTranslate does exactly that job. The service ships a JavaScript widget that injects language switching into a page without touching the underlying content system, then serves machine translated versions, with paid tiers adding indexable translated URLs, subdomain routing and human post-editing on top of the raw output. GTranslate Inc. has offered the product since 2008 on a Freemium model, and the pricing model is the detail that shapes how the numbers should be read.

Because the entry tier costs nothing, presence proves adoption rather than revenue. A detection tells you the operator wanted multilingual reach and wanted it cheaply, which is itself a useful segmentation. Cross-border stores, tourism and hospitality operators, immigration and relocation services and small exporters all show up in this population, and each of them has an international ambition that runs ahead of its localisation budget.

As of October 2026 the widget is present on 12,337 sites. United States accounts for 3,027 of them and the .com zone carries a large part of the total, but the remainder spreads thinly across many national markets, which is what you would expect from a tool bought precisely by operators whose readers are not in one place.

Age is the other thing worth weighing. A product available since 2008 accumulates installations that nobody has revisited, and no version marker appears in the page to separate an old deployment from a fresh one, so the population mixes live localisation strategies with switchers left running on abandoned pages. Detection also depends on the widget reaching the markup, and installations held behind a consent gate or a lazily loaded footer can be missed.

For a translation agency the list is a prospect file, because every domain on it has already admitted a multilingual need and settled for machine output. For a competing widget vendor the same file is a displacement target. For a researcher it is a map of which markets try to reach outward and which stay home. What makes the population workable is the filtering around it. A translation widget on a store that also runs a payment gateway and ships internationally is a live cross-border business, while the same widget on a static brochure page is an aspiration, and only a full export with the rest of the stack attached lets anyone tell those two apart. Checking one domain answers a support question. The export answers a market question, and the two are not the same exercise.