This section answers the questions we hear most often from content managers and site administrators who are setting up or managing a multilingual WordPress site with Lang Forge. If your question is not covered here, check the Troubleshooting section below or contact our support team.
Can I translate custom post types?
Yes. Go to Lang Forge > Settings and scroll to the Translatable Content section. You will see every post type registered on your site, including custom ones from other plugins (like WooCommerce Products, Events from events plugins, Portfolio items, Testimonials, etc.). Check the box next to each type you want to translate. After saving, the Language column and translation metabox appear on those post types.
What happens to my translations if I deactivate Lang Forge?
Your translations are not lost. Every translation is a regular WordPress post stored in your database. If you deactivate Lang Forge, the posts remain exactly where they are. However, the language routing (/es/about/), the language switcher, and the visible translation links between posts will stop working. If you reactivate Lang Forge later, everything is restored because the translation metadata is preserved in the database.
Can I use Lang Forge with page builders like Elementor?
Yes. When you create a translation of an Elementor-built page, the layout structure (sections, columns, widgets) is copied to the new translation draft. You open the translation in Elementor or Lang Forge’s Visual Editor and edit only the text content within each widget — the layout, styling, and design remain intact. When Lang Forge saves Elementor widget text, it clears Elementor’s rendered element cache so the translated frontend content refreshes immediately. Elementor Free/core widgets have been verified; Elementor Pro Theme Builder, Forms, Popup Builder, third-party widget packs, and Divi / Beaver Builder / WPBakery layouts should be checked on the target site before you remove the old translation workflow.
Does Lang Forge slow down my site?
No. Lang Forge uses an in-memory translation cache so language detection and content switching happen without extra database queries on every page load. Language detection runs once per request, not once per content element. On a properly configured host, the performance impact is negligible.
Can I have different menus for different languages?
Yes. Lang Forge automatically creates language-specific menu locations for every location your theme defines. You create separate menus for each language and assign them to the corresponding locations. See the “Translating Menus” section for detailed instructions.
Do I need my own AI API keys?
No. All AI translation runs through the Forge API, which is built into the plugin. You do not need accounts with OpenAI, Google Translate, or any other service. AI usage draws from your Forge account credit pool: the one-time welcome pack plus any pay-as-you-go packs you buy. Additional translation engines are on the roadmap.
What AI model is used to translate content?
Every Lang Forge installation uses ChatGPT 4o mini — a fast, cost-efficient OpenAI model that runs entirely on our servers. You can confirm which model is active on Lang Forge → Settings → Translation Model.
Can Lang Forge auto-detect a visitor’s language?
Yes. Enable Lang Forge → Settings → Auto-detect Language and, on a visitor’s very first page load, Lang Forge reads the Accept-Language header their browser sends. If it matches one of your active non-default languages, the visitor is redirected to the corresponding /{lang}/ URL (for example, a German browser landing on example.com/ is redirected to example.com/de/). The redirect fires once per browser — Lang Forge sets a long-lived cookie after the first visit, so the visitor can later navigate back to / and stay on the default language. The redirect is skipped for non-GET requests, AJAX calls, and search engine crawlers that don’t send Accept-Language, so it is SEO-safe. The older behaviour of silently serving translated content at the canonical URL has been replaced — that broke hreflang and duplicate-content signals.
Can multiple people translate at the same time?
Yes. Lang Forge supports a Translator role that lets you assign team members to specific languages. Each translator works on their assigned language simultaneously without conflicts. The Translation Analytics dashboard tracks who is translating what so you can coordinate effectively.
Does the language switcher work with caching plugins?
Yes. Lang Forge is compatible with WP Rocket, W3 Total Cache, LiteSpeed Cache, and WP Super Cache. Each language version of a page is cached separately. Just make sure your caching plugin is configured to vary the cache by URL, which is the default behavior for most plugins when you use the Directory URL format.
Can I translate categories and tags?
Yes. Go to any taxonomy page (Posts > Categories, Posts > Tags, Products > Categories, etc.) and click on a term. A translation interface appears where you can provide the translated name, slug, and description for each language.
What is the difference between the Visual Editor and the Frontend Visual Editor?
The Visual Editor (admin-side) shows original and translation side by side in a split-screen layout within the WordPress admin. Best for translating entire posts segment by segment. The Frontend Visual Editor lets you click on text elements on your live site and translate them in place. Best for reviewing, polishing, and making quick fixes to existing translations.
> Tip: If you have a question about a specific feature, use the search function in our support documentation (linked from Lang Forge > Account in your WordPress admin) for detailed articles.
> Good to know: Lang Forge is actively developed with regular updates. If a feature you need is not available, check the changelog or contact support — it may already be in development.
[Screenshot: The Lang Forge Account page showing links to documentation, support, and the FAQ section]
—