WordPress Now Has AI Built In. Can It Translate Your Site?

WordPress 7 added AI to core, and the WordPress.org AI plugin can translate a post. Here's what it does, what it doesn't, and what a multilingual site needs.
Get started
Take the tour
No card details No commitment

· Alex B · Blog

Summarize this post with: 10 min read
ChatGPT ChatGPT Perplexity Perplexity Grok Grok Google AI Google AI

WordPress 7.0 shipped on May 20, 2026 with something new in core: a built-in way for WordPress to talk to AI models. Three months later, the AI plugin published by WordPress.org added a translation feature.

So if you run a WordPress site and you’ve been meaning to add a second language, it’s a fair question. Do you still need a translation plugin, or can WordPress do it now?

The short answer: WordPress can now translate text. It still doesn’t build a multilingual site. Those are different jobs, and the gap between them is where most of the work lives.

Here’s what changed, what didn’t, and how to decide.

Key Takeaways

WordPress 7.0 added AI infrastructure to core, not a translation feature. You need a provider plugin and an API key before any AI works.

The WordPress.org AI plugin translates paragraphs, headings and the title of one post, replacing the original text in the editor.

Language URLs, hreflang, a language switcher and WooCommerce translation still need a translation plugin.

What did WordPress 7.0 actually add?

WordPress 7.0 “Armstrong” added an AI Client: a common, provider-agnostic way for plugins to send requests to AI models. It also added a Connectors screen under Settings → Connectors, where site owners manage connections to AI providers such as Anthropic, Google and OpenAI.

That’s real progress. Before 7.0, an AI plugin typically had to bring its own settings, its own key storage and its own way of calling a model. Now there’s one shared layer.

But it’s a layer, not a feature. The WordPress core team is explicit about this in its developer note:

“WordPress Core does not bundle any AI providers directly.”

To actually use AI, you install a provider plugin (for example, AI Provider for OpenAI), add an API key from that provider, and then install a plugin that does something with it. The 7.0 release post itself points readers to a separate AI plugin for features like generating titles, excerpts and alt text. WordPress 7.1 “Mary Lou”, released on August 19, didn’t add a translation feature to core either.

In other words, WordPress 7 gave plugins a shared way to reach AI. What your site does with it still depends on the plugins you install.

Can the official WordPress AI plugin translate my site?

It can translate a post, which isn’t the same thing. In August 2026, version 1.3.0 of the AI plugin from WordPress.org added a Content Translation experiment. In the words of its release post, it “lets editors translate content without leaving the post editor.” The plugin as a whole is labeled experimental, so its features may change.

Here’s how it works, according to the WordPress AI team:

  • It translates Paragraph and Heading blocks, plus the post title if you choose.
  • The translation replaces the original content in the editor, where you can review and adjust it before publishing.
  • In late August the team noted there’s no built-in glossary. Version 1.4.0 (October 5) lets translations draw on WordPress editorial “guideline categories”, but it isn’t documented yet whether these can lock specific terms.

That’s useful for one specific job: you wrote a post in one language and you want a draft of it in another. Translate, review, publish.

It isn’t built for running a site in two languages. Your original isn’t necessarily lost: you can undo the change, or restore an earlier revision. But the post still holds one language at a time. To offer English and Spanish side by side, you’d have to copy the post, translate the copy, publish both, and link them yourself, for every page you want in both languages.

This is the key distinction. AI is the engine that turns one sentence into another. A multilingual site is everything built around that engine: a separate, findable version of each page for each language, so every audience can reach its own.

Translated text vs. a multilingual site: what’s the difference?

According to W3Techs, WordPress runs 40.0% of all websites as of October 14, 2026. If your readers speak more than one language, serving them properly means building a structure around the translation, and that structure is exactly what an AI model doesn’t provide.

Here’s what a multilingual WordPress site needs, and where each piece comes from:

What you needWordPress 7 + AI pluginConveyThis
Translate text with AIYes Paragraph and heading blocks, plus the title, one post at a timeYes Pages across the site, within your plan's word limit
Keep the original language liveNo One post holds one language unless you duplicate itYes Every language lives side by side
A separate URL for each language (/es/, /de/)No You'd create and link copies yourselfYes Subdirectories or subdomains
hreflang tagsNoYes Added automatically
Translated page titles and meta descriptionsPartly Post title onlyYes Including social sharing tags
A language switcher for visitorsNoYes Customizable
Menus, widgets, forms and image captionsNoYes
WooCommerce products, cart and checkoutNoYes
Glossary to lock brand and product termsNot built inYes
New content translated without extra stepsNo You translate post by postYes New pages are translated automatically
Edit translationsYes In the post editorYes In a visual editor on the live page

Each of those rows is something site owners tend to discover later. Search engines need a separate URL to index each language version, like this:

example.com/about example.com/es/about example.com/de/about

Google recommends “using different URLs for each language version of a page rather than using cookies or browser settings,” partly because its crawler doesn’t request a particular language. If the language changes on one URL, Google may only ever see one version.

hreflang tags then tell search engines which URLs are language versions of the same page, so results can link to the right one. They aren’t a ranking boost on their own, but without them Google has to work out from other signals which version to show each searcher. And a product page in German isn’t much use if the checkout is still in English.

If you want the SEO side in more depth, our complete guide to hreflang tags walks through how search engines pick the right language version.

Is multilingual support coming to WordPress core?

Eventually, but there’s no date. Multilingual support is Phase 4 of the official WordPress roadmap, described as “Core implementation for Multilingual sites.” The roadmap gives no target release for it.

WordPress 7.2 is planned for December 2026, timed to the annual State of the Word address. The official 7.2 planning posts don’t list multilingual among its features. You may have seen articles saying multilingual support arrives in 7.2. We couldn’t find any official source that says so.

When core multilingual does arrive, it will most likely be a foundation, much like the AI Client is today, with plugins building on top of it. We plan to build on it too.

Until then, waiting for core means waiting an unknown amount of time. If your visitors need another language now, they need it now.

Who is actually translating WordPress sites?

Not who you might expect. In its State of the Word 2025 recap, WordPress.org reported that “over 56% of WordPress sites now run in languages other than English.”

We see a similar pattern from the other side. We looked at the several hundred WordPress sites that recorded page views through ConveyThis between October 1 and 14, 2026, using each site’s platform, source language and target languages as set in ConveyThis:

Source language

56% not English

Most often German, Dutch, Spanish and French.

Most-added language

English, on 1 in 2

Then Spanish (23%), French (16%) and German (14%).

Typical site

About 2 languages

Most sites add one or two languages, not ten.

Our finding

For many WordPress owners, translation isn't about reaching Spanish speakers in the US. It's often a European business translating into English to reach a wider market, or an English site adding one or two neighboring languages. Either way, the original language has to stay live alongside the translation.

So which should you use?

It depends on the job.

One post

WordPress AI plugin

Best when you wrote a one-off post and want a draft of it in another language, to publish as a separate, standalone post. It's free, it comes from WordPress.org, and for that job it's handy.

Whole site

Translation plugin

Best when you want your site to exist in more than one language: the same pages, each with its own URL, visible to search engines, with a switcher for visitors.

That second job is what ConveyThis does on WordPress:

Install

Add the ConveyThis plugin from the WordPress plugin directory. It's tested with WordPress 7.1.

Pick your languages

Your original stays exactly as it is.

Translation runs automatically

Across posts, pages, menus, forms and WooCommerce, with language URLs and hreflang added for you.

Fine-tune

Adjust wording in the visual editor, add glossary terms for your brand, or order professional translation for key pages.

You still get AI translation. ConveyThis uses its own AI alongside engines such as Google Translate. The difference is everything that comes with it.

For a step-by-step setup, see how to translate a WordPress website.

Start free: the ConveyThis Free plan includes 10,000 words and one language, no credit card required. Translate your WordPress site with ConveyThis →

Frequently asked questions

Does WordPress 7 translate websites automatically?

No. WordPress 7.0 added an AI Client and a Connectors screen to core, but no translation feature. Translation is available as an experiment in the separate AI plugin from WordPress.org, and it works one post at a time.

Can I use the WordPress AI plugin and ConveyThis together?

Yes. They do different jobs. You can use the AI plugin for writing and editing tasks, and ConveyThis to publish your whole site in other languages, with its own URLs, hreflang and language switcher.

Will the WordPress AI plugin hurt my SEO?

Not on its own. But if you translate a post and publish it in place, that URL now serves the new language and your original-language version is no longer live. To keep both, publish the translation as a separate post and add hreflang tags yourself, so search engines know the two pages belong together.

When will WordPress have built-in multilingual support?

There’s no official date. Multilingual is Phase 4 of the WordPress roadmap, with no target release. The official planning posts for WordPress 7.2, due in December 2026, don’t include it.

Does ConveyThis work with WordPress 7.1?

Yes. The ConveyThis plugin is tested up to WordPress 7.1 and works with WooCommerce and popular SEO plugins such as Yoast SEO.

Sources

Share:
G2 High Performer Spring 2023
G2 Easiest Setup Fall 2024
G2 Best Support Spring 2025