Content Health Score

The Health Score is the single number that summarizes how well a page is doing as a piece of knowledge content. It runs from 0 to 100 — higher is better — and is computed every time a page is scanned.

Where the score shows up

Where	What you see
Global Dashboard summary card	Average across all scanned pages in your instance.
Space Dashboard summary card	Average across all scanned pages in that space.
Per-page table rows (All Pages tab)	Each page’s individual score, sortable.
Inline byline lozenge	The page’s score on the page itself, under the title.
Optional page banner	A full-width banner at the top of the page when enabled.

Score bands

Pulse renders the score with a coloured lozenge based on simple bands:

Band	What it usually means
Healthy	The page is in good shape — recent, complete, structured.
Needs Attention	One or two signals are weak. Worth a quick look.
At Risk	Multiple signals are weak. The page is likely stale, thin, or broken.

What the score is built from

The Health Score is a weighted combination of several signals. The signal categories are visible in the Settings panel as rule names; the exact weights and thresholds are tuned by Bytera and may evolve as we learn from real-world content.

The signal categories are:

• Freshness — how recently the page was edited.
• Content depth — how substantial the page is (rough proxies like word count and heading density).
• Structure — whether the page has good headings, links, and supporting media — the things that make scanning the page easy.
• Engagement — how often the page has been updated by people over time, signalling that it’s actively maintained.
• Completeness — basic hygiene: does it have a real title (not a placeholder), is it more than a stub.
• Broken links — pages with dead internal links get a deduction.

Each of these contributes to the total. A page can earn a high score without being perfect on every signal — the goal is overall health, not gaming a single metric.

What the score is not

The Health Score is not:

• A judgment on the quality of writing — Pulse doesn’t read meaning, only structure.
• A measure of correctness — Pulse can’t tell if your code samples work or if your facts are accurate.
• A SEO score — it’s about internal knowledge management, not public-web discoverability.

Treat the score as a structural-hygiene signal, not a content-quality one.

Improving a page’s score

The “no-rocket-science” playbook for lifting a page’s Health Score:

1. Edit it. Even a tiny update refreshes the page and lifts the Freshness signal.
2. Give it a real title. Replace “Untitled page” or placeholder titles with the actual subject.
3. Add headings. Break long blocks of text into 2–3 sections with proper H2/H3 headings.
4. Fix broken links. Each one removed lifts the score directly.
5. Add at least one supporting element. A relevant image, a link to a sibling page, or a small table all help the Structure signal.

You don’t need to do all of these at once. Each move shifts the score upward on the next scan.

When the score updates

Trigger	When
Confluence event	The moment a page is created, edited, or deleted (a page event arrives at Pulse).
Weekly scan	Pulse re-scans every space on a regular weekly schedule.
Initial scan	The first time the Global Dashboard is opened after install.

You don’t typically trigger scans manually — the combination above keeps scores current.

Next

• AI-Ready Score — the companion score for AI tools like Rovo.
• Custom Policies — define your own rules and weights.
• Trends — track score movement over time.