Use case
Level 2 / ContextLaunches and migrations
Replatforming, redesigns and domain moves are when governance files break at scale. Staging rules go live, sitemaps point at the old site, and nobody checks until the traffic drops.
Without a check
What goes wrong
- A release ships the staging robots.txt with Disallow: /.
- The new sitemap references the old host or the wrong protocol.
- Redirected URLs stay in the sitemap for months after the move.
With Flowpane
What changes
- Checks the live origin, not what the deploy pipeline believes it shipped.
- Detects blanket disallows, mixed protocols and host mismatches.
- With a Deep Scan crawl, finds broken, redirected and orphaned URLs against what the sitemap declares.
What it looks like in Flowpane
Illustrative- Warningrobots.txtDisallow: / applies to every crawler.
- Issuesitemap.xml1,204 URLs use http:// on an https:// origin.
- Warningsitemap.xml318 declared URLs redirect.
Level 3 / Method
How each check works.
Each file, how it fails in public, what true looks like, and exactly how it is checked.
robots.txtrobots.txtrobots.txt tells crawlers which paths they may fetch. One stray line can hide a whole site, so Flowpane checks it against RFC 9309 on every run.ReadSitemapsSitemapsA 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.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.