Blog / Web management /

Why I keep a site register for every client

A domain renewal email lands while the one person who knows the setup is away. Nobody is sure which registrar account owns the domain. The site is still online, but a small admin gap has just become urgent.

A site register exists to stop that kind of knowledge living in one person’s head.

I keep one for every client website, because managing several sites means switching between different platforms, owners and setups all day. A short record gives me somewhere to check the basics before I change anything. It isn’t a password spreadsheet or a replacement for proper documentation. It’s an index of the people, systems and decisions that keep a site running.

Key takeaways

  • Keep a current register of each site’s platform, owner, hosting and critical services.
  • Store passwords and secrets in a password manager, not in the register.
  • Record renewal dates, support contacts and the reason for unusual settings.
  • Review the register when access, hosting or the site itself changes.

Start with what someone needs to know

The first fields should answer basic questions: what is the site, who owns it, who approves changes and what platform runs it? Include the primary domain and any important alternate versions. Record the platform and relevant theme or hosting arrangement at a useful level of detail.

The register should tell a new maintainer where to look. It shouldn’t hold every configuration value. Record the registrar and account owner, for example, but keep the credentials in the password manager. Note where DNS is managed, and never paste private keys or recovery codes into a shared spreadsheet.

Include the main business contact and technical contacts, with a note about who should be contacted for an outage, a content change or a billing question. A generic email address can be more reliable than a person’s name when staff changes, but confirm that someone monitors it.

Track renewals and critical dependencies

Domain renewals, hosting contract dates, SSL responsibility and backup arrangements only matter when someone misses them. Record where each service is managed, who gets the renewal notices and how renewal works. Don’t assume the person who built the site still owns the account.

List key dependencies such as DNS provider, hosting, CDN, email, analytics, Search Console and payment integrations where relevant. For each, identify the owner and where an authorised person can find access. The register should reveal dependencies, not expose sensitive information.

If the site has a custom setup, note it in plain language and point to the detailed documentation. “Checkout relies on app X” is more useful than a long undocumented configuration copied into a cell. Keep the main register scannable and link to deeper records when needed.

Separate access from secrets

A spreadsheet is convenient, but it isn’t a password manager. Keep passwords, API keys, security questions and recovery codes out of the register. Use a password manager with appropriate sharing and access controls, and grant named accounts where the platform allows them.

Record who has access and what role they hold, then review it when a person leaves or responsibilities change. Remove access that is no longer needed. Two-factor authentication should be used where available, especially for domain, hosting and administrator accounts.

Keep ownership with the client. I’m happy to work with the access I need, but the owner should keep control of the domain, hosting and platform accounts. It makes future handovers cleaner and stops a site being stranded when a working relationship ends.

Make the register useful during an incident

A site register is most valuable when something is wrong. If a page is down, it should help identify the host and support contact. If the site redirects unexpectedly, it should show where DNS is managed and who can review it. If a renewal is due, the owner and process should already be known.

Include a link to the maintenance log or change record. When troubleshooting, the team should be able to see what changed recently without relying on memory. The register itself should not become a detailed incident report; point to the correct record.

Write notes so someone else can understand them, not in shorthand only you follow. A note such as “custom DNS record supports email verification; check with owner before removal” is safer than “leave weird TXT”.

Protect and maintain the document

Limit access to people who need the information. Even without passwords, a register can reveal infrastructure and business contacts. Keep it in an approved location, use sensible permissions and have a backup or version history.

Choose an owner for the register and a review rhythm. Update it when a domain, host, platform, key contact or access role changes. A quarterly review can help, but the important part is updating it as changes happen rather than waiting for the calendar reminder.

If you inherit a site with no documentation, fill in what you can verify and mark the gaps. Don’t guess the registrar, and don’t assume a backup plugin is set up properly. Confirm with the owner and test the important processes.

Keep it short enough to use

A register should help someone take the next step quickly. Start with the fields that prevent outages, ownership confusion and risky changes, and add detail only when a real need appears. If nobody can find or understand the document, a perfect structure won’t matter.

What’s the one site detail your team would struggle to find during an outage?