Site Settings

Everything about how a connected site is translated is set in the panel, per site: open Sites,
pick the site and go to the Settings tab. While the site is connected, the plugin in WordPress
locks its own fields for these settings and links here instead.

Each card is outlined when it has unsaved changes. Press Save changes at the bottom to keep
them.

#Translation defaults

These are the defaults for every job on the site. A job started in the panel can change them for
that one job; a job started in WordPress always uses them.

AI source — who pays for the translation:

• LATW Credits — taken from your Credits balance, shown on the card. See LATW Credits and
  Pricing.
• Your key — billed by the AI provider to your own API key. Available from the Solo plan.
  Choose which of your keys this site uses in the field below. See Using Your Own API Key.

Quality — three presets, each a specific model:

Quality	Model	Best for
Economy	GPT-6 Luna	Fast and affordable. Blogs, product catalogs and most websites.
Standard	GPT-6.1 Sol	Natural, fluent translations for marketing and customer pages.
Premium	GPT-6 Astra	Highest quality for legal, technical and brand-critical content.

With LATW Credits, each option shows its price per 1,000 words on your plan. Change model opens
the full list. Claude and Gemini are listed as coming soon and cannot be chosen yet.

New sites start on Economy.

Mode — how new jobs are run:

• 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. Available from the Solo plan.

New sites start on Start now.

Target languages — the languages this site is translated into. You pick from the languages the
site reported when it connected; if none are listed, press Test connection to fetch them again.
The plugin takes this list over and locks its own setting.

#Glossary & prompt

• Glossary — which of your glossaries this site uses, or None.
• Prompt — which of your prompts this site uses. A job started in the panel can use another one for that job only. LATW Prompt is the built-in one.
• Website description — what the site is about, who reads it and in what tone. It is sent with
  every translation (it fills {{website_context}} in the prompt), up to 2,000 characters. When the
  site connects, it is copied from the plugin’s own Website Description; after that, the one set
  here is used.

Glossaries and prompts are created under Glossary & prompts and can be shared by any number of
sites. See Glossary and Prompts.

#Plugin

Shown only for plugins that have settings of their own here. They change how the plugin itself
behaves in WordPress, and while the site is connected they are set only here.

LATW AI Translation for WPML

• Translation editor — where a translation is opened in WordPress: Classic Translation Editor
  (WPML), WPML’s side-by-side editor with the AI translation filled in, or Native WordPress
  editor, where the translated post is edited in the standard post editor.
• Outdated translations — what happens when WPML marks a translation as outdated because the
  original changed (see below).

LATW AI Translation for Polylang

• Outdated translations — what happens when a translation is older than the last change of the
  post it was translated from:

Option	What is sent
Translate only changed strings (recommended)	Only the parts of the post that changed.
Translate only changed strings, with the whole page as context	The changed parts, with the whole page for context. Best quality, higher cost.
Re-translate the whole post from scratch	The whole post, as for a first translation.

Translating only what changed needs LATW Pro on the site. Without it the whole post is
translated again, and costs what a first translation costs.

#Webflow

A Webflow site has no plugin; this card, named Webflow, sets how LATW Cloud writes the
translations there:

• Publishing — whether translations wait for your Publish in Webflow (the default), CMS items
  go live at once, or the whole site is published after each job.
• Slugs — whether slugs not translated yet are made from the translated name.

Connecting Webflow explains each option.

#Budget limit

A Daily and a Monthly limit, in USD, for this site. Leave a field empty for no limit.

When a limit is reached, the site’s jobs pause. They do not start again on their own: raise the
limit, or wait for the next day or month (counted in UTC), then press Resume on the job. The
limit is checked between portions of a job, so a job can go slightly over it before it pauses.

There is also a limit for the whole account, under Settings → Preferences → Account budget
limit, which applies to all sites together.

#Connection

• Test connection checks that LATW Cloud can reach the site and shows how long it took. If it
  fails, the card lists the usual causes — see Site Unreachable.
• Rotate secret replaces the secret that signs the requests between LATW Cloud and the site.
  See Connecting a Site.
• Replace token (Webflow, instead of Rotate secret) — shows the last four characters of the
  site token in use and takes a new one, for example when Webflow deleted the old one. See
  Connecting Webflow.

#Danger zone

Disconnect site switches the plugin back to the engine it used before. It is not possible
while the site has active jobs. See Connecting a Site. For a Webflow site, LATW Cloud stops using
the site token; delete it in Webflow afterwards.