LATW Multilingual – AI Translation & Language Switcher

By szymon0zawadzki

★ 5.0/5 (3 ratings)20+ active installationsVersion 2.8.5

Lightweight multilingual plugin built for AI translation: one post stays one post. Language switcher, SEO URLs, WooCommerce, AI or manual.

Description

LATW Multilingual makes your WordPress site multilingual without the usual weight. It adds a language switcher, language URLs and multilingual SEO. It was also built for AI translation from day one: pages are translated paragraph by paragraph, so AI only works on text that actually changed, and your own corrections are never overwritten.

Translate by hand for free, connect LATW Cloud to have AI translate without an API key, or use your own AI keys with Pro.

Why LATW Multilingual

  • Lightweight: one post stays one post. Most multilingual plugins copy every post for every language. LATW keeps your original post and stores each language as an overlay in its own tables, so ten languages never means ten copies of your content. If you uninstall the plugin, your original posts stay exactly as they were.
  • Built for AI translation. Content is split into segments: paragraphs, headings, buttons. A sentence that appears on ten pages is translated once. When you change one paragraph, only that paragraph needs translating again. That keeps AI translation fast and cheap.
  • AI drafts, you have the last word. A translation you correct by hand is protected. Later AI runs never replace it, and if the original changes, your version stays live and is marked “Needs update” so you can review it.
  • SEO in every language. hreflang with x-default, canonical URLs, <html lang> and sitemap entries are generated automatically, in the free version.
  • Works with the tools you already use. WooCommerce, Elementor, Divi, Gutenberg, Yoast SEO, Rank Math, All in One SEO, SEOPress, Contact Form 7, and plugins built for WPML.

Three ways to translate

  • By hand (free). Translate in the native Gutenberg editor, the Divi Visual Builder, or the segment editor, which lists every paragraph next to its translation.
  • With LATW Cloud (free plugin, pay per word). Connect the site under Settings → LATW Cloud and AI translates your posts, pages, categories, strings and theme and plugin files in the background. You don’t need an API key or a Pro licence. Your first connected site gets 10,000 free words to try it. LATW Cloud is an optional paid service (see External services below).
  • With Pro (your own AI keys). Use seven engines on your own API keys, billed directly by the provider, or translate straight from your Claude or ChatGPT chat.

You can mix all three: AI makes the first pass, and you polish the pages that matter most.

Features

Languages and URLs

  • Unlimited languages, each with its own URL prefix, WordPress locale, label and flag.
  • Each language can live in a folder (/de/), on a subdomain (de.example.com) or on its own domain (example.de). Your default language keeps its URLs.
  • Translated URL slugs, including child pages and the base of custom post types.
  • Language switcher as a Gutenberg block, a widget, the [latwm] shortcode or the latwm_switcher() PHP function. It comes as a dropdown, inline or select, with optional flags.
  • Links inside your content point to the matching language automatically.

Content

  • Segment editor: every paragraph, heading and button next to its translation, showing what still needs translating. Its Published switch puts a translation on the site before it is finished, or takes one off the site without deleting it.
  • Translation memory: text you have already translated is reused on new pages.
  • Posts, pages, custom post types, categories, tags, menus, widgets and media (title, alt text, caption and description).
  • Elementor, including Theme Builder layouts, and Divi, including Theme Builder headers and footers and the Divi Library. Other page builders are translated through a dedicated editor.
  • Every language keeps its own revision history.

Theme and plugin text

  • Built-in .po/.mo string editor. New strings are added automatically when a theme or plugin is installed or updated.
  • Download ready-made language packs from WordPress.org for all your themes and plugins in one click.
  • Text saved in theme and plugin options, text stored in block settings, and the JavaScript strings used by the block-based cart and checkout.
  • Reads wpml-config.xml, so themes and plugins built for WPML work without installing WPML.

WooCommerce

  • Products, variations, categories, tags, attributes and their terms.
  • Block-based cart and checkout, payment and shipping method titles, and order emails sent in the language the order was placed in.

SEO

  • hreflang with x-default, canonical URLs, <html lang> and multilingual sitemap entries.
  • Translated SEO titles and meta descriptions in Yoast SEO, Rank Math, All in One SEO, SEOPress and SureRank.

Tools

  • Translation inspector: switch it on from the admin bar, click any text on your site, and it shows which layer the text comes from, with a link to the screen that translates it.
  • History of every translation, whether it was done by hand or by AI.

Pro

LATW Multilingual Pro adds AI translation on your own keys:

  • Seven engines: OpenAI, Anthropic Claude, Google Gemini, DeepL, Google Translate, MyMemory (no key needed) or any OpenAI-compatible endpoint. Each engine keeps its own key and model.
  • Translate from your Claude or ChatGPT chat, within the subscription you already pay for, with no per-token cost on top.
  • Bulk translation of the whole site in a background queue, with a cost estimate before it starts.
  • Automatic translation on publish and update.
  • AI translation of theme and plugin strings (.po).
  • Website description, custom prompt and glossary, so your tone and terminology carry into every language.

Learn more and get Pro: https://latw.ai/latw-multilingual/

Developer features

  • latwm_current_lang() – prefix of the current language ('' = default).
  • latwm_current_locale() – WordPress locale of the current language.
  • latwm_get_languages() – array of languages (including the default).
  • latwm_get_url( $lang, $url = null ) – path URL in the given language.
  • latwm_switcher( $args ) – echo/return the switcher markup.

Filters: latwm_languages, latwm_detected_lang, latwm_switcher_args, latwm_url, latwm_flag_url. Action: latwm_language_switched.

Translation layers: latwm_translatable_meta, latwm_translatable_term_meta, latwm_translatable_options (option name => paths inside the stored value), latwm_translatable_block_attrs (block name => attribute names).

External services

This plugin can connect to LATW Cloud, a translation service run by LATW at https://app.latw.ai, to translate the site’s content automatically. It is optional and off by default: nothing is sent to LATW Cloud until an administrator clicks Connect with LATW under LATW Multilingual – Settings – LATW Cloud (with the Pro add-on: Settings – AI, engine LATW Cloud) and authorizes the site in the LATW window.

  • When you connect: the site address and the address of its LATW Cloud REST endpoint, the site’s languages, the plugin version and the email address of the administrator who connects are sent to https://app.latw.ai, which returns a key the site and LATW Cloud sign their requests with.
  • While connected: LATW Cloud reads, through the site’s REST API (/wp-json/latw/v1/cloud/latw-multilingual/), the list of translatable content (titles, translation status, word counts) and the text of the posts, pages, terms, strings and theme/plugin translation files an administrator chooses to translate in the LATW Cloud panel, and writes the translations back. The site sends LATW Cloud requests for the plan summary, the connection test and disconnection. LATW Cloud passes the text to the AI provider of the model chosen for the site. It does not store source texts; a translation is kept on LATW’s servers only while the site cannot be reached, for up to 7 days.
  • Disconnecting in the same place stops all of this.

  • Service URL: https://app.latw.ai/

  • Privacy Policy: https://latw.ai/privacy-policy/
  • Terms of Use: https://latw.ai/terms-of-service/

Requirements

  • WordPress 6.0+, PHP 8.0+.
  • Pretty permalinks (any structure other than “Plain”).
  • Single-site.

Installation

  1. Install the plugin from Plugins → Add New, or upload it to /wp-content/plugins/.
  2. Activate the plugin through the Plugins screen.
  3. Go to LATW Multilingual → Settings and add your languages.
  4. Add the language switcher with the block, the widget, the [latwm] shortcode, or latwm_switcher() in your theme.
  5. Make sure Settings → Permalinks uses a pretty structure (anything other than “Plain”).

Start translating from the post editor and from LATW Multilingual → Translations. To have AI translate the site without an API key, connect it under LATW Multilingual → Settings → LATW Cloud.

FAQ

Is the free version usable on its own?

Yes. The free edition is fully functional: the switcher, language URLs, the SEO tags and manual translation of content, media and theme and plugin strings, with unlimited languages and no API key.

Can I translate with AI without Pro?

Yes, through LATW Cloud, an optional paid service. Connect the site under Settings → LATW Cloud, then start translations in the LATW Cloud panel. You pay per word with LATW Credits (or use your own AI provider key there), and your first connected site gets 10,000 free words to try it. Translations are saved on your site and stay there even if you stop using LATW Cloud. Nothing is sent anywhere until you connect.

Will AI overwrite my manual corrections?

No. A translation you edited by hand is never replaced by a later translation, whether that translation comes from LATW Cloud or from Pro. If the original paragraph changes afterwards, your version stays on the site and is marked “Needs update” until you approve or update it.

Why translate paragraph by paragraph?

Because it is cheaper and safer. A sentence that appears on several pages is translated once and reused. When you edit a page, only the changed paragraphs need translating again, so the rest of the translation, including your corrections, stays as it is.

Does it duplicate my posts for each language?

No. Instead of creating a separate post for each language, the plugin keeps the original post and stores the translation as an overlay that is swapped in when the language URL is requested.

Will it slow my site down?

It is built not to. Each URL is served by one post, with no duplicated content to query. The inspector and debug tools add nothing to a normal page load. In our tests, translated pages load as fast as the originals.

Do I need an API key?

No. Manual translation needs no key, and neither does LATW Cloud. You only need a key for Pro, from the AI provider you choose. MyMemory works without one.

Is this a WPML or Polylang add-on?

No. LATW Multilingual is a standalone alternative to WPML, Polylang and TranslatePress, so you install it on its own. If you already run WPML or Polylang and only want AI translation, LATW also makes separate add-ons for them: https://latw.ai/

Can I move my site from WPML or Polylang?

LATW Multilingual works best on sites that are starting out with several languages. There is no importer from WPML or Polylang yet, so content that is already translated has to be moved by hand.

Does it work with WooCommerce?

Yes. Product titles, descriptions and excerpts, variations, product categories and tags, attribute labels together with their terms, and the block-based cart and checkout are all covered. Interface strings such as “Add to cart” come from WooCommerce’s own language pack. Use Download packs on the Themes & Plugins tab to fetch it, then edit any string you want to change.

Does it work with Elementor?

Yes, including Elementor Pro’s Theme Builder. Elementor’s rendered-element cache is kept for each language separately, so a page rendered first in one language is never shown in another.

Does it work with Divi?

Yes, including the Divi Theme Builder and the Divi Library. Pages are translated in the Divi Visual Builder. Headers, footers and global modules are translated once and appear in that language on every page that uses them. Each language keeps its own module styles, so a translation with different styling never changes the original.

Does it work with SEO plugins?

Yes. Translated titles, meta descriptions, canonical URLs and language tags work with Yoast SEO, Rank Math, All in One SEO, SEOPress and SureRank.

My product is translated, but the text around it is still English

The text on a page comes from several places, and each one is translated on a different screen:

  • interface strings built into the theme or plugin: Translations → Themes & Plugins
  • category and tag names: the taxonomy tabs
  • menus and widgets: their own tabs
  • the content itself: the content tabs
  • text stored in theme options: Translations → Theme options

A string that stays English usually belongs to a layer you have not turned on yet.

How do I find out where a piece of text is translated?

Turn on Inspect translations in the admin bar and open your site. Click any text and the inspector shows which layer produced it (a theme or plugin string, a post, a term, a menu item, a widget or a theme option), with a link to the screen that translates it. Text that is not translated yet is reported as such. The mode is for administrators only and adds nothing to a normal page load.

I edited a string but the cart or checkout still shows the old text

Block-based screens render in JavaScript and read their strings from separate translation files, not from the .mo file. Saving a string in the editor rebuilds those files as well, so the change appears on the next page load. If a string still does not change, it usually belongs to a different layer. A page title, for example, is content, and some plugins store their labels in their own settings (see the Theme options tab).

My theme or plugin has no “Sync from template” file

Some large plugins, WooCommerce and Elementor among them, ship no .pot file and publish their translations on WordPress.org instead. Use the Download packs button at the top of the Themes & Plugins tab to fetch everything available for your languages in one go. The strings then become editable like any other.

Where does the list on the Theme options tab come from?

Many themes and plugins ship a wpml-config.xml file that lists which options, custom fields and block attributes hold front-end text. This plugin reads that file:

  • the option paths from its admin-texts section
  • the custom fields and term fields marked action="translate"
  • the block attributes declared as <key> under gutenberg-blocks

Fields marked copy or ignore are skipped, because an untranslated field already falls back to the original value. Inside block declarations, <xpath> entries are not read: the text they point to is HTML inside the page content, which is translated together with the content.

Your own file at wp-content/languages/wpml-config.xml is read too, and it takes priority over the theme’s and plugins’ files. Third-party declarations are often incomplete, so you can also add single option keys by hand in Settings → Translation.

Meta Box settings pages need no declaration at all. Their text fields are detected from the settings pages and field groups you built, and each page appears on this tab under its option name. Only text, textarea and WYSIWYG fields are offered, since a colour or a switch is not text. If a field you need is missing, add it in Settings → Translation as option_name:field_id.

What does Pro add?

AI translation on your own keys, with seven engines: one-click bulk translation of the whole site, automatic translation on publish and update, AI translation of theme and plugin strings, translation from your Claude or ChatGPT chat, a glossary and custom prompt, a background queue and a cost estimate before each run.

Screenshots

Changelog

2.8.5

  • Fix: in the block editor, the View Page button of a translation opened an address with the language in it twice (/es/es/page/ instead of /es/page/), which led to “page not found”

2.8.4

  • Fix: the sitemap of a language listed pages that are not translated into it. The sitemap opened under a language’s address (for example /de/page-sitemap.xml) listed every page, post and product, including the ones with no translation in that language, which answer with “page not found” or a redirect. It now lists only what is translated into that language, the way the language switcher shows only translated languages. Pages whose address is translated also got alternate-language links in that sitemap that led to “page not found”; they now point to each language’s real address.
  • Improvement: the segment editor shows the number of segments still to translate in orange, so an element restored from the original, which shows the original text until it is translated, stands out

2.8.3

  • Improvement: the LATW Cloud settings show your balance in LATW Credits (for example “Solo · 61.7 Credits”) and the plan without a subscription as Free, matching the new LATW Cloud plans.

2.8.2

  • Fix: language links on category and tag pages with a translated address. On a category or tag page whose address is translated, the language switcher and the alternate-language links for search engines (on the page and in the sitemap) used that language’s address in every other language too, so they led to “page not found”. Each language now gets its own address. The page is also no longer reachable under the original address in the translated language: that address now redirects permanently to the translated one.
  • Fix: saving a translation by hand removed links and formatting. In the translation editor of strings, widgets, forms, menus and categories, saving removed links, bold text and other HTML from the translations of that item, including the ones you had not changed: correcting the Accept button of a cookie banner removed the link to the privacy policy from its message. Formatting is now kept, and a translation you did not change is saved exactly as it was.
  • Fix: German addresses of translated pages, posts and categories dropped umlauts instead of spelling them out (uber instead of ueber, strase instead of strasse). The address of a translation now follows its own language’s spelling, whether it is generated from the translated title or typed by hand; addresses saved before keep their spelling.
  • Fix: a page translated after an image or file of the same title got a number added to its address (kuenstliche-intelligenz-3), because the image had taken the address first. Images and files no longer get a translated address, and the ones given to them before no longer take an address from a page.
  • Fix: a category and a tag with the same name got different translated addresses (seo and seo-2). They can now share one, as they do in the original language.
  • Improvement: questions before an action (Translate again, Restore from the original, Rebuild from the original layout, deleting a translation file, cancelling a queued translation and others) open in the plugin’s own dialog instead of the browser’s box, with a button named after the action and a red one for what cannot be undone. Messages after an action (“Sent successfully for translation”, “Saved”, errors) appear as a bar at the top of the page that stays in view while you scroll, instead of a browser box you had to click away.

2.8.1

  • Improvement: changing the layout of an Elementor translation affects only the widgets you changed. A widget you give a new paragraph or formatting of its own, remove, add or move in the translation keeps what you did, and the rest of the page keeps following the original: new and changed texts are still translated, and text you edit in Elementor counts as your own work. Elementor tells you after saving when widgets stop following the original, the page lists mark such translations, and the segment editor lists these widgets with a button to restore each one from the original, or to remove one that exists only in the translation.
  • Improvement: a clearer warning when a translation loses formatting. The History screen now says where each affected passage is and how it begins, and names what it lost in words (a link, bold text) instead of a technical code. The whole message opens with a click, with a link straight to the segment editor, which has a new Lost formatting filter listing just those passages.
  • Fix: after the layout of an Elementor translation had been changed, text edited there later did not show up in the segment editor, which kept showing the earlier automatic translation.
  • Fix: translations now show up without clearing the page cache by hand. A page translated into a newly added language kept showing “page not found”, and menus, forms and strings stayed in the original language on translated pages until the whole cache was purged. Saving a translation now clears the cache of the common caching plugins (LiteSpeed Cache, WP Rocket, W3 Total Cache, WP Super Cache and others): just the translated page when it already had a translation, or the whole cache when a page gets its first translation in a language or when menus, strings, forms, categories or header and footer templates are translated.

2.8.0

  • New: segment-by-segment translation with a translation memory. Posts, pages, Elementor and Divi pages and block widgets are now translated paragraph by paragraph (widget by widget in Elementor and Divi) instead of as one block. A sentence that appears in several places is translated once and reused everywhere, and a new page that repeats text you have already translated starts out translated. Changing one paragraph of the original only makes that paragraph need translating again; the rest of the translation stays as it is.
  • New: segment editor. Open it with the list icon next to a language in the LATW Translations box of a page. It lists every paragraph, heading and button next to its translation and shows what still needs translating. Its Published switch puts a translation on the site before it is finished, or takes one off the site without deleting it.
  • New: your corrections are protected. A translation you edited by hand is never replaced by a later translation. If the original paragraph changes afterwards, your version stays on the site and is marked “Needs update” until you approve or update it.
  • New: LATW Cloud in the free version. Connect the site to LATW Cloud under Settings – LATW Cloud and translate posts, pages, taxonomies, strings and theme and plugin files from the LATW Cloud panel – no PRO licence needed. Only the passages still to translate are sent, your manual corrections are never replaced, and every translation LATW Cloud writes is listed on the History screen.
  • Improvement: the LATW Translations box in the editor is easier to read.
  • Improvement: when you install or update a theme or plugin that comes with a .pot template, its new strings are added to your translations of it automatically, so you no longer have to click “Sync from template” after every update. Translation files that came with the theme or plugin and official WordPress.org language packs are left as they are.

2.7.0

  • New: languages on subdomains or separate domains. Each language can now live on its own subdomain (pl.example.com) or its own domain (example.pl) instead of a /pl/ folder. Choose it under Settings → Languages → Language in URL. A Check domains button tests DNS and certificates before you save. A WooCommerce cart follows the customer when they switch language.
  • Improvement: saving the language settings now clears the page cache of the common caching plugins (WP Super Cache, WP Rocket, W3 Total Cache, LiteSpeed Cache and others), so pages no longer keep showing the old language switcher and links.

2.6.7

  • Fix: with a permalink structure that puts a fixed word before the post name, such as /magazine/%postname%/, a post with a translated URL slug showed “page not found” in the other languages, while its address without /magazine/ still opened it. Translated posts now open at the same address their links point to, just like in the default language.

2.6.6

  • Improvement: Wolof can now be picked from the list when adding a language.

2.6.5

  • New: the URL slug of a translation can be edited with any page builder. In Elementor it is the new Translation URL field in Page Settings. For every editor, including Divi, Beaver Builder, Bricks, Oxygen and WPBakery, the LATW Translations box on the page edit screen now has a URL slug field under each translated language.
  • Fix: the address of a translated child page kept the original, untranslated parent in its path, so it was half in one language and half in another. Every level of the path is now translated, the old addresses are redirected to the new one, and a path with the wrong parent shows “page not found” instead of an empty page.
  • Fix: with Elementor 4.3, headings, paragraphs and buttons built with the new atomic widgets stayed in the original language when a page was translated with AI (PRO).
  • Fix: with Yoast SEO, the meta description of a custom post type’s archive stayed in the original language on translated pages, even though its translation was saved.

2.6.4

  • Fix: with Yoast SEO, an SEO title, meta description or social media title that contained variables such as %%title%% or %%sitename%% stayed in the original language on translated pages, even though its translation was saved.
  • Improvement: the X (Twitter) title and description entered in Yoast SEO are now translated too.

2.6.3

  • New: translated addresses for custom post types. The base in the address of a custom post type, such as projects or portfolio items, can now be different in each language – for example /progetti/my-project/ in Italian and /en/projects/my-project/ in English, the post type’s archive included. Translate it on the Strings screen: pick Post types, open the post type and fill in URL base. The old addresses keep working and are redirected to the new ones.

2.6.2

  • Fix: with SEOPress, a language code such as “et” or the page’s own address appeared as text in a strip above the page. The page language for social media sharing and the canonical address of translated pages are now output correctly, and the other languages of the page are listed for sharing too.
  • Fix: with SEOPress, quotation marks in a translated title or description could break the tags used when the page is shared on social media.

2.6.1

  • Fix: an SEO title or meta description entered by hand in All in One SEO stayed in the original language on translated pages, even though its translation was saved – including the title and description shown when the page is shared on social media.

2.6.0

  • New: Divi headers, footers and Divi Library. Theme Builder headers, footers and body templates and Divi Library items (global modules) can now be translated. Tick them under Content Types and translate them in the Visual Builder.
  • Fix: an SEO title or meta description entered by hand in Yoast SEO stayed in the original language on translated pages, including the title and description shown when the page is shared on social media.

2.5.0

  • New: Contact Form 7 forms can be translated. Labels, placeholders, options, the submit button and the form’s messages are translated once, on the Strings screen under the new “Contact Form 7” type, and the translated form then appears wherever it is embedded – shortcode, block, or a widget from Elementor, your theme or an add-on. Mail is still sent to you in the form’s original language.

2.4.0

  • New: every language now has its own revision history, kept by WordPress itself. Drafts, autosaves, the revisions panel and “restore” work on a translation exactly as they do on any post – including Elementor’s revisions panel and its “This is just a draft” notice – and each language sees only its own history, while the original keeps its own.
  • New: an occasional invitation on the plugin’s own screens to leave a wordpress.org review, dismissable for good.
  • Fix: editing a translation could leave the ORIGINAL page holding that translation. Every editor autosaves, and because a translation is edited on the source post, the autosave was a revision of the ORIGINAL carrying translated content – so reopening the original, or opening a different language, offered to restore the wrong language’s text and layout over it.
  • Fix: autosave was switched off entirely while a translation was open, so unsaved changes were lost when a tab was closed and “Preview” never showed anything that had not been saved yet. It works again, kept separately for each language.
  • Fix: “Preview” on a translation opened the ORIGINAL page in the default language – and could show the original’s own unsaved draft – instead of the translation being edited.
  • Fix: the block editor offered the ORIGINAL’s browser backup while editing a translation, and the other way round. Its backup slot is keyed by post id alone, and the source and all of its translations share one post.

2.3.1

  • Fix: the “View Page” button on the translation edit screen in Elementor takes you to the translated page, not the original one.

2.3.0

  • New: translations are edited on the post itself, with no hidden draft in between – two translations of the same post can be open side by side, and every save carries the language it belongs to.
  • New: Debug Mode now records what happens on each front-end page – the language detected, the routing rule that matched, whether the page had a translation, and which translated values were used – so a page that comes out wrong can be explained from the log instead of guessed at. Keys and tokens that appear in addresses are never written to it, and the log folder is no longer reachable from a browser.
  • Fix: addresses carrying a language prefix (/de/, /pl/) were never matched by the plugin’s own routing rules. WordPress read the prefix as a folder and stripped it, so a bare /de/ answered with the front page and every other prefixed address resolved by coincidence rather than by design.
  • Fix: saving a translation in Elementor could write it over the original page, leaving every language showing that one translation. The language now stays with the editor through a reload and through the save.
  • Fix: Elementor pages shared a single stylesheet and asset list between languages, so a section that exists in only one translation was served without its styling – depending on which language happened to be viewed first after Elementor’s cache was cleared. Each language now gets its own.
  • Fix: a refused save could leave a stray, unusable row behind in the translations table.

2.2.0

  • New: Meta Box settings pages are picked up automatically – the text fields of every settings page now appear on the Theme options tab, so they can be translated and show up translated wherever they are printed, MB Views shortcodes included.
  • New: a new way of editing translations – each one is now edited on the post itself rather than in a shared hidden draft, so several translations can be open at once without overwriting one another.
  • Improvement: in Elementor the save button on a translation now reads “Save translation”, settles into its saved state and confirms with a “Translation saved.” message, instead of staying on “Publish” with no sign anything happened.
  • Fix: saving the settings before installing ACF, WooCommerce, Filter Everything or a page builder switched that integration off permanently – installing it later could not turn it back on, and its text was quietly left untranslated.

2.1.0

  • New: full WooCommerce support – product names, descriptions, variations and attributes (including custom attributes typed directly on a product), payment method titles and descriptions, shipping method titles, Local Pickup title and pickup locations, checkout notices, and order confirmation emails (subject, heading and body) sent in the language the order was placed in.
  • New: a notice on the cart and checkout pages when a product in the cart has no translation yet for the language a shopper is browsing in.
  • New: works with plugins and themes built for WPML – strings and content they register through WPML’s own functions are now picked up and translated automatically, no WPML installation required.
  • New: theme/plugin translation files (wpml-config.xml) can now also declare shortcode attributes and nested custom-field text as translatable.
  • New: compatibility with Yoast SEO, Rank Math, All in One SEO, SEOPress and SureRank – translated titles, meta descriptions, canonical URLs and language tags now work correctly with each of these plugins.
  • New: “Filter Everything” product-filter plugin support – filter labels and tooltips can be translated.
  • New: custom post type names (e.g. “Projects”) and their archive titles can now be translated, from a new “Post Types” tab.
  • Improvement: editing a translation now hides fields that don’t actually get saved on it (author, featured image, format, comments, categories) and instead shows a clear, read-only overview of the post’s categories and tags with translate links.
  • Improvement: saving a translation now shows a “Translation saved.” message instead of the confusing “Draft saved.”
  • Improvement: the Posts and Taxonomies screens now search, filter and page through your full content directly, so nothing is left out of the list on large sites.
  • Improvement: the “Translations” column on the Products list now displays at a readable width and in the right place.
  • Improvement: the History screen’s Post ID and source language now link straight to the post.
  • Fix: a brand-new translation could get stuck with the Save button disabled until something was typed in it; it can now be saved right away.
  • Fix: translated URLs for custom post types (e.g. WooCommerce products) could fail to open the correct page.
  • Fix: translated URLs using non-Latin characters (e.g. Chinese) could show a “page not found” error.
  • Fix: WooCommerce’s mini-cart could briefly load in the wrong language.

2.0.3

  • Improvement: UI/UX improvements.
  • Fix: Add missing languages.

2.0.2

  • Fix: on sites running on a non-standard port (e.g. local dev environments like WordPress Studio, localhost:8881), switching languages with the widget dropped the port from the link, breaking it.

2.0.1

  • Fix: a child page with a translated slug returned a 404 under its full path.

2.0.0

  • New: translation inspector – switch it on from the admin bar, click any text on the front-end and be told which layer it comes from, with a link to the screen that translates it.
  • New: theme and plugin option strings, taken from wpml-config.xml files shipped by themes and plugins, from your own file in wp-content/languages/, or added by hand.
  • New: translation of server-rendered block attributes, so labels that live in block settings rather than in the page markup get their own list.
  • New: block interface translation – saving a string rebuilds the JavaScript translation files too, so block screens such as the cart and checkout follow the edit.
  • New: download language packs from WordPress.org, per bundle or for the whole site at once – the only way to reach plugins that ship no .pot of their own, such as WooCommerce, Elementor and Elementor Pro.
  • New: menu and widget translation.
  • New: WooCommerce support – products, variations, product categories and tags, and product attribute labels (“Size”) alongside their terms (“Small”, “Large”).
  • New: Elementor support, including Elementor Pro’s Theme Builder.
  • Fix: Elementor’s rendered-element cache is scoped per language; whichever language rendered first was being replayed to all the others.
  • Fix: WooCommerce’s browser-side mini-cart cache is scoped per language, which had the same symptom.
  • Fix: simple products kept their source title in headings and archive loops; variations showed the source name in the cart.
  • Fix: attribute taxonomies are registered as non-public by default and so never reached the translatable list – they are now offered explicitly.
  • Fix: the inspector no longer marks values that code parses. Markers inside _elementor_data broke the layout on builder pages, and markers inside a slug produced 404s.
  • Fix: the shared edit buffer no longer takes the source page’s slug, which could make the published page 404 until the buffer moved on.
  • Fix: the language switcher no longer wraps, and a null $wp_rewrite during early boot no longer throws.