Website maintenance after launch: what support includes and how to organise it.

After launch, many owners consider the work on their website finished: the design is approved, the pages are filled and enquiries are coming in. But a website is not a printed leaflet; it is a program that runs on a server and depends on updates, hosting and external services. Left unattended, it will sooner or later start to fail. We described what to do in the first weeks in our article on the first 30 days after launch; here we focus on ongoing maintenance.

We look at which work is needed regularly and which only when necessary, how support differs from site development, how contract formats work and what to look for when choosing a contractor.

Why a website needs support if it already works

Every content management system, whether 1C-Bitrix, WordPress or a custom engine, receives regular updates. Some add features, but the security fixes matter more. A site that has not been updated for years becomes an easy target for automated attacks, and search engines flag infected sites as dangerous, so traffic can disappear within days.

The second reason is that the environment changes by itself. The host moves servers to new versions of the programming language, the security certificate expires, the payment service changes its protocol, a form stops sending emails because of new mail provider rules. “We didn’t touch anything and the site broke” is a typical complaint from those without ongoing maintenance.

Website technical support: the basic scope

The set of tasks depends on the complexity of the project, but most contractors offer a similar one. Below are the regular tasks, their usual frequency and their purpose:

Minor content edits are usually included as well: prices, contacts, banners, new pages based on an existing template, plus advice on hosting and email.

System and module updates

Updating a live site is risky: a new version of a module may conflict with customisations made for your project. A competent contractor first deploys a copy on a test server, applies the updates there, checks the catalogue, cart and forms, and only then moves the changes to the live version.

The procedure depends on the platform. Building a site on Bitrix includes buying a licence with an update period, and once that period ends the core stops receiving fixes until the licence is renewed. A WordPress website needs no licence, but it relies on more third-party plugins, each updated on its own schedule. More on the differences in our article on choosing a CMS.

Backups

A backup is insurance that is rarely used, but without it a single mistake can cost you the whole site. Archives must be stored separately from the main server: if something happens to the hosting, copies kept on the same server will disappear along with the site.

Frequency depends on how often content changes. A small service website needs a weekly copy, while a turnkey online store with daily orders needs a daily database backup. Archives should be tested from time to time by restoring them on a test server: finding out that a copy is damaged on the day of an incident is too late.

Monitoring: what should be watched

Monitoring is an automatic check that the site opens, responds quickly and contains no changes that nobody made. A service polls the site every few minutes and immediately notifies the person in charge if something fails. Without such control, many companies in Moscow learn about a problem from their clients. Besides availability, several other indicators are usually monitored:

• server response time and disk usage;
• certificate validity and domain payment dates;
• email delivery from forms and payment processing;
• unfamiliar pages and files appearing;
• indexing errors in search engine dashboards.

The last item is often overlooked, although it is directly linked to promotion: technical errors quietly reduce visibility, and SEO specialists notice them only when traffic drops. We described how to run such diagnostics in our article on technical audits.

Contract formats

The two most common options are a subscription with a fixed monthly fee and hourly work on request. A subscription is convenient when the site matters to the business and something changes on it regularly: the contractor keeps the project in mind, and updates and backups follow a schedule. Hourly billing suits small sites that need edits a couple of times a quarter, but regular maintenance is often left undone under this model.

Whatever the format, the contract should answer several questions: what mandatory work is included, how many hours are covered, what the response time for urgent requests is, how tasks are recorded and what happens on termination. Access to hosting, the domain and the admin panel must remain with you - how to check this is explained in our article on hosting, domains and SSL.

Website improvements: where support ends

New sections, CRM integration, calculators, a personal account - this is no longer maintenance but development. Such tasks are estimated separately: a specification is written and the timeline and cost are agreed. If improvements are part of a subscription package, agree in advance how many hours go to them, otherwise scheduled work will be pushed aside by urgent requests.

Sometimes a constant flow of improvements reveals a deeper problem: an outdated structure or a design that does not allow new blocks without rework. Then it is wiser to discuss a redesign, and sometimes a new project: building a corporate website from scratch costs more than edits but ends the endless patching. Base the decision on numbers: what a year of piecemeal edits costs versus a new version.

Building, promoting and supporting a site in one place: how to choose a contractor

It is most convenient to entrust maintenance to the team that built the site: they know the code and will not break customisations during updates. If that is not possible, a new contractor will need time to study the project. You can check a web studio or a freelance developer in this order:

1. Ask for an initial review of the site with a description of the problems found.
2. Check their experience with your content management system and similar projects.
3. Request a sample monthly report.
4. Find out how the test server and backups are organised.
5. Agree on response times and a contact channel for urgent requests.

When one team is responsible for both the code and SEO improvements, the causes of failures are found faster and changes do not contradict each other. If you need maintenance for an existing site or want to order a new website with post-launch support, see how we approach website development and tell us about your task - we will suggest the right format.