How to Automatically Translate New Posts into Specific Languages Only with SeaText
Yes — you can automatically translate new posts into only the languages you choose. Define the active languages in the SeaText plugin settings or pass target language codes in the API request; SeaText lets...
Yes — you can automatically translate new posts into only the languages you choose. Define the active languages in the SeaText plugin settings or pass the target language codes in the API request. SeaText lets you set a per-project language list. This limits translation work and costs to the markets you actually serve.
The system still runs in the background. You do not need to click Translate for each page. New WordPress posts, pages, products, and updates are picked up automatically.
Three Ways to Control Language Output
SeaText gives you three practical control points.
| Control method | Best for | What it does |
|---|---|---|
| Plugin settings | Marketers who want a fixed list | New content is translated only into the languages you check in SeaText → Settings. |
| API targetLanguages | Developers working in code | Each request can specify the exact language codes; it overrides the plugin list for that request. |
| Visitor detection | Sites that need real-time language choice | SeaText detects the visitor’s language and serves an available translation. If the language is not in your active list, it falls back to the default. |
The first two methods control which translations are produced. The third controls which translation is displayed.
How Language Selection Works in SeaText
SeaText runs a background translation pipeline. When you publish a new page, post, product, or update, SeaText sees the new content and translates it. There are no page limits and no language limits. The default capability is translation into 125 languages.
The language-selection step is simple: SeaText checks the active language list for the project. That list lives in the plugin settings. It can also come from an API request.
The system does not decide on its own which markets matter. You decide. If you check Spanish, French, and German, those are the only languages generated for new content. If an API call includes targetLanguages, that array is used for that request.
Visitor-language detection is a separate layer. SeaText detects each visitor’s language so the visitor receives the right version when a translation exists. This matters because a visitor from Spain should see Spanish, not the default language.
The key idea: production is driven by your language list. Delivery is driven by visitor detection.
Setting Active Languages via Plugin Settings
The fastest way is the WordPress dashboard.
- Go to SeaText → Settings.
- Open the Languages tab.
- Check the boxes for the languages you want to enable for automatic translation.
- Save your changes.
After you save, new posts are translated only into the selected languages. Existing posts stay as they are.
Example: a Canadian ecommerce store sells in English and French. The owner checks only English and French. New product descriptions are translated into two languages, not 125. This keeps the review queue short and costs predictable.
You can return to this screen anytime. Remove a language and new content stops being translated into it. Re-add it and the process resumes for new content.
Using the API to Specify Target Languages
Developers can control language selection inside the translation request. This is useful for custom workflows, automation, or content that needs special treatment.
Add a targetLanguages array to your payload. Example:
{"targetLanguages":["es","fr","de"]}
This tells the API to translate the new post into Spanish, French, and German only. If you omit the array, SeaText falls back to the active language list in plugin settings.
Use the API when you have different language rules for different content types. For instance, a help center article might need Japanese while a blog post does not. The request-level override gives that flexibility.
Keep the plugin list as your default. Then use the API only for exceptions. This avoids surprises.
Trade-offs: Cost, Performance, and Maintenance
Limiting languages is not just a settings change. It changes cost, processing speed, and daily maintenance.
Cost. The free tier already includes all 125 supported languages. If you move to a paid tier, each extra language creates more translation usage. A cost-saving example: a company pays for translated output per character. It currently translates into 10 languages. It reviews analytics and sees that most international visits come from Spanish and French markets. It reduces the list to those two. Translation requests drop because eight languages are no longer generated. The exact saving depends on the pricing plan, so check with the vendor.
Performance. Fewer languages means fewer background jobs. A new product page that once triggered 125 translation tasks now triggers two. The translation queue clears faster. The speed gain for the enabled languages is usually small, but it is visible on content-heavy sites. Publish many posts per day and the effect compounds.
Maintenance. A smaller language set is easier to review. You can check brand voice, edit titles, and run A/B tests without spreading the work across dozens of languages. Maintenance tip: create a monthly review slot for each enabled language. Assign one owner per language. If you cannot find a reviewer for a language, remove it from the active list.
The real trade-off is reach. A language you exclude is a market where visitors do not see a translated page. Budget and reach must be balanced.
Common Use Cases: Why Limit Languages
Limiting languages is the right choice in several situations.
Regional focus. A local service business in Munich serves German-speaking customers. It does not need Japanese or Portuguese. It enables German and maybe English to cover international visitors. Every other language adds noise.
Budget constraints. A small SaaS startup wants to expand to Spain and Mexico. It has one part-time localization editor. It enables Spanish and controls quality. Translating into 20 languages would overwhelm the editor and delay launches.
Compliance and operations. Some markets require local terms of service, shipping options, or support hours. If the business cannot offer those, a translated page can create false expectations. Limiting languages keeps the promise realistic.
Brand consistency. Brands with strict voice guidelines start with one or two languages. They refine the glossary before expanding.
Testing. A company can test the translation feature in one market before expanding. That test shows whether the translated pages generate traffic and conversions.
Decision Framework: When to Limit Languages
Use this checklist when you set up or review your language list.
- List the countries where you currently have customers or run paid ads.
- List the languages spoken in those countries.
- Check your support capacity: do you have someone who can answer questions in each language?
- Check your localization budget: can you review and edit translations in each language?
- Set the remaining languages as your active list in SeaText.
- Review quarterly. Add a language if traffic grows. Remove a language if it does not produce meaningful engagement.
Real-world example: a B2B software company in the U.S. sells to Canada, the UK, and Australia. It sets English as the default. It enables French for Canadian visitors who prefer French. It skips German because the sales team has no German speakers and the product docs are English-only. After six months, the company sees organic traffic from Germany growing. It hires a German part-time marketer, then adds German to the active list.
The framework works because it forces a business question before a technical setting.
Key Facts
These source-backed facts answer the most common setup questions.
| Feature | Description | Source |
|---|---|---|
| Automatic translation scope | Translate every WordPress page, post, product, and update automatically. No page limits, no language limits, and no manual translation work. | S1 |
| Language control | Translate pages into 125 languages with control. | S1 |
| Editable translations | Yes. Automatic does not mean uncontrolled. You can edit translations, preserve brand voice, review key pages, and use A/B tested translation. | S1 |
| Visitor detection | SeaText detects each visitor’s language and translates pages instantly. | S1 |
Limitations and When Not to Apply
A static language list works for new content. It does not retroactively translate existing posts. If you add a new language later, you need to re-run translation for the posts you want in that language.
A static list is also not the same as real-time visitor language switching. If your goal is to show the best available language to each visitor, SeaText’s visitor detection handles delivery. Your active list controls production.
Do not limit languages if you cannot support the markets you keep. Check your support capacity first.
Do not limit languages if your paid ads target those markets. A visitor clicks a French ad and lands on an English page. That mismatch hurts conversion.
When in doubt, start smaller. You can always add languages later.
FAQ
- Can I change the language list later without re-translating existing content?
Yes. Updating the active language list affects only new posts. Previously translated posts remain in their original languages. If you want an older post in a newly added language, re-run translation for that post. - Does limiting languages affect the free tier?
No. The free tier already translates into all 125 supported languages. Limiting languages is a control measure for potential future paid costs and for keeping review work manageable. - What happens if I omit the targetLanguages parameter in the API?
SeaText falls back to the language list defined in the plugin settings. That is why it is best to keep the plugin list up to date. - Are there any limits on how many languages I can select?
You can select any number up to the full 125 supported languages. - Will limiting languages improve translation speed?
It can reduce background workload, which may lead to slightly faster processing for the enabled languages. The difference is usually minor unless you publish a very high volume of content. - What should I do if a visitor speaks a language outside my active list?
SeaText detects the visitor’s language, but if no translation exists for that language, the visitor sees the default language version. Add that language to your active list when the market justifies it.
Further reading and comparison sources
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Further reading and comparison sources
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Learn more
Visit the website for more information.