How pages are scored
Health, Quality and capture measure different things on purpose. A single blended number would hide the problem you need to see.
GrowthOS scores a page on six axes (lifecycle, momentum, traffic, query health, readiness and competition) and resists blending them into one number. That's a deliberate design choice, and it's the reason the scores are useful rather than decorative.
Health and Quality stay separate on purpose
A broken page and a thin page need opposite work. One needs an engineer, the other needs a writer.
A blended number would tell you neither. So Health and Quality are computed and shown separately. Big Picture does roll up (Health, Quality, impressions capture and traffic capture into one status), but only after you've been shown the parts.
Readiness follows the same rule. It combines Health and Quality as a pair rather than averaging them, because the average of "technically broken" and "well written" is a number that describes no real page and suggests no action.
Multiple axes separate problems a single score merges
A page can sit at Competing, Freefall and Clean at once: rankings settled, traffic falling sharply, nothing technically wrong.
That combination is informative. Rankings have stopped moving and traffic is dropping anyway, with a clean technical read, which points at content or competition rather than at anything you'd find in a technical audit. One number would have hidden it, and you'd have gone looking in the wrong place.
"Against its own potential" is the idea that matters
The scores do not ask is this page good. They ask how much of what this page could earn does it earn.
That reframing changes what the numbers mean:
- A page ranking third for a term nobody searches isn't succeeding.
- A page capturing 4% of an enormous keyword set isn't failing. It may be among the largest opportunities on the site.
Capture is the metric that carries this idea. Read it before you read position.
Capture is only as good as its inputs: it's computed from Google Analytics and Search Console, so a workspace missing either connection reads blind here.
Incomplete is not a bad score
Incomplete means fewer than two pillars are available, usually because the page is too new or is not inside an analysis zone.
Treat it as "not yet measured", never as "measured badly". Acting on an Incomplete score is acting on an absence of data.
Where this shows up
- Page detail shows every scorecard for one URL.
- Pages Portfolio shows the axes across the whole site.
Last updated at October 20, 2018
Agents draft, you decide
Every agent in GrowthOS produces a proposal and waits. Understanding that division of labour is how you get value out of it.
Reading a portfolio
Distribution is the honest read of a site. Averages hide the thing you needed to act on, and grouping is what turns a list into a decision.