Website support and maintenance: what it includes and why you need it

Website support is the regular work that keeps a site fast, secure and up to date after launch: updating the platform and plugins, backups, security and uptime monitoring, renewing the domain and hosting, updating content and making small improvements. Without it, even a well-built website gradually starts breaking, slowing down and going out of date — and problems are discovered only when a customer has already failed to send an enquiry.

Let us look at what maintenance consists of, how often each task should be done, which formats of working with a contractor exist and what to fix in the contract.

Why a website needs support after launch

A website is not a printed brochure made once. It operates in a constantly changing environment: browsers and platforms are updated, vulnerabilities are found in popular plugins, search engine requirements change, certificates and domain registrations expire. At the same time the business itself changes — new services, prices, staff and promotions appear.

A typical scenario without support looks like this: nobody touches the site for years, then the form stops working, or the domain is not renewed in time, or the site is hacked and someone else's links are placed on it. Fixing things at that point costs more and takes longer than regular maintenance, and some enquiries and reputation have already been lost.

What website support includes

Technical maintenance

• Updates. The CMS core, plugins, libraries and dependencies. Update carefully: first on a staging copy, then on the live site.
• Backups. Automatic backups of files and the database, stored in a separate location rather than on the same server. And, importantly, periodic checks that you can actually restore from a backup.
• Uptime monitoring. A service that checks the site and alerts you if it stops opening.
• Security. An SSL certificate, protection of the admin panel, limited user permissions, malware scanning, spam protection for forms. It is also worth enabling two-factor authentication for administrators and removing accounts of staff and contractors who no longer work on the site.
• Hosting and domain. Tracking renewal dates, server resources and correct operation of email on the domain.

Content and functionality

• Publishing news, case studies and vacancies, updating prices and contacts.
• Adding new pages based on existing templates.
• Small improvements: a new block, a form, an integration with a CRM or messenger.
• Fixing bugs found by users or the team.

Analytics and SEO hygiene

• Checking that counters and analytics goals work.
• Monitoring indexing errors and broken links in the search console.
• Watching load speed and Core Web Vitals.
• Regularly testing forms: do enquiries reach their recipients.

How often to do the tasks: a sample routine

Frequency depends on the complexity of the site and platform, but for a typical corporate website this schedule works.

• Continuously: uptime monitoring, automatic backups.
• Weekly: test form submissions, check incoming enquiries, review security notifications.
• Monthly: update the platform and plugins, check search console errors, report on analytics.
• Quarterly: test a restore from backup, run a speed audit, review users with access, check that content is current.
• Annually: renew the domain and certificates (better to set up auto-renewal), assess whether the platform is outdated, plan improvements.

Website support is insurance, not an expense. Regular maintenance is almost always cheaper than an emergency recovery after a hack, a failure or a lost domain.

Support formats

The choice of format depends on how actively you develop the site and whether you have your own specialist in-house.

• Hourly, on request. Suits simple sites that rarely change. The downside: nobody watches the site proactively, and work starts only when something breaks.
• Monthly package. A fixed scope of work and hours: routine tasks plus a set amount of time for improvements. Convenient for companies whose website is an important sales channel.
• In-house specialist. Justified if the site is complex, changes often or is integrated with internal systems. But it is hard for one person to cover development, design and security.
• Combined format. A company employee updates content, while a contractor handles technical tasks and improvements.

When choosing a contractor, ask how they test updates, where they store backups, how quickly they respond to outages and what the monthly report includes. Specific answers to these questions say more about the quality of support than a polished proposal.

The cost of support depends on platform complexity, the number of integrations, the volume of routine tasks and the required response speed. A simple site on a popular CMS is easier to maintain than a system with user accounts and payment integrations. More on what drives the budget in our article on website cost.

What to include in a maintenance contract

1. Scope of work. What is included in regular maintenance and what is billed separately.
2. Response times. Separately for critical situations (the site does not open, enquiries do not arrive) and for ordinary tasks.
3. Backups. How often they are made, where they are stored, how many versions, who checks restores and how.
4. Access and ownership. The domain, hosting, CMS, analytics and email should be registered to your company, with the contractor given access as a user. This protects you from losing control of the site when you change contractors.
5. Reporting. What was done during the month, which updates were installed, which problems were found.
6. Handover procedure. What the contractor hands over when the contract ends: current code, access credentials, documentation.

Who in the company is responsible for the website

Even if a contractor handles the technical side, the company needs someone who "owns" the website internally. This does not have to be an IT specialist — more often it is a marketer or a department head. Their tasks:

• knowing where access credentials are kept and controlling who has them;
• collecting changes to prices, services and vacancies from colleagues and passing them on for publication;
• accepting the contractor's work and reading monthly reports;
• receiving monitoring alerts and outage notifications;
• making sure enquiries from the site reach the sales team.

Without such a person, the site gradually becomes "nobody's": the contractor waits for tasks, staff assume someone is looking after the site, and customers are the ones who discover problems. Appointing an owner is the cheapest and most underrated step in website support.

Signs your website lacks support

• Nobody in the company knows exactly where the domain is registered and who pays for hosting.
• The platform and plugins have not been updated for more than a year.
• Nobody knows when the last backup was made — or there is none.
• Forms sometimes "lose" enquiries, but nobody has checked why.
• News and prices are outdated, and only a former contractor can make changes.
• The browser warns about an insecure connection.
• The site has become noticeably slower than it was at launch.

If several points apply, start with an audit: gather access credentials, make a backup, update the platform and test the forms. Sometimes it turns out the site has reached its technical limits and it makes more sense to plan an update — see our article on website redesign.

Checklist: where to start right now

• Check who the domain and hosting are registered to, and turn on auto-renewal.
• Collect all credentials in the company's secure password manager.
• Make sure backups run automatically and are stored separately.
• Send a test enquiry through every form on the site.
• Connect a free uptime monitoring service.
• Assign someone responsible for content and agree on how often it is updated.

If you need a contractor to take over technical maintenance and improvements, the Dasta Creative team supports the sites it has built and takes on existing projects after an audit — see our web development page.