Issues and recommendations
Finding types
| Type | Meaning | Score treatment |
|---|---|---|
| Issue | Objective defect in the observed artefact | Read the finding and score shown in Flowpane |
| Warning | Risk or publisher-intent review trigger | Always score-neutral |
| Recommendation | Flowpane improvement advice | Read the finding and score shown in Flowpane |
| Information | Context or provenance | Always score-neutral |
Finding type is not a legal or compliance verdict, and not every finding needs a fix. Platform guidance uses bounded declared/observed evidence; Flowpane does not infer that a CMS plugin manages the artefact.
Choose the next action
Read the finding’s evidence and decide whether it is an objective defect, a policy choice or useful context. A warning about broad robots rules may require confirming intent, while a malformed contact URI may need an authored correction. A recommendation is Flowpane advice, rather than a universal legal requirement.
Use Review for supported quick fixes and Draft editor for wider changes. Missing and inaccessible resources need different treatment. After authorised publication, run a check to assess the public result rather than treating a prepared fix as resolved.