QA checks

QA checks automatically scan your translations for common issues, such as placeholder mismatches, invalid ICU syntax, or exceeded length limits. They catch problems that are easy to overlook during translation but can break your app or degrade the user experience once released. Each check can be configured per project, so you can decide which issues are reported as warnings, which are treated as errors that block saving, and which are not checked at all.

Supported QA checks

Localizely currently supports the following QA checks:

Severity levels

Each QA check can be set to one of three severity levels, letting you control how strictly it is enforced:

Configuring QA checks

You can configure QA checks on the Settings page of your project. Each check has its own severity level, so you can adjust the checks to fit the needs of your project. By default, all QA checks are set to Warning.

Some checks, such as Placeholder consistency, ICU syntax validity, and Tag consistency, detect issues that can cause errors at runtime. For these checks, the Error severity is often a good choice.

Tracking QA issues

The Dashboard page includes a card with QA issue statistics. It lists all types of issues currently detected in your project, along with the number of occurrences for each. This gives you a quick overview of the translation quality in your project and helps you keep track of issues that still need attention.

Reviewing QA issues

On the Translations page, every translation with a detected QA issue is clearly marked, so you can immediately see what triggered the warning or error and fix it. You can also filter translations by QA issues and work through them one by one.

Occasionally, a translation may require an exception from a QA check. In German, for example, repeated words like die die are grammatically correct, and some translations keep their leading or trailing newlines to preserve the page layout.

For such cases, you can ignore the reported issue by clicking the Ignore this issue button below it. This keeps known exceptions from cluttering the reported issues, so you always have a clear view of what actually needs fixing.