Website Reliability Planning: Mapping Who Holds the Keys to Your Site
Most small business websites do not fail because of dramatic technical collapses. They stall because a single person holds the login for the domain, nobody remembers which company hosts the files, or a renewal notice goes to an inbox nobody checks. Reliability planning starts before anything breaks, with a clear picture of who controls each part of your web presence and how you would reach them under pressure. This article walks through the questions to answer now, so that a future outage becomes a routine task instead of a scramble.
Start with an inventory of every account
Your website is not one thing. It is a collection of accounts: the domain registration, the DNS settings that point the domain to a server, the hosting or platform account that serves pages, the email service, any form tools, analytics, and the payment processor if you sell online. Each account has an owner, a login, a billing method, and a renewal date. Write them all down in one place. A spreadsheet works well if it is stored somewhere the business can reach without relying on one employee's personal device.
For each account, record the registered email address, the name of the person who created it, the payment method on file, and whether two-factor authentication is enabled and where the second factor lives. Many small businesses discover during an emergency that the recovery code was printed once and thrown away, or that the phone number on the account belongs to a former employee. A complete inventory exposes these gaps while there is time to fix them.
Separate the domain from the website
A common source of confusion is treating the domain name and the website hosting as the same contract. They are often managed by different companies and renewed on different schedules. If the domain lapses, your business can lose its address even though the site files still exist. If the hosting lapses, the domain still resolves but shows nothing useful. Both are avoidable with a short list of questions: Who is the registrar? When does the domain expire? Who receives renewal reminders? Where is the DNS managed, and can more than one trusted person log in to it?
Ask whether the registration is set to renew automatically and whether the payment method attached to it is current. Confirm that the reminder emails go to a shared business address, not only to an individual. Treat the domain as a business asset that outlives any single vendor relationship.
Write down your recovery contacts
When a site goes down, the first question is not technical. It is who can act. Build a short contact sheet listing each service provider, the support channel they use, the account identifier they will ask for, and the hours they staff. Include a named internal person for each category: someone who can approve spending, someone who can verify identity with a vendor, and someone who can reach a developer or outside helper if needed.
Ask every provider what their verification process looks like. Some require the account holder to confirm identity before any change is made, which protects you but slows emergency work. Knowing this in advance lets you designate a backup contact and set up authorization early, rather than discovering the requirement at 9 a.m. while customers are trying to order.
Define what 'down' means for your business
Reliability planning benefits from plain definitions. A site returning an error page is different from a site loading slowly, a contact form failing silently, or checkout breaking only for mobile visitors. Decide which failures matter most and how you would notice them. Ask whether anyone currently receives an alert when the site is unreachable, or whether you learn about outages from customers. If you have no alerting in place, that is a question to put to your provider directly rather than assuming one exists.
Also decide how long an outage is tolerable for each function. A brochure page being offline for an afternoon may be an inconvenience. A booking form being offline during a busy week may cost real business. These judgments are yours to make, and writing them down helps you prioritize when several things go wrong together.
A practical checklist before your next renewal cycle
Work through these items once and repeat them each year. Confirm the registrar, the expiration date, and the auto-renew setting for your domain. Verify that at least two trusted people can log in to DNS and hosting accounts. List the email address and phone number tied to each account, and update any that belong to people who have left. Store recovery codes in a shared, secure location that the owner controls. Check that payment methods on every service are current. Note the support hours and verification steps for each provider. Finally, run a short tabletop exercise: pick a hypothetical outage and walk through who you would call, in what order, and what information you would need to hand over.
The goal is not to predict every failure. It is to make sure that when something does go wrong, your business is answering a known set of questions rather than searching for passwords, old invoices, and the one person who remembers how the site was built. Clear ownership and written contacts turn a crisis into a checklist.