Skip to main content
Back to Solutions

Website Monitoring for Digital Agencies

You see each client's outages, expiring domains and broken pages in one dashboard, and walk into every check-in with a list of what to fix.

No credit card required·Every client site in one workspace

Uptime and incidents

The client should never be the one who tells you the site is down

When a client hears about an outage from their own customer, the next question is what the retainer pays for. Uptime monitors check each client site and the pages that matter most from multiple global locations, such as London and New York, with a check interval from 30 seconds to 24 hours, depending on your plan. Alerts reach your team by email, in Slack from Starter and through a webhook from Pro.

A blip at 3am should not wake the team. You can set a monitor to alert only after a number of failed checks in a row, and on paid plans a timeout or connection error is checked again from the monitor's other selected locations before an incident opens. On Starter and higher plans, each outage becomes an incident with its duration recorded, so you can tell the client how long it lasted. It closes on its own when the site answers again.

Simple arithmetic: 99.9% uptime still allows about 8 hours 46 minutes of downtime per site a year, so 40 client sites at 99.9% add up to about 350 hours somewhere in your portfolio. You can try your own numbers in the uptime calculator.

Incidents

Last 24 hours

  • acmecorp.com

    Uptime · Timeout · 4 min

    CriticalOngoing
  • api.techstart.io

    Uptime · Status code · 7 min

    CriticalResolved
  • shop.globalretail.com

    SSL · SSL check · 2 h

    HighResolved

Alerts sent by email and Slack

SSL and domains

Their domain, their registrar, your problem when it lapses

Certificates and domains often renew through the client's own hosting or registrar account, so a failed renewal usually reaches you only when the site breaks. A lapsed domain takes the site and the client's email down together, and an expired certificate puts a browser security warning in front of the client's brand.

Domain monitoring reads WHOIS or RDAP data every day and, by default, warns you 30 days before a domain expires. SSL monitoring checks the served certificate daily and warns 15 days ahead, raising the severity as the date gets closer. If a domain goes on registrar hold or slips past expiry into redemption or pending delete, WebPixie sends a Domain Suspended alert, so you can get the client on the phone with their registrar.

Expiration incidents

All client sites

  • financehub.net

    SSL certificate

    3 days

    Critical
  • edulearn.org

    Domain

    6 days

    Critical
  • shop.globalretail.com

    SSL certificate

    12 days

    Medium
  • acmecorp.com

    Domain

    24 days

    Medium

Keyword and status checks

The site is up, but the page shows a critical error

A PHP error page or a maintenance screen someone forgot to switch off still returns a page, so a check that only asks whether the server answers reports the site as up. An uptime monitor can require words that must appear on the page, such as the client's brand name or the "Add to cart" button, and words that must not appear, such as "critical error".

You can also list the status codes that count as up, choose whether redirects are followed, and add HTTP authentication to watch a password-protected staging site before launch. WebPixie looks for the words you set, so you can add the error messages your client's platform shows when something goes wrong.

Uptime monitor · shop.acmecorp.com

Check rules

Accepted status codes
200
Must contain
Add to cart
Must not contain
critical errorBriefly unavailable
Alert after
2 failed checks in a row

Last check · London

Status 200, page contains "critical error"

Down

Links and sitemaps

A client edit should not leave visitors on a 404

Clients rename pages and delete old products in their CMS, while the ads and emails that point to those pages keep sending visitors there. The Link Crawler starts at the homepage, follows internal links and checks each one up to your plan's link limit, then crawls again about once a week. Pages that return a 404 or a server error are listed with the pages that link to them, so you know what to fix and where.

On Starter and higher plans, Sitemap Monitoring reads the client's sitemap and flags crawled pages that are missing from it.

Links · globalretail.com

Crawled 2 days ago

412

OK

18

Redirect

6

Broken

Broken links

  • /summer-sale-2025on 3 pages404
  • /products/oak-lampon 1 page404
  • /blog/feedon 12 pages500

Search and AI crawlers

Still visible to Google, Bing, ChatGPT and Claude after launch?

A launch or a migration can carry the staging robots.txt into production, with a rule that tells every crawler to stay out. The Indexability Checker reads the client's robots.txt and llms.txt line by line. It shows which AI crawlers, such as GPTBot and ClaudeBot, have explicit rules, lists any Content-Signal directives, and tells you whether robots.txt points to the sitemap.

The Link Crawler marks crawled pages that robots.txt blocks, and on Starter and higher plans Sitemap Monitoring also flags pages the sitemap leaves out. On-page SEO checks and Lighthouse scores are coming soon.

robots.txt · edulearn.org

After launch

  • All crawlers

    Disallow: / left from staging

    Blocked
  • GPTBot

    No explicit rule

    Not set
  • Sitemap directive

    Not found in robots.txt

    Missing
  • Pages blocked by robots.txt

    Found by the Link Crawler

    38

    Review

Findings and Site Score

You walk into every check-in with a list of what to fix

Work the client cannot see is work they stop paying for. WebPixie reviews the security headers, SSL setup, DNS records including SPF and DMARC, and domain status of each client site. Every finding is ranked from Critical to Info and links to fix guidance, so each one is a task you can propose, and the WebPixie Site Score from 0 to 100 shows where the site stands today.

The same data gives you reasons to call: an expiry date coming up is a renewal conversation, and a recurring incident or a slower response time is a hosting conversation that helps you catch slowdowns before they become outages. For the monthly email, each uptime monitor shows its uptime rate, down count and response-time chart, and on Starter and higher plans the incident list shows what happened and how long it lasted.

Taking over a site from another developer? The findings, the broken-link list and the Certificates Manager, which lists certificates seen for the domain and its subdomains, show what was left behind in the first week.

Findings · globalretail.com

Site Score 71

  • No Strict-Transport-Security header

    Security headers

    High
  • Cookie set without the Secure flag

    Security headers

    High
  • No DMARC record

    DNS

    Medium
  • TLS 1.0 still accepted

    SSL

    Medium

Folders, tags and roles

Fifty client sites in one dashboard, sorted by client

You can put each client's sites in a folder, and tag sites and uptime monitors by client or contract. You can filter by a tag to see one client's monitors, or compare the Site Score of every site to see which client needs attention first. Plan limits apply per workspace, so one workspace on the right plan covers your whole client list.

You give each teammate the Owner, Admin or User role, and every configuration change is kept in an audit trail. On your plan's schedule, WebPixie emails the team a PDF digest of the workspace with the median Site Score, the top and bottom sites and the incidents of the period, which makes a good agenda for your internal review.

Roles apply to the whole workspace, so anyone who joins it sees every client's sites. A client who wants their own login needs a workspace that holds only their sites, on its own plan. The client can pay for it and invite your team, and you switch between workspaces from the same login.

Sites

Filtered by tagretainer

Acme Corp

  • acmecorp.comretainerScore92
  • shop.acmecorp.comretainerScore88

Global Retail

  • globalretail.comretainerScore71
  • shop.globalretail.comretainerecommerceScore64

You can set up your client portfolio

Three steps to bring your client list into WebPixie.

  1. 1

    You add client sites

    You enter each client domain and pick the checks that run on it, and monitoring begins right away. For a long list, you can add sites with the GraphQL API on the Starter plan and above.

  2. 2

    You sort them by client

    You create a folder for each client, then tag sites and uptime monitors by client or contract.

  3. 3

    You invite your team

    You add teammates with the role they need. Alerts go to every member by email by default, and to Slack from Starter.

Site, monitor and team limits apply per workspace. You can compare them on the pricing page. Moving a large client list from another tool? Talk to us and we will walk you through WebPixie.

Frequently Asked Questions

Common questions for agencies using WebPixie.

Yes. The simplest setup is to add every client site to a single workspace and organize it with folders and tags, so one dashboard covers your whole client list. Workspace management lets you put each client's sites in a folder and tag sites and uptime monitors by client, contract or project, then filter by a tag to focus on one client. For each site you choose which checks run, such as uptime, SSL, DNS, domain and link checks. Site and monitor limits apply per workspace and depend on the plan: Free (1 site), Starter (10 sites), Pro (50 sites), Enterprise (unlimited). A plan belongs to one workspace, so opening a separate workspace for every client means a separate subscription for each one. You can compare limits on the pricing page and see agency workflows under solutions for agencies.

The right plan depends on the number of client sites and uptime monitors you need in one workspace, because limits apply per workspace and the two are counted separately. Site limits are Free (1 site), Starter (10 sites), Pro (50 sites), Enterprise (unlimited), and uptime monitor limits are Free (3), Starter (20), Pro (50), Enterprise (unlimited). A site covers the daily checks for one domain, such as SSL, DNS, domain and link checks, while each uptime monitor watches one URL. A client whose homepage and checkout page you want to watch therefore uses one site and two monitors, so it helps to count monitors as well as sites when you size the plan. Incident tracking is included on the Starter, Pro, Enterprise plans, and check intervals, team seats, Slack and webhook alerts and the support level also change by plan. If you are moving a large client list from another tool, you can talk to us and we will walk you through WebPixie. The full breakdown is on the pricing page.

Yes, through a workspace that holds only that client's sites, because WebPixie roles apply to a whole workspace rather than to single sites. If you invite a client contact with the read-only User role to your shared agency workspace, they will see every site in it, including other clients' sites. Inside your agency, one workspace with a folder per client is enough, and nothing in it is visible to anyone outside your team. Once a client should log in, their sites belong in a separate workspace that runs on its own plan: either the client pays for it and invites your team as Admins, or you run it for them. Each plan has its own user limit, so it is worth checking that it leaves room for the client and your team. Inside that workspace the client can follow uptime, incidents, WebPixie Site Score and the periodic PDF report without changing any settings. You can see how roles work in workspace management and compare user limits per plan on the pricing page.

Your team shares one workspace, and each person gets the Owner, Admin or User role that fits their job. As workspace management describes, Owners control billing, membership and workspace settings, Admins manage sites, uptime monitors and incidents, and Users have read-only access. On paid plans, everyone sees the same incident during an outage, with its severity, affected resource and duration. Admins can add a note to it, such as what the host said or when the client was told, so whoever picks it up next has the context. Every configuration change is recorded in an audit trail. User limits depend on the plan, so you can compare team capacity on the pricing page.

You can bring each client the uptime rate, incident history and open findings of their own sites, while the automatic PDF report summarizes a whole workspace. For a monthly update, each uptime monitor shows its uptime rate, down count and response-time chart over a date range you pick, and on paid plans you can filter the incident list by site to show what happened and how long it lasted. The site's findings and WebPixie Site Score show what is still open. Each finding is ranked by severity and linked to fix guidance, so it can become a line in the client's maintenance plan, and domain and certificate expiry warnings arrive weeks before a renewal, which gives you a reason to call the client in time. The periodic PDF report is emailed to every member of a workspace and covers the median Site Score, the top and bottom sites and the incidents of the period. In a shared agency workspace it covers all of your clients, so it suits your team's own review; a client gets their own report from a workspace that holds only their sites. The schedule depends on the plan: Free: monthly; Starter: bi-weekly, monthly; Pro: weekly, monthly; Enterprise: weekly, bi-weekly, monthly. You can compare schedules on the pricing page.

No. WebPixie checks client sites from the outside with ordinary requests, so nothing is added to the site and there is no agent to install. Uptime monitoring sends a request per monitor at the interval you choose, and the daily checks fetch the homepage once along with certificate, DNS and registry data. The Link Crawler is the largest check: about once a week it requests the internal pages it finds, up to your plan's link limit per site, which is a light load for a typical site. You do not need hosting access or DNS changes to start. If a client's firewall blocks unknown traffic, you can set a custom User-Agent on each uptime monitor so its requests are easy to allow; this setting applies to uptime monitors only, not to the daily checks or the Link Crawler.

Everything you can monitor for a client

You can turn on the checks each client site needs.

Related Solutions

You can start with your first client site

Free plan, no credit card required. You can upgrade when you add more clients.