How to Skip AI Translation in WPML and Translate Content Manually Instead

Not every page should be handed to an AI. A legal disclaimer, a flagship landing page, or a carefully voiced brand story may need a human translator’s judgment before it ever reaches your multilingual site. If you use WPML, you are not locked into automatic translation—you can decide exactly which content gets translated manually and who gets to review it.
Knowing how to wpml skip ai translation gives you more than a way to avoid unwanted automation. It lets you keep sensitive pages out of the automatic workflow, assign work to the right translators, and publish only when the final copy meets your standards. The important part is understanding where that choice is made—before a page is sent off, not after you are left fixing a translation you never wanted.
Whether you want to exclude a single post or build a fully human-led translation process, a few WPML settings can put you back in control of the queue.
When Should You Skip AI Translation in WPML?

Understand WPML’s manual and automatic translation options
Not every page deserves the same translation workflow. WPML lets you use automatic translation credits or assign content for manual translation, and that choice can be made item by item. In other words, wpml skip ai translation does not have to mean abandoning automation across the entire site.
This distinction matters. You might automatically translate 80 blog posts to create a useful first draft, then send a high-conversion homepage or a legal notice to a professional translator. For a single post, choose the manual route in WPML’s translation workflow rather than sending it to automatic translation. For future work, adjust the default process only if most of your content genuinely needs human handling.
That is the sensible middle ground. AI is fast, but speed is not the same as approval.
Choose which content needs human translation
Manual translation is most valuable where a small wording error can create legal, commercial, or reputational trouble. A human translator can weigh audience expectations, local conventions, and the implication behind a phrase—not merely its dictionary meaning.
- Legal, regulated, and policy pages: terms, privacy notices, medical claims, financial disclosures, and compliance text need accountable review.
- Landing pages and brand campaigns: slogans, calls to action, humour, and emotional positioning often need transcreation rather than literal translation.
- Product descriptions: especially where specifications, safety information, sizing, or compatibility claims must stay exact.
- SEO-critical pages: core service pages and category pages may require locally researched search terms, not a direct keyword swap.
- Context-dependent strings: short buttons, interface labels, and messages can mean different things depending on where they appear.
A practical rule: use AI for volume and repetitive material; reserve human review for pages where a mistranslation costs more than the time saved. If you already run WPML, LATW AI Translator for WPML can still support the automated portion of that workflow, while WPML remains the place to route selected items to a human translator.
How to Skip AI Translation for a WPML Translation Job
Open WPML Translation Management and select your content
Skipping AI does not mean abandoning WPML’s workflow. It simply means keeping people in control of the words. In the WordPress dashboard, open WPML Translation Management and find the posts, pages, products, or custom post types you want translated. Select the target language for each item, then add the selected content to the translation basket. WPML menu labels can differ slightly by version, but the pattern is consistent: choose content, choose languages, and prepare a batch.
Assign the job to yourself or a manual translator
Open the translation basket and confirm who will handle the work before sending it. Assign the batch to yourself, a local translator, or a translation manager who will distribute it to the right person. Do not select an automatic translation service or a “translate automatically” option if the goal is a human-produced version. This is the key wpml skip ai translation checkpoint: review both the assignee and translation method before you submit the job.
Translate the page in WPML’s Translation Editor
The assigned translator can open the job from the WPML translation queue and work through it segment by segment in the Translation Editor. Enter the translation manually, including headings, body copy, SEO fields, and other available strings. Mark each segment as complete, then finish and save the translation. Depending on the site’s workflow, the completed page can go straight to publication or wait for editorial review.
Avoid clicking automatic translation for selected pages
WPML often places automatic-translation actions prominently, especially when credits or an AI service are available. Treat those buttons as a separate route, not a required next step. Before confirming a basket, check that the job is assigned to a human and that no automatic service is selected. For teams, a simple rule helps: translators receive assigned jobs; managers alone decide whether any page may use automation.
Manage Manual Translations Without Losing Control of Updates
Update translations after the original page changes
Manual translation is not a one-time task. Change a heading, add a pricing paragraph, or revise a call to action in the source page, and WPML may flag its translations as needing an update. That flag is useful, but it should trigger a review—not an automatic rewrite.
A sensible wpml skip ai translation workflow is to open the affected translation, identify the changed source segments, and update only those sections. Check surrounding sentences too: a small English edit can alter the meaning or tone of an otherwise unchanged paragraph. This approach protects approved wording and avoids turning a two-line correction into a full retranslation job.
Review slugs, metadata, and strings
The page body is only part of the localization work. Before calling a translation complete, manually review the translated title, excerpt, SEO title and meta description, taxonomy labels, and URL slug. A well-written French page can still underperform if its slug remains English or its metadata is clipped, generic, or inconsistent with the target keyword.
Also inspect entries in WPML String Translation. Navigation labels, cookie notices, form messages, button text, and theme or plugin strings are easy to miss because they do not appear in the editor. Treat these as public-facing copy, not technical leftovers.
Use a simple approval process for teams
Teams do not need a complicated localization department to stay organized. They do need clear ownership. A reliable process has three stages:
- The content owner updates and marks the source page ready.
- The translator completes or amends the manual translation.
- An editor or native speaker reviews language, SEO fields, links, and formatting before publication.
Keep translated pages unpublished until that final check is complete. It prevents accidental overwrites, gives reviewers a clean approval point, and creates accountability when several people work in WPML at once.
When to Use AI Translation as a Draft Instead of Skipping It
Create a page-by-page translation policy
Skipping automation entirely can protect quality, but it can also turn a manageable localization project into months of manual work. The smarter approach is not “AI or human?” It is deciding which pages deserve which level of scrutiny.
Build a simple policy with three lanes. Put legal notices, contracts, regulated claims, executive statements, and sensitive customer communications in the fully manual lane. These pages need a qualified translator who understands both the language and the consequences of one imprecise phrase.
Use AI draft plus human review for product pages, blog articles, support documentation, and marketing copy. An editor can correct tone, terminology, cultural references, and any claims that need local verification, while avoiding the slow work of translating every sentence from a blank page. For low-risk, frequently updated material such as archive pages, routine announcements, or internal documentation, bulk AI translation may be appropriate, with spot checks rather than line-by-line editing.
This policy makes a wpml skip ai translation decision practical: you skip AI where risk is high, not where it merely feels unfamiliar.
Reduce WPML translation costs with a compatible AI add-on
For sites already running WPML, LATW AI Translator for WPML offers a middle ground between WPML’s built-in automatic translation and translating every page from scratch. It is an add-on, not a standalone multilingual plugin: WPML must remain installed and configured to handle languages, URLs, and the translation workflow.
LATW can create AI-assisted drafts using your chosen provider’s API at provider-level token or character costs, then leave editors free to assign, revise, or complete any translation manually in WPML. In local mode, content travels directly from WordPress to the selected AI provider rather than through LATW’s servers. That can suit teams with privacy requirements as well as tight budgets.
Use it selectively: draft a 2,000-word article, review it against your glossary, and keep the legal disclaimer on a fully human workflow. Automation should reduce repetitive effort, not remove editorial accountability.
Keep Translation Decisions in Human Hands
To skip AI translation in WPML, assign the content for manual translation and complete it within WPML’s normal workflow. Treat each update as an editorial checkpoint: review the translated copy, confirm SEO titles, descriptions, slugs, and taxonomy fields, and do not overlook interface strings that shape the visitor experience beyond the page itself.
Manual translation is not a step backward when accuracy, nuance, and brand voice matter—it is a deliberate choice to keep accountability with the people who know the content best. If your workload grows, you can later introduce AI-generated drafts selectively through a WPML add-on such as LATW AI Translator for WPML, then review and refine them in WPML before publishing. Use automation where it saves time, but keep human judgment where it protects meaning.