Why a website needs care
A website is not a printed brochure. It runs on a server, uses code libraries and sometimes plugins, connects to email services, forms, maps and analytics, and sits behind a domain name and a security certificate. Each of these pieces changes or expires on its own schedule. When nobody is watching them, the site keeps working until one day it does not, and you often learn about it from a customer.
Updates
Frameworks, libraries, content management systems and plugins release updates regularly, many of them for security. Skipping them leaves known weaknesses open. Applying them carelessly can break a page or a form. Good care means updating on a regular schedule, testing the important pages and forms afterwards, and keeping a way to go back if something goes wrong.
Updates also concern what sits around the site: the server, the database and the version of the programming language the hosting runs. Hosting providers retire old versions on their own timetable, and a site that was never updated can stop working on the day they do.
Backups you can actually restore
A backup is only useful if it can be restored. Ask how often the site and its data are backed up, where the copies are kept (ideally away from the main server), how long they are kept, and when a restore was last tested. For a site with bookings, orders or an account area, daily backups are a reasonable starting point.
Certificate and domain renewals
Two renewals can take a site offline overnight. The security certificate, which gives you the padlock and HTTPS, has to be renewed regularly; on most modern hosting this is automatic, but automatic renewals sometimes fail. The domain name has to be renewed too, usually every year. If the renewal email goes to someone who has left, or the card on file has expired, the domain lapses and the site and email stop working.
Keep a list of both renewal dates, make sure the reminders reach someone who will act, and keep the domain in your company's name.
Most website outages are not dramatic attacks. They are a forgotten renewal, a failed update or a full disk.
Uptime monitoring
Monitoring means a service checks your site at regular intervals, day and night, and alerts someone when it stops responding. It can also warn you before the certificate or the domain expires. Without it, a site can be down for a weekend before anyone notices. With it, the right person knows within minutes and can act, and you get a record of how reliable the site has been. Our own monitoring service, Qafza Watch, works this way, and can send alerts to your team as well as ours.
Content changes and small fixes
Your business changes: new services, new prices, a new team member, new opening hours, a seasonal offer. The website should keep up. Some changes you will make yourself if the site has an editing area. Others need a developer: a new section, a form field, a fix on a page that displays badly on a new phone. A care plan should say which small changes are included and how much time they cover, and how larger requests are quoted.
What a care plan should include
Care plans vary, so read them carefully. A clear one says, in writing:
- Hosting: where the site runs, and who manages it.
- Updates: how often, and how they are tested.
- Backups: frequency, storage location, how long they are kept, and restores.
- Monitoring: uptime checks, alerts, certificate and domain expiry warnings.
- Small changes: which kinds are included, and the hours available each month.
- Support: how you report a problem, and the response time for each type of request.
- Reporting: what you receive each month.
Response times, written down
"We are always available" is not a response time. Ask for the promised time to respond, counted in business hours or days, and what counts as urgent: the site is down, a form is not sending, a payment page fails. Ask also how requests are tracked. A message to one person's phone gets lost when that person is busy. A ticket in a shared system, with a clock on it, does not.
Response time is a promise an agency can keep. It is not the same as a promise about how fast every problem will be solved, which depends on the problem. Be wary of plans that promise both without conditions.
A monthly summary
Once a month, you should get a short summary of what happened: availability over the month, updates applied, backups taken, requests handled and how quickly, and anything coming up, such as a renewal or a recommended change. This gives you a record of the care you are paying for, and an early warning when something needs a decision.
If you also track visits, enquiries and rankings, the same summary is a good place to put them side by side, so you can see what the site is doing for your business and decide what to improve next.
If you have no care plan today
Start with a short inventory: who has access to the hosting and the domain, when each renewal is due, when the last backup was made and where it is, and when the software was last updated. If you cannot answer one of these questions, that is where to begin.
How we work at Qafza
Our Care plans cover hosting, backups, updates, monitoring and small changes, with written response times and a monthly summary. Requests go through a support space where you can follow each one, not through a personal phone. We promise the scope of the plan and the response times; availability, enquiries and rankings are measured and reported to you each month.
We watch your website, day and night.Start Qafza Watch 
Free: the website launch checklist48 checks before and after launch, from phone speed to accounts in your name.Get the checklist 
Qafza teamOctober 7, 2026
