Guide
How to check Weglot translation quality
Check Weglot translations on the live site, page by page and language by language, because the problems that matter most only show up once the translated text is on the page: wrong-context machine translation, text that overflows, dynamic content left untranslated, and glossary terms that weren’t applied.
Loqalit is an agentic localization QA platform that checks your live and staging websites and web 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.
Updated October 2026
What does Weglot give you for reviewing translations?
Weglot translates your site with machine translation and gives you editors, glossary rules and review assignments to correct it. These tools help a person review; coverage depends on which pages and languages someone opens.
What should you check on a Weglot-translated site?
Check | What to look for | Where it usually shows up |
|---|---|---|
Wrong-context translation | A string translated correctly on its own but wrong for the element it labels, e.g. a verb translated as a noun | Buttons, navigation, form labels, error messages |
Overflow and truncation | Longer translated text that wraps, clips or pushes layout out of place | Buttons, menus, cards, tables, mobile layouts |
Untranslated dynamic content | Text that appears after the page loads and stays in the source language | Pop-ups, search results, cart and checkout steps, third-party widgets, text inside images |
Glossary violations | Brand names or product terms translated when they shouldn’t be, or translated differently across pages | Headings, navigation, product pages |
Wrong-context translation: machine translation sees a string, not the element it belongs to. Read key flows in each language, in context.
Overflow and truncation: check every language at both desktop and mobile widths.
Untranslated dynamic content: pages that mix languages are the clearest sign something was missed.
Glossary violations: confirm your glossary rules show up on the live pages, not only in the editor.
How do you check Weglot translations at scale?
Manually, someone opens each page in each language, at desktop and mobile widths. The time this takes grows with every page and every language you add.
The alternative is rendered-product QA. Loqalit scans the live translated pages of a Weglot site in every language, on a schedule, without anyone logged in. Every finding comes with a screenshot, a reason and an MQM severity, and you apply the fixes in Weglot’s editor. You can also export findings (CSV, XLSX, PDF or JSON) or connect through signed webhooks and the REST API.
File QA tools like Xbench check the translation file. TMS QA checks strings against rules. Loqalit checks what your users actually see.
Does this apply to other website translators?
Yes. The same checks apply to other website translation tools such as ConveyThis, Bablic and Localize.
Localization QA for live websites and web apps · All six categories of localization QA tools
Frequently asked questions
Is Weglot’s machine translation good enough?
It depends on the content. Check high-traffic and high-stakes pages, such as checkout, forms and legal text, in context in every language before relying on them.
Does Weglot check layout or overflow?
Weglot’s visual editor lets a person see translations on a live preview. Its quality checker is described as scoring translation quality for a URL; Weglot doesn’t describe layout or overflow checks.
Can Loqalit check a Weglot-translated site?
Yes. Loqalit scans the live pages, so it works on any translated website, whichever tool translated it. No Weglot integration is needed.
Is Loqalit affiliated with Weglot?
No.
Can I try Loqalit on my own site?
Yes. You can run one scan as a guest before creating an account.