GTranslate and Weglot are two of the most widely used translation plugins for WordPress, and on the surface they promise the same thing: a multilingual site, no code, live in an afternoon. Look a little closer and they're built on different economics — one charges for features and leaves your word count alone, the other charges by how much you translate and into how many languages. This is a neutral, side-by-side read of GTranslate vs Weglot for WordPress: how each one works, what they cost as you grow, how they handle SEO, and a simple way to tell which fits your site.
Everything below is drawn from each vendor's public pricing and documentation and from independent reviews, dated where it matters. Figures were checked in June 2026; pricing pages change, so confirm the current numbers on each vendor's site before you buy. The aim isn't to crown a winner — both are good at the job they're built for — but to make the trade-off legible so you can choose on fit.
In this guideBoth are no-code, hosted (SaaS) translation plugins with large WordPress user bases and machine translation at their core. The differences that decide most cases are the pricing model, how each treats word volume, and what comes included on the lower plans.
| GTranslate | Weglot | |
|---|---|---|
| Translation engine | Google neural machine translation; manual editing on paid plans | First-layer machine translation from DeepL, Microsoft, Yandex or Google by language pair; visual editor and access to professional translators |
| Pricing model | Flat monthly tiers; unlimited words and page views on every plan | Subscription priced by translated words × number of languages |
| Free option | Free-forever plan: unlimited words, but no search-engine indexing and no editing | Free plan: up to 2,000 words in one language, then a paid plan |
| Paid entry price | From $9.99/mo (billed monthly) | From €15/mo (≈ $17), billed annually |
| SEO / indexing | Server-side and indexable on paid plans; the free plan is not indexed | Server-side, indexable, with dedicated URLs and hreflang — included from the entry paid tier |
| Where translations live | On GTranslate's servers | On Weglot's servers |
| Often the better fit for | High-volume or fast-growing content on a contained budget | Editing control and translation quality on a defined set of languages |
Both install without touching your theme and add a front-end language switcher, so the day-one experience is similar. What differs is what happens underneath.
GTranslate installs from the WordPress.org directory — the "Translate WordPress with GTranslate" plugin has a large installed base and a high user rating — and renders your site through Google's neural machine translation into 100-plus languages. The free plan adds a language selector and machine translations with no cap on words or page views, but those pages aren't search-indexed and you can't edit the output. Paid plans add manual editing, search-engine indexing, translated URL slugs (from the Business tier) and the option to host languages on custom subdomains or domains (the Enterprise tier).
Weglot connects your site to its service, detects your content automatically, and lays down a first machine-translation pass — drawing from DeepL, Microsoft, Yandex or Google depending on the language pair — which you then refine in a visual editor that shows changes on a live preview of your page, or hand to professional translators booked through the dashboard. Multilingual SEO is set up for you: each language gets dedicated URLs and hreflang tags so the translated pages can be indexed and rank.
This is where the two genuinely diverge, and it's the single most useful thing to understand before you choose.
GTranslate charges for features, not volume. Every plan — including the free one — carries unlimited words and page views, so a large blog or a deep catalogue doesn't push the bill up. What you pay more for is capability: paid tiers run from $9.99/mo (a configurable "Custom" plan) through $19.99 (all languages, with indexing and editing), $29.99 (adds translated URLs) and $39.99 (adds language hosting on custom domains). Billing is monthly or annual, with annual saving roughly two months.
Weglot charges for volume. The subscription scales with the total number of translated words across your site and the number of languages you translate into, and the word allowance is a fixed total rather than a monthly refill. Plans start at €15/mo and the language caps step up unevenly, so adding one more language or growing your content can move you to the next tier regardless of the other dimension. Prices are in euros, so the dollar figure moves with the exchange rate.
On their paid plans, both plugins serve translated pages that search engines can crawl and index — real URLs per language with hreflang — which is what lets those pages rank rather than sitting behind a browser-only switch. The one documented exception is GTranslate's free plan, which isn't indexed and is meant for visitors switching language by hand; anyone who needs multilingual SEO will be on a paid GTranslate tier or on Weglot.
There's a second point worth knowing because it's structural, not a flaw in either tool: both are hosted services, so your translations live on the vendor's servers rather than in your own WordPress database. If you stop subscribing, the translated pages stop serving. That's the trade-off of the hosted model and it applies to both equally; plugins that store translations in your database (for example WPML or TranslatePress) make a different trade in the opposite direction. And because both work by translating the HTML that reaches the browser, content that never renders to a public page — WooCommerce transactional emails like order and shipping notifications, for instance — sits outside what either one translates.
The honest question isn't which plugin is better. It's whether your bill should scale with your feature list or with your word count.
— Choosing on fit, not on winnerRead it off your own site rather than off a ranking.
One thing both plugins share: their job is translation — making the WordPress site readable in another language. If the underlying goal is selling into a new market rather than only translating, that's a wider set of needs than a translation plugin covers, including localized SEO that ranks in-country, prices in local currency, duties and taxes at checkout, and local payment methods. That's a different category of tool — platforms such as Glopal, which has worked in cross-border e-commerce localization since 2007, sit there rather than alongside GTranslate and Weglot. If you're weighing the full picture, our rundown of the best Weglot alternatives for e-commerce lays the options out side by side.
A side-by-side of the tools that translate a site — and the platforms built for the whole cross-border journey.
Compare Weglot alternatives