Many companies assume the work is finished the moment a site goes live. In reality it is only the beginning. A website is a living tool: the platform is updated, browsers change, security requirements tighten, and customer habits and business needs are anything but constant. A site left without support begins to slow down and age after a few months, and in some cases becomes a security problem.
In this article we cover what needs to be done continuously after a site launches, what support formats exist, what they include and how to organise support properly.
Why launching a site is not the end
A website can be compared to a car: buying it is one thing, while refuelling, servicing and changing the oil are something else entirely, yet unavoidable. A site is the same: on the day it is delivered it works well, but if nobody looks after it, problems accumulate over time.
There are several reasons. The platform and add-on modules the site runs on are updated constantly, and vulnerabilities in old versions become public, making it harder to withstand automated attacks that scan for them. Browsers and devices change too, so a page that looks right today may render differently in six months. Finally, the business itself changes: new services, prices, promotions and contact details appear, and the site must reflect them.
What support includes
Support is not just 'fix it if it breaks'. It has several parts: technical monitoring (server, domain, SSL certificate), updating the platform and modules, creating and verifying backups, finding and fixing errors, and security monitoring. Small changes, such as updating a text, a price or an image, also count as part of support.
It is important to define the scope of support in advance, because everyone understands the word 'support' differently. Some think it only means fixing defects, others include adding a new section. When each item is written down, there are no disputes caused by mismatched expectations.
Updates and security
Outdated versions are among the most common reasons sites get hacked. For sites on a ready-made platform (CMS), updates contain security fixes, and delaying them leaves the site open to known vulnerabilities. Still, an update should not be thoughtlessly pushed straight to a live site: sometimes a new version conflicts with custom-built features and breaks part of the site.
The right order is this: first test the update on a staging copy of the site, make sure everything works, then apply it to the live site, always making a backup beforehand. In addition, remove unused modules and old user accounts, since every unnecessary module adds a potential weak spot. Administrator passwords must be strong, and two-factor authentication should be enabled wherever possible.
Backups
A backup is the site's insurance. In the event of a hacker attack, a faulty update, a server failure or an employee deleting something by accident, only the backup will save you. But having a backup is not enough: you need to be sure it works.
The main principles are simple. Backups should be created automatically and stored separately from the server where the site is hosted, because if the backup disappears together with the server it is useless. A backup must contain not only files but also the database. And most importantly, periodically test restoring the site from a backup: a site that has a backup that cannot be restored is only slightly better than a site with no backup at all.
Monitoring speed and errors
A site may be fast on launch day but slow down over time: new images load heavy, extra scripts are added, the database grows. Slowdown affects visitors leaving the site and its position in search engines, so it is worth measuring speed periodically.
You should also monitor the site's availability: if it stops opening, you should learn about it before your customer does. Monitoring services send a notification when the site does not respond. Keep an eye on the expiry dates of the domain and SSL certificate too: an expired domain or certificate makes the site unavailable in an instant, and it is one of the easiest problems to prevent.
Ask a question or leave a request
We take care of updates, backups, monitoring, small changes and site development, and clearly define the scope of work and response times.
By submitting the form, you agree to the processing of personal data.
Keeping content up to date
Outdated information is a quick way to destroy trust. If the price, address, opening hours or promotion shown on the site do not match reality, the customer begins to doubt other aspects of your work as well. So make it a habit to review the key information on the site at least once a quarter.
Search engines also favour sites that are updated regularly. Adding blog articles, publishing news and case studies, improving service descriptions: all of this affects the site's visibility in search over the long term. Focus on the usefulness of articles rather than their number: one in-depth article answering a real customer question brings more benefit than a lot of meaningless text.
Analytics: is the site working
It is not enough for a site simply to be visible; it must deliver results. Analytics shows these results: how many people visit the site, where they come from, which pages they stop at, how many leave a request or place an order. Do not limit yourself to visit counts, but tie the data to business goals: number of requests, order value, customer acquisition cost.
Check that goals are set up correctly in analytics (submitting a request, payment, tapping a phone number) and that requests reach the CRM with their source. Then you will see which channel brings profit and which only burns money. After a few months such data shows exactly what to improve on the site, and you do not have to rely on guesses.
Development: new features and improvements
You need to tell support and development apart. Support is keeping what exists working, while development is adding new capabilities: a new section, online payment, a personal account, integration with another system, a new language. These are usually priced and planned separately.
A good way to develop a site sensibly is to rely on analytics and customer feedback. Which page people often leave, which form stays unfilled, what they often ask about: improvements that answer these questions are frequently more effective than big new features. Small but steady improvements (shortening a form, making a button clearer, speeding up a slow page) produce a noticeable result within a few months. Large changes are best split into stages, testing each one.
Support formats: retainer and hourly billing
There are two main models for organising support. With a retainer, you pay a fixed amount every month, and in return an agreed volume of work (updates, backups, small changes, monitoring) and a response time are guaranteed. This is convenient for planning, and the site is never left unattended. With hourly billing you pay only for work actually performed; this suits small sites that rarely change, but the response time in an urgent situation may not be guaranteed.
Which to choose depends on how important the site is. If the site is the main sales channel (an online store, a subscription service), a regular retainer and a fast-response guarantee usually pay off. A simple business-card site may not need a large retainer. When choosing support, look not only at price but also at response time, the procedure for urgent situations and the way reporting is done.
What to specify in the contract
The support agreement must be specific. It should state the scope of the service (what exactly is included), response and defect-fixing deadlines, the contact method for urgent situations, the reporting format and the payment terms. The difference between warranty support and paid support should also be written down: defects made in the initial period are fixed free of charge by the previous contractor, while new features are separate work.
Another important clause is access and rights. Access to the site, hosting, domain and code must be yours, while the contractor receives temporary permission to work. If support has to be handed to another contractor, the ability to obtain documentation and code should also be agreed in advance, otherwise changing contractors becomes very expensive.
Common mistakes
The most common mistake is to 'forget' the site after launch: leaving it without updates, backups and monitoring. It works well for a few months, and then one day it is hacked through a vulnerability in an outdated module, or the domain expires and the site goes offline. The next mistake is to believe a backup exists but never try restoring from it even once.
It is also common to apply updates straight to the live site without testing, to leave the support scope unclear in the contract, to leave analytics unconfigured, and for nobody to check where requests end up. Finally, keeping access to the site in the hands of only one person (for example only a former employee or a private individual) is very dangerous: when they leave, you cannot get into your own site.
Checklist
- Support scope and response times are written into the contract
- The platform and modules are updated regularly, tested first on a staging copy
- Backups are created automatically and stored separately
- Restoring from a backup has been tested at least once
- Site availability monitoring is enabled
- Domain and SSL certificate expiry dates are monitored
- Unneeded modules and old accounts are removed, passwords are strong
- Key information on the site (prices, contacts, opening hours) is reviewed every quarter
- Goals are configured in analytics, requests reach the CRM with their source
- Access to the site, hosting and domain is kept within the company
- A list of improvements for development is maintained