Translation Workflow

LingoJS detects text on your website, generates translations, and serves only the versions you choose to publish.

How it works

1. The snippet scans the page in the configured base language.

2. New text is sent to the project as Pending for review.

3. You publish or block the detected source text.

4. LingoJS prepares the translated values after publication.

5. You can review and edit those values once they are available.

6. Published translations are returned to visitors using the target language.

Translation statuses

• Pending — detected source text awaiting a publish or block decision.

• Published — approved and available on the website once its translated values are ready.

• Blocked — intentionally excluded from the translation workflow.

Review and publish

Open Dashboard > Project > Translations to:

• search the detected source text;

• filter by status;

• publish or block one detected translation;

• edit a translated value after publication;

• apply status changes to several translations at once;

• retry processing when a Published translation remains incomplete;

• import translations from a LocalizeJS JSON file.

The import control is available to the organization owner. The JSON file must include sourceLanguage, a targetLanguage already configured on the project, and a LocalizeJS-shaped dictionary. Imported values are Published by default.

After publishing, reload the website and select the target language. CDN and browser caches may cause a short delay before a new translation appears everywhere.

Exclude content from translation

Add translate="no" to an element that should never be detected or translated:

<div translate="no">
  This content will not be translated.
</div>

The element and all of its children are ignored by the snippet.

Use this for identifiers, technical values, brand names, code samples, or interface elements that should remain unchanged.

Pending versus Auto-Publish

Pending is the default and safest workflow: nothing new appears to visitors until it is published.

Auto-publish is optional. Configure it only after the normal detection and publishing workflow works correctly on the production domain.

When auto-publish later detects text that already exists as Pending, that item is promoted to Published and completed for the missing target languages. Blocked items are never promoted automatically.