Transleti Translator – Multilingual & Automatic Translation

By TransLeti

★ 5.0/5 (1 ratings)10+ active installationsVersion 1.9.56

Translate WordPress into 49 languages — free manual mode, or unlimited automatic translation with a flat-rate API and a 14-day money-back guarantee.

Description

The plugin is 100% free and GPL. You can run a fully multilingual WordPress site with manual translations, hreflang sitemap, language switcher and slug translation without ever paying anything or connecting to an external service.

If you also want automatic translation across every language at once, connect the optional Transleti API — flat-rate, unlimited words and languages, backed by a 14-day money-back guarantee. The API is optional: the manual workflow keeps working forever, even if you never subscribe.

Transleti Translator handles posts, pages, custom post types, WooCommerce products, menus, slugs, SEO meta, and theme strings. A built-in visual editor lets you click on any text in the rendered page and refine its translation in a side-by-side panel — useful both for polishing automatic translations and for translating everything by hand.

Two ways to use it

  • Manual mode (free, forever) — edit each translation directly in the WordPress post editor or via the visual front-end editor. No API key, no subscription, no external connection required. Includes the language switcher, hreflang sitemap, slug translation and 49+ pre-defined language slots.
  • Automatic mode (optional Transleti API) — connect an API key and the plugin fans out translations to every target language in parallel. Flat-rate, unlimited words, with a 14-day money-back guarantee. If you decide to stop, the plugin keeps working in manual mode. Manual edits on top of automatic translations are preserved on re-translation.

Features

  • Free GPL plugin — fully functional in manual mode without any external connection or paid service.
  • Visual translation editor — open any front-end page in an editor frame, click on any string (titles, paragraphs, menu items, buttons, image alts) and edit its translation in a side panel with live preview.
  • Nothing goes live half-translated — a page only becomes available in a new language once its content, title and SEO description are ready. Until then visitors and search engines get a “translation in progress” response instead of a page that is still half in the source language, so nothing broken ever gets indexed.
  • Keeps your site translated on its own — publish a post and it gets translated in the background, in every language. Edit it later and the translations follow. No queue to launch, no per-post action, nothing to remember.
  • Manual translation editor — review and refine translations directly in the WordPress post editor for every language.
  • Optional unlimited automatic translation — flat-rate Transleti API subscription with a 14-day money-back guarantee. If you do not keep the subscription, the API stops and the plugin keeps working in manual mode.
  • Parallel translation (API mode) — requests fan out to every target language simultaneously. A site with 10 languages translates in roughly the same time as a site with 1.
  • Built on open source — the plugin itself is GPL, fully auditable, no proprietary lock-in.
  • Theme & builder-agnostic — works out of the box with Elementor, Divi, Gutenberg, classic editor, GeneratePress and any standards-compliant theme.
  • WooCommerce ready — translates product titles, descriptions, attributes and variations. Also supported in Connector Mode (with WooCommerce Multilingual & Multicurrency when running behind WPML).
  • Connector Mode for WPML, Polylang and TranslatePress — already using one of them? Keep it in charge of your languages, URLs, switcher and stored translations, and let Transleti act purely as the automatic translation engine behind it. Detected and enabled automatically; no double language switching or duplicate URLs.
  • Works with caching plugins — no setup needed. Each language is cached as its own page, a page is cleared from the cache as soon as its translation is ready, and pages still being translated are never stored. Tested with LiteSpeed Cache; also signals WP Rocket and W3 Total Cache. The plugin does not add caching of its own — it stays out of the way of the one you use.

Key features

  • Multilingual sitemap with hreflang — separate <url> entries per language (the format Google explicitly documents) with self-referential hreflang and x-default. Compatible with Yoast SEO, RankMath, SEOPress, AIOSEO and the WordPress core sitemap.
  • SEO meta translation — titles and descriptions for SEOPress, Yoast, AIOSEO and RankMath.
  • Visual translation editor — open any front-end page in an editor frame, click on any string (titles, paragraphs, menu items, buttons, image alts) and edit its translation in a side panel with live preview.
  • Manual translation editor — review and refine translations directly in the WordPress post editor for every language.
  • Manual edit protection — your manual fixes survive re-translation cycles.
  • Slug translation — translated URLs (e.g. /es/contacto/) for clean per-language SEO, or keep the original address for the content types you choose (hotels, brands, product references).
  • Menu translation — duplicates and translates navigation menus per language.
  • HTML entity and shortcode protection — prevents corruption of &copy;, [shortcode], and similar in translated output.
  • Custom “do not translate” word list — keep brand names, product codes and acronyms intact across all languages.
  • Language switcher — widget, block and shortcode in flag, dropdown or text styles.

Supported languages

49+ languages including English, Spanish, French, German, Italian, Portuguese (PT/BR), Dutch, Polish, Romanian, Bulgarian, Hungarian, Finnish, Russian, Ukrainian, Arabic, Hindi, Japanese, Korean, Chinese, Thai, Turkish, and more.

How it works

Manual mode (free):

  1. Install and activate the plugin.
  2. Choose your default language and the target languages you want to publish.
  3. For each post / page, open the translation editor (in the post editor sidebar or via the visual front-end editor) and type the translation by hand.
  4. The language switcher, hreflang sitemap and per-language slugs work out of the box.

Automatic mode (optional API):

  1. Install and activate the plugin.
  2. Sign up at https://transleti.com to get your API key (flat-rate subscription with a 14-day money-back guarantee).
  3. Enter your Transleti API key in the plugin settings.
  4. Choose your default language and the languages you want to publish.
  5. The plugin runs a background job that translates posts, menus, slugs and SEO meta automatically.
  6. Optionally refine any translation manually from the WordPress post editor — your edits are preserved on re-translation.

External Services

This plugin can optionally connect to the Transleti translation API (api.transleti.com) to translate site content automatically into the languages you select. This connection is optional — the plugin works in manual mode (typing translations by hand from the WordPress editor or the visual front-end editor) without contacting any external service. No external request is made unless you enter an API key in the plugin settings.

What data is sent (only in automatic mode): the text strings to translate (post content, titles, excerpts, menu labels, slugs, SEO meta, theme strings) along with the source and target language codes and your API key.

When it is sent: when the background translation cron runs, when you save a post that needs re-translation, or when you trigger a manual translation from the settings page.

Diagnostic reports (any mode, only on request): when you press “Send Diagnostic Report” in the Support tab, the plugin sends a report to api.transleti.com with your WordPress/PHP versions, theme, active plugins, Transleti settings (no secrets), translation counts, a connection test and recent Transleti-related debug.log lines. It also includes the issue description, the post you ask to inspect and the contact email, if you fill them in. Nothing is sent until you press the button.

Service provider: Transleti — https://transleti.com

  • Terms of Service: https://transleti.com/terms
  • Privacy Policy: https://transleti.com/privacy

No personal data of site visitors is sent to the service. Only the text content you choose to translate.

Installation

  1. Upload the transleti-translator folder to /wp-content/plugins/, or install through the WordPress plugin installer.
  2. Activate the plugin via the Plugins menu in WordPress.
  3. Go to Settings → Transleti Translator.
  4. Select your default language and target languages.
  5. (Optional) Enter a Transleti API key to enable automatic translation. Without a key, you can still translate every string manually from the post editor or the visual editor.
  6. Save settings.

FAQ

Do I need to pay anything to use this plugin?

No. The plugin is free GPL software and works fully in manual mode without any external connection or paid subscription. Automatic translation is an optional add-on that uses the Transleti API.

Can I use the plugin without an API key?

Yes. Without an API key the plugin runs in manual mode: language switcher, per-language slugs, hreflang sitemap and the manual / visual translation editors all work normally. You simply type translations by hand instead of having the plugin generate them.

How does billing work, and is there a guarantee?

The automatic translation API is a flat-rate subscription (unlimited words and languages) that you can start at https://transleti.com. It comes with a 14-day money-back guarantee: if it isn’t for you, ask for a refund within 14 days. The manual workflow always keeps working for free, whether or not you subscribe.

Who owns the translations, and what happens if I stop subscribing?

Your translations are always yours. Your translated content is stored in your own site’s database and keeps working in manual mode for free even if you later cancel your subscription — you never lose it. Your original content (your posts and pages in the site’s main language) is never touched by the plugin.

Is the plugin really fast even with many languages?

Yes. Translation requests for every target language are fanned out in parallel, so adding more languages does not multiply the wait time. A 10-language site translates in roughly the same time window as a 2-language site.

Does it work with WooCommerce?

Yes. Product titles, descriptions, short descriptions, attributes and variations are all translated automatically. When you run in WPML Connector Mode, install the free WooCommerce Multilingual & Multicurrency (WCML) add-on so WPML registers products, categories and tags as translatable — the plugin then feeds those translations automatically, and each shop only shows the products for the language being viewed.

I already use WPML, Polylang or TranslatePress. Can I use Transleti just as the translation engine?

Yes. When WPML, Polylang or TranslatePress is active, Transleti automatically switches to Connector Mode: your multilingual plugin stays in charge of languages, URLs, the language switcher and the stored translations, and Transleti works purely as the machine-translation engine behind it — no duplicate switchers or URLs. You can force plain Standalone mode from the Connector tab if you prefer Transleti to manage languages itself.

With WPML it translates your posts, pages, custom post types, WooCommerce products (with WooCommerce Multilingual & Multicurrency), taxonomy terms, menus, slugs, SEO meta and interface strings into every language you have set up.

With TranslatePress Transleti is added to its list of automatic translation engines, and it also translates your pages in the background instead of waiting for someone to visit each one in each language — so the site translates itself, including WooCommerce shops.

Does it support Elementor, Divi, Gutenberg and the classic editor?

Yes. Elementor pages translate the underlying _elementor_data JSON; Divi pages translate the et_pb_* shortcode content and text attributes (headings, buttons, CTAs, blurbs, tabs and more); Gutenberg parses blocks and translates innerHTML and block attributes; classic posts translate post_content directly.

Will Google index the translated pages correctly?

Yes. The plugin emits a separate <url> element per language in the sitemap (the format Google explicitly documents), with bidirectional hreflang and x-default. It also outputs <link rel="alternate" hreflang="..."> tags in the HTML head.

It also protects you from the opposite problem: a page that is only partly translated. Until the content, the title and the meta description are ready in that language, the page returns a temporary “translation in progress” response instead of a half-English page — so Google never indexes a broken version and has nothing to de-index later.

Does it cost more if I publish a lot of content?

No. The subscription is flat-rate: the same price whether you publish one post a month or twenty a day, in one language or in all 49. There is no per-word, per-character or per-API-call billing, and no credits to top up. Sites with continuous publishing are exactly what it is built for.

Can I edit translations manually?

Yes. There are two ways: (1) the visual editor, which lets you click on any string in the rendered page and edit its translation in a side panel — useful for menus, buttons, widgets and theme strings that don’t live in the post editor; and (2) each translated post is a standard WordPress post you can edit from the admin like any other content. Manual edits are detected and preserved during re-translation.

What happens if I update the source post?

The plugin detects content changes via MD5 hashing and queues a re-translation. Manual edits to translations are detected and preserved (unless the source change is structural).

Screenshots

Changelog

1.9.56

  • Fix: in manual mode, pages in other languages were never shown. Until a page was marked as translated, visitors got the “translation in progress” page, and only automatic translation set that mark. Without an API key it was never set, however much you had translated by hand. In manual mode you decide when a language goes live, so pages are now shown with your translations and the original text for anything not translated yet. Sites with an API key, including an expired one, keep the protection.
  • Fix: the language switcher could not take you back to the main language. On a translated page every internal link gets that language’s prefix, and the link to the main language has none, so it was given one and pointed back to the page you were reading. Switcher links are now left as they are, in the menu, the floating switcher and the shortcode.
  • Fix: the main language was missing from the floating switcher and the shortcode, so on a translated page they only offered the other languages.
  • Fix: with “Auto-detect visitor language” on, choosing the main language sent you back. The plugin remembers the language you were reading and honours it on the plain address of the site, which is also where the main language lives. Choosing it from the switcher now counts as a choice and is remembered.
  • Fix: the menu switcher was not shown as a dropdown in some themes. The current-language entry did not carry the class themes use for items with a submenu, so in Neve and similar themes the other languages appeared as plain items. Each language now also has its own position.
  • Fix: forms on translated pages could fail to submit. Forms that post to admin-post.php, wp-login.php or wp-comments-post.php were given the language prefix, an address where those files do not exist. They now keep their address; the language is still passed along.
  • Fix: with a hidden login page, /wp-login.php went to an address full of dashes. Plugins such as WPS Hide Login answer a direct visit to wp-login.php by rewriting it to a made-up address that returns “not found”. With the language prefix also on the main language, that address was redirected as /en/-/-/-/… instead of showing the plugin’s own page. Only regular pages are now redirected to their language.
  • New: keep the original address for chosen content types. In Machine Translation → Translation Rules, tick the content types whose address (slug) should stay the same in every language, with only the language prefix added — useful when the slug is a name, such as a hotel, a brand or a product reference. Works standalone and behind TranslatePress, WPML and Polylang. Addresses already translated are not changed.
  • Fix: the crawl bar on the dashboard never reached 100 %. It counted every public post, including WooCommerce products attached to another item, which the crawler skips because they only redirect to it. It now counts the same list of pages the crawler visits.
  • Fix: diagnostic reports could not find a page from its translated address. Pasting the address of a translated page (for example /en/about-me/) reported “post not found”. The language prefix and translated addresses are now understood.
  • Improvement: manual mode is shown as such. Without an API key the Translation Process tab said “Running”, which looked like a stuck translation. It now says “Manual mode” and explains what that means. Diagnostic reports also state it.

1.9.55

  • Fix: sites with WordPress installed in a subfolder could not show their translations. With WordPress at an address such as example.com/blog/, the plugin looked for the language right after the domain and found the folder name instead, so example.com/blog/en/ was never recognised as English and visitors got the original language. The visual editor also opened its preview without the folder (example.com/en/). Language addresses, the language switcher, translated page addresses, the editor and the “translation in progress” page now keep the folder. Sites installed at the root of their domain are not affected.
  • New: contact email in diagnostic reports. The Support tab has an optional contact email field, pre-filled with your administrator email, so support can reply to the report. Clear it to send the report without one. The readme now also explains what a diagnostic report contains.