11 Best WordPress Translation Plugins: Free, Paid & AI
By DigitalBerg · Sources checked 7 November 2026
The best WordPress translation plugin depends on how you want to work. TranslatePress suits visual editing, WPML suits structured business and shop translation, Polylang suits teams writing separate language versions, and Weglot suits a managed cloud workflow. Free options can be useful, but a free download does not necessarily include automatic translation, multilingual SEO or commercial service rights.
This guide compares 11 options, including specialist tools that solve different parts of localisation. Recommendations are editorial judgements based on official documentation, not a hands-on performance test or an independent translation-quality benchmark. No plugin can guarantee rankings or fluent copy in every language.
Quick comparison: free, paid and AI translation plugins
“Managed AI” means the vendor integrates the translation service into its product; it does not mean a model runs locally on your server. “Own API” means you connect a provider account and manage its billing. “Manual” means people supply the translated text.
| Plugin | Cost model | Translation integration | Best fit |
|---|---|---|---|
| TranslatePress | Free + paid | Managed AI; own Google API; DeepL on eligible paid plans | Visual editing on a single WordPress site |
| WPML | Paid | Managed PTC AI on CMS/Agency; manual workflows | Content-heavy business sites and WooCommerce |
| Polylang | Free + paid | Manual free; Pro integrates your DeepL API key | Teams maintaining separate language content |
| Weglot | Limited free + subscription | Managed cloud AI and human editing | Fast rollout with a hosted translation workflow |
| GTranslate | Restricted free service + paid | Managed machine translation; paid corrections | Automatic translation with paid multilingual SEO |
| ConveyThis | Limited free + paid | Managed AI/machine translation and manual edits | Business sites wanting a hosted visual workflow |
| MultilingualPress | Paid | Integrated external services, including DeepL and OpenAI | WordPress Multisite and regional autonomy |
| Bogo | Free | Manual; no native AI documented | Small multilingual blogs |
| Multisite Language Switcher | Free | Manual linking; no native AI documented | Existing WordPress Multisite networks |
| Loco Translate | Free plugin; provider costs may apply | External APIs including DeepL, Google and OpenAI | Theme and plugin interface strings |
| Ray Enterprise Translation | Free connector; service terms apply | Cloud machine, community and professional workflows | Polylang teams evaluating a translation management system |
1. TranslatePress: best for visual translation editing
TranslatePress lets editors translate the rendered page from the front end. Its free edition supports the original language plus one translated language and currently advertises a 2,000-word TranslatePress AI allowance. You can also connect your own Google Translate API key. Premium add-ons include extra languages, the SEO Pack and DeepL integration; availability depends on the plan.
Pros: useful page context, manual corrections and locally stored translations. Cons: advanced SEO translation needs the premium SEO Pack; ongoing automatic translation needs enough allowance or provider budget. Use it for: a business website where an editor wants to see each translation in its layout. Sources: official listing and feature limits, vendor plans.
2. WPML: best shortlist for complex business sites
WPML combines multilingual content management with translation workflows. Its managed PTC service uses site context and terminology. AI is included with Multilingual CMS and Agency, not the entry Blog plan. CMS also includes translation management, string translation and e-commerce support.
Pros: structured team workflows and broad shop coverage. Cons: more configuration to evaluate; AI usage beyond the allowance adds cost. Use it for: a WooCommerce store or large business site needing coordinated translation. PTC quality statements are vendor claims, not comparative proof that it beats every other engine. Sources: WPML AI documentation, plan comparison.
3. Polylang: best for human-led multilingual publishing
Polylang is a strong candidate when your team wants to write and maintain separate language versions in WordPress. The free plugin provides the multilingual framework; Polylang Pro adds a DeepL integration requiring your own API key. The Pro page explicitly says it does not provide a one-click “translate everything” feature and notes limitations with Elementor and some builders.
Pros: familiar publishing workflow and a manual-first free starting point. Cons: API setup and separate provider costs for automation; WooCommerce needs the relevant commercial product. Use it for: editorial teams adapting articles for each market rather than translating every page automatically. Sources: free edition, Pro features and caveats.
4. Weglot: best for a managed cloud workflow
Weglot detects website content and manages translations through its cloud service. Its official listing describes AI translation with brand guidance, a visual editor and team review. Its pricing page lists language and translated-word limits; those limits matter more than the fact that the WordPress connector is free.
Pros: integrated automation and editing, with multilingual URL and metadata support. Cons: recurring service dependency; higher content volume or more languages can require a larger plan. Use it for: a marketing team prioritising a quick managed rollout. Check the specific plan for translated slugs and advanced features. Sources: official plugin listing, current pricing and limits.
5. GTranslate: understand the free-versus-paid difference
GTranslate offers automatic translation, but its listing reserves search-engine indexing, language-specific URLs and manual corrections for paid services. Its current free-service terms restrict use to specified non-commercial purposes; a business must not assume that the free plugin grants free commercial translation service use.
Pros: automatic translation and paid SEO delivery options. Cons: the free service is not equivalent to an indexable multilingual business website; review service terms before choosing it. Use it for: a paid automatic translation deployment after checking editing, URL and email requirements. Source: GTranslate’s official listing, permitted use and paid features.
6. ConveyThis: a hosted alternative for business websites
ConveyThis describes a managed AI and machine-translation service with visual editing, glossary controls and optional professional translation. Its official listing advertises a free plan of 10,000 words and one language, plus paid options. Treat that allowance as a service limit, not unlimited free localisation.
Pros: automatic content discovery and an integrated review workflow. Cons: hosted-service dependence and plan limits; verify the features available in your chosen account before migrating. Use it for: teams comparing hosted translation services for a business or shop site. Source: ConveyThis’s official listing.
7. MultilingualPress: best for a Multisite architecture
MultilingualPress uses a network approach, allowing language sites to operate separately. Its current vendor page lists integrated translation services including DeepL and OpenAI, plus language URLs and hreflang support. This is a different architecture from adding a translator to one ordinary WordPress site.
Pros: separate language sites and regional flexibility. Cons: Multisite administration takes more planning; confirm provider credentials, usage billing and integration scope before purchase. Use it for: a developer-managed network where countries need different content or site settings. Evaluate the current commercial product rather than assuming the old directory edition is equivalent. Source: MultilingualPress features and plans.
8. Bogo: best for a simple manually translated blog
Bogo assigns one language to each post and lets you create a copy to translate yourself. Its official description is explicit that copying does not perform the translation. It provides a language switcher and uses WordPress language packs.
Pros: a straightforward free option for a small editorial site. Cons: no native AI workflow documented; it is not a managed localisation service. Use it for: a bilingual blog with a writer who can produce both versions. Test menus, metadata and your theme’s output before committing. Source: Bogo’s official listing.
9. Multisite Language Switcher: best free linking tool for a network
Multisite Language Switcher connects translated content across an existing WordPress Multisite installation. Its listing covers posts, pages, custom post types and taxonomies. It supplies the relationship and switching layer, rather than a documented native AI translation engine.
Pros: free and suited to teams already running language sites in a network. Cons: people still need to create translations; hosting and maintaining multiple sites has an operational cost. Use it for: an established Multisite network needing language navigation. Source: official plugin listing.
10. Loco Translate: best for theme and plugin strings
Loco Translate edits translation files used by themes and plugins. Its official listing includes API integrations such as DeepL, Google, Microsoft and OpenAI. That is useful for interface text, but it does not make Loco a substitute for multilingual post management, language URLs and hreflang.
Pros: in-dashboard string editing and provider integrations. Cons: solves a narrower problem; external translation services may charge separately. Use it for: translating interface labels or maintaining PO/MO files alongside your wider multilingual strategy. Source: Loco Translate’s official listing.
11. Ray Enterprise Translation: specialist translation management
Formerly associated with the Lingotek name, Ray Enterprise Translation describes cloud workflows for machine, professional and community translation. The connector works with Polylang. Its listing advertises a free processed-word allowance, but confirm account availability, support and current service terms directly before building a new workflow around it.
Pros: translation profiles and managed hand-off workflows. Cons: a more complex service relationship than a simple plugin; plugin availability alone does not verify a working commercial account or SLA. Use it for: teams evaluating a translation management system with a vendor-led pilot. Source: Ray Enterprise’s official directory listing.
Which AI translation integration is better?
Choose the workflow before choosing a model. A managed service reduces account setup; an API integration gives you a direct provider relationship; a manual workflow gives editors control over the wording. Each still needs quality assurance.
| Approach | Examples | Advantage | Check before buying |
|---|---|---|---|
| Native product workflow with managed cloud AI | TranslatePress AI, WPML PTC, Weglot, ConveyThis | Translation and review in one workflow | Word allowances, overage charges, retention and export; “native” does not mean offline |
| Integrated third-party API | Polylang Pro with DeepL; TranslatePress with Google/DeepL; Loco provider APIs | Direct control of provider account and budget | API key storage, billing, language coverage and which content is sent |
| Manual translation | Bogo, Polylang free, Multisite Language Switcher workflows | Editors can rewrite for local audiences | Staff time, consistency and keeping changed pages synchronised |
Our recommendation: shortlist TranslatePress for visual control, WPML for managed structured workflows, and Polylang Pro if you specifically want your own DeepL account. Compare Weglot and ConveyThis when hosted management is the priority. These are workflow recommendations, not measured linguistic rankings.
For a meaningful quality comparison, translate the same service page, product with variations and FAQ into your actual target language. Give a fluent reviewer a checklist covering terminology, tone, numbers, placeholders and calls to action. Record correction time and total cost. A generic “AI-powered” badge tells you less than this small pilot.
Verified pricing snapshots and the real cost of translation
These figures were visible on official pages checked on 7 November 2026. They are snapshots, not quotations or guaranteed renewal prices. No GBP conversion has been estimated. Confirm taxes, renewal terms, site limits and checkout totals before purchasing.
| Product | Observed price | Important scope |
|---|---|---|
| TranslatePress Personal | €99 billed yearly | 1 site; listed 50,000 AI-translated words. Check tax treatment at checkout. |
| WPML | Blog €39; CMS €99; Agency €199 | Each lists one year of updates/support. Blog excludes AI; CMS lists 22,500 AI words, Agency 45,000. Verify tax and renewal total. |
| Polylang Pro | From €99/year | DeepL requires your own API key; provider charges are separate. Verify selected licence and tax. |
| Weglot Starter | €15/month or €150/year, excluding VAT | 10,000 total translated words; 1 translated language. Free tier lists 2,000 words and 1 translated language. |
| MultilingualPress Starter | €149 annually, shown including VAT | 2 languages; 1 WordPress installation. Confirm translation-provider costs separately. |
For other paid services, use the official product links above for an account-specific quote rather than relying on an unverified starting price. Budget for licence or subscription, machine translation usage, human review, migration and maintenance. A 20,000-word site translated into three additional languages can involve roughly 60,000 target-language words before updates; vendors may count words or credits differently.
Real interface screenshots from official sources
The following are attributed links to genuine publisher-supplied screenshots. They are not DigitalBerg test captures. Reuse permission has not been established, so the images are linked at their official source rather than copied or hotlinked. The publisher’s gallery may show a different version from today’s interface.
- TranslatePress screenshot gallery — Cozmoslabs: view the front-end editor, WooCommerce translation and settings screenshots.
- Loco Translate screenshot gallery — Tim Whitlock: view the PO editor, translation progress and provider suggestions.
- Bogo screenshot gallery — Rock Lobster Inc.: view the post Language box and language-pack screen.
Multilingual SEO: what to verify beyond the plugin
A translation switcher alone is not an international SEO strategy. Build useful local versions of your most valuable pages first, then verify the output:
- Separate crawlable URLs: each indexable language page needs a stable address. Check the rendered page, HTTP status, robots directives and sitemap inclusion.
- Correct language relationships: inspect hreflang links, including return links and the page’s own language entry. Use supported language and region codes. Follow Google’s guidance for localised versions.
- Canonical URLs: inspect them alongside hreflang. Avoid accidentally canonicalising every distinct language page to the English page.
- Localised metadata: review titles, descriptions, headings, slugs where supported, descriptive image alt text and social metadata. Research how customers search locally rather than translating keywords mechanically.
- Complete customer journeys: test navigation, forms, validation messages, checkout, account pages and transactional emails. Product translation does not automatically verify every third-party checkout extension.
- Useful structured data: translated Article, Product or Service data must describe visible content accurately. Do not add product ratings or offers to this comparison without evidence.
Start on staging with a backup. Check mobile layout, right-to-left languages, longer text and cache behaviour. Benchmark representative translated pages before and after installation. If you are reviewing infrastructure, compare DigitalBerg SSD web hosting and Cloud VPS hosting against your actual workload; a plugin name alone cannot determine hosting requirements.
A practical selection and launch plan
- List target languages, page count, WooCommerce extensions, builder, editorial team and budget.
- Pick two candidates with the right architecture. Test one full customer journey on staging.
- Set a glossary and choose which content can be sent to external translation services. Review service data terms for your use case.
- Have a fluent reviewer approve your landing pages, products and checkout. Keep new languages unpublished until ready.
- Check URLs, metadata, language links, structured data and performance, then monitor indexing and conversions by language.
Need help choosing infrastructure for a multilingual WordPress site? Contact DigitalBerg with your languages, traffic expectations and plugin shortlist.
Frequently asked questions
What is the best free WordPress translation plugin?
For a human-led site, shortlist Polylang or Bogo. For visual editing, try TranslatePress free within its language and AI allowance limits. Multisite Language Switcher fits an existing network. The right choice depends on whether you need manual publishing, automation or indexable translated pages.
Which plugin is best for AI translation?
WPML PTC, TranslatePress AI, Weglot and ConveyThis offer managed translation workflows. Polylang Pro integrates your own DeepL account. Compare them using your target languages, glossary, review time and total cost; this guide does not establish an independent quality winner.
Does Loco Translate translate a whole WordPress website?
Loco Translate primarily handles theme and plugin translation files. It is useful for interface strings, but does not replace the multilingual content and URL management required for a complete multilingual website.
Can free GTranslate help a commercial website rank in other languages?
Do not assume so. Its listing places indexing and SEO URLs among paid features and restricts free-service use to specified non-commercial purposes. Review the current permitted-use terms and paid plan before deploying it on a business site.
Do I need FAQ schema for this article?
No. Visible FAQs can still help readers. Google’s current documentation changelog says FAQ rich results stopped appearing from 7 May 2026. This article therefore omits FAQPage structured data and uses Article and BreadcrumbList instead. See Google’s official documentation updates.
How this comparison was researched
DigitalBerg checked the official plugin listings, vendor feature pages and public pricing linked throughout this article on 7 November 2026. Features and service terms can change. No affiliate tracking links were added. Specialist tools are labelled by purpose so that a string editor or network switcher is not mistaken for a complete automatic website translator.
We excluded Transposh from the recommended shortlist because its official WordPress.org listing is closed for a security issue. The Hostinger comparison was used only as topic inspiration; this article’s wording, workflow analysis and selection are original.
Leave a Reply
Want to join the discussion?Feel free to contribute!