Translating a WordPress site: WPML vs Polylang vs TranslatePress
WPML suits large sites and stores, Polylang lean content sites, TranslatePress small sites with visual editing. Prices as of October 2026.
By Sohail Hussain20 November 20266 min read
Choose WPML for large sites, WooCommerce stores, three or more languages, or work sent to translation agencies. Choose Polylang for content sites where editors work in the normal WordPress editor and you want little overhead; its free version handles a bilingual blog or brochure site. Choose TranslatePress for small sites where a non-technical editor wants to translate by clicking on the live page; its free version covers one extra language. All three handle Arabic and right-to-left text, provided the theme supports RTL.
We build bilingual WordPress sites as part of our Arabic and multilingual websites work. If you are still deciding whether WordPress suits the site at all, read WordPress for business websites first. The plugin choice matters less than how the site and the translation process are set up, which the guide to building an Arabic website covers. But the plugin is hard to change later, so it is worth choosing deliberately.
How do the three plugins work differently?
There are two models underneath.
One post per language. WPML and Polylang create a separate WordPress post or page for each translation and link them together. The Arabic "Services" page is its own page, with its own title, slug, content, featured image and custom fields. This is flexible: the Arabic page can have a different layout, an extra section or a different image. It also means more posts to manage, and a page built in a page builder is duplicated, so a design change has to be made in each language.
One page, translated strings. TranslatePress keeps a single page and stores a translation for each piece of text on it. When a visitor opens the Arabic URL, the plugin swaps each string for its translation as the page is generated. There is one layout to maintain, and editors translate by clicking text on the front end. The cost is flexibility: making the Arabic page structurally different from the English one is awkward.
For most bilingual company sites, where both languages show the same pages with the same structure, either model works. If the Arabic site will differ in content or emphasis, as it often does for Saudi-first businesses, the one-post-per-language model fits better.
What does each plugin cost?
Prices are per year, excluding VAT, as of October 2026, from each plugin's pricing page.
| Plugin | Free version | Paid plans |
|---|---|---|
| WPML | None | Multilingual Blog €39 (1 site, no string translation, page builders or WooCommerce); Multilingual CMS €99 (3 sites, with WooCommerce and page builder support and 22,500 AI translation words); Multilingual Agency €199 (unlimited sites, 45,000 words) |
| Polylang | Yes, the core plugin | Polylang Pro from €99; Polylang for WooCommerce from €99; Business Pack with both, €139 |
| TranslatePress | Yes, one translation language | Personal €99 (1 site); Business €199 (3 sites, adds DeepL); Developer €349 (unlimited sites) |
Check the current figures on the WPML, Polylang and TranslatePress pricing pages before you buy. Polylang's pricing page states that renewals are discounted. WPML states that the plugin keeps working if you stop renewing, but you lose updates, which on a live site you should not go without for long.
For most real business sites the realistic choice is WPML Multilingual CMS at €99, Polylang free or Pro, or TranslatePress free or Personal. WPML's Blog plan leaves out string translation, which is needed for theme text such as buttons and footer labels, so it rarely suits a business site.
How do they compare on the features that matter?
| WPML | Polylang | TranslatePress | |
|---|---|---|---|
| How translations are stored | Separate post per language | Separate post per language | Translated strings for each page |
| Translating in the page builder | CMS plan and above | Each language is its own builder page | Translated on the rendered page |
| WooCommerce | CMS plan and above | Paid add-on | Supported in the free version |
| Slugs per language | Each translation has its own slug | Own slug per post; Pro adds translated post type and taxonomy bases | Translated slugs in the paid SEO Pack |
| Machine translation | AI translation words included in CMS and Agency | Pro, with DeepL and your own API key | Google Translate with your own key; DeepL on Business and above; AI words included in paid plans |
| Translation management | Built-in workflow and agency integrations | Basic | Basic |
| Best fit | Large sites, stores, agencies, 3+ languages | Lean content sites | Small sites, visual editing |
The translation management row matters more than it looks. If the content is translated by an outside agency, WPML's job queue and agency integrations save a lot of copying and pasting. If one bilingual person in the client's team translates as they go, Polylang or TranslatePress is simpler.
What do you need to check for an Arabic site?
The theme must support RTL. All three plugins switch WordPress's locale per language. When the locale is Arabic, WordPress marks the page as right-to-left and loads the theme's rtl.css if it has one. If the theme has no RTL styles and uses left and right throughout its CSS, the Arabic pages will be laid out backwards in places. Test the theme in Arabic before you buy any plugin. The layout rules are in RTL web design.
The page builder must support RTL. The major builders do, but third-party add-on widgets often do not. Check sliders, tabs and icon lists.
The Arabic font is your job. None of the plugins choose or load an Arabic font. Add one in the theme for Arabic pages only; best Arabic web fonts has the options.
Check the hreflang output. All three write hreflang tags for translated pages. View the source of one English and one Arabic page and confirm that each lists both versions with full URLs. Compare against the output of our hreflang tag generator if in doubt.
Count the words before you choose a plan. If you plan to use included AI translation words for drafts, paste your main pages into a word counter. A 30-page site can exceed a smaller allowance on the first pass.
What goes wrong after launch?
Speed. Every translation plugin adds work to each page load. The one-post-per-language plugins add database queries; TranslatePress processes the page output to swap strings. On a site with good full-page caching, the difference is small. On a slow shared host without caching, a translation plugin can be what tips the site over. Speeding up WordPress covers caching.
Updates. Translation plugins hook into almost everything: posts, menus, widgets, WooCommerce, SEO plugins. Update them on a staging copy first, and check one page of each type in both languages afterwards. Updating WordPress safely has the routine.
Drift. The plugin makes it possible to keep both languages complete. It does not make it happen. Someone has to own the Arabic site, and every new English page needs a translation task before it goes live.
Lock-in. All three store data in their own ways, and switching between them later costs real work, so pick for the site you will have in three years rather than the one you have today. If each language is run by a separate team, a separate site per language on WordPress Multisite may suit better than any plugin; WordPress multisite explains when that makes sense.
Was this guide useful?