Use case
Level 2 / ContextFiles nobody owns
The files that govern a site are usually written at launch, by someone who has since moved on. They keep being served, and trusted, long after they stopped being true.
Without a check
What goes wrong
- A root sitemap still lists sections that were retired years ago, while the live inventory is declared somewhere else.
- security.txt passes its expiry date and quietly stops counting.
- humans.txt and ai.txt describe a team and a policy that no longer exist.
With Flowpane
What changes
- Treats every file as a claim and checks it against the live origin on a schedule.
- Shows the exact line that is wrong, and what it costs you.
- Keeps an immutable history of every run, so you can see when a file changed and what changed.
What it looks like in Flowpane
Illustrative- Issuesitemap_index.xml3 of 6 children return 404.
- Issuesecurity.txtExpires passed 11 days ago.
- Advicehumans.txtLast update is more than a year old.
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.
SitemapsSitemapsA sitemap is a public claim about your URL set. Flowpane tests that claim against the live file, a crawl of the site and what Search Console accepted.Readsecurity.txtsecurity.txtsecurity.txt tells researchers where to report a vulnerability. RFC 9116 requires a Contact and an Expires date, and an expired file scores 0.Readhumans.txthumans.txthumans.txt credits the people behind a site. It is tiny and optional, yet a current, dated file is a clear public sign that someone still owns the site.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.