Website maintenance: what does webmaster support really cover?
Updates, bugs, backups, and new offers: what website maintenance concretely changes, even when everything seems to be working perfectly.
Sur cette page5 sections
You call to change a price on your site. Three lines of text, nothing extraordinary. And you're told they need to find the developer, check the site version, request a quote. Meanwhile, your visitors continue to see the old price.
That's also what website maintenance is about. Not just someone who comes to fix things when everything is broken, but someone who already knows your site and can help it evolve with you. The technical side matters, obviously. What matters to you is not having to start a major project every time your business moves forward.
It also evolves in an environment that doesn't wait for you: browsers change, payment tools release new versions, technical components receive patches. You can leave a site alone for a while. You cannot assume that what works today will work indefinitely without monitoring.
In the industry, we talk about preventive, corrective, and evolutionary maintenance. Put like that, it sounds like a boiler service contract. In practice, it's three simple things: maintaining what works, fixing what no longer works, and adapting the site to what you need now.
Take a booking page. After an intervention, it still displays, the colours are right, the button too. Except the visitor can no longer choose a time slot. If we only checked that the page opened, we missed what made it useful.
At Cadarsir, technical core monitoring is accompanied by human checks before and after updates. We check functionality, not just appearance. Backups are also performed several times a day on monitored sites, to ensure recent restore points are available.
However, a copy is only useful if it can be used. I explain more specifically what to check in website backups : their content, their location, and the ability to get the service back up and running.
Centrally collected errors help trace this chain. We look at what happened and in what context, instead of randomly changing three settings hoping the problem disappears.
There are then two stages: restoring useful functionality, then addressing the cause if it requires more work. Temporarily disabling a faulty function can be a good emergency measure. That's no reason to forget about it afterwards.
At Cadarsir, the stated operational goal is a restoration within twenty minutes when a bug and intervention conditions allow. This isn't a promise that all outages, including those of an external service, will be resolved in twenty minutes. The benefit of regular monitoring is primarily knowing the site before the incident: we don't start by asking where the access details are while your business is waiting.
Evolutionary maintenance serves this purpose. We update content, adapt a user journey, or add a function while considering what's already there. At Cadarsir, a page modification is also accompanied by an SEO refresh: the text, title, and information used for ranking must continue to tell the same story.
Some improvements can be shared across multiple sites thanks to a shared technical base. If a function meets a common need and fits this model, the relevant sites can benefit at no extra cost. Development specific to your business still needs to be scoped; sharing doesn't mean any request becomes free.
And sometimes, the current structure really reaches its limits. We can then consider a redesign rather than an accumulation of small repairs. But that's a decision to be explained, not the automatic response to every request.
All three forms of maintenance are covered in the Cadarsir subscription. Their scope must be understood from the start, particularly to distinguish routine maintenance from new business development.
What I want to avoid is a site delivered with its keys and then left alone. You should be able to talk about your business and what you want to improve, without having to translate every need into developer-speak. Maintenance is useful when it allows you to do that, even on days when nothing is broken.
That's also what website maintenance is about. Not just someone who comes to fix things when everything is broken, but someone who already knows your site and can help it evolve with you. The technical side matters, obviously. What matters to you is not having to start a major project every time your business moves forward.
The site is delivered, but your business doesn't stop
At launch, you have up-to-date photos, a well-presented offer, and a working form. Six months later, you've added a service, changed your hours, or hired someone. The site won't guess that on its own.It also evolves in an environment that doesn't wait for you: browsers change, payment tools release new versions, technical components receive patches. You can leave a site alone for a while. You cannot assume that what works today will work indefinitely without monitoring.
In the industry, we talk about preventive, corrective, and evolutionary maintenance. Put like that, it sounds like a boiler service contract. In practice, it's three simple things: maintaining what works, fixing what no longer works, and adapting the site to what you need now.
Maintenance isn't just clicking "update all"
An update can fix a security issue or make one component compatible with another. It can also change how a form behaves. So the work doesn't stop at the little green tick in the admin panel.Take a booking page. After an intervention, it still displays, the colours are right, the button too. Except the visitor can no longer choose a time slot. If we only checked that the page opened, we missed what made it useful.
At Cadarsir, technical core monitoring is accompanied by human checks before and after updates. We check functionality, not just appearance. Backups are also performed several times a day on monitored sites, to ensure recent restore points are available.
However, a copy is only useful if it can be used. I explain more specifically what to check in website backups : their content, their location, and the ability to get the service back up and running.
When it breaks, understanding what broke
"The form isn't working" can mean several things. The button doesn't respond, the submission fails, or the message was sent but doesn't reach your inbox. For you, the result is the same: an enquiry doesn't arrive. To fix it, we have to find where it stopped.Centrally collected errors help trace this chain. We look at what happened and in what context, instead of randomly changing three settings hoping the problem disappears.
There are then two stages: restoring useful functionality, then addressing the cause if it requires more work. Temporarily disabling a faulty function can be a good emergency measure. That's no reason to forget about it afterwards.
At Cadarsir, the stated operational goal is a restoration within twenty minutes when a bug and intervention conditions allow. This isn't a promise that all outages, including those of an external service, will be resolved in twenty minutes. The benefit of regular monitoring is primarily knowing the site before the incident: we don't start by asking where the access details are while your business is waiting.
A new offer shouldn't require a new website
You start with three services. Then you add a fourth, you want to show your work or ask an extra question before an appointment. These are normal evolutions. The site must be able to accommodate them without someone systematically suggesting you redo everything.Evolutionary maintenance serves this purpose. We update content, adapt a user journey, or add a function while considering what's already there. At Cadarsir, a page modification is also accompanied by an SEO refresh: the text, title, and information used for ranking must continue to tell the same story.
Some improvements can be shared across multiple sites thanks to a shared technical base. If a function meets a common need and fits this model, the relevant sites can benefit at no extra cost. Development specific to your business still needs to be scoped; sharing doesn't mean any request becomes free.
And sometimes, the current structure really reaches its limits. We can then consider a redesign rather than an accumulation of small repairs. But that's a decision to be explained, not the automatic response to every request.
What you should be able to ask your webmaster
Good support should make these questions easy to ask: who checks that important functions work? What happens if the site goes down? How do we change an offer? And what is included, or not, in the subscription?All three forms of maintenance are covered in the Cadarsir subscription. Their scope must be understood from the start, particularly to distinguish routine maintenance from new business development.
What I want to avoid is a site delivered with its keys and then left alone. You should be able to talk about your business and what you want to improve, without having to translate every need into developer-speak. Maintenance is useful when it allows you to do that, even on days when nothing is broken.
