About this plugin
Publish independent WordPress pages and posts in multiple languages, with your chosen original language. Keep existing original-language URLs and place translated pages beneath native language homepages, such as /da/kontakt/ and /de/kontakt/.
Each translation is separate content that you can edit in WordPress or Avada. Use manual or optional local browser translation, without an API key. Nothing is synchronized or published automatically.
Features:
- Language homepages, translated page hierarchies and original-language source relationships.
- A shortcode language switcher with text, local country flags or both; horizontal and dropdown layouts.
- Optional classic-menu mappings and navigation links that follow a selected language. An explicit preference is remembered in browser storage for 30 days.
- Reciprocal hreflang and x-default links, page language/direction, native sitemaps and indexing controls, with Yoast/Rank Math integrations.
- Copy pages/posts or create linked translation drafts, retaining local builder metadata, custom fields, featured-image references and terms.
- A translation overview, language/missing-translation filters and explicit review checkpoints that flag changes to the original.
- Exact short-label dictionaries, reusable original-word lists and local browser translation of pending labels.
- A browser workbench with visual/text editing, supported text formatting and URL names based on the translated title, original name or custom input.
Scope and compatibility
On a new installation, choose any supported original language using a preset or custom language values before adding translation languages. The choice is locked once a translation language is added. Changing the original language on an established site requires a separate migration.
This setting does not change WordPress Site Language or translate existing content. Use pretty permalinks and a static original-language homepage. Translated posts keep ordinary WordPress post permalinks; only pages use language folders.
Products, taxonomies, archives, search results, checkout and emails are not automatically translated. Label dictionaries cover supported exact frontend labels, not every theme/plugin string.
Create translation and Copy retain local Avada/ACF metadata. Browser translation saves supported formatting and selected ACF text fields, excluding layouts, other fields, terms and SEO settings. Configure global builder elements and externally stored data separately.
Menu replacement applies to classic theme locations. Explicit Avada menu selections and Navigation blocks need manual configuration. Test with your theme, SEO plugin and cache; deactivate competing multilingual routing plugins.
SEO plugins can apply additional indexing rules. Hreflang and sitemaps do not guarantee Google indexing. Canonical tags are not replaced.
Browser translation and privacy
Optional browser translation starts only after a click, using the native Translator API in a supported desktop browser such as Chrome. HTTPS or localhost and an available original-to-target language pair are required. Availability depends on browser policy, device support and storage.
Manual editing and saving remain available without this API.
Translation runs on the user’s device. The plugin sends no text to a hosted translation API, requires no API key or translation account, and has no cloud fallback. Chrome may connect to Google’s infrastructure to download language models after translation is started, involving normal download connection information handled by Chrome.
The plugin does not fetch executable PHP or JavaScript from that infrastructure.
Saving workbench results sends translated content, source ID/fingerprint, language, URL choices and a security nonce to your own WordPress server. Dictionary saving sends its edited form rows there. Nothing is saved, published or marked reviewed automatically; review accuracy before saving.
Copy unsaved work before leaving.
Provider information:
com/docs/ai/translator-api
com/privacy
com/chrome/terms/
com/terms
No analytics, telemetry or diagnostic uploads are included. Optional language navigation stores an explicit language choice and a 30-day expiry in localStorage, without a preference cookie or telemetry upload. Settings, relationships and saved dictionaries remain in the WordPress database.
The voluntary support link opens PayPal only when clicked.
Third-party resources
txt. No flag files are fetched externally.