How to manage multiple client websites without losing track

To manage multiple client websites, keep one inventory of every site, put the accounts in your clients' names, watch every site from outside, review all of them for fifteen minutes each week and send each client a short monthly report. None of it needs a special tool to start. It needs one place where the facts live and a routine that does not depend on remembering.

This guide sets up that system step by step. It works for three sites and for thirty.

What does managing multiple client websites involve?

Four jobs, whatever the sites are built with:

1. Know what exists. Every domain, host, repository and renewal date, written down in one place.
2. Keep access clean. Clients own their accounts. You can get in without being the only one who can.
3. Notice problems first. Downtime, expiring certificates and domains, failed deploys and falling search traffic reach you before they reach the client.
4. Show the work. A short report tells each client what happened and what you did.

Most freelancers do the first job in their head and the third by luck. Fix those two and most emergencies disappear.

Step 1: Build one inventory of every client site

Make one row per site, not per client. A client with a shop and a blog has two rows.

A spreadsheet is fine. What matters is that it is the only list and that you update it the day something changes.

Step 2: Put accounts in the client's name, access in yours

• Domain and hosting belong to the client. Use their name and their payment method, and add yourself as a user or through delegated access. You avoid paying for their renewals and they avoid being locked out if you disappear.
• Use a role address for renewal notices. Send registrar and certificate emails to a shared address on your own domain, such as a sites mailbox, or to the client and you together. A personal or former address is how renewal notices get lost.
• Keep credentials in a password manager. One shared vault per client, with recovery codes and the owner of each two-factor login noted.
• Write down who to call. The registrar, the host and the client's IT contact, if they have one, belong in the inventory row.

Step 3: Watch every site from outside

Monitoring from outside your network is the only way to hear about a problem before the client does.

• Uptime. Check each site every one to five minutes and confirm the failure with a second check before alerting. Our guide to setting up uptime monitoring for client websites covers checks, intervals and alert routing.
• Renewals. Warn at 60 and 30 days before a domain expires. For certificates, alert a week before the date and again in the last few days, because a certificate that close to expiry usually means automatic renewal already failed. The expiry tracking guide has a one-line check for each.
• Deploys. Send failed builds from your host or CI to one channel you read. A failed deploy often looks like nothing at all, because the old version keeps running.
• Search. Look at clicks and impressions per property once a week. Search Console shows one property at a time, so see how to view all your Search Console sites in one place.

Step 4: Run a fifteen-minute weekly review

Pick a fixed slot, such as Monday morning, and go through every site in the same order.

1. Anything down, degraded or failing its checks. Fix it or tell the client today.
2. Any certificate or domain due in the next 60 days, and any date you could not read.
3. Any deploy that failed since last week, and whether the live version is the one you expect.
4. Any search drop you cannot explain, compared with the week before.
5. Update the "Last reviewed" date in the inventory.

If a site has nothing to report, it takes seconds. The review is what turns monitoring into action.

Step 5: Report to each client once a month

A short note does more for retention than a long one. Include uptime for the month, any incident and what you did about it, renewals coming up, search clicks and impressions against the previous month, and the work you did. The website maintenance plan guide has a report template. If a site went down, use the client downtime message templates for the first message.

How do you know the system has stopped working?

• You hear about an outage from a client.
• A renewal surprises you or the client.
• You cannot say, in a minute, which sites need attention this week.
• You cannot say what a client's sites cost you and whether they pay for themselves.

When that happens, the inventory and the monitoring are spread across too many tools to review in fifteen minutes. That is the point where one dashboard for all client sites starts to pay off.

Where Datumboard fits

Datumboard is being built to hold this whole system in one place: a project per client site, with uptime, SSL and domain renewals, deploys, Search Console, Lighthouse and costs side by side, sorted by what needs attention. It reads what it can from GitHub, Netlify, Vercel and Search Console, and you add the rest by hand. It is in early access, and you can join the list below.