12:30Compare

Smartling LQA and Loqalit: the translation and the page

Smartling measures translation quality inside its platform, with a predictive Quality Confidence Score and human LQA scored with MQM. Both look at translations. Loqalit looks at the product: it checks your live and staging pages in every language on a schedule and flags what users actually see, from clipped buttons to text that never reached Smartling, each with a screenshot and a suggested fix.

Last reviewed:November 2026

At a glance

Numbers in brackets link to the source for each claim about the other product.

Smartling quality featuresLoqalit
Where it runsInside Smartling, on translations[1][2]On your live or staging pages, in a real browser
Quality scoreA predictive Quality Confidence Score, and LQA scores with MQM[1][2]An MQM category and severity per finding, and page scores normalized per 1,000 words
What it seesStrings and their translationsThe page your users see: layout, context, hard-coded text, mixed languages
WhenDuring and after translation, in the TMSAfter deployment, on a schedule you set, and as a release gate in CI
EvidenceA score, and the errors a reviewer annotatesA screenshot, a reason, an MQM severity and a suggested fix for every finding
Text outside the TMSNot visible: it scores what was sent for translationFound: hard-coded and untranslated text shows up on the page

Why teams choose Loqalit

What you get when QA looks at the product your users load, not only at the text that went into it.

It sees what your users see

Loqalit loads your live or staging pages in a real browser, so it catches clipped buttons, hard-coded text and translations that are right as a string but wrong on the page.

Every page, every language, every run

Scans run on a schedule you set, with nobody at the keyboard. No sample to plan, no reviewer to book.

Evidence with every finding

A screenshot of where it appears, a reason, an MQM severity and a suggested fix that fits the space.

Agents that do the legwork

Scout finds pages you aren’t watching yet, Editor drafts fixes against your glossary, and Verifier rechecks a page before an issue is called fixed.

A gate before release

A GitHub Actions step can fail the build on critical or major findings on your staging site.

Fixes land where your team works

Accepted fixes are posted to Crowdin or Phrase as comments with a screenshot, or exported as PDF, Excel, CSV or JSON.

When to use which

Use Smartling quality features for

  • Predicting which translations need review, inside Smartling
  • Human LQA rounds and vendor quality tracking
  • Content that never renders as UI, such as documents
  • Quality dashboards across your translation providers

Add Loqalit for

  • A translation is clipped or overlaps in the real layout
  • Text was hard-coded or never sent to Smartling
  • A good translation appears in the wrong context on the page
  • You need regressions caught on live or staging pages after each release

Smartling scores the translation. Loqalit checks the page.

Keep Smartling’s quality features for translations. Add Loqalit after release, to see the product the way your users do.

Frequently asked questions

Does Loqalit replace Smartling?

No. Smartling is where translation and its quality scoring happen. Loqalit checks the rendered product after release. They answer different questions.

Is a high Quality Confidence Score enough?

It tells you a translation is likely to be good. It can’t tell you the translation fits its button, appears in the right place, or that every string on the page was sent for translation. Those only show on the rendered page.

Does Loqalit use MQM too?

Yes. Every finding gets an MQM category and severity, and pages get a score normalized per 1,000 words, so the numbers sit next to your LQA results.

Can I try Loqalit on my own site?

Yes. Get a free QA report on up to 3 languages, or try the Chrome extension as a guest: one free scan per device, no account needed.

Sources

Claims about other products come from their own public pages and from published descriptions of them. Product names belong to their owners.

  1. Smartling: Translation analytics and Quality Confidence Score · checked 16 November 2026https://www.smartling.com/software/translation-analytics/
  2. Smartling blog: Translation quality assurance · checked 16 November 2026https://www.smartling.com/blog/translation-quality-assurance

See what a translation score can’t: get a free QA report.

We scan your live site in up to 3 languages and email you a PDF with screenshots, MQM severities and suggested fixes.