Site verification
Open the Workspace selector in Flowpane, choose your Workspace and select the pending Site on its dashboard. Sign in if prompted.
When you add a Site it starts in the Pending state. Verify ownership by publishing a proof using one of three methods. Verification enables you to start checks; it does not prove that automatic checking is active.
Verification methods
Each Workspace has one stable verification value. You can reuse it across every Site in the Workspace and across all three methods. Keep it private except where it must be published as the proof.
- File — download the verification file from Flowpane and publish it at
https://<your-site>/.well-known/flowpane-verify-<id>.txt. Flowpane also accepts it athttps://<your-site>/flowpane-verify-<id>.txt. The exact path and filename are shown in the verification panel. - DNS TXT — publish the supplied value as a TXT record at
_flowpane.<your-site-hostname>. No HTTP request is needed, so this method works even when a firewall blocks Flowpane. - Meta tag — publish the supplied
<meta>tag in the<head>of your homepage.
Verifying
- Open the Site, or select it in the Sites list.
- Choose the method whose proof you have published.
- Click Verify.
Bulk Verify appears on the dashboard while any Sites are pending, with Verify selected and Verify all. It always shows which method will be applied. Each Site is still checked independently, so a partially successful run reports its successful and failed Sites separately.
Verification and Site status
After verification the Sites list shows a status that reflects run evidence, not the score:
| State | Meaning |
|---|---|
| Pending | Ownership proof succeeded, but no governance run has reached a completed or failed outcome yet |
| Active | At least one governance run has reached a completed or failed outcome |
| Inactive | The Site is not currently both activated and monitoring-enabled |
Until a score is available the list shows — rather than a number.
Recurring checks apply to eligible verified Sites with monitoring enabled. Verification alone does not establish a completed first result. See Check scheduling.
Troubleshooting
If verification fails:
- Confirm the method selected in Flowpane matches the proof you published.
- For File or Meta, confirm the URL is public and that your firewall does not block Flowpane. Flowpane publishes a guide for firewall administrators at app.flowpane.com/help/site-verification explaining how to allow its user agent and verification paths in Cloudflare and Akamai, and why the exception should stay narrow.
- For DNS, confirm the TXT record is on the dedicated
_flowpanehostname and allow time for propagation. - Retry after correcting the proof. If verification fails, correct the proof and retry; check the verification status shown for the Site.
Verification is one boundary
Verification records control of the configured Site. It does not certify governance, connect a CMS or enable Managed changes. If the host or Site address changes, confirm the current record and offered verification method before relying on previous evidence.
To diagnose a failed attempt, compare the exact public address and required verification evidence, including redirects, caches and access restrictions. Avoid repeated checks while an existing attempt is still in progress. See troubleshooting.
Verify Site
To verify Site control, follow the current method above for the exact configured address. If verification fails, confirm that the required public evidence is reachable before retrying.