At a glance
WPML
WordPress plugin, one post per language
€39 a year
A yearly licence by number of sites. AI translation counts source words once per target language; after the included words and 500 free words a month, pay as you go from €3.00 per 1,000 words, down to €0.40 with volume. Free: No free plan. 30-day money-back guarantee. Checked 7 October 2026.
What it does well
- Each translation is a WordPress post in your own database, linked to the original.
- Translations keep showing on your site if you stop renewing.
- Review controls: hold AI translations as drafts for a Translation Manager, or publish and queue them for review.
- hreflang with x-default in the page head and in Yoast or Rank Math sitemaps, with settings for translated slugs.
- Translates page builder designs, such as Elementor, and WooCommerce sites with popular extensions.
- Multiple currencies and payment gateways for WooCommerce stores.
- Sends content to more than 70 professional translation services from the WordPress admin.
- Its own LLM-based engine, PTC, that learns from the edits you make.
The WPML alternatives worth a look split into three groups. Polylang keeps WPML's model of one WordPress post per language at a lower entry price. TranslatePress and LangRelay keep a single post and translate the page WordPress renders. Weglot and Linguise are hosted services that take the translation work off your server altogether. Which group fits depends on what made you look beyond WPML.
I build LangRelay. What follows about WPML and the four other vendors is as their own sites stated it on 7 October 2026.
Why sites move off WPML#
WPML stores each translation as a WordPress post linked to the original, translates page builder layouts and WooCommerce stores on its CMS and Agency plans, and can hold AI translations as drafts for a Translation Manager to approve. Its translations also keep showing on your site if you stop renewing. The reasons people look elsewhere come from the same design.
A post per language multiplies the content you maintain. A site with 40 pages, each translated into four languages, holds 200 posts, and a layout change made to an original has to reach the four posts that translate it. With Translate Everything Automatically switched on, WPML picks up edits and translates them; without it, you send each change to translation yourself.
Price is the other reason. WPML has no free plan, and its prices exclude VAT. Multilingual Blog costs €39 a year for one production site but leaves out AI translation, the Advanced Translation Editor, String Translation and WooCommerce support. Multilingual CMS, at €99 a year for three production sites, includes 22,500 AI words. Past those and the 500 free AI words WPML gives each month, AI translation is pay as you go, priced in monthly volume bands: €3.00 per 1,000 words for the first 2,000 paid words in a month, falling band by band to €0.40 only past 2,500,000 words in a month.
The alternatives, side by side#
Each vendor's entry price as listed on its own pricing page on 7 October 2026.
Polylang: the same model for less#
Polylang keeps WPML's model of a post per language and has a free version. The free plugin on WordPress.org has no limit on the number of languages and supports a subdirectory, subdomain or separate domain per language. Each translation is again its own post, so the maintenance cost of a post per language stays.
The gap is machine translation. Polylang Pro, from €99 a year for one site, connects to DeepL with your own API key and translates one post, page or product at a time. Polylang's DeepL guide says the integration does not work with content built in Elementor, Divi and some other page builders, and that editing the original does not update its DeepL translation. WooCommerce needs a separate add-on, Polylang for WooCommerce, from €99 a year, which works with the free plugin or with Pro. If you translate by hand anyway, the free plugin may be all you need. The WPML vs Polylang comparison goes through the two plugin by plugin.
TranslatePress and LangRelay: one post per page#
Both of these leave your posts alone and translate what WordPress renders, so a layout change made once applies to every language.
TranslatePress stores each translation in its own database tables, one string at a time, and its front-end editor lets you translate on a live preview of the page, even in the free version. Paid plans start with Personal at €99 a year, which includes 50,000 TranslatePress AI words, its SEO Pack for translated slugs and metadata, and as many languages as you add. If the licence expires, TranslatePress's FAQ says the plugin keeps working as configured, without its AI. I found no approval step for single translations on TranslatePress's site; with automatic translation on, a new string is translated the first time a visitor opens the page in that language.
By default LangRelay puts a translation live as soon as it is ready, and free checks hold a page with untranslated text, the wrong language or a changed price. To approve every page yourself, as WPML can be set to do, choose Ask me first. Its plugin tells LangRelay about each edit roughly a minute after it is saved, only the new text is translated, and Relay, a built-in agent, drafts the changes you ask for in plain language. During the pilot LangRelay translates between nine languages, against WPML's 65 pre-configured ones, it does not write a multilingual XML sitemap, and translated slugs are set by hand.
Weglot and Linguise: hosted translation#
A hosted service keeps translations off your WordPress database. Weglot stores them in its own database and charges by the total number of translated words your site holds across languages, a total that does not renew: Starter is €15 a month for one language and 10,000 words. Linguise charges per domain, counts source words times languages, and sells 200,000 words on START for $15 a month with no limit on languages. Both suit a site owner who would rather not run translation inside WordPress at all. By default, neither holds a new translation back for approval.
A worked example: what one edit costs#
Say you rewrite a 300-word section of a 2,000-word page translated into three languages, and the page ends up the same length. A worked example, using each vendor's documented rules.
WPML's rule makes it cheap to keep an existing page current, and that is worth weighing before you leave. It applies only with Translate Everything Automatically and PTC; WPML's pricing page says every other path pays per updated word. The cost of WPML shows up on new pages and on sites that need more AI words than a licence includes.
Before you switch#
Moving from WPML to another post-per-language plugin means checking how the new plugin will link the posts WPML created, since WPML records those links in its own database tables. Moving to a one-post tool means the translated posts WPML created become unused content, and the new tool builds its translations from the originals. Either way, list the translated slugs you rely on first, so you can set the same URLs again.
For a closer look at the pairs, read TranslatePress vs WPML, Weglot vs WPML and LangRelay vs WPML. The Polylang alternatives page covers the next step if Polylang's manual workflow is the sticking point.
WPML and LangRelay side by side
From each vendor's own pages, on the dates in the sources below.
| Capability | LangRelay | WPML |
|---|---|---|
| Delivery and SEOHow translated pages reach visitors and search engines. | ||
| How translated pages are servedHow the translated page reaches visitors: from your own server, through a proxy, or swapped in by the browser. | Yes: WordPress plugin serves translated HTML from your server. A script tag works on any other site, without SEO. | Yes: WordPress plugin. Translations are WordPress content served by your site, in directories, (sub)domains or a ?lang= parameter. Source, checked 7 October 2026 |
| WordPress: one post, no copies per languageWhether WordPress keeps one post per page, instead of a separate copy for every language. | Yes: Translates the rendered page. Your posts stay as they are. | No Each translation is its own WordPress post, linked to the original. Source, checked 7 October 2026 |
| hreflang and per-language URLsA URL per language with hreflang tags, so search engines find and index each language. | Yes: Subdirectories (/fr/), hreflang with x-default, a canonical per language, and translated titles and meta. | Yes: hreflang with x-default in the page head and in Yoast and Rank Math sitemaps. Source, checked 7 October 2026 |
| Translated URL slugsURLs in the visitor’s language, like /fr/a-propos instead of /fr/about. | Partly Set by hand per page and language. Automatic slug translation is on the way. | Yes: Translated by default, and editable. Source, checked 7 October 2026 |
| Workflow and reviewWhat happens when content changes, and who decides what goes live. | ||
| Picks up edits to the originalWhen you edit the original page, whether the tool notices and translates what changed. | Yes: The WordPress plugin reports an edit about a minute later, and only the new text is translated. Other sites can call a change hook from their CMS or deploy. | Yes: With Translate Everything Automatically on, new posts and edits are picked up and translated. Otherwise you send them to translation yourself. Source, checked 7 October 2026 |
| Approve before it goes liveWhether a person can check a translation before visitors see it. | Yes: When you choose Ask me first. By default pages go live as they are ready, and free checks hold a page with untranslated text, the wrong language or a changed price. Legal pages, pricing pages and sweeping changes always wait for you. | Yes: PTC can publish at once, hold drafts for a Translation Manager’s approval, or publish and queue for review. Source, checked 7 October 2026 |
| Visual editorEditing translations on the page itself, rather than in a list of strings. | Yes: Click text on the rendered page to edit, at desktop, tablet and mobile widths. | Partly The Advanced Translation Editor is side by side, with a front-end preview you can click to edit. Not on the Blog plan. Source, checked 7 October 2026 |
| GlossaryFixed translations for names and terms, applied every time they appear. | Yes: Per-language terms, “keep as source”, and match case. Paid plans. | Yes: Glossary for product names and terms to keep untranslated, with PTC and DeepL. Source, checked 7 October 2026 |
| AI and integrationsHow much of the work AI takes on, and how you reach it. | ||
| Machine translationThe machine or AI translation the tool uses. | Yes: AI translation that follows your glossary and each language’s formality. | Yes: PTC, WPML’s own LLM-based engine, by default. DeepL, Google and Microsoft remain as legacy engines. Source, checked 7 October 2026 |
| AI quality reviewAI that checks translations for mistakes, not only writes them. | Yes: Relay reviews any page you ask it to, the way a language expert would, quoted in AI credits first. It reviews legal pages, pricing pages and sweeping changes on its own while you have AI credits. | Partly PTC learns from your repeated edits and suggests fixes. No separate reviewer found. Source, checked 7 October 2026 |
| AI assistant in the productAn assistant inside the product that you can ask in plain language. | Yes: Relay, a chat agent that reads your Site’s pages and translations and drafts changes for your approval. | Not found No chat assistant found. |
| MCP server for your own AILets your own AI assistant, such as Claude or ChatGPT, work with the tool directly. | Planned On the way: connect Claude or ChatGPT to your Sites. | Not found Not found on wpml.org. |
| APIProgrammatic access for developers. | Planned On the way, for the Growth plan and up. | Partly PHP filter and action hooks for themes and plugins. No public REST API for site translation found. Source, checked 7 October 2026 |
- No · Not offered
- Partly · With a limit
- Planned · Announced, not shipped
- Not found · Not on the vendor’s own pages when we checked
- Yes · Included
Where the table comes from
WPML
- wpml.org/documentation/customizing-wpml/ai-translation-settings/ (checked 7 October 2026)
- wpml.org/documentation/support/wpml-coding-api/ (checked 7 October 2026)
- wpml.org/documentation/translating-your-contents/posts-and-custom-post-types/ (checked 7 October 2026)
- wpml.org/documentation/getting-started-guide/language-setup/language-url-options/ (checked 7 October 2026)
- wpml.org/documentation/translating-your-contents/glossary/ (checked 7 October 2026)
- wpml.org/documentation/translating-your-contents/multilingual-seo/ (checked 7 October 2026)
- wpml.org/home/how-to-build-a-multilingual-wordpress-website/ (checked 7 October 2026)
- wpml.org/documentation/support/wpml-tables/ (checked 7 October 2026)
- wpml.org/documentation/translating-your-contents/advanced-translation-editor/ (checked 7 October 2026)
- app.wpml.org/purchase (checked 7 October 2026)
- wpml.org/documentation/getting-started-guide/language-setup/ (checked 7 October 2026)
- wpml.org/documentation/translating-your-contents/multi-currency-and-payment-gateways-for-woocommerce/ (checked 7 October 2026)
- wpml.org/documentation/translating-your-contents/professional-translation-via-wpml/ (checked 7 October 2026)
- wpml.org/documentation/automatic-translation/automatic-translation-pricing/ (checked 7 October 2026)
Product names and logos belong to their owners; shown to identify them for comparison, no affiliation or endorsement.
Sources
The pages this one cites, with the day each was read.
- 01WPML, Purchaseapp.wpml.org, checked 7 October 2026
- 02WPML documentation, Automatic translation pricingwpml.org, checked 7 October 2026
- 03WPML documentation, Database tableswpml.org, checked 7 October 2026
- 04WPML documentation, AI translation settingswpml.org, checked 7 October 2026
- 05WPML documentation, Translating posts and custom post typeswpml.org, checked 7 October 2026
- 06Polylang on WordPress.orgwordpress.org, checked 7 October 2026
- 07Polylang, Polylang Pro pricingpolylang.pro, checked 7 October 2026
- 08Polylang, Pricingpolylang.pro, checked 7 October 2026
- 09Polylang documentation, How to use DeepL machine translation with Polylang Propolylang.pro, checked 7 October 2026
- 10TranslatePress on WordPress.orgwordpress.org, checked 7 October 2026
- 11TranslatePress, Pricingtranslatepress.com, checked 7 October 2026
- 12TranslatePress, Frequently asked questionstranslatepress.com, checked 7 October 2026
- 13TranslatePress documentation, TranslatePress AItranslatepress.com, checked 7 October 2026
- 14Weglot, Pricingweglot.com, checked 7 October 2026
- 15Weglot Help Center, What is the number of translated words and how is it calculated?support.weglot.com, checked 7 October 2026
- 16Weglot, Technical presentationweglot.com, checked 7 October 2026
- 17Linguise, Priceslinguise.com, checked 7 October 2026
- 18Linguise, WordPress automatic translation pluginlinguise.com, checked 7 October 2026
- 19Linguise documentation, Edit translations using the front-end editorlinguise.com, checked 7 October 2026
- 20WPML documentation, Language setupwpml.org, checked 7 October 2026
- 21Weglot, AI translation qualityweglot.com, checked 7 October 2026
- 22Polylang, Polylang for WooCommerce pricingpolylang.pro, checked 7 October 2026
- 23Polylang, Homepolylang.pro, checked 7 October 2026
- 24Linguise, Homelinguise.com, checked 7 October 2026




