AI translation in Drupal: keeping three languages current
š§ Listen to every article back to back
An Estonian service page changes its delivery time from five days to ten. The English and Finnish pages still promise five. AI can translate the new sentence quickly, but someone must notice the change and decide when the other languages should go live.
Start with service pages
WebPro recommends testing AI translation on one content type first: perhaps ten service pages in Estonian, English and Finnish. Use them to check the complete journey from a source edit to a published translation. Translating a thousand pages at once says little about whether next week's changes will reach the right places.
Drupal's AI capabilities received renewed attention in Rotterdam in late September. The Drupal AI initiative's updates (opens in a new tab) discuss translation alongside other editorial tools. For a business, the immediate question is who finds out when another language version is no longer accurate.
Our multilingual Drupal overview covers the foundations. This article focuses on maintaining translations after their first publication.
A translation button does not create a change queue
The AI Translate module (opens in a new tab) can send translatable Drupal content to a configured AI provider and create a translation inside the CMS. Its documented options include creating new translations as drafts and changing instructions for each target language.
That alone does not establish an automatic task for every source edit. Change detection, notifications and updates to existing translations need separate verification in the chosen implementation.
For the delivery-time example, we would propose this sequence:
- An editor changes the Estonian page to ten days.
- The people responsible for English and Finnish receive tasks with the changed text and its source revision.
- AI prepares drafts that reviewers can compare with the existing translations.
- A reviewer checks numbers, conditions and wording before approving publication.
This is a proposed workflow, not a claim about Drupal's default behaviour. Test what happens when someone edits the source again while a translation is awaiting approval. A draft based on the earlier revision must not accidentally become the approved translation of the newer text.
Keep terminology consistent
Give the translation process approved service names, product names and examples of suitable wording. If a product name must remain unchanged across languages, say so explicitly. Ten separate requests should not produce ten names for the same service.
A short terminology list is enough to begin. Instructions might require preserving product names, prices, units and links. Then check whether the selected provider follows them. An instruction is not a guarantee.
AI drafts can be useful for an initial translation of service descriptions with a recurring structure. Contract terms, specialist language and sales copy for a new market need someone who understands both the language and the subject. A fluent sentence can make a different promise from its source.
Check what remains public during review
Test translation and approval with an account that has the actual editor's permissions. An administrator's successful test does not tell you whether a translator can accidentally publish unreviewed content.
Drupal's documentation explains translation and moderation together (opens in a new tab), but the site's versions and configuration still require verification. Do not assume outdated-translation tracking works as intended without testing it.
An older translation may remain public while a new draft awaits approval. For a price or delivery-time change, decide whether all languages must launch together or whether the outdated offer should be temporarily hidden. Creating a draft does not resolve contradictory public information.
Know what leaves the site
Before connecting an AI provider, inspect which fields will be sent. A public service description and an unpublished customer story need different handling. For the initial trial, we would use public text and limit the submitted fields to what translation requires.
Set request-volume and cost limits, and define how failures are handled. A failed translation should remain visible as an unfinished task rather than silently disappearing from the queue.
Finish the trial on the public-facing page
For the ten service pages, check that prices and deadlines are preserved, links lead to the appropriate language, and buttons and image descriptions make sense. A Finnish button label must fit on a phone screen. Language switching and forms must remain usable with a keyboard.
Also measure how long a person spends correcting each draft. If every translation needs substantial rewriting, improve the source text, terminology or instructions before increasing volume.
Through WebPro's AI and Drupal service, we can start with this limited trial: one content type, agreed languages and a named reviewer. That makes it possible to assess real time savings and whether the next content change reaches every language too.
Need Drupal help?
Send the website URL and a short context. We will tell you whether the sensible next step is an audit, maintenance, an upgrade or a migration.