Most multilingual plugins translate the post title and content \u2014 and stop there. Elementor keeps its page content separate from WordPress's standard fields, so headings, text widgets, accordions, and buttons often stay in the original language. Fluentor was built the other way around: it reads Elementor's page data directly, so widget content translates along with everything else.<\/p>\n\n
On top of full Elementor coverage, Fluentor gives you language-aware URLs, SEO-ready hreflang, one-click DeepL translation, and a translation-file editor for WordPress core, theme, and plugin strings \u2014 the everyday work you'd otherwise reach for Loco Translate to do. New AI translations are created as drafts for your review. You don't even need an AI key: duplicate any page into a new language and translate it by hand, layout intact.<\/p>\n\n
[fluentor_language_switcher]<\/code> shortcode.<\/li>\n<\/ul>\n\nMultilingual structure<\/h4>\n\n\n- Language-aware URLs in directory (\/en\/about\/) or subdomain (en.example.com\/about\/) modes.<\/li>\n
- Optional hiding of the language prefix for the default language and browser-language detection.<\/li>\n
- Slug sharing across languages, or automatic slug translation for post types and taxonomies.<\/li>\n
- Language assignment for posts, pages, custom post types, and terms, with a visual setup wizard.<\/li>\n
- One-click Polylang bridge \u2014 imports your existing languages, translations, and settings.<\/li>\n<\/ul>\n\n
AI translation<\/h4>\n\n\n- Translate any post or page with one click \u2014 the Translate<\/strong> quick action duplicates the page and translates it in a single step through DeepL.<\/li>\n
- Free with no usage caps \u2014 bring your own DeepL key and pay the provider directly, not a subscription.<\/li>\n
- Duplicate any post or page with its layout intact for manual translation \u2014 no AI and no limits.<\/li>\n
- Translates post fields, custom fields (including ACF), and Elementor widget content (titles, text, accordions\/FAQ, links, and more).<\/li>\n
- Provider API keys are encrypted at rest and masked in the settings screen.<\/li>\n<\/ul>\n\n
SEO<\/h4>\n\n\n- Automatic hreflang alternate tags with optional x-default fallback.<\/li>\n
- Localized canonical URLs \u2014 compatible with the Yoast SEO, Rank Math, and AIOSEO canonical filters.<\/li>\n
- Correct lang and dir attributes, plus locale meta tags.<\/li>\n<\/ul>\n\n
Translation file editor<\/h4>\n\n\n- Browse and edit translation files (.po) for WordPress core, themes, and plugins.<\/li>\n
- Compile to .mo, .json, and .l10n.php; generate POT templates; import from translate.wordpress.org or upload your own PO file.<\/li>\n
- Timestamped backups per file with diff and restore.<\/li>\n<\/ul>\n\n
Fields & media<\/h4>\n\n\n- ACF and Pods support \u2014 post fields, repeaters, and relationships follow their translations. (ACF options pages and term fields are part of Fluentor Pro.)<\/li>\n
- Media translation with optional auto-duplication of uploads per language.<\/li>\n<\/ul>\n\n
Reliability<\/h4>\n\n\n- Repeated phrases are remembered, so the same text is never sent to your provider twice \u2014 faster and cheaper over time.<\/li>\n
- If a provider is slow or busy, translations are retried automatically.<\/li>\n
- Translation history with automatic cleanup, plus an optional debug log for troubleshooting.<\/li>\n<\/ul>\n\n
Fluentor Pro<\/h4>\n\n
A separate Fluentor Pro<\/strong> plugin adds 13 more AI providers (OpenAI, Gemini, Claude, DeepSeek, Mistral, and more), custom domains per language, ACF options pages and taxonomy-term translation, batch translation with diff previews, AI auto-translation of theme and plugin text files, and Elementor Theme Builder template swapping.<\/p>\n\nDocumentation and support<\/h3>\n\n\n- Website and documentation<\/a><\/li>\n
- WordPress.org support forum<\/a><\/li>\n<\/ul>\n\n
Requirements<\/h3>\n\n\n- WordPress 5.6 or newer.<\/li>\n
- PHP 7.4 or newer.<\/li>\n
- Elementor is recommended (required for Theme Builder template swapping and the language switcher widget; core multilingual features work without it). Tested with Elementor through 4.2.<\/li>\n<\/ul>\n\n
Privacy<\/h3>\n\n
Fluentor does not track users or send data to external servers on its own. No analytics, telemetry, or third-party assets are loaded from outside your site; all plugin code, scripts, and styles are served from your own installation.<\/p>\n\n
The only data that leaves your site is the content you explicitly choose to translate, which is sent to the AI provider you configure (DeepL in this plugin; the separate Fluentor Pro plugin adds OpenAI, Gemini, Claude, OpenRouter, and more) to produce the translation. Each provider is a separate service with its own terms of use \u2014 by adding an API key and translating content you consent to that provider processing the submitted text; the DeepL terms of use and privacy policy are linked in the External services section below.<\/p>\n\n
API keys are stored encrypted at rest on your site and are never shared with any third party.<\/p>\n\n
This plugin (the WordPress.org version) includes no usage-tracking SDK and shows no data-collection consent screen on activation. The separate Fluentor Pro<\/strong> plugin is licensed and updated through the Freemius service; Fluentor Pro connects to that service only to validate your license and check for updates.<\/p>\n\nExternal services<\/h3>\n\n
AI translation connects to the DeepL API<\/strong> to translate the text you choose. Bring your own key: add your DeepL API key in Multilingual Settings, and the service is contacted only when you choose to translate content.<\/p>\n\n\n- What the service does:<\/strong> neural machine translation of the text you select.<\/li>\n
- What is sent and when:<\/strong> the text you choose to translate plus its source and target languages, sent only when you run a translation; your API key is used solely to authenticate the request and is stored encrypted at rest.<\/li>\n
- Service:<\/strong> DeepL SE \u2014 Terms of Use<\/a> \u00b7 Privacy Policy<\/a><\/li>\n<\/ul>\n\n
The separate Fluentor Pro<\/strong> plugin adds additional AI providers (OpenAI, Google Gemini, Anthropic Claude, and more); those providers are not part of this plugin and are never contacted by it.<\/p>\n\n\n\n- In your WordPress admin, go to Plugins \u2192 Add New<\/strong>, search for \"Fluentor\", and click Install Now<\/strong> (or upload the plugin ZIP under Plugins \u2192 Add New \u2192 Upload Plugin<\/strong>).<\/li>\n
- Activate the plugin.<\/li>\n
- Complete the Multilingual Setup Wizard<\/strong> to choose languages, URL behavior, media\/post-type\/taxonomy settings, and slug options.<\/li>\n
- Optionally, add your DeepL API key<\/strong> under Fluentor \u2192 Multilingual Settings \u2192 Machine Translation<\/strong> to enable one-click AI translation \u2014 you can translate manually without any API key.<\/li>\n<\/ol>\n\n\n
\nWhy doesn't my Elementor content translate with other multilingual plugins?<\/h3><\/dt>\nElementor keeps its page content separate from the standard WordPress content field. Many multilingual plugins only read the standard fields \u2014 title, post content, excerpt \u2014 and never touch Elementor's own page data, so widget text, headings, and buttons stay in the original language even after the page is \"translated.\" Fluentor reads and translates that page data directly, so widget content translates along with everything else.<\/p><\/dd>\n
Which AI providers are supported?<\/h3><\/dt>\nThis plugin supports DeepL<\/strong> \u2014 add your API key under Fluentor \u2192 Multilingual Settings \u2192 Machine Translation. The separate Fluentor Pro<\/strong> plugin adds 13 more providers, including OpenAI, Google Gemini, Anthropic Claude, DeepSeek, and Mistral.<\/p><\/dd>\nDo I need an AI provider (API key) to use Fluentor?<\/h3><\/dt>\nNo. Without any API key you can still build your full multilingual structure and translate content manually: use Duplicate (Translate Later)<\/strong> to copy a post or page into another language with its layout intact, then write the translation yourself. A DeepL API key is only needed for the one-click AI translation.<\/p><\/dd>\nWhat is the difference between Fluentor and Fluentor Pro?<\/h3><\/dt>\nFluentor (this plugin) is free and fully functional. The separate Fluentor Pro<\/strong> plugin shares the same settings and adds 13 more AI providers, batch translation with diff previews, custom domains per language, ACF options pages and taxonomy-term translation, and Elementor Theme Builder template swapping. To upgrade, install and activate Fluentor Pro \u2014 it takes over your content and settings, and the free plugin is deactivated automatically so the two never run at once.<\/p><\/dd>\nDoes Fluentor require Elementor?<\/h3><\/dt>\nThe core multilingual, URL, slug, and AI-translation features do not require Elementor. Elementor is needed for the dedicated language switcher widget \u2014 and, in Fluentor Pro, for Theme Builder template swapping.<\/p><\/dd>\n
How do I translate a single post?<\/h3><\/dt>\nOn the post list table for any enabled post type, use the Translate<\/strong> row action, choose the target language, and confirm. The quick action duplicates the page and translates it in one step with DeepL. To copy a page with its layout intact for manual translation, use Duplicate (Translate Later)<\/strong> in the same dialog \u2014 it does not use AI.<\/p><\/dd>\nHow do existing posts get a language?<\/h3><\/dt>\nThe setup wizard and the Multilingual Settings \u2192 Existing Content Assignment<\/strong> tool assign languages to existing content (only content without language information, content in the default language, or all enabled content types).<\/p><\/dd>\nCan I use Fluentor alongside Polylang?<\/h3><\/dt>\nWhen Polylang is detected, Fluentor runs in a bridge mode and offers a Polylang Bridge<\/strong> migration screen to import Polylang content and settings into Fluentor metadata.<\/p><\/dd>\nHow are translation files stored?<\/h3><\/dt>\nOverride translation files are stored in a plugin-owned folder inside your uploads directory (wp-content\/uploads\/fluentor<\/code> by default), so your WordPress core language files are never overwritten. Developers can change the location and add extra write protections with two optional constants \u2014 see the plugin documentation.<\/p><\/dd>\n\n<\/dl>\n\n\n1.0.0<\/h4>\n\n\n- Initial release on WordPress.org.<\/li>\n
- Full multilingual setup with folder or subdomain URLs per language, language switcher, SEO-ready hreflang tags, and translated media.<\/li>\n
- Translate Elementor pages \u2014 titles, text, accordions, FAQs, links, and more \u2014 and duplicate pages across languages with the layout intact for manual translation.<\/li>\n
- Full ACF and Pods support for post fields, repeaters, and relationships.<\/li>\n
- One-click AI translation of any post or page through DeepL, and a complete translation-file editor for theme, plugin, and WordPress text.<\/li>\n
- One-click import from Polylang.<\/li>\n
- The separate Fluentor Pro plugin adds 13 more AI providers, batch translation, custom domains per language, and ACF options and term translation.<\/li>\n<\/ul>","raw_excerpt":"Free AI translation and multilingual content for WordPress, built for Elementor \u2014 page-builder content included, not just post text.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/mn.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/359216","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mn.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/mn.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/mn.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=359216"}],"author":[{"embeddable":true,"href":"https:\/\/mn.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/tresv"}],"wp:attachment":[{"href":"https:\/\/mn.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=359216"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/mn.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=359216"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/mn.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=359216"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/mn.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=359216"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/mn.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=359216"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/mn.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=359216"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}