WordPress can translate posts now. Keep paying for WPML?

The official WordPress AI plugin added Content Translation on August 18, 2026, and the headline reads like the end of an era for paid multilingual plugins. It is not. The feature translates paragraph and heading blocks inside the editor into a language you pick. That is one part of a multilingual site, and it is not the part you were paying for.

The distinction is worth ten minutes before your next renewal. Translation and multilingual are different jobs, and WordPress core now does one of them.

What does WordPress Content Translation actually do?

It translates blocks in the editor, one post at a time. Content Translation is an experiment in the canonical WordPress AI plugin that translates paragraph and heading blocks into a selected language using whichever AI provider the site has configured (AI plugin on WordPress.org).

That scope is narrower than it sounds. It is an editorial aid inside the block editor, sitting beside slug generation, alt text and content classification (AI team release notes). It is also labelled an experiment. In this plugin that means it can change shape between monthly releases.

The plugin's requirements matter too. It needs WordPress 7.0 or higher, PHP 7.4 or higher, the block editor rather than the classic editor, and at least one AI connector plugin with valid API credentials. Sites still on the classic editor get nothing from it.

What does a multilingual plugin do that this does not?

Everything around the words. A multilingual plugin is one that gives a site a language structure: separate URLs per language, a switcher, translated taxonomies, and the hreflang tags that tell search engines which page serves which locale.

Here is the split, feature by feature:

Job	AI plugin Content Translation	WPML or Polylang
Translate the words in a post	Yes, block by block	Yes
Separate URL per language	No	Yes, as subdirectory, subdomain or domain
hreflang tags for search engines	No	Yes
Language switcher for readers	No	Yes
Translated categories and tags	No	Yes
Translated menus and widgets	No	Yes
Translation memory or workflow	No	Yes, on paid tiers
Cost	Your API tokens	$39 to $199 a year, plus tokens

The hreflang row decides the answer for most sites. The hreflang attribute is the markup that tells a search engine a page has equivalents in other languages, so the right version is served to the right reader. Without it, translated pages compete with one another instead of being understood as a set, which is the exact outcome anyone translating a site is trying to buy.

Which paid tier does the AI plugin actually threaten?

The automatic translation credits, not the plugin licence. That is the honest reading of the price lists.

WPML sells three annual tiers. Multilingual Blog is $39, Multilingual CMS is $99, and Multilingual Agency is $199 for unlimited sites. The CMS tier is the popular one. It bundles 90,000 automatic translation credits along with string translation and the translation management screens (WPML automatic translation pricing). Polylang takes a different shape: the free plugin already covers posts, pages, media, categories, tags, menus, widgets, the language switcher, URL structure options and XLIFF import and export, while Polylang Pro at EUR 99 per site per year adds DeepL machine translation with your own API key, professional support and ACF Pro integration (Polylang Pro pricing).

Read the two lists side by side. The overlap is narrow and specific. The AI plugin competes with WPML's translation credits and with Polylang Pro's DeepL integration. It does not compete with the multilingual framework in either product, because it does not have one.

Should I cancel my renewal?

Only in one configuration, and it is a real one. Consider a small site running free Polylang for structure, with a modest number of posts, whose only reason for a paid licence is machine translation. That site can plausibly drop to free Polylang plus the AI plugin and pay per token instead of per year.

The decision in order:

1. Are you on free Polylang for a paid translation add-on? This is the case where switching is worth modelling. Price your token spend against the licence.
2. Are you on WPML for the workflow? Keep it. Translation management, string translation and the visual editor have no core equivalent.
3. Do you need translated categories, menus or hreflang? Keep the multilingual plugin. The AI plugin does not produce any of them.
4. Are you on the classic editor? The AI plugin does not apply at all.
5. Do you translate a handful of posts a year? The AI plugin alone may be enough, if the translated posts live as ordinary posts and you accept no language routing.

Token spend is easy to underestimate here. Translation output is as long as its input, and output tokens cost several times input on every major provider. It is the one AI feature whose per-item cost is meaningful rather than rounding error, and the cheapest AI API is not the cheapest to run when the output is a whole article.

What about translation quality and data handling?

Quality depends on the model you configured, because core supplies none. For example, a budget model and a frontier model reach the same button through the same connector interface (AI Client announcement). The plugin routes through whichever connector you installed, and no quality label is attached to the result.

That differs from a dedicated machine-translation integration. There the engine is fixed, and its behaviour on your language pair is documented. With the AI plugin the burden of testing moves to you. Translate three representative posts, read them with a native speaker, and only then run anything in bulk.

Data handling deserves the same scepticism. Your content leaves the site for the provider you configured, under that provider's terms, which is a question worth answering before an archive goes through it. Does the free AI API tier train on your data? For paid API tiers the answer is usually no, but it is set by the provider's policy rather than by WordPress.

Translation is a feature. Multilingual is a system

The reason this comparison keeps getting made badly is that both things are called translation. One is turning English words into German words. The other is running a site that serves German readers a German URL, a German menu and a German category page, and tells Google how those relate to the English ones.

WordPress core now helps with the first. Everything in the second column is still someone else's plugin. If your licence renewal is only buying machine translation, price the alternative honestly this month. If it is buying the system, the announcement changed nothing for you.