LATW Multilingual
One plugin with everything you need: full SEO support, a language switcher, and clean URLs. Its overlay architecture works unlike anything else, delivering real speed, plus cheap, automatic AI translation billed straight to your own API key.
Gutenberg
Going multilingual usually costs you speed, simplicity or SEO. LATW was built so you give up none of them.
No duplicated posts, no heavy queries, no render-blocking scripts. A site that scores 100 in Google PageSpeed before LATW still scores 100 after - in every language.
Install, pick your languages, hit publish. There's no framework to migrate to and no 40-screen setup wizard - you keep writing in the same Gutenberg editor you already know.
hreflang, canonical URLs and sitemap entries are generated automatically - even in Free. Google understands your language structure from day one, so each version can rank in its own market.
Most multilingual plugins duplicate your content. LATW keeps a single post and swaps its content in on the fly.
Tools like WPML create a full copy of each page for every language and link them into a translation group. One article becomes four rows in the database, each with its own ID, revisions and metadata to keep in sync. Remove the plugin and you're left with a pile of orphaned duplicate posts.
There is only ever one post. Each language lives as an overlay in its own separate tables, and LATW swaps the right content in at render time when a visitor changes language. Your original stays untouched and canonical, the database stays clean, and nothing is duplicated.
Full hreflang and sitemap support even in the free version, with no slowdown to your site.
Free actually works, unlimited languages, full SEO. Pro sells time and scale, not artificially locked basics.
Instead of a separate post per language, the original stays single and the translation is a layer on top. Less database mess, and the original is always canonical.
Translate automatically, then polish in native Gutenberg. The best of both: machine speed with human precision.
You pay the AI provider exactly what you use, no "10,000 words/mo" subscription like Weglot-style SaaS. On big sites, an order-of-magnitude cost difference.
You can remove the plugin at any time without leaving a mess in your database. Because it works as an overlay, it only operates on its own extra tables, so your original content stays completely untouched.
Switcher, clean URLs, complete SEO and real translation, content, interface and media, all in one plugin.
Bring your own OpenAI key and translate a whole site in one click, then fine-tune by hand in Gutenberg.
/en/, /de/ on WordPress native routing, clean, fast and SEO-friendly, no ugly query strings.
Translate a post in ordinary Gutenberg while the original stays untouched. A translation is an overlay, not a copy.
Products, variations, categories, attribute labels and their terms, plus the block cart and checkout. See the shop page →
A built-in .po/.mo editor to translate buttons, labels and theme text too, not just your posts.
hreflang + x-default, self-canonical, <html lang> and sitemap annotations. Google understands your language structure right away.
Title, alt text, caption and description of attachments, translated per language so your media reads right everywhere.
Gutenberg block, widget, [latwm] shortcode and a PHP function for your theme. List, dropdown or select, with or without flags, with your own CSS.
A clean API (latwm_switcher(), latwm_get_url(), latwm_current_lang()…) plus filters and actions for full control.
Click any text on your site and be told exactly which layer produced it - and get a link to the screen that translates it. No more hunting for that one stubborn English word.
Builder pages, templates and Elementor Pro Theme Builder layouts translate in a dedicated shadow editor, with Elementor's element cache scoped per language so no page is ever served in the wrong one.
Big plugins like WooCommerce and Elementor ship no .pot file - they publish translations on WordPress.org. One button pulls every pack available for your languages, then you edit any string you disagree with.
Menus, widgets, categories and tags, labels stored in theme and plugin options, and text kept in block settings rather than in the markup - each gets its own list, read from wpml-config.xml where one exists.
Cart, checkout and other block-based screens read their strings from JavaScript translation files. Saving a string rebuilds those files too, so your wording actually shows up on the next page load.
Text on a WordPress page comes from half a dozen places at once: the post, a term, a menu item, a widget, a theme option, or a string compiled into a plugin. Every multilingual plugin makes you guess which one.
Switch the inspector on in the admin bar, open your site and click the word. LATW tells you the layer it came from - with the whole chain it sits inside, a label within a block within a post - and links straight to the screen that translates it. Nothing is added for visitors: with the mode off, the page is exactly as it was.
Want a simple bilingual site (e.g. PL/EN) with a nice switcher and correct SEO.
Free is enoughDozens or hundreds of pages to translate, where doing it by hand is a non-starter.
Pro saves hoursProducts, variations, attributes, cart and checkout in every language you sell in. See the shop page →
Free covers the shopRun many client sites and need brand consistency (glossary) with a fast rollout.
ProFree is a complete multilingual plugin. Pro adds automation and scale.
A bi- or multilingual site with manual translation works out of the box, no language limits, no license.
Translate 300 posts with one click instead of one at a time, auto-translate on publish, glossary and cost estimates included.
I've been coding for about 8 years, and honestly, I just enjoy sitting in my room and building things. Apps, plugins, side projects… especially the kind that make work easier, faster, or less annoying.
The first plugin started as an internal tool for another project of mine - Wishgram. We wanted to reach more people with our blog in different languages, but startup budgets are tight and premium auto-translation was way too expensive for us. So I built my own solution for automatic translations. After using it for a while, I realized how ridiculously good it was - and keeping it to myself just didn't make sense.
My goal is simple: build plugins that help people translate WordPress sites cheaply, quickly and with real quality.
Can't find what you're looking for? Reach out to support directly.
No. LATW Multilingual is a standalone multilingual plugin - switcher, URLs, SEO and translation are all built in. There's no separate framework to migrate to.
No. Translations are stored as an overlay on top of the original post, so the original stays single and canonical - no extra posts cluttering your database.
Yes. Free gives you unlimited languages, the switcher, language in the URL, full SEO (hreflang) and manual content, media and .po translation - a complete bilingual site with no license.
Only for Pro's automatic translation. You bring your own OpenAI key and pay the provider directly for tokens - no per-word markup, no bundled credits. Manual translation in Free needs no key at all.
No. It runs on WordPress native routing and stays lightweight - full hreflang and sitemap support are included even in the free version without slowing the front end.
Yes, end to end: product titles and descriptions, variations, product categories and tags, attribute labels together with their terms, and the block-based cart and checkout. Shops have their own page - see "For WooCommerce" in the menu.
Yes, including Elementor Pro's Theme Builder. Builder pages are translated in a dedicated shadow editor, and Elementor's rendered-element cache is kept per language, so a page rendered first in one language is never replayed in another.
Turn on the translation inspector in the admin bar and click any text on your site. It tells you which layer produced it - a theme or plugin string, a post, a term, a menu item, a widget or a theme option - and links straight to the screen that translates it. It is administrator-only, so a normal visit stays untouched.
Yes. Some large plugins, WooCommerce and Elementor among them, publish their translations on WordPress.org instead of shipping a template. One button downloads every pack available for your languages, and the strings become editable like any other.
Absolutely. In Pro you can auto-translate a whole site in one click, then fine-tune any post by hand in native Gutenberg - machine speed with human precision.
Switcher, clean URLs and full SEO for free. Add AI auto-translation on your own key when you're ready to scale.
Get plugin