A business website is usually built as a project, with a schedule, a budget and a launch date. After launch, however, the website lives on for years, and that period decides whether it is a business tool or a liability. Website maintenance means all the work that keeps a site working, secure, fast, findable and legally compliant after it goes live.
This guide covers the areas of maintenance, a realistic workload and how to divide the responsibilities. Each area has its own in-depth article on siteadmin.fi.
The five areas of maintenance
In practice, maintenance falls into five areas. They are connected: an update can break a form, for example, and then a working backup and monitoring save the day.
| Area | What it includes | Typical rhythm |
|---|---|---|
| Technical maintenance | Updates to the CMS, plugins and themes, PHP version, server environment | Weekly |
| Security | User accounts, two-factor authentication, firewall, malware scanning, logs | Continuously and monthly |
| Backups | Copies of files and the database in a separate location, restore tests | Daily, tested quarterly |
| Content maintenance | Keeping texts, images, contact details, prices and the privacy notice up to date | As needed, reviewed annually |
| Visibility and performance | Search Console, broken links, speed, Core Web Vitals, visibility in AI search | Monthly |
Technical maintenance
Most business websites run on a content management system, most often WordPress. The system consists of a core, a theme and dozens of plugins, all updated on different schedules. Technical maintenance means updating them in a controlled way: first a backup, then the update, and finally a check that the site and its forms still work.
The server side is often forgotten. Each PHP version has its own life cycle, and once a version is out of security support, no more fixes are released for it. For example, support for PHP 8.1 ended at the end of 2025 and security support for PHP 8.2 ends on 31 December 2026. Read more in WordPress website maintenance.
Security
Website security is not a single plugin but a set of practices: strong, unique credentials, two-factor authentication for administrators, removal of unnecessary accounts, up-to-date software and monitoring. Most break-ins are not targeted. They are automated scans looking for known vulnerabilities in outdated plugins. That is why the update rhythm is the single most important security measure. The topic is covered in depth in Website security.
Backups
A backup is insurance that has to be checked before you need it. Good practice is a daily automatic copy stored on a different server from the website itself, plus regular restore tests. The hosting provider's own backup is a good addition, but if the website and its backups are in the same place, the same fault can take out both. See the backup guide.
Content maintenance
Outdated content is a quiet problem. A wrong phone number, a discontinued service or a price list that is years old erodes trust and can mislead customers. Statutory content such as the privacy notice, the cookie notice and, where required, the accessibility statement also needs regular checking. Content maintenance often suits the company's own staff, because they know the services best.
Visibility and performance
Maintenance also includes monitoring: does Google find the pages, are there indexing errors, do the links work and does the site load quickly on mobile? As AI search becomes more common, it is worth also tracking whether the company is mentioned in the answers of AI assistants. Read more in technical SEO and GEO: visibility in AI search.
How much work does maintenance take?
The workload depends more on the type of website than on its size. A ten-page brochure site with a few plugins is light to maintain. An online shop with payment processing, an inventory integration and customer accounts is a system that changes constantly.
| Type of website | Basic maintenance per month (estimate) | Special features |
|---|---|---|
| Brochure site (5–30 pages) | 1–2 h | Updates, backups, testing forms |
| Content site or blog | 2–4 h | Also broken links, image optimisation, Search Console |
| Online shop | 4–15 h | Payments, integrations, order testing, load during campaigns |
| Integrated service or portal | Case by case | APIs, user management, log monitoring |
The figures in the table are indicative estimates of basic maintenance. They do not include content production, development work or troubleshooting incidents.
Division of responsibilities: who owns the website?
The most common reason maintenance fails is organisational, not technical. The agency that built the site has moved on to other projects, the marketing manager has changed jobs and the domain renewal notices go to a former employee's mailbox. That is why the first maintenance task is to write down who is responsible for what.
Record at least the following:
- Domain: in whose name the domain is registered, with which service and to which address the renewal notices are sent.
- Server and hosting: the provider, the contract holder and the control panel credentials.
- Content management system: administrator accounts assigned to named people, no shared accounts.
- Third-party services: analytics, Search Console, the cookie tool, form services and email sending services.
- Contact person for incidents: who does what if the site goes down on a Friday evening.
Store credentials and documentation in the company's own password manager, not with an individual employee or supplier. That way staff or supplier changes do not put the website at risk.
A maintenance plan in practice
A maintenance plan can be a one-page document. Its purpose is to make the tasks recurring and visible. A good plan answers three questions: what is done, how often and by whom.
- Inventory: list the CMS, plugins, server, PHP version, domains, integrations and credentials.
- Rhythm: agree on the schedule for updates, backups, restore tests and monitoring.
- Change management: decide whether updates are tested in a staging environment first and who approves larger changes.
- Incident instructions: write down what to do after a break-in, an outage or a broken update.
- Annual review: once a year, go through the contracts, regulations, content accuracy and the life cycle of the site.
If maintenance is bought from an outside supplier, the plan becomes a maintenance agreement. Its contents are covered in more detail in Maintenance agreement.
When is maintenance no longer enough?
Maintenance can extend a website's life cycle a long way, but at some point a redesign becomes the cheaper option. Signs of this include a theme that is no longer updated, plugins that do not support the current PHP version, content management that needs a developer for every change and a layout that does not work on mobile. In a redesign, the knowledge gathered during maintenance is valuable, and redirects from the old addresses in particular should be planned carefully. Read more in Site redesign and 301 redirects.
Summary
A well-maintained website does not make the news and does not cause surprises. It comes down to three things: a clear division of responsibilities, a recurring rhythm and tested backups. When these are in place, security, speed and search visibility can be built on top of them.
Frequently asked questions
How much time does website maintenance take?
Basic maintenance of a typical WordPress website with 10–50 pages usually takes 1–4 hours a month when updates, backup checks and monitoring are handled regularly. Content updates, development work and incidents come on top of that. An online shop or a site with integrations needs considerably more.
Can a business maintain its own website?
Yes, if someone in the company has the time, the skills and, above all, the responsibility for the job. When you do it yourself, rhythm matters most: weekly updates, regular restore tests of backups and clear instructions for incidents. Many businesses handle content themselves and outsource technical maintenance.
What happens if a website is not maintained?
Outdated plugins and an old PHP version are the most common ways in for attackers. The site also gets slower, forms and integrations can stop working without anyone noticing, and search visibility declines. In the worst case the domain expires and both the website and email stop working.
What is the difference between maintenance and development?
Maintenance keeps the existing website working, secure and up to date. Development adds new features, page templates or integrations. Define the boundary carefully in the maintenance agreement, because that is where most billing disputes start.