Back to blog

WPML Automatic Translation Turned On After an Update? How to Stop It

7 min read
WPML Automatic Translation Turned On After an Update? How to Stop It

You update WPML, return to your dashboard, and discover translation credits have been used—even though you never meant to start a new job. It is the kind of surprise that turns a routine maintenance task into an expensive question: what just translated, and how do you make it stop?

If WPML automatic translation turned on after update is the problem you are facing, the priority is not untangling every setting at once. First, prevent further credit use. Then trace the activity, check what was translated, and regain control over when—and how—your site sends content for translation.

The frustrating part is that translation activity can be easy to miss until the credits are gone. A few targeted checks can reveal whether an update changed a setting, resumed a workflow, or exposed a configuration that was already waiting in the background—and help you choose a workflow that does not spend on your behalf.

First: Stop WPML Automatic Translation and Prevent More Credits From Being Used

Credits can disappear faster than most site owners expect: one bulk job can send dozens of pages, fields, and strings into translation before anyone notices. If wpml automatic translation turned on after update is what you are seeing, contain the activity first and investigate the update later. WPML’s menu labels and settings can vary by version, so look for controls referring to automatic translation, translation mode, Translation Management, or the translation basket rather than relying on one exact path.

Pause translation jobs and check the Translation Management queue

Open WPML’s Translation Management area and inspect the queue before editing pages. Look for jobs marked active, pending, in progress, or queued, then pause or cancel them where WPML provides that option. Prioritize anything already submitted: those items may already be consuming credits. A page sitting in the translation basket, or a draft merely selected for translation, is not necessarily an active job. Remove unneeded selections from the basket as an added safeguard.

Turn off automatic translation in WPML’s translation settings

Find the setting that allows automatic translation, automatic completion, or automatic processing, and disable it. Save the change, reload the admin screen, and confirm the control still shows as off. Take a screenshot before changing anything and another afterward. That small record matters if you later need to compare settings, explain the issue to support, or establish when the configuration changed.

Temporarily restrict access if several team members manage translations

An update is an easy suspect, but it is not the only explanation. A colleague may have started a translation batch at nearly the same time. Tell editors and translation managers to avoid bulk actions until the setup is verified, review who has translation-management permissions, and check recent activity where available. For a busy site, a short pause in publishing translations is far cheaper than allowing another unintended queue to run.

Why WPML May Start Automatic Translation After an Update

A sudden run of translations can look like an update spent credits on its own. That is a reasonable concern, but the evidence usually points to a setting, a pending workflow, or another process that resumed after the update. If you are searching for wpml automatic translation turned on after update, treat the timing as a clue—not proof of a single cause.

A changed or newly surfaced translation setting

Updates can introduce new controls, migrate older preferences, or make a previously overlooked automatic-translation option more visible. They can also preserve a setting that was enabled months ago but had not yet had content to process. Compare today’s Translation Management and automatic-translation preferences with screenshots, staging settings, backup copies, or internal notes from before the update. Check who can translate, whether translations are sent automatically, and which languages are included. Do not rely on memory when credits are involved.

Previously queued jobs, translation baskets, or automatic workflows

An update may simply unblock work already selected. A translation basket created last week, a bulk job awaiting completion, or an “translate automatically” workflow can proceed once a compatibility problem or configuration error is resolved. Review WPML’s translation history and look for a pattern: the job creation date, affected target languages, and content types. If only product pages or newly published posts were translated, that points to a prior rule rather than a site-wide setting being newly enabled.

Other plugins, integrations, and user actions that can trigger jobs

WPML is not always the only actor. Audit recent plugin changes, connected translation services, scheduled cron events, background workers, and administrator activity. A colleague may have approved a basket, changed a workflow, or clicked bulk translation without realizing its downstream effect. If you suspect an integration, reproduce the sequence on a staging site and inspect the logs there. Repeatedly toggling settings on production can create more jobs and make the original trigger harder to identify.

Check What Was Translated, What It Cost, and Whether You Can Recover

Review WPML translation history and credit activity

Before undoing anything, preserve the evidence. When WPML automatic translation turned on after update, the immediate instinct is to delete the output; that can make it harder to establish what happened or ask for a credit review later.

Compile a simple incident list covering each affected page, post, product, taxonomy, or string; its target language; the job timestamp; and the credits used. Check WPML’s translation-management and account credit records, then export records where possible or take dated screenshots. Include totals as well as individual jobs. A 200-page batch translated into four languages is not one event—it is potentially 800 translation outputs and a materially different cost question.

Identify accidental translations and decide what to keep

Not every unexpected translation is worthless. Separate completed, usable translations from drafts, wrong-language output, duplicate jobs, and pages that should never have entered the queue. Keep a record of that decision.

Delete cautiously. In WPML, translated content is linked to its source-language item, and removal may affect language relationships, translated slugs, SEO fields, and front-end URLs. Test the proposed cleanup on staging first when the site is important or heavily indexed. Check hreflang tags, language switcher links, product variations, and key landing pages after each change.

Prepare a clear WPML support request

A factual timeline is more useful than an accusation. State the WordPress and WPML versions, the update date and time, when you noticed the activity, which settings were enabled before and after, and the affected content and languages. Attach screenshots of relevant settings, translation jobs, and credit timestamps, plus the incident list.

  • Include steps that might reproduce the behaviour.
  • Note whether the issue also appears on a staging site.
  • Say which jobs were completed, cancelled, or deleted.

Whether credits can be reversed depends on the provider’s policies and whether completed translation work was already consumed. Ask for a review, but do not assume a refund is automatic.

How to Keep Future Website Translation Costs Under Control

Use a staging checklist before updating WPML

A single unchecked setting can turn a routine update into an unexpected translation bill. If you have dealt with wpml automatic translation turned on after update, make staging a non-negotiable part of your release process. Before updating, back up the site and record the current translation settings, automatic-translation status, and available credit balance. Update WPML on staging first, then publish a small test change. Check whether it enters the translation queue, whether a job starts automatically, and what the estimated cost shows. Only repeat the update on production after that test behaves exactly as expected.

Set approval rules for bulk and automatic translation

Automatic translation is useful only when someone owns the decision to spend. Limit permission to start translation jobs to a small group, and require a cost review before any bulk action. Translate one representative page first, inspect the result and estimate, then approve the wider job.

  • Record expected source-word totals before starting.
  • Confirm every target language included in the job.
  • Review the queue after major content imports or plugin updates.

Language count matters more than many teams expect: translating 1,000 source words into five languages means roughly 5,000 translated-word units. A seemingly harmless “translate all” action can multiply usage quickly.

Consider a BYOK translation workflow for WPML

For sites already running WPML that want tighter control over provider costs, LATW AI Translator for WPML is a practical add-on. It does not replace WPML; WPML remains the multilingual framework, and an active WPML installation is required. In local mode, content goes directly from WordPress to the selected supported AI or machine-translation provider using the site owner’s API key. Its glossary, job history, and cost-conscious processing options give teams clearer tools to approve work, enforce terminology, and audit what was translated before costs drift.

Regain Control Before You Investigate

If WPML automatic translation turned on after update describes what happened on your site, act in the order that protects your budget and content first: stop any active translation jobs, check the automatic-translation settings, and record the credits used and pages affected. Once the immediate activity is contained, review the update and translation workflow history—and contact WPML support with those details if the change cannot be explained.

The longer-term fix is not just a setting; it is a process. Test updates on staging, require clear approval before bulk translation, and keep translation costs visible enough to spot an unexpected run quickly. Translation automation should accelerate a workflow you control, never quietly create one for you.