WPML automatic translation is not only a way to translate a page once. With the right settings, it can become an ongoing multilingual WordPress workflow that also handles newly published content. The central elements are PTC, WPML’s Private Translation Cloud, the WPML Translation Dashboard, publishing controls, and a clear review process.
This workflow gives site owners and agencies control over what is translated, how translation jobs are routed, and whether completed translations are published or held for approval. It does not establish that automated translations are universally accurate or suitable for every type of content. Legally sensitive, commercial, medical, financial, technical, and brand-critical content may need additional human review before publication.
What WPML Automatic Translation Does
WPML’s Translate Everything Automatically mode uses PTC as the active translation engine. When enabled, the workflow can automatically pick up newly published posts, pages, and products, so the administrator does not need to send each new item through a separate manual translation round.
The alternative is Translate Some, which gives the site owner more selective control over the content sent for translation. The two modes serve different operating models: broad automation can support a continuously updated site, while selective translation can be more suitable when content requires deliberate routing or review. WPML documents that users can switch between these modes without losing prior translations.
Automatic and selective translation modes
Choose Translate Everything Automatically when the site needs an ongoing process for eligible new content and the team has defined how completed translations should be handled. Choose Translate Some when the team wants to decide which posts, pages, products, or other content items enter the translation workflow.
In both cases, the important distinction is between translation processing and editorial approval. Automatic processing may reduce manual sending, but it does not remove the need to decide which content is suitable for publication without review.
Before You Enable Automation
Before enabling broad automation, confirm that PTC is the active translation engine. WPML documents PTC as a requirement for Translate Everything Automatically, so this mode should not be presented as available with every translation engine.
Next, review the site’s translation configuration. Post types, custom post types, custom fields, taxonomies, media text, and SEO fields can have separate translation settings. A workflow that is correct for standard posts may not automatically cover every custom content type or field used by a WordPress site.
Publishing behavior also deserves attention before activation. Decide whether completed translations should be published or saved as drafts. Check whether existing translations should be published or held when the original post is published. These settings connect the technical translation process with the editorial process used by the site.
A backup and a staging check are sensible implementation preparations before changing translation behavior across a production site. They are practical precautions, not a documented WPML requirement. The purpose is to give the team a controlled way to verify scope, publishing behavior, and content presentation before applying the workflow broadly.
Define the approval path first
Identify the people responsible for reviewing, editing, approving, and publishing translations. In a small site, one administrator may perform several of these tasks. In an agency workflow, they may belong to different people or roles.
Define what happens after a translation is completed. If the site requires editorial approval, configure a draft or hold behavior where available and make sure the responsible person knows how to review the job. Translation completion and publication should be treated as separate decisions when the content carries higher commercial, technical, legal, or brand risk.
How to Enable Translate Everything Automatically
To start the documented setup path, open the WordPress administration area and go to WPML > Translations > Dashboard. When PTC is active, locate the Translate Everything Automatically card and use its setup control.
The setup screen displays the intended translation scope and cost. Review these details before confirming the process. The screen also provides publishing preferences and content limits, allowing the administrator to decide how the resulting translations should enter the site’s editorial workflow.
Before starting, verify that the selected scope matches the actual content plan. Broad automation may be appropriate for some content, while other material may need selective routing or human handling. Confirm how completed translations will be published, saved as drafts, or held for review according to the available settings.
Start the process only after checking these choices and confirming the setup. If another translation engine is active, the documented workflow requires switching to PTC before enabling Translate Everything Automatically. Do not assume that changing the mode alone is sufficient when the required engine is not active.
Confirm scope and publishing behavior
Use the setup screen as a final checkpoint rather than treating activation as an irreversible content decision. Review the displayed scope, cost, publishing preference, and content limits. Then confirm that the selected behavior matches the approval path defined for the site.
Turning Translate Everything Automatically off stops new content from being picked up by this mode. It does not mean that content already translated is deleted; existing translations remain in place according to the documented workflow.
Using the Translation Dashboard for Ongoing Control
The Translation Dashboard is the main control point for monitoring and routing translation work. It supports both Translate Everything Automatically and Translate Some, so the team can use broad or selective processing as the site’s needs change.
Global filters help narrow the working view. The Dashboard can filter by source language, target language, publication status, translation status, and keyword search. Section-level filters can also help identify content types such as posts and pages, with relevant taxonomy or parent-page filters available where applicable.
These controls are useful when an agency needs to inspect a specific language pair, find untranslated content, or review a selected group of items rather than process the entire site. The Dashboard also displays word-count information before content is sent for translation, which helps the team understand the size of a selected job.
The documented workflow includes SEO metadata in the relevant post translation process. That describes how the metadata moves through the workflow; it does not guarantee search visibility, rankings, or SEO performance. Language-specific review remains important for metadata that represents the site’s commercial or editorial message.
Route different content through different methods
The Dashboard supports six translation methods:
- Automatic translation.
- Manual translation in the Advanced Translation Editor.
- Assignment to a translator.
- Assignment to a translation service.
- Duplicating content.
- Doing nothing.
This makes it possible to use a mixed workflow. Content suitable for the selected automatic process can follow PTC, while specialized or higher-risk material can be assigned to a translator, handled manually, or sent through a translation service. Duplication or no translation should be selected only when it matches the content plan.
What Happens When You Publish New Content
When Translate Everything Automatically is enabled, WPML documents that newly published posts, pages, and products can be picked up automatically for translation. Under this workflow, the team does not need to perform a separate manual send round for each newly published item.
This behavior applies within the documented automatic workflow, but it should not be interpreted as a guarantee that every custom post type, field, taxonomy, media item, or SEO field will be included. Those elements depend on the site’s translation settings and should be checked before broad automation is enabled.
If the feature is turned off, new content stops being picked up by this mode while content that has already been translated remains translated. The selected publishing behavior still matters: a new translation may be published, saved as a draft, or held according to the configured process.
Check the workflow after publishing
After publishing a new item, verify that its content type is configured as translatable and check the resulting translation status. Confirm whether the translation has been published, drafted, or held as expected. This simple check connects the automatic workflow with the actual editorial behavior of the site.
For agencies, record who checks new items and how exceptions are handled. A missing translation or an unexpected publishing state should be routed back through the Dashboard and the site’s defined approval process.
How to Review and Control Automated Translations
Automated translation is most controllable when it is combined with explicit review rules. WPML’s Advanced Translation Editor provides side-by-side source and target editing, allowing an editor to correct translation segments. It also supports front-end review before publication, so the team can inspect how translated content appears in a visitor-facing context.
Human review is a risk-management recommendation, not a universal requirement for every site, language pair, or content type. However, it is especially sensible for legally sensitive, commercial, medical, financial, technical, and brand-critical material. WPML’s documented workflow includes manual translators and professional translation services, so PTC should not be presented as a replacement for professional translators in every use case.
A practical agency review sequence
An agency can organize the process into a repeatable sequence:
- Set publishing controls before translation jobs are completed, using draft or hold behavior when editorial approval is required.
- Use the Advanced Translation Editor to compare source and target content side by side.
- Correct individual translation segments where the wording does not reflect the intended meaning or terminology.
- Use front-end review before publication when the content’s risk or the client’s process justifies it.
- Monitor automatic, manual, and external-service jobs in the Translation Manager view.
- Filter jobs by language pair, content type, or status to focus attention on the relevant work.
- Cancel or reassign a job when the selected route or assigned responsibility is no longer suitable.
This sequence separates translation production from approval. It also gives the agency a practical way to intervene without treating every item as identical.
Client editing and approval
Agencies can assign translation work to named translators or Translation Managers and define how the client participates. WPML documents workflows in which clients can edit translations after PTC has produced them. That can be useful when the client owns brand terminology or has responsibility for final language decisions.
Roles should remain explicit. Translators and Translation Managers have different responsibilities in the documented workflow, and the person monitoring jobs is not automatically the person approving publication. Agree who reviews the translated text, who makes corrections, who gives final approval, and who publishes it.
Translation Managers can monitor automatic, manual, and external-service jobs, filter them by language pair, content type, or status, and cancel or reassign jobs when necessary. These controls help agencies keep the automated process aligned with client priorities without claiming that every translation result is ready for immediate publication.
WPML automatic translation works best as a configured workflow rather than a single switch. First confirm that PTC is active and review post types, fields, taxonomies, media text, and SEO settings. Then configure Translate Everything Automatically from WPML > Translations > Dashboard, check the displayed scope and cost, and select appropriate publishing behavior. Use Dashboard filters and translation methods to route content deliberately, verify how newly published items are handled, and apply review rules based on content risk. Explore our WordPress plugins, WooCommerce extensions, themes and membership plans to find the right tools for your website.