At a glance
Prices below are the published entry paid prices checked for this guide. Currencies are left as published rather than converted.
| Rank |
Product |
Entry paid price |
Included translation capacity |
Main buying consideration |
| 1 |
Linguise |
Start: $15/month |
200,000 translated words; unlimited languages; one website |
Requires an active subscription to serve translations. |
| 2 |
Weglot |
Starter: €15/month or €150/year, excluding VAT |
10,000 total translated words; one translated language |
The allowance is a fixed total, not a fresh monthly allocation. |
| 3 |
TranslatePress |
Personal: €99/year |
50,000 AI-translated words; one website |
Annual payment and a WordPress-based editing workflow. |
The prices and allowances come from each vendor’s pricing page. Weglot describes its displayed US-dollar prices as estimates based on the exchange rate at subscription, so we use its euro prices here. (linguise.com)
Why Linguise comes first
For this buyer, we give more weight to room for additional languages than to a tightly limited starting subscription. Linguise offers that room, plus documented WordPress support for translated URLs and metadata. That combination earns its narrow lead in our desk rubric; it doesn’t establish that its translated sentences are better. (linguise.com)
The dependency is worth accepting deliberately. Linguise isn’t a one-time translation purchase that can then be disconnected. Its pricing FAQ says an active plan is required to supply translations to visitors. An owner who wants generated content stored in the WordPress database should look closely at TranslatePress instead. (linguise.com)
When Weglot is worth choosing instead
We would favor Weglot when the owner’s priority is managing terminology and reviewing pages through its documented glossary and editing workflow. Those are concrete reasons to choose it, without accepting the vendor’s claims about translation accuracy as independently established. (weglot.com)
Check the URL requirement before choosing a subscription. Weglot can publish language-specific page URLs, but its current pricing table reserves translated URL slugs for Pro. An additional-language page path isn’t the same thing as translating the words in that path. (weglot.com)
Why TranslatePress is the annual-budget pick
TranslatePress suits an owner who already has help maintaining WordPress and wants translation editing in that environment. Its page editor provides direct text correction, while the included SEO Pack in Personal covers metadata and slug translation. We would choose it over a hosted workflow when that local editing arrangement matters more than avoiding WordPress administration. (translatepress.com)
The qualification is the annual commitment. Also decide who will review the pages: a requirement for separate translator accounts moves the purchase beyond Personal. (translatepress.com)
Start with an enquiry journey, not every page
Our recommendation is to launch one additional language first. Choose a service page, its supporting information, and the route to an enquiry. Ask a fluent reviewer to check the offer, service area, form labels, confirmation message, and promised next step before promoting it.
Treat this as a launch checklist, not a test we performed. Don’t assume that translating the visible page also covers an embedded form, booking service, or follow-up email. Make those separate acceptance checks.
If the enquiry form itself needs replacing, our Typeform vs. Tally comparison addresses that separate buying decision.
Budget for languages as well as pages. Linguise describes its allowance as page words multiplied by target languages; TranslatePress likewise counts AI words per language. Neither allowance should be read as the size of the original website regardless of how many translations are added. (linguise.com)
Who should skip the purchase
We would postpone all three if the business can’t identify an additional-language audience or can’t answer enquiries in that language. A translated website should support a service the business is ready to deliver.
For a small initial experiment, consider commissioning a reviewed landing page before translating the whole site. Decide in advance what would justify expansion: relevant enquiries, completed consultations, or another business outcome. Our ranking doesn’t establish that any of these products will produce those results.
