Langloom
Langloom translates a WordPress site without creating duplicate posts. Translations live in dedicated database tables and are swapped in at request time via WordPress filters, so your post count stays clean and your database stays lean.
Key features:
- No duplicate posts: translations are stored in two custom tables, not as post copies
- Clean URLs: each language gets its own slug (e.g.
/fr/about/) with properhreflangand canonical tags - Visual translation editor: click any text on the front-end to translate it inline, no Gutenberg required
- AI translation: one-click AI-assisted draft translations (requires an API key)
- Full SEO support: translated
<title>, Open Graph tags,<html lang>, and XML sitemaps - Form element support: placeholders, button labels, and select options are automatically detected and translatable
- Query-string mode: optional
?lang=fr_FRrouting for setups that can’t use subdirectories - WordPress 6.5+ native: uses
WP_HTML_Tag_Processor; zero third-party dependencies
Free vs Pro
Langloom is fully functional for one additional language. The visual editor, AI translation, and the complete SEO stack (hreflang, canonical, sitemaps, translated title, meta description and Open Graph) are all included, with no metered character limits and no feature locked behind a paywall.
If you need more than one additional language, Langloom Pro is a separate add-on that raises that limit. It is not required for anything else, and the plugin is fully usable without it.
External services
Langloom works fully offline by default and does not contact any external service during normal site operation. No data is ever sent about your site’s visitors.
The plugin can optionally connect to a third-party machine-translation service only to power the “AI translation” feature, and only when you have explicitly enabled it. To use it you must turn on AI Translation in Settings → Langloom, choose a provider, and paste your own API key. Nothing is sent until an administrator clicks Translate on a piece of content in the editor. Each request sends the text you chose to translate together with the source and target language codes and your API key. Your visitors never trigger these requests.
You can use either of the following providers:
DeepL API
Used to generate machine-translation suggestions for the text you are editing.
What is sent, and when: the selected text plus source/target language codes and your DeepL API key, sent only when an administrator clicks Translate with DeepL selected as the provider. Requests go to https://api-free.deepl.com (free keys) or https://api.deepl.com (paid keys).
Terms of Use: https://www.deepl.com/en/pro-license
Privacy Policy: https://www.deepl.com/en/privacy
Google Gemini API
Used to generate machine-translation suggestions for the text you are editing (works well for Asian and right-to-left languages).
What is sent, and when: the selected text plus source/target language codes and your Google API key, sent only when an administrator clicks Translate with Gemini selected as the provider. Requests go to https://generativelanguage.googleapis.com.
Terms of Use: https://ai.google.dev/gemini-api/terms
Privacy Policy: https://policies.google.com/privacy
Privacy Policy
Langloom does not collect, store, or transmit any personal data about your site’s visitors. The only outbound network requests are the optional, admin-initiated machine-translation calls described under External services above, which are made solely to the provider you configure with your own API key.