Below are answers to the most common questions we receive from site owners and content managers working with Lang Forge. If your question is not listed here, contact our support team for help.
Installation and Setup
Q: What are the minimum requirements to run Lang Forge?Lang Forge requires WordPress 5.8 or higher and PHP 7.4 or higher. It works with any standard WordPress hosting environment, including shared hosting, VPS, managed WordPress hosts (like WP Engine, Kinsta, and Flywheel), and local development tools like MAMP and Local. No special PHP extensions or server modules are required beyond what WordPress itself needs.
Q: Can I install Lang Forge alongside WPML, Polylang, or TranslatePress?We recommend running only one multilingual plugin at a time. While Lang Forge includes a WPML compatibility layer that prevents function conflicts, having two multilingual plugins active simultaneously can cause unexpected behavior with URL routing and language detection. When Lang Forge detects that WPML’s core (SitePress) is active and configured, it shows a yellow warning notice on every wp-admin page and an inline conflict callout at the top of Lang Forge → Languages explaining the specific tables and behaviours that collide. If you are migrating from WPML, Polylang, or TranslatePress, activate Lang Forge and deactivate the previous plugin in the same session. See the “Recipe: Migrating from WPML to Lang Forge” section for a detailed migration guide.
Q: Does Lang Forge work on WordPress Multisite?Yes. Lang Forge can be activated on individual sites within a Multisite network. Each sub-site manages its own set of languages and translations independently. Network-wide activation is also supported, allowing the network administrator to activate Lang Forge across all sites at once. PRO licenses on Multisite count each sub-site as one site toward your plan limit.
Q: I activated Lang Forge but I do not see the menu in my admin sidebar. What is wrong?This is almost always a user role issue. Only users with the Administrator role see the full Lang Forge menu by default. If you are logged in as an Editor or another role, you will see a limited set of menu items. If you are an Administrator and still do not see the menu, deactivate and reactivate the plugin from the Plugins page. This forces WordPress to re-register the menu items.
Translation Workflow
Q: Can I translate the same post into multiple languages at the same time?Yes. Each language has its own independent translation draft. You can open translations in multiple browser tabs and work on them simultaneously, or assign each language to a different team member. There is no locking mechanism that prevents parallel translation — each translation is a separate WordPress post with its own editing state.
Q: How do I translate categories, tags, and custom taxonomies?Lang Forge does not create the translated term for you. Add it yourself as an ordinary term with its own name, slug, and description: on Posts > Categories, or on the list page of any other public taxonomy, fill in the Add New form. The form has a Language select, so choose the language of the new term there. Then link the two terms. Open the original term: its edit screen has a Language select and a Translations row that lists the other active languages. For a language with no linked term, type the ID of the translated term into the Term ID to link field and save the term. A linked term appears as a link to its edit screen, and the x button next to it removes the link. The term list also has a Language column.
Q: Can I schedule translated posts to publish at a specific date and time?Yes. Translated posts support the same scheduling feature as any regular WordPress post. Open the translation in the editor, set the desired publication date and time in the Publish panel, and click Schedule. The translation will go live at the scheduled time. The language switcher will not show the language for that page until the scheduled post actually becomes published.
Q: What happens when I update the original post after it has been translated?If you have PRO, the Content Diff feature detects the changes and flags all linked translations as “needs update.” You will see a “Content Changed” notice with a warning icon in the Language metabox of the translation, and its Show Changes button shows exactly what changed. The post list does not mark these translations. On the Free plan, there is no automatic detection — you need to check manually whether translations are still current after editing the original.
Q: What is the AI Quality Check in the Visual Editor, and should I trust its suggestions?The AI Quality Check (QA Check button in the Visual Editor toolbar) is a second-opinion reviewer. It compares the original with your translation and flags missing content, meaning changes, tone mismatches, and grammar issues, then offers one-click fixes. Treat it as a spellchecker-style assistant, not an authority — for marketing copy and brand voice you should still review every suggested fix before applying. For factual content (product specs, technical documentation), suggestions are usually safe to accept directly.
When you click “Fix” on an issue, the translation is updated both on the server and live in the editor so you see the change immediately. You can always edit the applied text further before saving.
Q: Can I use Lang Forge to translate comments on my blog posts?Yes. Comment auto-translation is a PRO feature. You can turn this on with the Translate Comments option in the AI Translation card of Lang Forge > Settings. Once it is on, each new comment is saved with the site language that was current when it was posted, and a visitor who reads it in a different site language sees an AI translation of it with an “(auto-translated)” note. Comments posted before the option was turned on have no saved language and are not translated, and very short comments are left as they are. The translation is saved with the comment, so it is made once per language. Comments are translated using AI credits, and the original comment is always preserved — the translated version is stored separately.
URL Format
Q: Can I change the URL format after my site has been live for months?You can change it, but you need to handle redirections manually. When you switch URL formats, previously indexed URLs (like yoursite.com/es/about/) will stop working. Install a redirect plugin such as Redirection or Safe Redirect Manager and create 301 redirects from every old translated URL to the new format. Without redirects, visitors arriving from search engines or bookmarks will see 404 errors.
The Directory format requires “pretty permalinks” to be enabled (anything other than the Plain setting in Settings > Permalinks). If you are using plain permalinks, Lang Forge automatically falls back to the Parameter format (?lang=es). We recommend switching to a pretty permalink structure (such as Post name) for readable URLs.
Lang Forge supports Unicode slugs, so translated URLs can contain characters from any script — Cyrillic, Chinese, Arabic, and others. WordPress encodes these characters in the URL using percent-encoding, which is standard web behavior. For readability, most browsers display the decoded characters in the address bar. You can also manually set a Latin-character slug for any translation if you prefer ASCII-only URLs.
Compatibility
Q: Does Lang Forge work with my theme?Lang Forge does not depend on specific theme features or frameworks. Themes that use standard WordPress functions for menus, widgets, and content display work without any adjustments. Lang Forge copies the layout data of Elementor and Divi in the free plugin, and of WPBakery, Beaver Builder, Oxygen, and Brizy in the Pro add-on. There is no code specific to Astra, OceanWP, or any other theme, apart from the post settings of Kadence and GeneratePress that the Pro add-on copies. If your theme uses hardcoded text instead of translatable strings, those pieces of text will need to be handled through custom CSS or theme file edits.
Q: Is Lang Forge compatible with WP Rocket and other caching plugins?With the Directory URL format each language version of a page has its own URL, so a page cache stores it as a separate entry. If you use the Parameter format, make sure your caching plugin is configured to vary the cache by the lang query parameter.
Yes. CDNs cache pages by URL, and since each language version of a page has its own unique URL (whether through directories, subdomains, or parameters), the CDN will cache and serve each language independently. With the Directory or Subdomain URL formats each language version has its own URL. If you use a cookie-based language detection alongside a CDN, make sure to configure the CDN to bypass cache for requests with the Lang Forge language cookie, or disable cookie-based detection entirely and rely on URL-based language routing.
Performance
Q: How many languages can I add before performance becomes a concern?Language detection and content routing happen once per page request, not once per element. The main consideration with many languages is content management overhead — translating a single post into 30 languages is a significant amount of work.
Q: Does Lang Forge add extra database queries to every page load?Yes. Lang Forge reads the language from the address. It reads the translation groups of the posts on a page with one query, with one more query for the items of each menu, and keeps them for the rest of the request. The posts of a translation group are loaded into the WordPress object cache with one query; a persistent object cache such as Redis or Memcached keeps them between requests.
License and Billing
Q: Can I transfer my PRO license to a different website?Yes. Go to your account dashboard on the Lang Forge website and deactivate the license on the old site. Then activate it on the new site using the same license key. License transfers can be done as many times as needed within your plan’s site limit.
Q: What happens when my license expires?When your annual license expires, the free features keep working and all translations, settings, and content remain stored. Free-plan access is enforced again at runtime: AI translation, bulk jobs, Translation Memory REST/import/export, Content Diff, QA checks, Analytics, and import/export stop executing until the license is renewed. Unlimited languages, Glossary, and WooCommerce translation remain available on Free. Existing PRO data is preserved and becomes active again after renewal; it is not deleted during downgrade. You no longer receive Pro updates or AI credits until you renew, and unused credits stay in your account.
Direct admin REST/AJAX writes follow the same active language set as the UI and frontend. Free no longer caps the number of active languages, but unknown or inactive language codes still return language_not_available / HTTP 403 instead of mutating _langforge_language through a hidden request.
No. All AI credits — the one-time welcome bonus granted at the first activation of a paid Forge license, plus any pay-as-you-go packs you buy — live in a single account-level pool that carries forward indefinitely. There’s no monthly reset, no billing-cycle boundary, no “use it or lose it” allowance: your plan is license-only, credits are separate and always yours until spent.
Migration
Q: I have an existing site with WPML. How long does migration take?Migration time depends on the size of your site and on how much of the migrated content you review. The data migration step — Lang Forge reads the WPML translation tables and recreates the language links automatically. WPML Translation Management jobs, Advanced Translation Editor history, translator assignments, baskets, and review statuses are not converted into Lang Forge workflow state. See the “Recipe: Migrating from WPML to Lang Forge” section for the complete process.
Q: Can I migrate from Polylang to Lang Forge?Yes. The migration process for Polylang is similar to WPML migration. Lang Forge reads Polylang’s taxonomy-based language assignments and term relationships to reconstruct translation groups. Since Polylang stores language data as custom taxonomies, the migration is straightforward. Go to Lang Forge > Tools > Migration and select “Polylang” to start the automated migration.
Q: Can I migrate from TranslatePress to Lang Forge?Yes. Go to Lang Forge > Tools > Migration and select “TranslatePress.” TranslatePress stores translated page content in dictionary tables instead of separate translated posts, so Lang Forge creates translated post copies, links them to the source post, imports default/active language settings, preserves the “hide default language in URL” setting, and imports TranslatePress gettext strings into String Translation. Review the migrated pages before deleting TranslatePress.
Q: Will migration break my existing URLs and SEO rankings?If you use the same URL format in Lang Forge as you had in your previous plugin, your URLs will remain identical. For example, if WPML was configured with the Directory format (/es/about/) and you choose Directory in Lang Forge, all translated URLs stay the same. Lang Forge generates the hreflang tags and sitemaps again.
AI Credits
Q: How accurate are AI credit cost estimates shown before translation?Credits are charged per action: translating a whole post starts at 3 credits, a single segment or string starts at 1, and an AI quality check starts at 1. The estimate shown for a bulk translation is the number of posts times 3 credits. In a bulk run, the title and the excerpt of a post go as one request of 3 credits and every piece of its text (split at about 2,000 characters) as one more request of 1 credit, so the final usage is higher than the estimate for a post that has text; a request above 10,000 tokens costs more than its starting price.
Q: Can I use my own translation API (Google Translate, etc.) instead of the built-in AI?Lang Forge’s AI translation uses the Forge API exclusively (GPT-4o-mini) and does not support plugging in third-party translation APIs directly. This design lets the AI translation use your glossary and Translation Memory. If you prefer a specific translation engine, you can export your content as XLIFF, translate it externally, and import the completed translations back into Lang Forge.
Q: Which AI model translates my content?Every Lang Forge installation uses ChatGPT 4o mini — a fast, cost-efficient OpenAI model running on our servers. You can confirm this on Lang Forge → Settings → Translation Model. You do not enter an API key.
Q: Is there a way to preview an AI translation before it uses credits?Credits are only consumed when the translation is actually generated. The strings page and the Visual Editor show the cost of a run in a dialog, Duplicate + AI Translate shows the Estimated Translation Cost before it starts, and the AI button of a post carries a credit badge with the price. Your remaining balance is in the credit chip in the header of every Lang Forge screen. Once the translation is generated, you can review, edit, and even discard it — but the credits for that generation are already used. If a request fails on the service, no credits are deducted for it: the service deducts credits only after the AI has returned a translation. A post is translated in several requests, so the parts that came back before a failure were charged; they are kept for one hour and a second try asks the AI only for the parts that failed.
Language Detection
Q: How does Lang Forge decide which language to show a first-time visitor?If Auto-detect Language is off (the default), visitors always land on the site’s default language unless they click a specific language in the switcher or navigate to a language-prefixed URL. If Auto-detect is on, Lang Forge reads the Accept-Language header from the visitor’s browser on their first page load. If the browser’s preferred language matches one of your active non-default languages, Lang Forge issues a 302 redirect to /{lang}/. A lf_autodetect_done cookie (1-year lifetime) is set at the same time, so the redirect runs only once per browser — the visitor can navigate back to / later and stay on the default language. POST requests, AJAX calls, and anything without an Accept-Language header (search engine crawlers) are never redirected, so SEO signals are not affected.
Previously, enabling Auto-detect would serve translated content at the canonical URL (for example, German content at example.com/). That broke hreflang annotations (the / URL was in two languages at once), confused search engines into merging or de-duplicating pages, and made the default-language URL un-cacheable by CDN. The 302 redirect approach keeps every language on its own URL, so hreflang, canonical URLs, duplicate-content signals, and page caching all behave correctly.
—