GrowthXDocs
PlatformManageRead portfolio health

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.

Open in ChatGPTOpen in Claude

Reading portfolio health is how you decide where to spend the week before you touch a single page. The Page Portfolio can run to thousands of URLs, and staring at the full list tells you nothing. The Big Picture label and a grouping turn that list into a short set of decisions: which section is underperforming, and what one fix would lift the most pages at once.

This page covers the portfolio-level read. For one page's detail, see read a page's scores.

Read the Big Picture label first

Every page carries a Big Picture status: one readable label that rolls up Health, Quality, and how much traffic and impressions the page captures against its own potential. Graded against potential is the part that matters. The label asks how much of what a page could capture it actually does, not whether the page is good in the abstract.

LabelRead it as
OptimalCapturing close to its potential
GoodPerforming well, with minor headroom
DevelopingClimbing, not there yet
Needs WorkUnderperforming its potential
IncompleteMissing the data or content to judge

These are the short reads. The taxonomy and scoring page explains how the four signals combine, and reference: scores holds the precise definitions. Scan the labels to find where the gap between current and potential is widest. That gap is your work.

Group to turn URLs into decisions

A flat list of labels still hides the pattern. Grouping is the move that surfaces it. Group the portfolio by Content Cluster to see coverage by strategic territory, or by persona to see who your pages serve well and who they don't.

Group by territory or persona. Pick the lens that matches the decision in front of you. Territory shows which bet is underfed; persona shows which buyer your site reads weak for.

Find the section with the worst aggregate read. A cluster full of Needs Work pages, or a persona with thin coverage, is a section-level problem, not a page-level one.

Route the fix to the section, not the page. A template or structural fix applied across a cluster repairs many pages in one move.

Grouping works because problems cluster. A weak format or a missing answer capsule rarely shows up on one page in isolation; it shows up across a whole territory that was built the same way. Find the shared cause and you fix the section.

Route the highest-leverage fix

Once you've found the section, decide what to do with it. Portfolio health routes to one of three places.

What the read showsWhere it routes
A cluster underperforming its potentialA section-wide fix: restructure or refresh the pages together
A strategic territory with no pages behind itCreate: research becomes new pages
A single page dragging an otherwise healthy clusterRead its scores and fix it directly

The reason to start at the portfolio level is leverage. Urgency in GrowthOS compounds across factors rather than summing, so a high-traffic territory that's slipping outranks a quiet one with the same symptoms by a wide margin. The fixes worth doing first are the ones that repair a whole section of the site at once, and you only see those from the portfolio view.

Common questions

How often should I read portfolio health? Weekly is enough for routing. The labels move as pages gain or lose traffic, so a weekly scan catches a slipping section before it costs you much.

Does a low label always mean the page is bad? No. Incomplete means the system is missing data or content to judge, not that the page failed. Needs Work means the page is underperforming what it could capture, which is the one to act on.

Should I fix the worst page or the worst section? The worst section. A section-wide fix lifts more pages per unit of effort than chasing one URL.

Where to go next

Last updated at June 3, 2026

On this page