A Shareable Status Page for Your Client Sites
A shareable status page for your client sites is a single link a client can open to see whether their website is up right now and how it has behaved recently. They get the answer without emailing you, and you skip the ten minutes it usually takes to prove that the site was fine all along.
Almost every agency knows the message. It arrives on a Tuesday morning, says "is the site down?", and in most cases the site isn't down at all. The client's office Wi-Fi dropped, a browser served a cached error, or someone mistyped the domain. You still have to open a browser, check, reply, and reassure. A status page lets the client do that check themselves.
Status page or dashboard?
The two get confused, and mixing them up is the most common way a status page goes wrong.
A dashboard is for your team. It holds everything: canonical diffs, noindex detections, sitemap URLs added or removed, tag changes, expiry dates. A status page is for someone who doesn't know what a canonical is and shouldn't need to. It answers one question in plain words: is my site working, and has it been working?
If you put SEO findings on a client-facing page, two things happen. The client sees a "canonical changed" line they can't interpret and asks you about it, which defeats the purpose. And you lose control over how problems are explained, because the client reads the raw event before you've had a chance to look at it.
What belongs on the page
Three pieces of information are enough for most clients:
- The current state, in words anyone understands (online or offline).
- Uptime over a recent period, so a single bad hour is visible in context.
- Some indication of response behaviour, because a site that takes eight seconds to load feels broken to a customer even if it technically responds.
Leave off internal alert history, SEO scan results, and anything that needs a sentence of explanation. If a figure would prompt a "what does this mean?" email, it belongs in your monthly report instead, where you can add the context yourself. Our guide to website monitoring in client reports covers that side.
Where the link does its work
The status page is only useful if the client remembers it exists. A few places make that likely.
Put it in the onboarding email, right next to the login details and support contact, so it's part of the handover rather than an afterthought. Add it to the footer of every monthly report beside the uptime figure. And when a worried message does come in, reply with the link first. After two or three of those replies, most clients start checking the page before they write.
There's also a quieter benefit during real incidents. When a site genuinely goes offline, you and the client are looking at the same source. Nobody argues over whether the outage happened or how long it lasted, and the conversation moves straight to what caused it.
For agencies that sell monitoring as part of a branded service, the status page fits alongside a white-label monitoring setup. It's the one piece of that setup the client actually touches.
What a status page can't tell the client
A green status page means the server answered. It says nothing about whether Google can still index the site. A theme update can add <meta name="robots" content="noindex"> to every template while the homepage loads perfectly, and the status page will stay green the whole time. The same goes for a GA4 tag that disappeared or a sitemap that lost half its URLs.
That's why the status page shouldn't be the only monitoring you run. It covers availability for the client's peace of mind. The checks that protect traffic sit behind it, and we explain how the two layers fit together in uptime and SEO monitoring.
Status pages in Deltio
Every site you add to Deltio gets a status page you can share by link, showing uptime and the site's current state. The same site is also checked on a daily cycle for noindex, robots.txt, canonicals, titles, sitemap URLs, SSL and domain expiry, and marketing tags, with alerts going to your team by Slack or email rather than to the client. So the client sees availability, and your team sees everything else.
If you want to try it with one client, the 14-day trial gives a site enough time to build a few days of uptime history before you send the link.
Frequently asked questions
- Should the status page use my agency's domain or branding?
- It helps if the page looks like part of your service, but the content matters more than the wrapper. A client who bookmarks the link and checks it before emailing you gets the value either way. If branding is important to your positioning, handle it in the onboarding email and reports that point to the page.
- Does a status page replace downtime alerts to my team?
- No. A status page is passive: someone has to open it. Your team still needs alerts by Slack or email when a site goes offline, so you're working on the problem before the client thinks to look.
- Should I share the status page before a site has any uptime history?
- It's better to wait a few days. A page with a single data point looks empty and invites questions. Once there's a short run of history, the uptime figure has some meaning and the page reassures rather than confuses.
- What should I do if the status page shows an outage the client already saw?
- Acknowledge it with the same data they're looking at: when it started, when it recovered, and what caused it once you know. Because you're both reading the same source, you skip the debate about whether it happened and go straight to the explanation.
- How much does Deltio cost?
- Starter covers up to 50 sites for £24 / €29 / $31 a month, or £20 / €24 / $26 a month billed annually. Professional (up to 200 sites) is £49 / €59 / $64 a month and Enterprise (up to 500 sites) is £119 / €139 / $149 a month, with lower annual rates. Every plan has a 14-day free trial.