
The question
We have been offered a maintenance contract for our website or online shop. What should it actually include, and do we really need it?
After a website or online shop launches, many companies also receive a maintenance proposal. The wording differs from one provider to another, and “maintenance” can mean anything from an update done now and then to continuous monitoring, tested backups and interventions guaranteed in writing.
This guide explains which activities usually fall under maintenance, why each one matters, in which situations you can do them yourself or do not need them, and which questions are worth asking before you sign, so that you can compare proposals on the same points.
If you want us to handle this for you, see our service Maintenance or our service Web and cloud hosting.
What maintenance means in practice
A website is not a finished product at launch. It runs on a server and uses a content management system (for example WordPress), a theme and modules or plugins written by other developers, an SSL certificate that must be renewed and, sometimes, connections to other software: invoicing, couriers, payments, CRM. Each of these components receives updates, and some stop being maintained.
Maintenance is the periodic work that keeps these components up to date, compatible with one another and recoverable if something breaks. It does not usually include new features or design changes; those are development work, agreed separately.
What happens when nobody does it
A site that is not maintained does not necessarily break straight away. Problems appear gradually and are often noticed late, by a customer or a colleague rather than by someone who monitors the site.
The most common situations are predictable and, for the most part, avoidable:
- Outdated plugins or themes with publicly known vulnerabilities, through which the site can be compromised.
- An expired SSL certificate, after which browsers show visitors a security warning.
- An update made directly on the live site that breaks a page, the shopping cart or the contact form.
- A module abandoned by its author that no longer works with the new version of the platform or the server.
- Backups that do not exist, are out of date or cannot be restored when they are really needed.
- The site goes down and nobody finds out until a customer calls.
What a maintenance plan should include
Not every site needs all the points below, but a serious proposal should state clearly which are included, how often they are carried out and what falls outside the plan:
- Updates for the platform, theme and plugins, at an agreed frequency, with a check that everything works after each update.
- Testing major updates on a test copy before the live site, especially for online shops.
- Automated backups of files and the database, stored separately from the server, with a stated retention period.
- A periodic restore test, so that you know a copy can actually be used.
- Availability monitoring, with an alert sent to a named person when the site does not respond.
- Tracking the renewal of the SSL certificate and flagging in good time a domain that is about to expire.
- Checking critical functions after changes: forms, cart, payment, emails sent by the site.
- Interventions for problems that arise, with a clear way to report them and a response time written into the offer.
- A short report on what was done, so that you can check the work.
A backup only matters if it can be restored
Many hosting providers make automatic copies, and many plugins promise the same. The useful question is not “do you have a backup?” but “when did you last restore a copy, and how long did it take?”. A copy that has never been tested is not a guarantee.
An online shop adds a further difficulty: reverting to an older copy can wipe out the orders, customers and invoices recorded in the meantime. A good plan sets out how new data is saved before restoring and who decides when to roll back.
Also check where the copies are kept. If they sit only on the same server as the site, a problem with the server or the hosting account can affect all of them.
Who is responsible for what: provider, hosting and your company
Many misunderstandings start from unwritten responsibilities. The site depends on several providers, and the one doing the maintenance does not control all of them. For example, if the hosting or the domain is with a third party, an outage at that provider cannot be fixed directly by whoever maintains the site, only reported and followed up.
It is also worth setting down in writing who owns the accounts. The domain, hosting, paid licences and administrator account should be in your company’s name, or at least accessible to it at any time, whether or not the maintenance provider changes.
- The maintenance provider: what the plan states, from updates to backups and interventions.
- The hosting provider: the server, its availability and, if included, server-level backup.
- The domain registrar: registration and renewal of the domain.
- Your company: the content, access to accounts, paying providers on time and decisions about changes.
When you can do part of it yourself or do not need a contract
On a hosted platform such as Shopify, the server, platform updates and platform security are the platform provider’s responsibility. The installed apps, the theme, the integrations and the content still need watching, but the volume of technical maintenance is smaller than for a site on your own server.
A simple brochure website with few plugins that is rarely changed can also be maintained by someone in the company, provided they have administrator access, a verified backup and the patience to read what changes with each update. Some hosting companies also offer automatic updates and backups; check exactly what their offer covers.
A plan run by a specialist becomes useful when the site brings in sales or enquiries every day, when there are integrations with other software, when a shop has many plugins, or when nobody in the company has the time or experience for updates and recovery.
Questions to ask before you sign
Ask for the answers in writing and put the same questions to every provider, so that you compare like with like:
- Which activities are included, and how often is each one carried out?
- Are updates tested on a copy before the live site?
- Where are the backups kept, for how long, and when is a restore test carried out?
- How do I report a problem, and how quickly will I get a response under the contract?
- What is part of the plan and what is invoiced separately, for example new features or recovery after an attack?
- Will I receive a report on what was done?
- In whose name are the domain, hosting, licences and administrator account?
- What happens to access and backups if we end the contract?
