Common humans.txt issues

File not found

humans.txt is an optional web convention rather than an external compliance requirement. Flowpane nevertheless recommends it and assigns a missing file an artefact score of 0/100, which participates in the overall Site score alongside other governance evidence.

Creating or saving a starter draft does not change that observed score. Deploy the file and run a later check before Flowpane can score the live content.

Empty file

A file that is present but contains no useful content is a genuine quality problem.

HTML returned instead of text

Fix the server route or static-file mapping. Flowpane does not automatically replace an HTML response with a text patch.

Missing TEAM, SITE, Name, or Last update

These are optional conventions. Include the credits and details your organisation has approved for publication.

Template not customised

Default template text without actual team information.

Fix: Replace sample text with credits and Site facts you have verified.

Resolve the cause, then verify

First compare the finding with the obtained Current content. If the expected text URL returns a theme page, challenge or redirect, ask the responsible host or CMS maintainer to correct that response. A browser-visible page does not establish that the resource was readable to Flowpane.

Agree whose credits should be public and how they should be described. Names and contact details need an appropriate publication decision.

Prepare a focused correction, check authored details and use your authorised publication process. This is an optional convention rather than a legal or technical requirement. Flowpane recommendations about headings or dates do not make one credit format mandatory. A saved draft or dismissed notice is not proof of remediation; repeat the public check afterwards.