Website maintenance: what does webmaster support really cover?
Preventive, corrective and evolutionary maintenance: discover how Cadarsir secures, fixes and evolves your site within its subscription plan.
summary5 sections
A website is not a finished project on the day it goes live. To remain reliable, visible, and useful, it must be monitored over time. This is precisely the role of web maintenance.
But the word "maintenance" covers several realities. It does not only consist of repairing a page when it no longer works. Complete support is based on three complementary pillars: preventive maintenance, corrective maintenance, and evolutionary maintenance.
These three approaches answer three simple questions: how to avoid problems, how to solve them when they appear, and how to continue to progress the site? At Cadarsir, all three types of maintenance are included in the maintenance subscription.
At Cadarsir, technical foundation updates are carried out continuously. The goal is not to accumulate late versions and then have to catch up on a long list of changes in an emergency. On the contrary, regular monitoring allows the site to evolve in small steps and limits technical gaps.
Sites monitored by Cadarsir are backed up several times a day to provide frequent restoration points. This frequency reduces the distance between the current state of the site and the last available return point. It is particularly useful when a site regularly receives requests, content, or modifications.
Backing up is therefore part of a prevention logic: we prepare the rollback before needing it, rather than looking for a solution after data loss or the appearance of a problem.
At Cadarsir, the proper functioning of sites is verified humanly and manually before and after updates. This verification allows for comparing expected behavior, spotting an anomaly that would not show up in an automatic check, and reacting before the problem is discovered by a visitor.
To remember: preventive maintenance does not promise that no incident will ever happen. It organises technical monitoring, backups, and checks to reduce risks and provide rollback solutions when necessary.
The goal is for a detected error to be treated in a targeted and lasting way. It should not simply be hidden only for the same problem to return a few days later. Error tracking allows for keeping a record of the analysis and verifying that the correction has produced the expected effect.
This is a Cadarsir operational goal, not a general contractual guarantee applicable to all situations. The nature of the incident, its origin, available access, and external dependencies can influence the time required. The commitment to method remains the same: understand quickly, correct cleanly, and verify the return to normal operation.
This approach is important for small businesses: a technical error is not just a developer's issue. It can prevent a prospect from contacting the company, block a request, degrade the site's image, or interrupt a commercial action.
At Cadarsir, an SEO refresh is performed with every page modification. The goal is to maintain consistency between the visible content, the page structure, and the information useful for its ranking. This monitoring prevents a modification from improving the text while forgetting an important element for visibility.
Evolutionary maintenance allows these needs to progress as they come, with already acquired knowledge of the site. This avoids starting from scratch for every small request and maintains continuity in technical and editorial choices.
This operation allows for benefiting from improvements already developed, tested, and maintained, while maintaining a reasonable approach for a small or medium-sized business. It does not mean that every specific request is automatically included: an evolution specific to a single project may require a dedicated study or development. The shared model, however, makes it easier to share building blocks useful to several clients.
Want to know how to secure and evolve your site? Let's talk: the first exchange allows us to take stock of your existing situation, your priorities, and the level of support adapted to your activity.
But the word "maintenance" covers several realities. It does not only consist of repairing a page when it no longer works. Complete support is based on three complementary pillars: preventive maintenance, corrective maintenance, and evolutionary maintenance.
These three approaches answer three simple questions: how to avoid problems, how to solve them when they appear, and how to continue to progress the site? At Cadarsir, all three types of maintenance are included in the maintenance subscription.
The three types of web maintenance at a glance
- Preventive maintenance seeks to reduce risks before an incident occurs.
- Corrective maintenance intervenes when an error or bug is detected, to restore operation and then treat the cause.
- Evolutionary maintenance allows the site to adapt to new needs, content, and business objectives.
1. Preventive maintenance: avoiding problems before a breakdown
Preventive maintenance consists of acting before a malfunction disrupts the site or the company's activity. It relies on regular updates, frequent backups, and human checks.A constantly updated technical foundation
A site rests on a technical foundation: framework, CMS or business components, libraries, extensions, server, and connected services. This foundation is constantly evolving. Keeping it up to date allows for a consistent, compatible environment that is more resistant to known problems.At Cadarsir, technical foundation updates are carried out continuously. The goal is not to accumulate late versions and then have to catch up on a long list of changes in an emergency. On the contrary, regular monitoring allows the site to evolve in small steps and limits technical gaps.
Backups several times a day
A backup is not just for keeping a theoretical copy of the site. It must allow for the recovery of a recent functional state if a modification, update, or incident requires it.Sites monitored by Cadarsir are backed up several times a day to provide frequent restoration points. This frequency reduces the distance between the current state of the site and the last available return point. It is particularly useful when a site regularly receives requests, content, or modifications.
Backing up is therefore part of a prevention logic: we prepare the rollback before needing it, rather than looking for a solution after data loss or the appearance of a problem.
Human verification before and after updates
Automating an update is not enough to guarantee that a site is working correctly. A change can have an effect on a page, a form, a private area, or a business feature.At Cadarsir, the proper functioning of sites is verified humanly and manually before and after updates. This verification allows for comparing expected behavior, spotting an anomaly that would not show up in an automatic check, and reacting before the problem is discovered by a visitor.
To remember: preventive maintenance does not promise that no incident will ever happen. It organises technical monitoring, backups, and checks to reduce risks and provide rollback solutions when necessary.
2. Corrective maintenance: quickly treating errors and their causes
Corrective maintenance intervenes when a bug, display error, breakdown, or unexpected behavior is detected. It does not only consist of making the symptom disappear: we must understand what happened, correct the problem, and prevent it from reappearing in the same form.Centralised error recovery
Site errors are recovered centrally to provide a clear view of incidents. This centralisation allows for identifying problems more quickly, linking them to their technical context, and focusing the intervention on the real cause.The goal is for a detected error to be treated in a targeted and lasting way. It should not simply be hidden only for the same problem to return a few days later. Error tracking allows for keeping a record of the analysis and verifying that the correction has produced the expected effect.
A goal of operational restoration in 20 minutes
When a bug blocks an important feature, speed of intervention matters. At Cadarsir, the practice aims for an operational restoration in 20 minutes when a bug allows it and the diagnostic and intervention conditions are met.This is a Cadarsir operational goal, not a general contractual guarantee applicable to all situations. The nature of the incident, its origin, available access, and external dependencies can influence the time required. The commitment to method remains the same: understand quickly, correct cleanly, and verify the return to normal operation.
Fix fast, but above all fix sustainably
An effective correction must meet two needs: put the site back into service and avoid creating a new weakness. After an intervention, verification ensures that the fix does not degrade another part of the site.This approach is important for small businesses: a technical error is not just a developer's issue. It can prevent a prospect from contacting the company, block a request, degrade the site's image, or interrupt a commercial action.
3. Evolutionary maintenance: progressing the site with the business
Evolutionary maintenance concerns everything that allows the site to remain adapted to the company's needs. The site is not frozen: offers change, content evolves, visitors ask new questions, and new ideas appear.An SEO refresh with every page modification
Modifying a page does not only consist of replacing a few words. A content evolution can have an effect on the title, structure, internal links, tagging, or the search engine's understanding of the page.At Cadarsir, an SEO refresh is performed with every page modification. The goal is to maintain consistency between the visible content, the page structure, and the information useful for its ranking. This monitoring prevents a modification from improving the text while forgetting an important element for visibility.
Quickly integrating new needs
A company may need to add a page, modify a form, present a new offer, publish a project, or improve a user journey. These requests do not always justify a complete redesign, but they must be able to be integrated quickly so that the site remains aligned with the activity.Evolutionary maintenance allows these needs to progress as they come, with already acquired knowledge of the site. This avoids starting from scratch for every small request and maintains continuity in technical and editorial choices.
Sharing certain features at no extra cost
Cadarsir sometimes develops features that can meet needs common to several sites. When they match the Cadarsir shared model, these features can be shared with the relevant sites at no extra cost.This operation allows for benefiting from improvements already developed, tested, and maintained, while maintaining a reasonable approach for a small or medium-sized business. It does not mean that every specific request is automatically included: an evolution specific to a single project may require a dedicated study or development. The shared model, however, makes it easier to share building blocks useful to several clients.
All three types of maintenance are included in the Cadarsir subscription
Useful maintenance support does not choose between preventing, correcting, and evolving. The three dimensions reinforce each other:- preventive maintenance reduces risks through updates, backups several times a day, and human checks;
- corrective maintenance allows for recovering errors, intervening quickly, and treating bugs sustainably;
- evolutionary maintenance keeps the site aligned with the activity, with an SEO refresh at each modification and rapid integration of new needs.
Want to know how to secure and evolve your site? Let's talk: the first exchange allows us to take stock of your existing situation, your priorities, and the level of support adapted to your activity.
