Monitoring your sites
SiteOps checks your site the way a customer would - in a real browser, on a schedule - and records what it finds.
Two ways to set it up
You can configure monitoring however you prefer - both do the same thing:
- Ask the AI (fastest) - e.g.
start monitoring example.comorchange my check frequency to 5 minutes. It drafts/previews the change and applies it on your confirmation. - Use the Settings page (manual, full control) - go to Settings in the sidebar and set each option by hand. See Configure in Settings below and UI elements.
The dashboard is where you then view everything and your usage - see UI elements.
Sites
A site is a URL you want watched. Each site has its own settings:
- Uptime check frequency - how often SiteOps runs the fast heartbeat (e.g. every 5 / 15 minutes). Faster intervals are available on higher plans.
- Failures before alert - how many consecutive failures before an incident/alert fires (avoids flapping).
- Alert cooldown - minimum time between repeat alerts.
- Business hours - optionally only check/alert during hours you choose.
- Paused - temporarily stop checks without deleting the site.
Add a site by asking the AI (start monitoring example.com) or with the Add site button on the dashboard.
User journeys
A user journey is the real flow that matters - checkout, login, signup, contact form. You describe it in plain English and the AI builds it from the real buttons and fields on your site, then SiteOps replays it step-by-step in a real browser with assertions, flagging the exact step that broke, with a screenshot. This is the difference between "the homepage responded" and "customers can actually check out."
Journeys run automatically on a schedule set by your plan - roughly every 12h on Free, 30 min on Starter, 15 min on Pro, and as fast as 5 min on Agency. Faster journey checks are the main reason to upgrade. Your plan also sets how many journeys you can save (1 on Free up to 25 on Agency).
Journeys can sign in behind a login, stop safely before payment, self-heal when a button is renamed, and be suggested for you automatically. See the full guide: User journeys.
Site health scans
Beyond your journeys, a site health scan crawls the pages you mapped (your scan map) and checks that each one loads with real content, no broken links, errors, or missing elements. Site health scan modes:
| Mode | Meaning |
|---|---|
off |
No site health scans |
weekly |
A site health scan once a week |
daily |
Once a day |
interval |
Every N minutes (higher plans) |
Set it when you create a site, change it any time (change my site health scan to daily → preview → confirm), or leave the AI's drafted default. Your plan sets how many site health scans you get per month (3 on Free up to 360 on Agency).
On-demand checks
Don't want to wait for the schedule? Run one now:
- Ask the AI:
run a check on my site now - It queues a real scan; results appear on the dashboard and as an incident if something's wrong.
On-demand checks are rate-limited so they can't be spammed, and they count toward your monitoring usage.
Configure in Settings (manual)
Prefer to set things by hand? Open Settings in the sidebar. The SiteOps settings screen gives you full control, section by section:
| Settings section | What you set |
|---|---|
| Active Site | Which site these settings apply to (switch between your sites) |
| Monitoring | Turn monitoring on/off, pause/resume |
| Uptime Checks | Check frequency, failures-before-alert, alert cooldown, business hours |
| Site Health Scan Configuration | Site health scan mode (off / weekly / daily / interval) and interval |
| Scheduled Site Health Scans | When site health scans run (time / day) |
| Notifications | Email, Slack, Discord, weekly report - see Alerts |
| Public status page | Enable and name your public status page |
| Scan Map / Excluded Actions | Click Map my site to build the scan map, then fine-tune which pages/actions are scanned |
Every value here is the same one the AI edits when you ask it - use whichever you like. Values are clamped to your plan's limits (e.g. minimum check interval).
What a check records
Every run stores:
- Result - healthy / warning / critical, and the failing step if any
- Response time and HTTP status
- Screenshot evidence (for journeys and site health scans)
- Uptime and success rate over your chosen window
SSL & domain expiry
SiteOps also watches your TLS certificate and domain registration and warns you before they expire - a silent killer that plain uptime checks miss. Ask when does my SSL expire? any time, or let the daily sweep alert you. See Alerts, SSL & status page.
Next: what happens when something breaks - Incidents & AI fixes.