Websites do not sit still. Certificates expire, software rots, domains lapse, and content goes stale while everything looks fine. Maintenance is noticing before your customers do.
Website maintenance is the ongoing work that keeps a site working, current and safe: content edits, software updates, tested backups, uptime monitoring, and the renewals that take a site down when they lapse.
It is the umbrella. Two parts of it are big enough to be their own jobs: website security, which is the hardening and protection, and speed optimization, which is diagnosing what is actually slowing it down. Maintenance is the routine that keeps both from degrading in the first place.
The word gets used to mean anything from a monthly invoice for nothing to a genuine service. Here is what is really in it.
The part you will actually use. Hours changed, a service added, a price removed, a photo swapped, a staff member gone. It sounds trivial and it is the most common reason a site loses trust: wrong hours on a Sunday sends someone to a locked door, and they do not come back.
If you are on a content system, plugins and core need patching, and the security advisories that matter are usually for something you installed once and forgot. If you are on a static site, this section barely applies, and we will tell you so rather than invent work.
Automated, off the same box as the site, retained long enough to be useful, and checked. The retention point is the one people miss: a backup that goes back a week is no help for a problem that started a month ago.
Something checking the site is up, and telling us rather than you. The alternative is finding out from a customer, which costs you the customer and the confidence.
Domain renewal, certificate renewal, and the billing card behind both. A lapsed domain is the worst failure on this page: your site and your email stop at the same moment, and getting it back can range from a phone call to a legal problem. These lapse because the reminder went to an old address nobody reads. We watch them.
Who the domain is registered to, where DNS is answered, where the site is hosted, who has the logins. Half of the emergencies we see are not technical. They are an hour of detective work because nobody wrote it down. See Cloudflare management for how we usually set this up so it is not a mystery.
What the site is built on, where it lives, who owns the domain, what state it is in. This regularly turns up something nobody knew, and it changes what care means for you.
No point monitoring a site that is broken today. Whatever is outstanding gets cleared first, and you get told what it was.
Backups, monitoring, renewal tracking. The unglamorous half, and the half that saves you.
Updates where there are updates, edits when you need them, and someone noticing when something drifts.
You should be able to see what was done. A care plan where nothing is ever reported is indistinguishable from a care plan where nothing is ever done.
Care means you have someone to email, and someone watching when you are not. Our published options are on the plans page, and if none of them fit what you need we will say so.
It depends on what it is built on, and the honest answer is not always. A static site of a few pages that never changes needs very little: the domain renewed, the certificate valid, and someone noticing if it goes down. Selling a heavy monthly plan for that would be selling you air.
A site on a content system with plugins is different. That stack has a genuine security surface and things break on their own, without anyone touching them. If nobody is updating it, it is decaying whether you look at it or not.
The other half is content. Hours, services and prices go stale. That is not the platform's fault, and it is the part customers actually notice.
Usually nothing, for a while. That is exactly why this gets ignored. Then one of a short list of things happens: the certificate lapses and browsers start warning people away, an unpatched plugin gets exploited, the domain expires because the renewal went to an inbox nobody reads, or the site quietly goes down and you find out from a customer.
None of these are dramatic on their own. All of them are cheaper to prevent than to fix, and the domain one is the worst, because a lapsed domain can be genuinely difficult to get back.
Yes, and some owners do it well. It is not secret knowledge. We published the actual list: the website maintenance checklist, free, with no requirement to talk to us.
The reason it usually does not happen is not capability. It is that it is nobody's job, so it slips, and it slips silently because a site that needs updating looks fine right up until it does not. Be honest about whether you will actually do it.
We do not put a promise on a page that we would then have to weasel out of, so here is the real shape of it: small text and photo changes are usually a same or next business day thing, and anything larger gets a straight answer about when rather than an optimistic one. Our published hours are on the contact page.
What we will not claim is round the clock coverage. We are a small team and we would rather tell you that up front than have you discover it at midnight. See care plans for what is actually covered.
Backups yes, and the second half of that question is the one that matters. An untested backup is a belief, not a restore. Plenty of businesses discover their backups were failing silently for months on the one day they need them.
The other thing worth knowing: your hosting provider probably has backups, and they are probably not enough on their own. They are often short-retention, which is useless if a problem went unnoticed for weeks, and they are in the same place as the thing that failed.
Ongoing website care and support options.
Certificates, hardening, and protection against the common attacks.
Find what is actually slowing the site down, then fix it.
What to check weekly, monthly and yearly.
Rebuild an existing site without losing the rankings you already have.
DNS, SSL, caching and protection, configured properly.
That uncertainty is usually the answer. Send us the URL and we will tell you what state it is actually in, including if the answer is that it is fine and you do not need us.