Website maintenance covers agreed technical checks, backups, updates and action when a feature stops working. Copy changes, product uploads and new features may be included, but they should be listed separately. Hosting, maintenance and content editing are different services, and the responsibilities depend on the technology and how your business uses the website.
The most useful question is therefore more than “how much does maintenance cost?” Ask what will be done, who is responsible and how the result will be checked. The following worksheet can help you agree this with an existing supplier or before building a new website.
How do hosting, maintenance and content changes differ?
Hosting provides the environment where your website runs. Depending on the package, it may include server administration, a certificate, backups and other services. That alone does not confirm that somebody tests your enquiry form, fixes plugins or updates your opening hours.
Technical maintenance covers the agreed tasks that support the operation of the website: availability monitoring, important feature checks, appropriate updates and recovery procedures. Content editing means changing copy, photographs, price lists and other information. A new booking feature or connection to business software usually needs a separate development estimate.
One team can perform all these tasks. Still, separate them in the proposal so you know what is included, who approves changes and what costs extra. Our guide to website development costs and related expenses covers the other items to consider.
Does every website need the same maintenance tasks?
No. A WordPress website, a static company website and an application with user accounts have different components. The task list should reflect the actual solution, without charging for systems your website does not use.
For a WordPress website, the relevant components include the core system, theme and plugins in use. The official WordPress update guide recommends preparing a backup before starting, so the website can be restored if something goes wrong.
Automatic updates for themes and plugins have separate settings. Enabling them does not confirm that checkout or the contact form has been tested after a change. Agree who monitors notifications and checks critical features. If you are choosing a platform, read when WordPress suits a business website.
A static website does not necessarily have a CMS or database on the public server, but it still has a domain, hosting, a publishing process and possibly forms or external services. A custom application may also need checks for user sign-in, background tasks and integrations. Record who maintains each component and what access they need.
How should the business, supplier and host divide responsibilities?
Name a person or team in the agreement, rather than just a service. This matrix is a suggested starting point to adapt to your project, not a universal support package. The same company may take on several roles.
Scroll the table sideways to see all columns.
| Task | Website owner | Supplier | Hosting provider | Evidence of completion |
|---|---|---|---|---|
| Domain and service renewals | Approves costs and confirms details. | Tracks deadlines if agreed. | Provides information for its own services. | Confirmed renewal and next expiry date. |
| Software updates | Approves the timing of important changes. | Assesses, applies and checks the change. | Maintains the agreed server components. | Change log and check results. |
| Backups | Agrees acceptable loss of recent data. | Checks coverage and a trial restoration. | Creates and stores backups if included. | Backup date and recovery test result. |
| Contact form | Confirms receipt of a test enquiry. | Tests delivery and fixes issues within its scope. | Checks its infrastructure when needed. | Confirmed receipt, not just an on-screen message. |
| Content changes | Supplies and approves accurate information. | Uploads and checks it if included. | Has no editorial role. | Approved change on a specific URL. |
| Fault reports | Provides an example and business impact. | Leads diagnosis and coordination. | Resolves a confirmed issue in its service. | Recorded cause, action and verification. |
Have one known reporting channel and a person who follows the issue through to closure. A website owner should not have to guess whether a plugin, server or email service caused the problem before receiving help.
How can you check that a backup can actually be restored?
Ask what the backup includes, where it is stored, how long it is retained and who can restore it. WordPress needs the appropriate files and database. The WordPress backup guide explains that distinction and recommends keeping a copy separately from the web server.
One practical check is to restore a selected backup into a separate test environment. Record the backup date, open several important pages and inspect information that should have been preserved. Confirm that an authorised editor can sign in. Protect the test environment from public access and disable real messages, payments and other external actions.
Then record what was restored successfully, what was missing and how long the process took. This is a suggested practical test, not a guarantee of future recovery time. For a store or portal, explicitly discuss how to preserve newer orders and entries created after the backup date. Restoring the entire system without this plan can erase newer data.
Who acts when a form, payment or another feature fails?
Distinguish in advance between an unavailable website, a failed critical feature and a minor display issue. For each category, agree a reporting channel, support hours and an expected initial response time. An initial response is different from resolving the issue, particularly when a bank, email service or another supplier is involved.
A report should include the URL, time, device, steps leading to the error and a brief description of its effect. A screenshot can help, but remove passwords, card details and personal information that is unnecessary for diagnosis. The responsible person then confirms what they are investigating and when you can expect the next update.
After a fix, repeat the whole user task. For a form, check that the message arrives; for a store, agree a safe test of the order process and relevant notifications. An accessible homepage does not confirm that every feature works.
How often should the website be checked?
The schedule depends on risk and how frequently things change. A rarely updated company website and a store receiving daily orders need different arrangements. This example is a basis for discussion, not a universal standard:
- Before an important change: check the backup and the ability to return to the previous state.
- After publishing a change: check the affected pages and connected critical features.
- At agreed intervals: review error notifications, backups, important forms and available updates.
- Periodically: test recovery and review access permissions and renewal dates.
- When business details change: update contact details, opening hours, services and prices.
Serious incident reports and important security notices should be assessed when they arrive, rather than automatically left for a monthly report. Agreed monitoring should specify which events it checks and who receives alerts.
What should the maintenance agreement include?
List the covered websites, technologies, tasks, responsible people and support boundaries. Clarify whether content changes are priced per request or covered by an agreed time allowance, who pays for licences and how additional work is approved in advance. Do not assume a recurring fee covers every future feature.
Define access and documentation handover if you change suppliers. Agree which accounts belong to the business, who has administrator access and how unnecessary permissions are removed. Instructions for routine editing and an overview of external services make it easier to continue operating the website.
SEO work also needs to be named: technical checks after changes, content writing and results analysis are different responsibilities. When comparing packages, use a consistent scope from our guide to comparing website development quotes, instead of comparing monthly fees alone.
What should a maintenance report record?
A short report should show completed tasks and unresolved questions. Copy this blank monthly template into a shared document, adjusting the reporting period to the support agreement.
Scroll the table sideways to see all columns.
| Item | Information to enter |
|---|---|
| Period and responsible person | From/to; person or team. |
| Changes and checks | Date, URL or component, work completed and result. |
| Backups and recovery | Backup status; last recovery test date and any gaps found. |
| Reported issues | Description, action, status and verification. |
| Outstanding tasks | Next step, owner, deadline and required approval. |
If you are planning a new business website, discuss responsibilities after launch from the start. If your website already exists, send its address and a description of important features so we can first establish what needs maintaining and what you want to edit yourself.