Public website evidence, request identity and site-owner choices
Flowpane reads publicly accessible website evidence to help site owners check their governance files and sitemaps. It can also read public HTML and, when a customer starts a Deep Scan, follow internal links to compare reachable pages with the site's sitemap.
A crawl has page, depth and time limits and may finish before it has visited every page. Governance-file acquisition and bounded page crawling are distinct: a governance check does not imply a full crawl.
Checking observes your public site. It does not itself publish changes. Use Flowpane's separate publishing or management actions when you intend to change website output.
| User-Agent | Flowpane/1.0 (+https://crawler.flowpane.com) | |
| Compatible UA | Mozilla/5.0 (compatible; Flowpane/1.0; +https://crawler.flowpane.com) | |
| Operator | Flowpane | |
| Contact | assist@flowpane.com | |
| Website | flowpane.com |
Checks can request robots.txt, ads.txt, security.txt, llms.txt, ai.txt, humans.txt, XML sitemaps and public HTML relevant to the check. Some checks may use browser-based reading when an ordinary HTTP response is insufficient. Flowpane does not sign in to access private pages.
Deep Scan evaluates the robots.txt rules applicable to Flowpane before crawling page URLs. An applicable wildcard group is used when there is no Flowpane-specific group. If the policy cannot be read reliably, page crawling for that origin stops. A missing robots.txt can permit crawling.
Crawl-delay influences Deep Scan pacing, with a maximum supported delay of ten seconds. This is not a global request-rate guarantee. Redirect following is bounded to five hops (301, 302, 303, 307 and 308) and must stay within permitted public destinations.
Flowpane's standard request identity is Flowpane/1.0 (+https://crawler.flowpane.com). The robots.txt product token is Flowpane. A browser-compatible User-Agent is also shown above.
A User-Agent can be copied by another client and does not authenticate a request by itself. This trust page's hosting address is not a verified inventory of every outbound crawler address.
The public key directory is available for verifying Flowpane request signatures. Use a signature verifier to check the signature and its validity against the matching public key. The presence of a User-Agent or a signature header alone is not proof of authenticity.
This page does not promise that every acquisition path sends a signed request. If you need help identifying an unexpected request, contact assist@flowpane.com.
If your firewall blocks Flowpane, a check may show blocked or unavailable evidence rather than a missing file. Review your firewall's request logs and use its documented controls to permit only the traffic you intend to allow.
Do not treat a User-Agent match alone as authentication. For help with a blocked check or unexpected requests, contact assist@flowpane.com.
To exclude page paths from Deep Scan, add rules for User-agent: Flowpane in robots.txt. For example:
User-agent: Flowpane Disallow: /
Blocking page crawling does not guarantee that Flowpane stops requesting public governance files, including robots.txt itself.
Questions or unexpected requests: assist@flowpane.com.