Publish localised content from source-backed data.
Ingest content once and publish it in several languages—AI rewrite then translation, with every item reviewable before it goes live.
Multilingual teams use Ingestics (Business) to ingest source content and translate it into localised posts—AI rewrite runs first to improve the source, then translation via DeepL, Google, LibreTranslate, Azure or an AI provider, with separate API/RSS schedules and editorial review.
Recommended configuration
- Recommended tier
- Business
- Sources
- International news APIs + regional RSS
- Schedule
- Every 2–4 hours; separate API/RSS schedules
- Transform
- AI rewrite → translation (7+ providers)
- Optional
- Polylang language assignment per provider (Pro)
Your step-by-step workflow
One source, several language editions, under control.
Ingest the source
Configure providers for your source content (APIs and feeds).
Improve then translate
AI rewrite cleans the source text; translation then renders it into each target language.
Review localised drafts
Hold translated items as drafts so a native reviewer can approve them.
Assign language
Optionally assign a Polylang language per provider (Pro) so editions stay organised.
Publish per locale
Publish localised posts, attributed to source, on independent schedules.
Capabilities for this use case
Seven translation services
DeepL, Google, LibreTranslate, Azure—plus OpenAI, Anthropic and Gemini.
Twig templates
Build language-specific front-end templates with custom formatting per locale.
Blocked keywords
Keep content that violates regional rules out of specific markets.
What the pipeline looks like
Configure one provider per language.
Each target-language provider shares the same source but a different translation target; AI rewrite runs first for cleaner output.
How is translation handled?
+
Can I review translations first?
+
Does it work with Polylang?
+
Can I format each language differently?
+
Go multilingual
Start free, then enable transform on Business when you scale.