Guides

Set up continuous monitoring

A one-off scan is a snapshot. Monitoring rescans your site on a schedule and tells you when something changes — a new tracker, a dropped header, a certificate nearing expiry.

How monitoring works

When you register a site, Sift Health stores its baseline findings. On each scheduled rescan it diffs the new results against the baseline and raises alerts for meaningful changes: a new_finding, a resolved_finding, a score_drop, or a cert_expiring event. Rescans run on a shared scheduler that processes due sites in small batches.

Set it up

  1. Register the site

    Add the site in Settings → Sites (or POST /v1/sites). You provide the root URL and a display name.
  2. Verify domain ownership

    Monitoring requires a verified domain. Add a DNS TXT record or a meta tag, then confirm — see the domain verification guide.
  3. Choose a cadence

    Pick weekly (Starter) or daily (Practice and above). Daily is worth it for sites whose marketing team ships frequently, where a tag manager can quietly add a pixel between releases.
  4. Tune alerts

    Decide which events notify you and where. Most teams start with new findings and cert-expiry alerts on, score-drop alerts on, and resolved-finding notifications off. See Guides → Configure alerts.

Authorization

By verifying a domain and enabling monitoring you represent that you’re authorized to request recurring scans of that site. Scans remain passive and limited to publicly accessible pages.