For agencies
Stop hearing about broken client sites from your clients
You can't open every client site every hour — so too often a client is the one who spots the broken page. Sitewatch checks every site the way their visitors do, alerts you the moment one breaks, and sends the client a report with your branding on it. You make the call, instead of taking it.
- Up to 100 client sites and 25 critical pages each on Pro
- Group by client, filter in one click, see who needs you first on Monday
- Branded reports and incident summaries generated for you, not by you
- Incidents ranked by what they cost the client, not by technical severity
A client site broke after a deploy
Plain-English summary
The checkout page is asking for a script that is no longer being served, so customers cannot pay. The site itself loads perfectly.
Free scan
Scan a client site right now — free
Their uptime tool says the site is fine. See what their visitors actually get: missing scripts, broken styling, dead links and more. No signup.
02What can go wrong
The call you don't want on a Monday.
It is almost never your fault. It is almost always your problem — because the client's experience is that they found it and you did not.
- 01You are looking after thirty client sites, each on its own stack and its own update schedule.
- 02One of them ships a deploy, or a plugin updates itself overnight.
- 03Every site still answers, so the uptime tool on your dashboard stays entirely green.
- 04A client's checkout has been broken since Friday and their customers found it before anyone else did.
- The phone call starts with "why didn't you know?"
03Why traditional monitoring misses this
Your uptime dashboard is green because it is answering the wrong question.
Ping-based monitoring asks whether the server responded. We don't just check that a client site is online — we check that their visitors can actually use it.
Traditional uptime monitoring
Thirty green dots that only rule out one kind of failure.
Sitewatch
Green means the client's site actually works.
04How Sitewatch catches it
One question, on every check, on every client site.
Not "did the server respond?" — but the one your client will judge the retainer on: can their visitors actually use this site today?
- ✓The layout loads
- ✓Scripts load
- ✓Forms still work
- ✓Images appear
- ✓Links still resolve
- ✓Checkout pages load
- ✓Certificates are valid
- ✓Domains are not about to expire
05Typical failures we catch
The client-site breakage that becomes your problem.
A client's checkout stopped taking payments
A deploy or plugin update leaves the payment script unserved.
→Their revenue stops and the conversation starts badly
A contact form stopped submitting
The script behind it went missing after an update.
→Enquiries vanish for weeks before anyone notices
A site is rendering unstyled
A stylesheet is missing or being served as an error page.
→The client screenshots it and asks what happened
A certificate expired
A renewal you set up two years ago quietly stopped working.
→Browsers block the site entirely — the most preventable outage there is
A domain is about to lapse
Nobody owns the renewal because nobody remembers it exists.
→You lose the domain and the recovery is expensive and public
Links across the site stopped resolving
A content change or restructure leaves internal links pointing nowhere.
→Search rankings slip and the client asks why traffic is down
A third-party widget went quiet
Booking, chat or reviews stops loading from someone else's infrastructure.
→The feature the client cares most about silently stops
A page has quietly doubled in weight
Plugins and scripts accumulate on a site nobody is watching.
→The site gets slower every month and you find out at review time
A site is genuinely down
The fundamentals still matter, and they are covered too.
→Confirmed and alerted before the client refreshes their phone
06A real example
A broken client checkout, caught before the client called.
Their deploy ships
A client's developer pushes a change on a Friday.
Checkout breaks
A script the payment form needs is no longer served.
Incident opened
Sitewatch confirms it and ranks it by what it costs.
Your team is alerted
In Slack, tagged to that client, with the file named.
You call them
With a branded report attached, before they call you.
07Fits your workflow
Running in under five minutes
- 01
Sign up in under a minute
Email or GitHub. The free plan monitors one site with no credit card, which is enough to test it on the client you would least like to lose.
- 02
Add your client URLs
Paste the URLs and the first check runs immediately. Nothing is installed on the client's site, so you do not need hosting access or their developer's cooperation.
- 03
Point alerts at your team
Six channels including Slack, email and PagerDuty, routed per site. Issues are confirmed before alerting and repeats are suppressed, so a portfolio does not become a firehose.
- 04
Use maintenance mode for planned work
Deploying a client site? Pause that site's monitoring for the window and switch it back on in one click when you are done.
08What happens the moment we find it
Detection is not the outcome. The client conversation is.
Every incident arrives client-ready, which is the difference between an alert and something you can bill against.
We confirm it is real first
Every issue is re-checked before anyone is alerted, and repeat alerts for the same problem are suppressed — so thirty sites do not produce thirty channels of noise.
Written for the client, not just the developer
"The checkout page cannot load its payment script, so customers cannot pay." Forwardable as-is, with the technical detail underneath it.
Ranked by what it costs them
A broken checkout and a missing blog footer are not the same incident. Severity reflects business impact so you triage across clients correctly.
A branded report on resolve
When the incident closes, the client gets a report with your logo on it — evidence of the work, generated without anyone writing it.
09What you get
Built for a portfolio, not a single site
One view across every client
Thirty sites on thirty stacks, in one dashboard, with per-client health at a glance. Broken deploys stop going unnoticed for days because nobody owned the checking.
Beyond the uptime ping →
Your current tool says every client site is up. Meanwhile a script is missing on a checkout page and a redirect loop has killed a blog. Sitewatch checks what actually loads.
Everything each page loads, verified →
Every script, stylesheet, image and font the page references is fetched and checked. When a deploy or a CDN breaks one, you get the exact file rather than a guess.
Organised by client →
Tag sites by client, project or environment. Filter in one click and see per-client health without maintaining a spreadsheet alongside it.
Your brand, not ours →
Your logo, colours and company name on every report and alert. On Pro you can remove the Sitewatch badge entirely.
Reports that write themselves →
Branded health summaries, monthly on every plan and weekly on Pro, emailed to your clients with a shareable link. The reporting you keep meaning to systematise.
One digest across the whole portfolio →
A weekly roll-up of your worst performers, open incidents, and upcoming certificate and domain expiries. You walk into Monday knowing which client needs you first.
Incident reports on resolve →
When something closes, the client gets a written record of what happened and what was fixed — in client language or technical detail, whichever fits.
Severity that reflects the client →
A broken checkout outranks a missing footer image. Triage across a portfolio only works if the ranking means something.
Dead links caught too →
Links that go nowhere hurt rankings and break journeys. Every check covers them, with the link text and the page it sits on.
Checked from outside their network →
Failures in a CDN, a DNS record or a third-party vendor are invisible from inside. Sitewatch checks the way a visitor arrives.
10Everything we detect
What Sitewatch checks across your client sites
The pages and what they load
- Missing scripts, stylesheets, images and fonts
- Files served as the wrong kind of file, so the browser refuses them
- Unexpected content changes against the page's baseline
- Pages returning something other than a web page
Hosting and routing
- Redirect loops that leave visitors on a dead end
- A domain resolving to a server you did not expect
- Hard outages, timeouts and server errors
- Certificate expiry and domain expiry, with early warning
Weight and dependencies
- Pages that have grown past sensible download limits
- Pages loading an excessive number of separate files
- A CDN, font host or analytics vendor going dark across every site that uses it
- Response times drifting well above the site's own normal
Links and SEO
- Internal links pointing at pages that no longer exist
- Outbound links to sites that have moved or gone
- Evidence with each one: the address, the link text and where it sits
- Fix steps tailored to WordPress, Next.js, Nuxt, Shopify and more
11vs. your uptime tool
Your clients find the bugs before you do. That ends now.
| Scenario | Generic uptime tools | Sitewatch |
|---|---|---|
| The dashboard | A list of sites, up or down | Every client site with the detail underneath |
| What gets checked | Nothing beyond the server answering | Every script, stylesheet, image and font |
| What the incident says | "Site went down at 3:42 PM" | Which page, which file, what a visitor would hit |
| Alerts | An email saying the site is down | Six channels, with evidence, deduplicated |
| Planned deploys | Mute everything and hope | Per-site maintenance mode, one click back on |
| Client organisation | A flat list of URLs | Tags, filters and per-client health |
| Report branding | The vendor's logo | Yours, on every report and alert |
| Client reporting | You build it manually each month | Generated and sent automatically |
| Portfolio roll-up | Open each site and look | One weekly digest, ranked worst first |
| Dead links | A separate tool and a separate bill | Checked on every run |
| Page weight drift | Not watched | Tracked every check, with thresholds |
| Third-party vendors | Not watched | Per-domain outage detection across all sites |
| Certificates and domains | A calendar reminder someone will move | Tracked per site, warned early |
| Pricing at agency scale | Per-seat pricing that adds up fast | $19/mo for up to 100 sites ($190/yr annual) |
The dashboard
- Generic uptime tools:
- A list of sites, up or down
- Sitewatch:
- Every client site with the detail underneath
What gets checked
- Generic uptime tools:
- Nothing beyond the server answering
- Sitewatch:
- Every script, stylesheet, image and font
What the incident says
- Generic uptime tools:
- "Site went down at 3:42 PM"
- Sitewatch:
- Which page, which file, what a visitor would hit
Alerts
- Generic uptime tools:
- An email saying the site is down
- Sitewatch:
- Six channels, with evidence, deduplicated
Planned deploys
- Generic uptime tools:
- Mute everything and hope
- Sitewatch:
- Per-site maintenance mode, one click back on
Client organisation
- Generic uptime tools:
- A flat list of URLs
- Sitewatch:
- Tags, filters and per-client health
Report branding
- Generic uptime tools:
- The vendor's logo
- Sitewatch:
- Yours, on every report and alert
Client reporting
- Generic uptime tools:
- You build it manually each month
- Sitewatch:
- Generated and sent automatically
Portfolio roll-up
- Generic uptime tools:
- Open each site and look
- Sitewatch:
- One weekly digest, ranked worst first
Dead links
- Generic uptime tools:
- A separate tool and a separate bill
- Sitewatch:
- Checked on every run
Page weight drift
- Generic uptime tools:
- Not watched
- Sitewatch:
- Tracked every check, with thresholds
Third-party vendors
- Generic uptime tools:
- Not watched
- Sitewatch:
- Per-domain outage detection across all sites
Certificates and domains
- Generic uptime tools:
- A calendar reminder someone will move
- Sitewatch:
- Tracked per site, warned early
Pricing at agency scale
- Generic uptime tools:
- Per-seat pricing that adds up fast
- Sitewatch:
- $19/mo for up to 100 sites ($190/yr annual)
12Which do you actually need
Where Sitewatch fits in an agency stack.
Most agencies already run three or four tools. This is where each one is genuinely the right answer.
What you need
What to use
This probably isn't for you if…
- You build sites and hand them over with no ongoing relationship — there is no reputation exposure to cover.
- You need backups, updates or security cleanup. Those are a different category of tool entirely.
- You want per-client billing and time tracking. Sitewatch reports on site health, not on your commercials.
100
Sites on the Pro plan
$19/mo
For the whole portfolio
90 days
Data retention on Pro
Your clients deserve better than "we didn't know"
Free plan monitors 1 site. Pro covers 100 sites at $19/month ($190/yr annual).
13Questions
Agency questions, answered
One on Free with 7 days of history, 25 on Starter with 30 days, and up to 100 on Pro at $19/month with 90 days. Annual billing saves two months — Starter $90/yr, Pro $190/yr. There is no per-seat pricing, so the whole team works from the same account.
That is the failure mode we designed against. Every issue is confirmed with a retry before it alerts, repeat alerts for the same problem are suppressed for a cooldown period, and incidents are ranked by business impact so a broken checkout does not arrive alongside a missing footer image with equal weight. Alerts route per site, so client work can go to the channel that owns it.
Yes, and this is one of the strongest reasons agencies use it. When an incident resolves, Sitewatch can generate a branded report — in client language or with the technical detail — and send it with your logo on it. Clients also get a status page they can check themselves, which quietly removes a category of email.
No. Everything happens from outside, the way a visitor arrives, so there is nothing to install and nothing to ask their developer for. In practice this means you can monitor a site you have inherited, or one where another agency still has the keys.
Yes. Pause a site's monitoring while you deploy so planned work does not generate incidents, and switch it back on in one click. It is per site, so the rest of the portfolio keeps running.
Those tools check whether the server responded, and they do it well. They will not tell you that a client's checkout script is missing, that a stylesheet is being served as an error page, or that a form has stopped collecting leads — because on all of those, the server responded perfectly. Many agencies keep their ping tool and add Sitewatch for the layer above it.
Every 30 minutes on Free, every 15 on Starter and every 5 on Pro, configurable per site. You can also run a check on demand from the dashboard or trigger one from a deploy hook — which is the single most useful moment to check a client site.
Tag sites with whatever labels match how you actually work — a client name, a project, an environment. Filter the dashboard by tag in one click and see per-client health. Bulk tagging makes onboarding a new client fast. Available on every plan.
Yes. Add your logo, colours and company name in workspace settings and every report, alert and shared link uses them. On Pro you can remove the "Powered by Sitewatch" badge entirely.
Yes, up to 50 links per page, internal and external. Each broken link becomes an incident with the address, the link text, what came back, and fix steps tailored to the platform — WordPress, Next.js, Shopify and others.
14Explore more
Live monitoring
Sitewatch is watching these sites right now
Real sites we check every few minutes for the failures uptime tools miss — the pages that stay “up” while something quietly breaks.