by szymon0zawadzki 5 (2 reviews)

LATW Multilingual

Name: LATW Multilingual
Rating: 5.0 (2 reviews)
Author: szymon0zawadzki

Lightweight multilingual WordPress with an overlay architecture: language switcher, clean language URLs, hreflang SEO, unlimited languages.

LATW Multilingual ranks #25,550 among WordPress.org plugins with 20+ active installations, is #286 of 833 in the Language Tools category, a 5/5 rating from 2 reviews, and was last updated Oct 28, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Compatible with WP 7.1

v2.7.0 Current Version v2.7.0

Updated 1 week ago Last Update on 28 Oct, 2026

Refreshed 1 week ago Last Refreshed on

#286 of 833 in Language Tools Top 50% by installs Downloads -71.7% this week Actively maintained

View on WordPress.org

Rank

#25,550

— No change

Active Installs

20+

-28.6%

KW Avg Position

81.5

15.5 worse

Downloads

1.9K

+20 today

Support Resolved

100%

— No change

Rating

100%

Review 5 out of 5

5 (2 reviews)

Next Milestone 30

Total Progress 80%

20+ 30+

2,805

Ranks to Climb

Growth Needed

8,000,000

Active Installs

Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

Exact install estimates within tiers
Track install growth over time
Milestone progress predictions

Upgrade to Pro

Need 2 more installs to reach 30+

Rank Changes

Current #25,550

Change

Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Upgrade to Pro

Active Installs 0,000,000+

Growth +0.0%

Peak 0,000,000

Downloads Growth

Downloads

Growth

Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

5.0

2 reviews

Overall 100%

2 (100%)

0 (0%)

Support Threads Overview

Resolved

Unresolved

Total Threads

Resolved

Unresolved

100%

Resolution Rate

Track This Plugin

Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.

Start Tracking Free

Plugin Details

Version: 2.7.0
Last Updated: Oct 28, 2026
Requires WP: 6.0+
Tested Up To: 7.1
PHP Version: 8.0 or higher
Author: szymon0zawadzki

Support & Rating

Rating: ★ ★ ★ ★ ★ 5
Reviews: 2
Support Threads: 1
Resolved: 100%

Keywords

language switcher multilingual seo translation woocommerce

Upgrade to Pro

Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.

Upgrade Now

Similar Plugins

Adminify – White Label, Admin Menu Editor, Login Customizer

6K+ installs

#2,757

Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits

Translate WordPress with GTranslate

TranslatePress – Translate Multilingual sites with AI Translation

Connect Polylang for Elementor

100K+ installs

#294

WPML Multilingual & Multicurrency for WooCommerce

100K+ installs

#330

View all Language-tools plugins

Frequently Asked Questions

Common questions about LATW Multilingual

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

No. Instead of creating a separate post per language, the original post is kept and the translation is stored as an overlay that is swapped in when the language URL is requested.

No. Because there is one post per URL and no heavy duplication, a site that scores 100 in Google PageSpeed before LATW still scores 100 after - in every language.

Not for the free version - manual translation requires no key. AI translation is a Pro feature and uses your own OpenAI key, so usage is billed directly to you.

No. LATW Multilingual is a standalone plugin. It is not a replacement or add-on for WPML or Polylang - install it on its own.

Yes. It supports Gutenberg and page builders for content, and works alongside SEO plugins such as Yoast SEO and Rank Math. My product is translated, but the text around it is still English Text on a page comes from several places, and each is translated somewhere else: interface strings compiled 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), and text stored in theme options (Translations - Theme options). A string that stays English usually just belongs to a layer you have not enabled yet.

Many themes and plugins ship a wpml-config.xml file listing 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", and the block attributes declared as <key> under gutenberg-blocks. Fields marked copy or ignore are skipped: in an overlay model an untranslated field already falls back to the original value, so there is nothing to do for them. Inside block declarations, <xpath> entries are not read - the text they address is HTML inside the page content, which is already translated with the content itself. Your own file at wp-content/languages/wpml-config.xml is read too and takes priority over the theme's and plugins' files. Declarations by third parties 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 the page shows up on this tab under its option name. Only text, textarea and WYSIWYG fields are offered - 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. 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 rather than from the .mo. Saving a string in the editor now rebuilds those files as well, so the change applies on the next page load. If a particular string still does not follow, it usually belongs to a different layer - a page title is content, and some plugins store their labels in their own settings (see the Theme options tab).

Turn on Inspect translations in the admin bar and open your site. Clicking any text 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 to the screen that translates it. Text that is not translated yet is reported as such. The mode is administrator-only and nothing is added to a normal page load.

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.

Yes, including Elementor Pro's Theme Builder. Builder pages are translated in the 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.