Understanding scores and findings
Flowpane uses numeric scores from 0 to 100. A score reflects the current understanding of the artefact or Site, the evidence available when assessed and the active criteria used. Read its Findings and assessment time alongside the number.
What 100 means
100 means best-in-class under the current active Flowpane criteria and evidence model. A Site can reach 100 by satisfying every active, applicable criterion that Flowpane can assess and the customer can fulfil. Valid syntax alone does not establish complete, useful or well-governed content.
Only active criteria affect the score. A capability that Flowpane does not currently assess is not applicable in this model; it does not create an unresolvable Finding or prevent 100. This includes the current limits on deep cookie interaction, full llms.txt linked-resource checks and cryptographic signature verification.
Our understanding develops as artefacts and guidance evolve. Flowpane researches changes in advance and adopts criteria through scoring updates. A Site at 100 today may receive a lower score under newly adopted criteria even when its public content is unchanged. Historical results retain the criteria used at the time. Criteria changes are distinguished from Site regressions.
One Site score, two contributions
The Site score combines applicable implementation quality and governance assurance. An expandable breakdown explains their contributions without replacing the headline Site score.
Implementation Findings explain public content or policy defects. Governance-assurance Findings explain an available evidence control, such as comparing a confirmed supported CMS's source state with its public output. Installing a connector or enabling management alone earns no points.
Monitoring cadence does not buy points. Identical public and source evidence receives the same score on every plan. A faster service can detect problems sooner; a quiet, unchanged Site can remain healthy.
Applicability and evidence
A measured zero is a score. Unavailable means a numeric result cannot be established from current evidence. An incomplete observation proves neither absence nor success.
Optional artefacts can be currently present, explicitly adopted, intentionally retired or unknown. Current absence can remove optional applicability where no explicit obligation remains. A soft-404 does not establish adoption. Earlier presence and Findings remain in history.
For a confidently confirmed or owner-declared supported CMS, an unconnected source integration can create a proportionate Flowpane governance best practice Finding. Every plan, including Free, can establish the supported connection. Unsupported platforms are not penalised for Flowpane's lack of a connector. A platform mismatch needs clarification before platform-specific assurance is assessed.
Read and act on Findings
Findings explain the gap, supporting evidence, authority, contribution and next step. Required and Recommended identify a governing source; Flowpane best practice and observed industry practice describe their own basis. A recommendation does not become a legal obligation.
Review details are available to authorised artefact readers on every plan. Editing, saving, AI assistance and applying a managed change have their own permissions. Confirm business identities, contacts, seller relationships and intended policy before changing them. Deliberate permissive and restrictive AI-crawler policies can both demonstrate strong governance when clear and consistent.
Resolved requires positive evidence that an active rule now passes. Not applicable and criteria retired are separate historical states; neither is reported as a customer fix. Reopening preserves the earlier Finding history and original criteria.
Observed and projected scores
Current public scores describe observed state. Proposed content, Save and downloads do not publish it. An estimated or conditional projection uses the same active criteria as public scoring and retains remaining Site limits, contradictions, assurance uncertainty and verification requirements. Publish through the authorised workflow, then verify the public result.
See Site score, Review and Flowpane Impact in Analytics.