Use case
Level 2 / ContextMany sites, one queue
Every site drifts on its own schedule. At twenty sites, a quarterly audit is already out of date before it is finished, and the worst site is rarely the one you hear about.
Without a check
What goes wrong
- No single review catches everything, because each site changes at a different time.
- Findings live in spreadsheets that nobody re-runs.
- Attention goes to the loudest client, not the riskiest site.
With Flowpane
What changes
- Checks every site on a schedule, from weekly on Starter to hourly on Enterprise.
- Ranks what needs attention across a workspace, with file coverage and AI readiness across the portfolio.
- Bulk verify, bulk run, tags and CSV import for onboarding many sites at once.
What it looks like in Flowpane
Illustrative- Issueatlas-foods.exampleSite score 47. robots.txt blocks /products/.
- Warningnorthwind.exampleSite score 61. security.txt expired.
- Infoharbour-health.exampleSite score 91. No change since last run.
Files involved
Most relevant for
Level 3 / Method
How each check works.
Each file, how it fails in public, what true looks like, and exactly how it is checked.
ScoringHow the score worksFlowpane scores each of eight artefacts from 0 to 100, then weights them into one site score. Only the next public check moves it. Drafts and errors never do.ReadCoherenceCross-file coherenceEach governance file can pass validation alone and still contradict another. Flowpane's coherence engine compares them and reports where your files disagree.ReadCrawler identityHow Flowpane fetchesFlowpane reads public HTTPS only, never signs in, and signs requests with Web Bot Auth so firewalls can verify them. Blocked is never reported as Missing.Read
See what your sites are claiming.
Add an origin and get a score, the gaps, and the evidence behind each one. Then Flowpane keeps checking, so the answer stays current.
Free during the beta. Flowpane only reads your origin.