Verify a site
A site starts pending and becomes verified when the widget is found on its homepage. Subblog domains (*.nibgate.xyz) are auto-verified by being linked to a hub wallet and skip the widget sweep entirely.
States
pending: site was registered but ownership is not verified yet.verified: widget was found on the registered origin.missing_widget: the homepage does not carry the widget marker.failed: the site homepage could not be fetched to verify the widget.
Verification process
Register origin
The dashboard creates the site record and token. Only register domains you control.
Crawl homepage
The backend fetches the registered origin and checks for the Nibgate widget marker (data-nibgate-site with the site id).
Mark verified
If the marker is found, the site is marked verified and can stream content and activity events. (Event ingestion separately validates the site token.)
Recheck health
Scheduled checks make sure verified sites do not silently remove the widget.
If the widget is removed after verification, a recheck flips the site to missing_widget. Note that event ingestion still accepts events from any site with a valid token, so the widget marker is a discovery-surface health signal rather than a hard event gate.
Removal behavior
Removing a site soft-deletes it (deletedAt), hiding it from active dashboard and Explore views. Historical metrics stay archived for reporting and audit context.