Connecting Webflow

A Webflow site connects to LATW Cloud without a plugin and without a Webflow app: you generate a
site token in Webflow and paste it in the panel. LATW Cloud then reads your content and writes
the translations through the Webflow API, into the languages of Webflow Localization. The AI model,
the prompt, the glossary, the budget and the target languages are set in the panel, and you order
translations there, in the site’s Content tab.

A Webflow site is a site like any other in LATW Cloud: it works on every plan and takes one site
slot.

#What gets translated

In Webflow	What LATW Cloud translates
Pages	The texts of the page, form placeholders, button labels, dropdown options, the texts you changed in a component on that page, and the page title, SEO title and description, Open Graph title and description
Collection template pages	The texts of the template around the CMS fields — they are the same for every item of the collection
CMS collections	Each item’s name, plain text and rich text fields, and the alt text of its images
Components	The texts of the component and the default values of its text properties. A change here shows wherever the component is used, unless a page changed that text for itself
Products (Webflow E-commerce)	The product’s name, description and your own text fields, like a CMS item

The source is the site’s primary language. Each translation is written into its own language only:
the primary language, images, prices, references and the other fields of an item are never
changed.

Slugs are not sent to AI. LATW Cloud makes them from the translated name (see Slugs below).

Not translated:

• Images themselves, and the alt text of images placed on pages: the Webflow API does not localize
  them. Change them in the Designer.
• Variant options of products (e.g. Size: Small) and SKU names.
• Draft and archived pages, archived CMS items, and items that exist only in a secondary language.
• Components from a shared library, which can’t be changed in this site.
• Texts without a letter in them (numbers, prices, symbols).
• Content you excluded from translation in Webflow. If your site uses translation exclusions,
  LATW Cloud reads pages and components the way Webflow shows them for translation, without what
  you excluded.

#Before you start

• Webflow Localization with at least one more language. Turn it on in the Designer and add the
  languages you want; how many you can add depends on your Webflow plan. A language that is turned
  off in Webflow is not chosen as a target, but you can add it in the site’s Settings.
• A site plan with CMS if you want to translate collections. Pages and components need no CMS.
• Admin access to the site in Webflow, to generate the token.
• A free site slot on your plan. See Plans.

#Generate a site token

1. In Webflow, open the site’s Site settings → Apps & integrations → API access and press
   Generate API token.

2. Give it Read and write access to Pages, CMS and Components, and Read access
   to Sites (scopes sites:read, pages:read, pages:write, cms:read, cms:write,
   components:read, components:write).

   Give Sites write access (sites:write) only if LATW Cloud should publish the whole site after
   each job — see Publishing.

3. Copy the token. Webflow shows it only once.

A token belongs to one site. Webflow allows five tokens per site and deletes a token that has not
been used for a year.

#Connect

1. In the panel, open Sites → Add site and choose Webflow (or press Connect with a token
   on the Webflow card under Integrations).
2. Paste the token into Site token. The first time you connect a site, tick I accept the
   Data Processing Agreement.
3. Press Connect site.

LATW Cloud reads the site with the token before it saves anything: it checks that the token sees
one site, that Localization has a language to translate into, and that the token can read pages,
collections and components. If something is missing, the form says what. A token without write
access is only noticed by the first job, which then waits with Webflow’s reason.

When the site is connected, the panel opens its Overview. The site is named by its custom
domain, or by its webflow.io address when it has none.

Connecting sends LATW Cloud the site’s name, its domains and its languages. The token is stored
encrypted and is never shown again in the panel — only its last four characters.

Connecting the same Webflow site again, with a new token, does not create a second site: it keeps
its settings and jobs.

#How languages and statuses work

LATW Cloud shows the languages by Webflow’s codes in lower case, e.g. de-de for German
(Germany). Choose the target languages in the site’s Settings tab.

Webflow does not record whether a text is translated or out of date, and LATW Cloud does not keep
track of it for Webflow either. So on a Webflow site:

• Every item shows as Translated in every language, in the Content tab and on the
  Overview, whether it was translated or not. The status filter does not tell you what still
  needs translating — choose the items yourself.
• A job always translates the whole items you selected, also the ones translated before. There
  is no Translate again option in New job: it is always on.
• A job overwrites the selected items’ texts in the target languages, including translations
  you made or corrected in Webflow. Select only the items you want translated again.

Opening an item in the Content tab shows each text with its current translation in every
language.

#Settings in the panel

The site’s Settings tab has a Webflow card with two settings.

Publishing — what happens after a translation is written:

Option	What happens
Wait for my Publish (default)	Translations wait in Webflow as unpublished changes until you publish the site.
Publish CMS items	A translated CMS item goes live in its language at once, if it is published in the primary language. Pages and components still wait for your Publish.
Publish the whole site after each job	When a job wrote something, LATW Cloud publishes the site to all its domains. This also publishes every other unpublished change made in the Designer. Needs sites:write.

If publishing fails — the token has no sites:write, or Webflow refused — the translations are
still saved, and the job’s timeline says why the site was not published.

Slugs — the address of CMS items and pages in a translated language:

• Translate slugs not translated yet (default) — the slug is made from the translated name or
  page title, but only while it is still the same as in the primary language. A slug that was
  translated once is never changed, so links and search results keep working. Letters with accents
  and Cyrillic or Greek letters become plain Latin letters; a name in Chinese or Japanese keeps the
  original slug.
• Keep the slugs as they are.

When Webflow refuses a slug — it is taken in that language — the translation is written with the
slug the item had, and the job’s timeline says so. The home page, template pages and utility pages
keep their slugs. Webflow lets you change page slugs in a secondary language only on its Advanced
and Enterprise localization plans.

#What it costs and how long it takes

Words are counted and billed the same way as on any other site — see LATW Credits and Pricing.
Because a job sends the whole items, translating an item again costs as much as its first
translation, even if only one text changed. The estimate counts every text of the selected items.

Webflow limits how many API requests a token makes: 60 a minute on Starter and Basic site plans,
120 on CMS, Business and E-commerce. The panel’s Content tab and the jobs share that limit.
LATW Cloud therefore works on one item of a Webflow site at a time, and a large job on a smaller
Webflow plan simply takes longer. When Webflow says the limit is reached, LATW Cloud waits and
continues on its own; the Content tab asks you to try again in a minute. Lists in the
Content tab can be up to two minutes old.

#Replacing the token

When Webflow deletes the token — you removed it, or it was not used for a year — or it lacks a
scope, the site’s jobs wait and the site shows as Unreachable. Generate a new token with the
same access and paste it in the site’s Settings → Connection → Replace token. LATW Cloud checks
that it belongs to the same Webflow site and uses it from then on.

#Disconnecting

Open the site’s Settings tab and press Disconnect site. A site with active jobs can’t be
disconnected — cancel them or wait until they finish.

LATW Cloud stops using the token and forgets it. Translations already written stay in Webflow.
The Webflow API can’t delete a token, so delete it yourself in Site settings → Apps &
integrations → API access.

To connect the site again, paste a new token in Sites → Add site → Webflow; the site comes
back with its jobs and settings.

#If something does not work

• “Add a language in Webflow Localization” — Localization is off or has no other language.
• “The token has no … scope” — generate a new token with the access listed above.
• A job waits with “Webflow refused the request” — the token can’t write (no write access to
  Pages, CMS or Components) or Localization was turned off. Fix it in Webflow, replace the token if
  needed, and resume the job.
• A translation was refused — the job shows Webflow’s reason, e.g. a text longer than the
  field allows, or HTML that does not match the page’s.

Site Unreachable lists the causes for every platform.