Loqalit is an agentic localization QA platform that checks your live and staging websites, web apps and mobile apps in every language you ship. It catches translation, context and layout bugs in the rendered product, scores them with MQM, and routes fixes into Crowdin or Phrase.
This guide covers localization QA for the live, rendered product: how it works, what it catches that file and TMS QA miss, and which tools do it.
Updated October 2026
You check translation quality on a live website by reviewing the rendered pages in each language, not the translation files, because many localization bugs only exist after the text lands in the layout.
There are three ways to do it:
If you only do one thing, check the pages that changed since your last release, in every language you ship.
Translating your site with Weglot? See how to check Weglot translation quality.
In-context LQA (linguistic quality assurance) for web apps means evaluating translations inside the running product, where each string sits next to the element it labels, instead of in a spreadsheet or string list.
Context changes the verdict. A translation can be correct as a segment and still be wrong in place: the wrong sense of an ambiguous word, a label too long for its button, or a term that changes from one screen to the next.
In-context LQA can be human-led, with a reviewer working in an in-context editor, or automated, with a tool doing the review across every page on a schedule. Loqalit does the automated version. Its agents open your pages in a real browser, judge each string where it renders, and score what they find with MQM.
Rendered-product QA catches bugs that only exist after translated text is rendered: overflow, truncation, layout overlap, RTL mirroring errors, translations that are wrong in context, hardcoded strings that never reached the TMS, and terminology that drifts between screens.
File QA tools like Xbench check the translation file. TMS QA checks strings against rules. Loqalit checks what your users actually see.
| Error type | File QA (e.g. Xbench) | TMS QA | Loqalit |
|---|---|---|---|
| Missing translations | Yes | Yes | Yes |
| Terminology vs glossary | Yes | Yes | Yes |
| Placeholder mismatches | Yes | Yes | Yes |
| Text overflow in the rendered UI | No | No | Yes |
| Truncation and clipping | No | No | Yes |
| Layout breaks and overlap | No | No | Yes |
| RTL mirroring errors | No | No | Yes |
| Context-wrong but segment-correct translations | No | No | Yes |
| Cross-screen terminology conflicts | Within the file only | No | Yes |
| Hardcoded / untranslated strings in the build | No | No | Yes |
| MQM-scored severity across the product | No | No | Yes |
File and TMS QA still matter. They catch errors earlier and more cheaply, before anything is built. Rendered-product QA is the layer after them, not a replacement. See how TMS QA checks and in-context QA work together.
Continuous localization quality monitoring means scanning the same pages in every language on a schedule, so a regression is caught when a release ships rather than when a customer reports it.
In Loqalit, it works in four steps:
Language coverage and its trend over time are tracked, so a drop can be dated.
The Chrome extension is one way to run Loqalit on demand; the platform runs scheduled scans without anyone logged in.
Only a few tools check translations on the rendered page. Most localization QA tools check files or strings.
For bilingual-file checks before delivery, a file QA tool like Xbench is still the right choice. See all six categories of localization QA tools.
Yes. Rendered-product QA works on any live or staging page, so you can scan a release candidate in every language before it ships.
No. Keep your TMS’s built-in checks switched on. They catch string-level errors early. Rendered-product QA checks what those checks can’t see: the product after rendering.
Any language your site renders, including non-Latin scripts and right-to-left languages such as Arabic. Loqalit analyses the text on the page instead of using a fixed language list.
No. Loqalit is a platform with two ways in. The Loqalit platform runs scheduled scans with agents and nobody logged in. It starts with a demo, and our team onboards you. The Chrome extension scans the page you’re on, on demand, and anyone can try it today.
With MQM (Multidimensional Quality Metrics). Each finding gets an error category, such as accuracy, terminology or design, and a severity. Read our MQM scoring guide.
Yes. Accepted fixes are posted server-side to Crowdin or Phrase as comments with a screenshot, where your translators already work.
The agentic platform starts with a free QA report and a demo. Guests can try the extension with one free scan per device, no account needed.