Reading your governance score
Governance results produce an artefact score from 0 to 100 for each artefact, and a weighted Site score. A score can also be unavailable when Flowpane could not establish usable evidence.
How scoring works
The six fixed text artefacts use a shared finding contract. Issues and Recommendations deduct only when that artefact's assessor supplies a positive penalty. Warnings and Information are always score-neutral. Repeated findings can share a family so duplicate instances receive bounded treatment, and some artefacts cap recommendation deductions.
Cookies & Consent reports an observation-risk score, not legal compliance. Sitemaps uses its dedicated layered scoring model.
Score bands
| Range | Colour | Meaning |
|---|---|---|
| 80–100 | Green | Healthy result within Flowpane's model |
| 60–79 | Amber | Improvements needed |
| 0–59 | Red | Material findings or a missing required artefact |
| — | Grey | No score yet, or the Site is unscorable |
Site score
Each Site has a weighted composite across the eight artefact types: Sitemaps 35, robots.txt 15, Cookies & Consent 12, security.txt 12, ads.txt 8, llms.txt 7, ai.txt 6 and humans.txt 5. The composite uses persisted last-good results. Required missing artefacts contribute zero; recommended missing artefacts are excluded; required blocked evidence can make the score unavailable.
The Site score is shown on the Site overview page, in the Sites list, in Workspace analytics and on the cover of the governance report. All of them read the same stored value.
Score history
Every check stores an immutable Result, so each artefact's score history is retained. Proposed editor changes never enter score history; a later public check is required to change observed scoring.
What the finding types mean
- Issue — an objective defect; may deduct
- Warning — a score-neutral risk or intent review trigger
- Recommendation — improvement advice; may deduct when explicitly configured
- Information — score-neutral context or provenance
Finding types are not legal-compliance conclusions. Platform guidance is bounded by declared and observed evidence and does not prove that a CMS plugin manages the artefact.
For the full model see Governance scoring.