There is no best website translation tool, only the one that fits how your site is built and how your translation is already handled. The products in this category do genuinely different jobs under one phrase: some translate and serve pages, some manage strings and push them into a CMS, and some keep the record around both. Judging them starts with knowing which of the three you need.
Best website translation: the ranking, and the criterion
- Weglot: Judged on published price and shape: $17 a month for one language and 10,000 unique translated words, read 2026-09-06, for a product that translates and serves the pages itself, so the bill scales with words and languages.
- Google Search Central's own guidance: Judged as the baseline every tool is measured against: the documented requirement that each language version lists itself and all the others, and that missing return links make annotations ignorable. A tool that does not produce this is not a candidate.
- Hreflangly: Judged on what it does and does not do: it translates nothing and keeps the record and the tags, priced per site rather than per word, which suits a site whose translation is already handled elsewhere.
Judge on your own site, not on a table
Four questions decide it. Does your site already have translations, or do you need them produced? Where do the translated pages live: your CMS, the vendor's proxy, or your repository? Who edits them after launch? And what happens to the hreflang tags when a page exists in three locales and not the fourth? Ask those and the shortlist sorts itself.
What the categories cost, roughly
Translation products are priced per language and per translated word, so the bill scales with the site: Weglot's Starter plan is $17 a month for one language and ten thousand words, read on 2026-09-06. Record and management products are priced per site or per seat, so they do not. Neither is cheap or expensive in general; they scale differently, which is the thing to check against your own size.
The question the demos skip
Show me a page that exists in three of four locales. Every product handles the fully translated case; the partial case is where the tags go wrong, where the fallbacks differ and where the record either exists or does not. It is also the normal state of a real multilingual site, so it is the case worth twenty minutes.
What to do before you buy anything
Run the scope sheet and the hreflang map on this site. Knowing your word count, your locale count and the tag volume turns a vendor conversation from a demo into a comparison, and it usually shows that the decision is about the record rather than about the translating.
Questions people ask about best website translation
Is there one best website translation tool?
No. There are three different product shapes under the phrase, and the right one depends on whether your translations exist and where the pages live.
What should we test in a demo?
A page that exists in some locales and not others. That is the normal case and the one that separates the products.
Do we need one tool or two?
Plenty of sites run a translation product and keep the record separately, because the two jobs are genuinely different and the tools that do both do one of them thinly.
What does the record product on this site do that a translation product does not?
It keeps one row per page per locale with a status and a date, generates the hreflang set from those rows, and says which translated pages are behind their source. It does not translate and does not serve pages. A translation product does those two things and rarely keeps the row.