Sites
Add, inspect and delete the sites in your organization.
Everything belongs to an organization, never to a person — so a site added by one member is visible to the whole team, and stays if that person leaves.
The list
Domain, Status, Last heartbeat. Plus a Connect site button, which is disabled in effect once you hit your plan's site cap.
A single site
Header with the domain and status, then:
| Field | Notes |
|---|---|
| Last heartbeat | When the plugin last checked in |
| Timezone | Always UTC for sites added through the dashboard |
| Plan | The organization's plan |
Below that, the full Timeline for that site, both views, and a danger zone.
Adding a site
Sites → Connect site, one field: Site domain, like shop.example.com. Paste a full URL
and the https:// and path are stripped for you.
You then get a token, shown once. The easier route for most people is the one-click connect from inside WordPress, which never asks you to handle a token at all.
Over your plan's limit, you get: "Site limit reached for the free plan (1). Upgrade to add more sites."
Deleting a site
Delete site in the danger zone.
Permanent
Deleting removes the site and everything attached to it — events, metrics, incidents, ranked causes, uptime history — and revokes its token. There is no undo and no export.
It does free a slot on your plan, which is the usual reason to do it.
The plugin on that site keeps trying and gets rejected; deactivate or disconnect it there too.
Things you cannot do yet
Rename or edit a site. The domain is fixed at registration. A changed domain means registering the new one — see Moving or cloning a site.
Rotate a token. No rotate button exists. If a token leaks, delete the site and register it again, or re-run the one-click connect.
Change what gets probed. Uptime monitoring is automatic and always checks your homepage. Ask through Need help? if you need a different URL.
Turn off uptime monitoring. Same — ask.
One site per token, always
A token is bound to the domain it was issued for. Copying a working site to staging puts the copy into safe mode rather than mixing its data into your live site's.