When you add a new language to an established site, you might be looking at dozens or hundreds of posts and pages that need translations. Creating them one by one would take days or weeks. The bulk translation feature lets you duplicate your entire content library into a new language — and optionally AI-translate it all — in a single operation that runs in the background while you continue working.
This feature is the fastest way to launch a new language version of your site. Combined with the Glossary (for consistent terminology) and Translation Memory (for reusing past translations), bulk translation can take a 200-page site from zero to fully translated in a matter of hours instead of weeks.
Understanding the two bulk options
| Option | What it does | Time required | Best for |
|---|---|---|---|
| Duplicate All | Creates a draft copy of every translatable post and page in the target language, with content still in the original language | Minutes (no AI processing) | Teams who will translate manually, teams sending content to a translation agency via XLIFF export, teams who want full control over every translation |
| Duplicate + AI Translate | Creates draft copies AND runs AI translation on each one | Minutes to hours depending on content volume | Launching a new language quickly, sites with mostly straightforward content (not highly creative), teams who will review AI output before publishing |
Step-by-step: Duplicating all content to a new language
- Go to Lang Forge > Tools and open the One-Click Site Duplication card (the bulk duplicate controls live in Tools, not under Translation Status — Translation Status is a read-only overview page)
- Pick the source language dropdown on the left (typically your default language) and the target language dropdown on the right (the language you want to populate)
- Click Duplicate Only
- A cost-estimate panel appears showing the total number of posts and pages that will be duplicated and a confirmation note that all duplicates land as Drafts in the target language
- Click Proceed to start the duplication
- A progress bar shows how many posts have been processed. Bulk duplication runs in the background — you can navigate away or close the browser, the queue keeps processing
- Once complete, navigate to Posts > All Posts and filter by the new language to see all your draft translations
- Use the Translation Status page (Lang Forge → Translation Status) to confirm the new language now has progress bars and an Untranslated Content list
Step-by-step: Duplicating and AI-translating an entire site
- Go to Lang Forge > Tools → One-Click Site Duplication (same card as above)
- Pick source and target, then click Duplicate + AI Translate (the green button to the right of Duplicate Only)
- A detailed dialog appears showing:
– The estimated total word count across all posts
– The estimated AI credit cost (for example, “Estimated: N credits”)
– Your current credit balance (for example, “Your balance: N credits”)
- If you have enough credits, click Confirm to start
- The process runs in the background in two phases: first, all content is duplicated as drafts; then, each draft is sent through the AI translator one by one
- A progress bar shows the current status. For large sites, this process can take 30 minutes to several hours
- You can leave the page or even close your browser — the process continues on the server
- When complete, all translated drafts are ready for review
Estimating credit costs before you start
Before running a bulk AI translation, it is wise to estimate the total cost:
| Site size | Approximate posts | Estimated credits per language |
|---|---|---|
| Small blog | 20-50 posts | N credits |
| Business site | 50-100 pages | N credits |
| Large content site | 200-500 posts | N credits |
| WooCommerce store | 100-300 products + pages | N credits |
If the estimated cost exceeds your remaining balance, purchase an add-on credit pack before starting (all packs never expire — see avakode.com/pricing for sizes and prices), or translate in batches as your balance allows.
After bulk translation: Review and publish workflow
All translated posts from a bulk operation start as Drafts. This is intentional — it gives you a chance to review before anything goes live. Here is a recommended review workflow:
- High-priority pages first. Open your homepage, About page, Contact page, and product/service pages. Review each translation carefully and publish one by one
- Blog posts in batches. Go to Posts > All Posts, filter by the new language, select 10-20 posts at a time, skim each one, and use the WordPress bulk action to change status to Published
- Use the Frontend Visual Editor. Browse your site in the new language and spot-check translations in context. Fix anything that looks awkward
- Check menus and widgets. Bulk translation does not create menus. Remember to set up a translated menu for the new language
What happens on the Free plan
On the Free plan, the Translation Status page still shows the per-language progress overview across all your active languages — but the One-Click Site Duplication card on Lang Forge → Tools is locked: the Duplicate Only and Duplicate + AI Translate buttons are dimmed and a “PRO” badge with an Upgrade link replaces the active controls.
Common mistakes to avoid
- Not setting up the Glossary first. If you run bulk AI translation without a Glossary, brand names and key terms may be translated inconsistently across hundreds of posts. Set up the Glossary before starting
- Publishing all drafts without reviewing. AI translation is good but not perfect. At minimum, review your most important pages before publishing
- Running bulk translation when credits are low. The process stops when credits run out, leaving some posts untranslated. Make sure you have enough credits for the entire batch
> Tip: Before running a bulk AI translation, set up your Glossary with brand names, product names, and key terminology. The AI checks the Glossary during translation, which prevents you from needing to fix the same term across hundreds of posts afterward.
> Good to know: The bulk translation process is designed to be resumable. If it is interrupted (server timeout, hosting restart, credits running out), you can run it again — it skips posts that already have a translation draft and only processes the remaining ones.
[Screenshot: The Translation Status page showing language columns with progress bars and the “Duplicate + AI Translate” button with a credit estimation dialog]
—