Read a page's scores
Open a page's detail panel and read it in two parts: Health for whether it's well built, Quality for whether it's the right page for the searcher. Each read points at a different fix.
Reading a page's scores means splitting one question into two. Health asks whether the page is well built. Quality asks whether it's the right page for the searcher. GrowthOS keeps them apart in the detail panel on purpose, because a broken page and a thin page need opposite fixes, and a blended number would hide which one you're looking at.
This page covers the page-level read. To decide which page to open in the first place, start with portfolio health.
Read Health and Quality apart
Open a page and the detail panel shows both scores side by side. Read them as two separate stories, because they route to two separate kinds of work.
| Health | Quality | |
|---|---|---|
| The question | Is this page well built? | Is this the right page for the searcher? |
| What it looks at | Crawlable, fast, structured, machine-readable | Format fit, trust, structure for extraction, originality |
| Measured against | Technical standards | The page's search intent |
| What a low score routes to | A technical fix, often an engineering ticket | A content fix: refresh, rewrite, or restructure |
A low Health score is a plumbing problem. The page might be slow, hard to crawl, or missing the structure an engine needs to read it. A low Quality rating is a content problem. The page loads fine but it's the wrong format for the query, says nothing new, or buries the answer. Reading them apart is what lets you send the right fix to the right team without guessing.
Read Quality per persona
Quality is judged per persona where it's relevant, so the same page can read strong for one buyer and weak for another. A pricing page can answer a procurement lead cleanly and leave an end user cold. The panel shows both reads, so you see who the page serves and who it misses.
When the per-persona reads disagree, the action is to decide who the page is for. If it's meant to serve both, the gap is a brief to widen it. If it's meant to serve one, the weaker read is noise you can ignore. Either way, the per-persona view turns a single Quality rating into a targeting decision.
What the six Quality dimensions imply
Quality breaks into six dimensions, each asking a different question about whether the page serves the searcher. Read each one as the action it implies, then follow the deep definitions in reference: scores and taxonomy and scoring.
| Dimension | What a weak read implies you do |
|---|---|
| Intent alignment | Change the format to match what the query's stage calls for. The wrong format fails regardless of the writing, so fix this first. |
| Entity trust | Add author, organization, and first-hand-experience signals an engine can verify. |
| Information gain | Say something the top results don't, or an engine has no reason to cite you over them. |
| Content structure | Add the answer capsule: a short, self-contained summary right after the headline that an engine can lift and cite. |
| Brand presence | Build the domain-level authority signals that back the page up. |
| Engagement craft | Rewrite the hook and the flow so the page holds attention. |
Read the order as a sequence, not a checklist. Get the format right first, then earn trust and say something new, then structure it so a machine can read it. Working out of order wastes effort on a page that fails on format anyway.
A Health score and a per-persona Quality rating ship today, and so does the per-page read. The full Quality model that resolves Quality into a single 0-to-100 score across the six dimensions, and the ranked diagnosis queue that orders the whole portfolio into one work list, are on the roadmap. We label what's live and what's coming so you always know which is which.
Common questions
Health is high but traffic is low. What's wrong? Health only measures whether the page is well built. A clean page can still be the wrong page for the query. Read the Quality rating next; the answer is usually there.
Which score do I fix first? Whichever is weaker against the page's potential. A 95 Health page with a weak Quality read needs a content fix, not an engineering one, even though the Health number looks great.
Why isn't there one combined score? Because a clean-but-empty page and a strong-but-broken page can average to the same middling number, and yet one needs a rewrite and the other needs an engineering fix. Blend them and you throw away the one thing you needed to know.
Where to go next
Step back up to the portfolio to decide which page to open next.
Why Health and Quality stay apart, and what each dimension measures.
Precise definitions of every score and rating.
The detail panel this read lives in, and everything it holds.
Last updated at June 3, 2026
Read portfolio health
Read the whole Page Portfolio, find the section that needs attention, and route the highest-leverage fix. Big Picture labels and grouping turn a wall of URLs into a set of decisions.
Create
Expand your surface area with new pages. The journey in one line: accept an Opportunity, choose a Content Template, draft, review, publish.