Website maintenance is the work needed to keep an existing site usable and manageable after launch. It is not the same as adding new pages, running campaigns or improving search rankings. The right scope depends on the technology, the functions customers rely on and the condition of the site when support starts. See the scope of our Website care service.
Match the plan to the website
A static informational website, a WordPress site and a WooCommerce store have different maintenance needs. WordPress introduces core, theme and plugin updates; a store also needs attention to catalogue and checkout functionality. A static site has no WordPress administration to update, but hosting, certificates, forms and deployments still need an owner.
Compare the alternatives in our maintenance options. They are alternatives for different technologies, not charges to add together. Initial remedial work and later functionality changes need their own scope.
Review the site before taking it over
Identify the hosting account, domain, CMS, installed extensions, licences and known faults. Confirm that the required access is available and establish what can be backed up and restored. Existing problems should be recorded so that taking over maintenance is not mistaken for an unlimited repair commitment.
If you do not know which technology the site uses, start with its public address and the information you hold about the provider. Avoid sending passwords through an ordinary enquiry form. Agree an appropriate access process when the work is confirmed.
Test the functions that matter to customers
A page loading successfully does not prove that every form, booking or payment works. Establish a proportionate checking process and distinguish safe test actions from real submissions or purchases. Tests that send emails or place orders must be agreed with the business.
For a dental practice, a physiotherapy clinic or a psychology practice, the website enquiry route should remain separate from collecting clinical information. A maintenance provider does not need real patient histories to test a commercial form.
Know what backups and updates cover
Ask where backups are stored, which parts of the site are covered and what recovery work is included. An update process should allow faults to be identified and changes reversed where appropriate. It cannot guarantee that third-party software will never have vulnerabilities or compatibility problems.
Clarify who pays for licences and who approves replacements when a tool is no longer suitable. Also distinguish content editing from technical changes: replacing a paragraph is a different task from building a new booking workflow.
Agree responsibilities and limits in writing
Check the channels for reporting an issue, the support scope, exclusions and any work charged separately. Do not assume round-the-clock monitoring or a response-time guarantee unless it is explicitly agreed. You can compare these responsibilities with the recurring costs described in our website quote guide.
A maintenance plan should make ownership and responsibilities clearer. It should not be used as an artificially low headline price for designing a new website.
