Translating Content

A translation in LATW Cloud is a job: a set of items, the languages to translate them into,
the model and how it is paid for. You can start one from the panel or from WordPress.

#Starting from WordPress

Use the plugin’s translation screens as you did before the site was connected. Instead of
translating on your server, the plugin hands your selection to LATW Cloud, which tells you the
number of the job it became. The job uses the site’s settings — model, AI source, mode, glossary, prompt
— from Site Settings. In the panel it shows with the origin wp-admin.

#Starting from your AI agent

From the Solo plan, the AI agent you work with — Claude Code, Cursor, VS Code, Codex, n8n, Claude.ai, ChatGPT — can
check what needs translation, show you the price and start the job, or translate the texts with its
own model. Its jobs use the same site settings and show with the origin MCP. See Translating
from Your AI Agent (MCP).

#Starting from the panel

Open the site’s Content tab (Sites → your site → Content), or Content in the menu,
where you pick the site at the top.

LATW Cloud reads the list live from your site, so it always matches what WordPress has. The tabs
along the top are the content types your plugin offers — posts, pages, products, categories,
strings and so on — each with its count.

#Finding what to translate

• Language and Status narrow the list to, for example, everything Missing in German.
• After shows only content modified after a date.
• Search content searches your site’s content of the chosen type.

Each item shows its source language and, for every target language, its status:

Status	Meaning
Missing	No translation in this language yet.
Outdated	The original changed after it was translated.
Translated	Up to date.

The statuses come from the plugin on your site, not from LATW Cloud. A Webflow site has no plugin
and no statuses: every item shows as Translated there (see Connecting Webflow). A language with
a spinning icon is being translated by another job right now — the link takes you to it. An item
busy in every shown language cannot be selected until that job ends.

#Strings

Groups of strings — a theme’s or plugin’s text domain, for example — show the number of strings
instead of a date. Click the group’s name to browse its strings and pick single ones; a group with
only some strings picked shows how many. With a search, the list tells you how many strings in each
group match.

#Selecting and starting

Tick the items, or the box in the header to take the whole page, and press Translate in the bar
at the bottom. The New job window walks you through three steps.

1. What to translate. Ticked by default are the site’s target languages, and Select all
ticks or clears every language at once. A language is not offered when every selected item is
written in it. Below the languages is what you selected and Translate again, which sends the
whole items, also the ones that are up to date. Without it only missing and outdated translations
are sent, and an outdated one is updated the way the site’s Outdated translations setting says.
A Webflow site has no Translate again: its jobs always send the whole items.

2. How to translate. The site’s defaults are preselected; changing them here changes this job
only.

• AI source — LATW Credits or Your key (from the Solo plan). Your key can be chosen
  only when the site has an API key picked in its Settings.
• Quality — Economy, Standard or Premium. A site set to another model in its
  Settings also offers that model here.
• Mode — Start now: each item is written to your site as soon as it is translated. Batch
  mode: the job goes to the AI provider’s batch service, 50% cheaper, with results within 24
  hours (from the Solo plan).
• Prompt — the prompt this job translates with. It starts as the prompt chosen in the site’s
  Settings; pick another of your prompts, or LATW Prompt, to use it for this job only. See
  Glossary and Prompts.

3. Estimate. LATW Cloud asks your site to count the words that would be sent, and shows what you chose (site, content, languages, engine, mode and prompt) and:

• Words — words per language × the number of languages.
• Estimated cost — with LATW Credits, the most this job can cost. You are billed per word and
  never more than this amount.
• Available credits — and Top up when they are not enough for the job.

If the estimate says Nothing to translate, the selected items are up to date in those languages.
Go back and tick Translate again to translate them anyway.

Press Start job. With LATW Credits, starting reserves the estimated amount from your available
balance; what the job does not use goes back when it ends. See LATW Credits and Pricing.

The Estimate step can be switched off under Settings → Preferences → Show cost estimate before
starting a job. The job then starts after the How to translate step, but your site still counts the words
first: the job never costs more than that count, and it does not start when your available
credits do not cover it or when there is nothing to translate.

#When content changes during a job

LATW Cloud translates what it reads from your site at the moment it gets to each item. If an item
grew by more than a few words since the estimate, it is not translated, so you are never charged
more than you agreed to. It is marked as failed; Retry it on the job’s page to accept the new
price. See Following and Managing Jobs.

#What gets translated

Which fields of an item are sent — the content, custom fields, SEO title and description — is
decided by the plugin and your multilingual plugin, exactly as when the plugin translates on its
own. The plugin’s documentation explains those rules; for WPML see What Gets Translated?.