A health score is a strange thing to hand someone. It compresses everything about a site, its security posture, its config, its broken links and aging content, into one number between 0 and 100, and then asks you to feel something about it. Most people glance at it, decide whether they are relieved or worried, and move on. That is a waste of a genuinely useful signal. The number is only worth having if you know what it is measuring, what it deliberately leaves out, and what actually makes it move. Read that way, it stops being a grade and becomes a to-do list you can act on.
What the score is, and what it is not
A RecapWP health score is a composite reading of your site's current state, taken from the same findings a full audit surfaces. It is not a vanity metric, and it is not curved to make you feel good. If a site sits at 64, the audit means 64: there are real, open issues pulling it down, and the list will tell you exactly which ones. The number and the findings are two views of the same truth, one glanceable and one actionable, and they never disagree.
It is also deterministic. The score is computed from defined checks against your site's actual configuration, so the same site in the same state produces the same number every time. Nothing is estimated, sampled, or guessed. That matters more than it sounds: a score that drifts on its own, or that changes because a model felt differently today, is a score you learn to ignore. One that only moves when your site actually changes is one you can trust to mean something.
Only the findings that matter move it
The most common misreading of a health score is treating every issue as if it counts the same. It does not. RecapWP weights the score by severity, and the weighting is steep: a Critical finding costs far more than a High, a High far more than a Medium. The worst exposures dominate the number, exactly as they should, because they are the ones that do real harm if left alone.
Below Medium, the math changes shape entirely. Low and Info findings are advisory: they carry no penalty at all. They are still listed, still explained, still worth a look when you have time, but they do not drag the number down. This is deliberate. A site whose only open items are minor or optional advisories is, in every way that matters, a healthy site, and its score should say so. If your number is high but the list still has entries, check their severity before you worry. Very often the remaining items are precisely the ones that were never meant to move it.
The practical consequence is that you cannot meaningfully raise a score by clearing a pile of Low items. The points are not there. To move the number you address what is actually weighing on it, and the worst-first ordering of the findings list points you straight at those items first. The score tells you how much work is left; the list tells you which work it is.
What a low score is actually telling you
A low number is not a judgment on you or your site. It is a measurement of distance: how far the current state sits from a clean one, expressed as a single figure so you can take it in at a glance. Treated as a verdict, it is discouraging. Treated as a queue, it is the most useful thing on the dashboard, because the same findings that produced it are sitting right there, ranked, ready to work through.
And because the score reflects your open findings, it responds to the work you do. Resolve a high-severity finding and the number climbs as the change lands. Accept a finding you have deliberately reviewed, and it stops counting against you the way an unresolved one would. The score is not a static report card filed once a month; it is a live reading that follows the state of the site, so the effort you put in this afternoon is visible this afternoon, not abstract.
A health score is not a grade you were given. It is the distance to a clean site, written as one number so you can see at a glance how much of it is left.
The trend says more than the number
If you only ever read the score as today's figure, you are missing the more valuable half of it. A single reading tells you where you stand right now. The trend tells you whether you are keeping the site healthy or slowly losing ground, and that is the question maintenance is really about. RecapWP keeps a history of your scores across audits and charts the direction: where you started, where you are now, and where you are aiming.
Read that way, the absolute number matters less than its slope. A site that holds a steady 82 audit after audit, never regressing, is in better hands than one that spikes to 94 after a big cleanup and then bleeds back down to 70 over the following months because nothing was watching. Config drifts, plugins update, content ages, new links break; a site is a moving target, and a flat or rising line is the sign that someone is keeping pace with it. When the line dips, the history shows you which audit it dipped on, which is usually enough to remember what changed.
Why the score is yours to trust
Underneath all of this is a quiet but important fact: the score is a reading of your site, taken on your own server. RecapWP computes it from your site's real state, inside your own admin, and it is available for every install to see, not held back behind an upgrade. Your score, and its history, belong to the site they describe. Nothing about how the number is produced depends on an outside service forming an opinion about you.
That is what lets the score be blunt. Because it is deterministic, local, and tied directly to findings you can open and read, there is no incentive for it to flatter you and no mechanism by which it could. It would rather be useful than reassuring. A number you can trust to be honest, even when the honest answer is uncomfortable, is worth far more than a comfortable one you have learned to discount.
So the next time you land on the dashboard, do not just note whether the score is good or bad. Read it as a queue: check the trend to see which way the site is heading, open the findings behind the number worst-first, and clear or consciously accept the items that are actually holding it down. The figure will follow the work, and after a few passes it stops being a source of anxiety and becomes what it was always meant to be, a fast, honest read on whether your site is in good hands.