Lang Forge integrates with a wide range of WordPress plugins to deliver a seamless multilingual experience. The table below lists all supported integrations, what each one does, how to set it up, and any special notes.
Page Builders
| Plugin | What Lang Forge Does | Setup | Notes |
|---|---|---|---|
| Elementor | Copies full page layout (sections, columns, widgets) to translation drafts. AI translates text within widgets. | No setup needed. Create a translation and the Elementor data is copied automatically. | Lang Forge clears Elementor’s rendered element cache after widget text updates so translated frontend content refreshes immediately. Regenerate Elementor CSS only if styling looks stale. |
| Elementor Pro | Translates Theme Builder templates, popups, and dynamic content in addition to standard Elementor features. | No setup needed. Same workflow as standard Elementor. | Global widgets are shared across languages. If you need different content, override the global widget in the translation. |
| Divi Builder | Copies Divi module structure to translation drafts. AI translates text in modules. | No setup needed. Create a translation and the Divi layout data is copied automatically. | Use the Divi Visual Builder to edit translations for accurate preview. |
| Beaver Builder | Copies page layout and module content to translation drafts. | No setup needed. | Saved rows and modules are shared. Override content in translations as needed. |
| WPBakery Page Builder | Copies shortcode-based layout to translation drafts. AI translates text within shortcodes. | No setup needed. | Legacy backend editor content is also supported. |
SEO Plugins
| Plugin | What Lang Forge Does | Setup | Notes |
|---|---|---|---|
| SEO Forge | Full integration. SEO title, meta description, and focus keyword are included in the translation workflow and translated by AI. | No setup needed. SEO fields appear automatically in the Visual Editor and AI translation. | SEO Forge and Lang Forge share the same Forge API, so the integration is deep and seamless. |
| Yoast SEO | Hreflang tags are coordinated to prevent duplicates. SEO title and meta description are included in the translation workflow. | No setup needed. Lang Forge detects Yoast and integrates automatically. | Yoast’s own hreflang output is suppressed in favor of Lang Forge’s to avoid duplicates. |
| Rank Math | Compatible. Lang Forge adds hreflang tags alongside Rank Math’s SEO features without conflicts. | No setup needed. | If Rank Math generates its own hreflang, disable it in Rank Math settings to avoid duplicate tags. |
| All in One SEO | Compatible. Operates independently without conflicts. | No setup needed. | Disable AIOSEO’s hreflang feature if it has one to avoid duplicate tags. |
E-Commerce
| Plugin | What Lang Forge Does | Setup | Notes |
|---|---|---|---|
| WooCommerce | Translates products, categories, attributes, variations, cart, checkout, emails, and all store strings. Syncs prices, stock, and SKUs across languages. | Enable “Products” in Translatable Content settings. Current builds force-include products when WooCommerce is active. | Free core feature; PRO adds AI and bulk workflow assistance. |
| WooCommerce Subscriptions | Translates subscription product content and subscription-related emails and strings. | No additional setup beyond WooCommerce integration. | Subscription billing and renewal data is shared across languages. |
| WooCommerce Bookings | Translates booking product content and booking-related strings. | No additional setup beyond WooCommerce integration. | Booking availability and calendar data is shared across languages. |
Custom Fields
| Plugin | What Lang Forge Does | Setup | Notes |
|---|---|---|---|
| Advanced Custom Fields (ACF) | Translates all ACF field types including text, textarea, WYSIWYG, repeaters, flexible content, and groups. Fields appear in the Visual Editor for side-by-side translation. | No setup needed. Lang Forge detects ACF fields automatically. | Repeater and flexible content fields are displayed with their full structure in the Visual Editor. |
| ACF Pro | Same as ACF, plus support for Options Pages and Gallery fields. | No setup needed. | Options Page fields are translatable through String Translation. |
| Field Forge | Full integration. All Field Forge field types are translatable. Fields appear in the Visual Editor and are included in AI translation. | No setup needed. Field Forge and Lang Forge share the Forge architecture. | Custom table storage is handled transparently. |
Forms
| Plugin | What Lang Forge Does | Setup | Notes |
|---|---|---|---|
| Form Forge | Translates form labels, placeholders, error messages, and confirmation messages. Each language can show a different version of the form. | No setup needed. Form Forge and Lang Forge integrate natively. | Form submissions record the language used. |
| Gravity Forms | Not fully verified as a dedicated integration yet. Lang Forge does not currently copy Gravity Forms form/entry storage when a translation is created. | Use String Translation only for Gravity Forms strings that Gravity Forms or its add-ons register. | Keep Gravity Forms forms/entries managed in Gravity Forms until a dedicated Lang Forge layer is implemented and tested. |
| WPForms | Translates form field labels and messages through String Translation. | Go to String Translation and filter by Source: “WPForms.” | Lite and Pro versions are both supported. |
| Contact Form 7 | Translates form content through String Translation. | Go to String Translation and filter by Source: “Contact Form 7.” | Each form is a post — you can also create translated form posts directly. |
Caching
| Plugin | What Lang Forge Does | Setup | Notes |
|---|---|---|---|
| WP Rocket | Fully compatible. Each language version is cached separately. | No additional setup needed with the Directory URL format. | If using the Parameter format, add “lang” to the “Cache query strings” setting in WP Rocket. |
| W3 Total Cache | Fully compatible. | No additional setup needed with the Directory URL format. | Page cache is automatically separated by URL path. |
| LiteSpeed Cache | Fully compatible. | No additional setup needed with the Directory URL format. | LiteSpeed’s Vary by Cookie feature works with Lang Forge’s language cookie. |
| WP Super Cache | Fully compatible. | No additional setup needed. | Make sure “Cache pages for logged-in users” is handled correctly if editors preview translated content. |
Media and Content
| Plugin | What Lang Forge Does | Setup | Notes |
|---|---|---|---|
| Yoast Duplicate Post | Compatible. Duplicate Post does not interfere with Lang Forge’s translation duplication feature. | No setup needed. | Use Lang Forge’s Create Translation button instead of Duplicate Post for translations to ensure language linking. |
| Redirection | Useful for URL format migrations. Create 301 redirects from old translated URLs to new ones. | Install and create redirects manually as needed. | Recommended if you change your URL format after going live. |
| Safe Redirect Manager | Same use case as Redirection. | Install and create redirects manually as needed. | Preferred on enterprise hosting that supports this plugin. |
Other Integrations
| Plugin | What Lang Forge Does | Setup | Notes |
|---|---|---|---|
| The Events Calendar | Translates event titles, descriptions, and venue information when Events are enabled as a translatable post type. | Enable “Events” in Translatable Content settings. | Event dates and times are shared across languages. |
| LearnDash | Translates course titles, lesson content, and quiz questions when LearnDash post types are enabled. | Enable LearnDash post types in Translatable Content settings. | Course enrollment and progress data is shared across languages. |
| BuddyPress | Translates BuddyPress strings (activity labels, profile field names) through String Translation. | Go to String Translation and filter by Source: “BuddyPress.” | Member-generated content is not auto-translated. |
| bbPress | Translates forum and topic labels through String Translation. | Go to String Translation and filter by Source: “bbPress.” | Forum structure (forums, topics, replies) can be translated as custom post types. |
Common Integration Scenarios
Scenario: WooCommerce store with Elementor product pages.Set up WooCommerce translation first (enable Products in Translatable Content), then translate Elementor-built product pages using the standard translation workflow. The Elementor layout is copied automatically, and AI translation handles the text within each widget.
Scenario: Corporate site with ACF custom fields and Yoast SEO.Enable the relevant post types in Translatable Content. When translating a page, ACF fields and Yoast SEO fields all appear in the Visual Editor side by side. AI translation covers everything in one pass.
Scenario: Blog with Gravity Forms contact form and WP Rocket caching.Translate blog posts normally. For the contact form, translate form labels through String Translation. WP Rocket caches each language version automatically — no configuration needed.
> Tip: When using multiple integrated plugins, translate the main content first, then check String Translation for any interface strings from those plugins that also need translating.
> Good to know: Lang Forge’s integration detection is automatic. When you activate a supported plugin, Lang Forge detects it and enables the integration. There is no manual “enable integration” step — it just works.
—