Transleti Translator – Multilingual & Automatic Translation
| 开发者 |
transleti
grupobouso |
|---|---|
| 更新时间 | 2026年8月18日 05:30 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- 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.
- 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.
- Multilingual sitemap with hreflang — separate
<url>entries per language (the format Google explicitly documents) with self-referential hreflang andx-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. - Menu translation — duplicates and translates navigation menus per language.
- HTML entity and shortcode protection — prevents corruption of
©,[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.
- Install and activate the plugin.
- Choose your default language and the target languages you want to publish.
- 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.
- The language switcher, hreflang sitemap and per-language slugs work out of the box.
- Install and activate the plugin.
- Sign up at https://transleti.com to get your API key (flat-rate subscription with a 14-day money-back guarantee).
- Enter your Transleti API key in the plugin settings.
- Choose your default language and the languages you want to publish.
- The plugin runs a background job that translates posts, menus, slugs and SEO meta automatically.
- Optionally refine any translation manually from the WordPress post editor — your edits are preserved on re-translation.
安装:
- Upload the
transleti-translatorfolder to/wp-content/plugins/, or install through the WordPress plugin installer. - Activate the plugin via the Plugins menu in WordPress.
- Go to Settings → Transleti Translator.
- Select your default language and target languages.
- (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.
- Save settings.
屏幕截图:
![Language Switcher — floating selector, [transleti-switcher] shortcode and automatic navigation menu integration with flags, dropdowns or text styles.](https://cdn.jsdelivr.net/wp/transleti-translator/assets/screenshot-3.png)
常见问题:
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).
更新日志:
- New: works properly alongside caching plugins. Serving pages from a cache is what makes a site fast, but a translated site has to be careful about which pages get stored. When a page finishes translating, its cached copy is now cleared straight away, so visitors see the new text instead of waiting for the cache to expire on its own.
- Fix: the "translation in progress" page could be cached and outlive the translation it was waiting for. A visitor could be shown that holding page for as long as the cache entry lived — up to a week on some setups — with the finished page sitting right behind it. It is now kept out of the cache in all four setups: on its own, and alongside WPML, Polylang or TranslatePress.
- Fix: the entry page could get stuck in the first visitor's language. With automatic language detection and a cache in front, the first visitor's redirect could be stored and then handed to everyone else, so a German visitor landed in Spanish. The entry page is no longer cached while detection is switched on.
- Fix: the "Test connection" button reported a failure when running alongside WPML, Polylang or TranslatePress, against a translation server that was answering perfectly.
- New: four more English variants — Canada, Ireland, New Zealand and Singapore. Each gets its own address, its own hreflang tag and its own stored translations, so a search engine can serve the right one to each market instead of collapsing them into a single page. Canadian English is treated properly rather than as a copy of British: it takes "colour", "centre", "travelled" and "licence", but keeps "organize", "realize" and "analyze", which is how Canada actually writes.
- Fix: text your theme or plugins had already translated was being translated a second time. If a theme ships its own Spanish, German or French wording, that wording was being picked up as if it were your original English and sent to be translated again — so a menu item could drift from the theme's own phrasing into a second-hand version of it, and the same text piled up in the stored translations of every language. Interface text now goes through a single path, whichever theme you use.
- Fix: currency symbols were being translated. The currency selector lists every currency in every language, so a bare symbol like "kr" reached the engine with no context and came back as something else entirely — in some languages a whole unrelated word. Symbols and currency abbreviations are now left exactly as they are.
- Fix: a translation could arrive cut off half-way and still be published. When a translation contained quotation marks, everything after the first one could be lost, and the shortened text was stored and shown as if it were complete — a headline could end mid-sentence. Incomplete translations are now rejected and translated again.
- Fix: text captured while a page was being served in the wrong language is no longer stored as new source text, which was the other way the problem above could start.
- Fix: the whole site could start returning 404 on every page except the front page. WordPress rebuilds the rewrite rules in .htaccess from your site address, and while a translated page was being served the language ended up written into that file (
RewriteBase /pl/), so every pretty permalink pointed at a folder that does not exist. Anything that regenerates those rules could trigger it: saving your permalink settings, activating a plugin, or any theme or plugin that refreshes them. Two things made it hard to spot — nothing is written to any log, and the web server keeps serving from the rules it already had in memory, so the site carries on working and only breaks at the next server restart, hours or days later. The language is now kept out of that file whatever regenerates it. If your site is currently showing 404 on inner pages, open Settings → Permalinks and press Save once after updating; that rewrites the file correctly. Earlier releases are listed in changelog.txt, included with the plugin.