Add & edit sites — field by field
Open Sites → Add site, or click Edit on a site detail page. The form is grouped into blocks; only Basic info is required.
#Basic info
- Name: for display — pick something you'll recognize at a glance (e.g. "Main site", "API").
- URL: the full URL. Any path works, not just the homepage; https sites also get a certificate check for free.
#Monitoring
| Field | Meaning | Suggestion |
|---|---|---|
| Check interval | How often to check | Low tiers (1–2 min) for critical sites; 5 min for the rest |
| Timeout | How long without a response counts as failure | Default 15s; raise it for cross-border sites |
| Consecutive failures | Failures in a row before an incident | Default 3; raise for sites prone to false alarms |
| Keyword | Words the page must contain / must not contain | One stable marker word each is enough |
#Advanced (optional)
- Request method / headers / body: switch to POST and add headers like
Authorizationwhen monitoring APIs. - Accept-Language: for multilingual sites — pin which language version to fetch.
- Fetch channel: route the check through a specific proxy or your own node (see Vantage points & proxies).
- Internal site: sites resolving to internal IPs are blocked by safety rules by default; mark it here only if the internal network is yours.
Note
Setting Consecutive failures to 1 sharply increases false alarms; 10 can delay detection of a real incident by half an hour. When in doubt, keep the default.
Related: Judgement rules in detail · Domain ownership verification