D3bris Website monitoring for agencies: watch every client site in one place
How agencies monitor many client websites reliably: what to check, how alerts work without false-alarm floods, and which parts D3bris takes care of.
If you look after ten, thirty or seventy client websites, you can’t open every page every day. Clients still expect their agency to notice first when something is wrong – not themselves, and certainly not their own customers. Website monitoring closes exactly that gap: a service requests the websites at fixed intervals and tells you when a check fails.
What agencies need that a single site owner doesn’t
A company with one website mostly needs one answer: is my site up? Agencies need more:
- Mapping to clients. “example.com is unreachable” is of little help if someone first has to look up which client it belongs to and who looks after them.
- More than the homepage. For practices, law firms or tradespeople, business depends on the contact, booking or quote page. The homepage can load while exactly those pages are broken.
- Calm across many sites. With 50 websites, even a few false alarms a week mean that alerts eventually go unread.
- A predictable price. Monitoring is often part of a maintenance retainer. Its cost should be easy to include per website, not per individual check.
Which checks make sense
| Check | Answers the question | Typical cause of failures |
|---|---|---|
| Availability (HTTP) | Does the server respond with a successful status code? | Server outage, hosting incident, broken update, DNS change |
| TLS certificate | Is the certificate valid and does it match the domain? | Failed renewal, domain move, misconfiguration |
| Key subpages | Do contact, booking or shop pages work? | Plugin or theme update, deleted page, template error |
| Expected text | Is the essential content still on the page? | Button or form gone after an update |
All of these run from the outside and need no access to the client’s system. How they differ from checks that submit forms or play through whole journeys in a browser is explained in the guide uptime monitoring vs. functional checks.
How D3bris does it
- Grouped by client. You create clients and assign websites to them. The overview shows the worst state of each website’s pages.
- Up to three pages per website. The homepage plus two more pages on the same domain, each optionally with a text that must appear in the HTML.
- Every 5 minutes. If a check fails, D3bris checks again after one minute. Only the second failure counts as an outage.
- One email per event. One message with the cause when an outage is confirmed, a second one with the duration when it recovers. No repeats in between.
- Certificate warnings. 14 days before a certificate expires, and immediately if it is invalid or doesn’t match the domain. More on the TLS monitoring page.
- No plugin. Works the same for WordPress, TYPO3, Shopware, Webflow or static sites. See WordPress monitoring without a plugin.
Where the limits are
D3bris checks from one server in the EU. Regional problems, for example with a single internet provider, may not be visible to us. Outages shorter than one check interval can go unnoticed. Forms are not submitted, JavaScript-generated content is not evaluated, and pages behind a login are not checked. Notifications are sent by email; there are no SMS or chat integrations at the moment.
For many agencies that is exactly the right scope: catch the most common and most expensive problems early without maintaining yet another tool. If you need to test payment flows end to end, you’ll need a synthetic browser-testing tool in addition.
Get started in five minutes
- Sign in with your email address – no password, no payment details.
- Create your first clients and add each client’s website.
- For important clients, add the contact or booking page as an extra page.
Which pages and settings work well is covered in our checklist for agencies.