Understanding the Health Score
Learn how to read the Health Score in UX ContentHub, what each indicator means, and how to fix flagged issues before exporting to your Team Library.
Sébastien Verschaete
Concept

When you're managing multilingual content across a Figma file, it's easy to lose track of what's complete, what's inconsistent, and what just needs a second look. The Health Score gives you a single number to answer that question at a glance.
A score out of 100
The Health Score rates the overall quality of your content setup from 0 to 100. The higher the score, the cleaner your file.
The score is weighted: not all issues carry the same importance. Critical issues have the most impact on your score. Warnings count for less. Items in the For Review category have almost no impact — they're signals, not blockers.
Three categories, three levels of attention
The Health Score breaks down into three sections, each with a different level of urgency.
Critical Issues are problems that affect the integrity of your content. Missing translations leave strings untranslated in your file. Unbound variables are variables that were created during a project but never assigned to any layer — they remain in the collection without being used, quietly polluting it over time.
Warnings flag things that work but could cause problems down the line. Duplicate variables create redundancy and make maintenance harder. Naming issues indicate variables whose prefix or name doesn't follow the English source text, making content harder to identify and manage consistently.
For Review is the lightest category. Flagged items are variables you've manually marked for a second look. QA warnings are automatically generated when a translation deviates from the source text in ways worth noticing — a string that's significantly longer than the original, a difference in punctuation, and so on. These aren't errors. They're prompts for a conscious decision: is this deviation intentional?
Act directly from the score
The Health Score is available in the Local Collections tab of the plugin, where it gives you an immediate overview of your file's content quality. Each issue type comes with a direct action button — Show missing translations, Review unbound, Show duplicates, Fix naming issues. You don't need to hunt for problems manually. The Health Score surfaces them and takes you straight to the relevant view.
Next step
Once your local variables are clean and complete, you're ready to share them beyond your current file. Learn how to push them to your Team library in From local variables to your Team library.




