Beyond "fixing things when they break"
Website maintenance is the ongoing, recurring work of keeping a website secure, functioning correctly, and up to date most of it invisible when done well, and only noticed when neglected. It is closer to maintaining a car (regular oil changes, not just emergency repairs) than to a one-time renovation.
The work, in plain terms
Keeping the software current. Your website runs on software a content management system, plugins, themes and that software receives updates, much like your phone's apps do. Applying these updates, particularly security-related ones, closes off ways that automated attacks could compromise your site.
Making sure you have a backup. If something goes wrong a hack, a bad update, a hosting failure a recent, working backup is what allows you to restore your site rather than starting from scratch.
Watching that the site is actually online. Websites occasionally go down sometimes for reasons within your control (an expired domain), sometimes not (a hosting provider issue). Monitoring catches this quickly rather than discovering it days later from a customer complaint.
Keeping content accurate. Your business hours change, you add a new service, a team member leaves the website needs to reflect current reality, not what was true when it launched.
Fixing what breaks quietly. Links to other pages or external sites stop working over time as things change elsewhere on the internet. These broken links degrade the visitor experience and, at scale, can affect how search engines crawl and rank your site.
Why this work is easy to neglect
None of these tasks are visually exciting. A successfully applied security update looks identical to the website before the update the value is entirely in what did not happen (a hack that was prevented) rather than something visible that did happen. This makes maintenance one of the easiest business expenses to defer, right up until the deferred risk materialises as an actual problem.
What it costs to skip maintenance
A website left unmaintained for an extended period does not break all at once it degrades gradually and then, often, breaks suddenly. Security vulnerabilities accumulate silently. Page speed slowly worsens as unoptimised content piles up. And then, at some point, a vulnerability is exploited, or an outdated plugin conflicts with a hosting environment update, and the site goes down or is compromised at a moment with no warning, often during a period when the business can least afford the disruption.
Who is responsible for this
For a small business, this can be the business owner directly (with some learning investment), an in-house team member with technical comfort, or an external agency or freelancer on a maintenance retainer. What matters is that someone is clearly responsible and a recurring schedule exists the work happening "whenever someone gets to it" is functionally the same as it not happening at all.
Frequently asked questions
No hosting is the server space where your website's files live; maintenance is the ongoing work of keeping the software on that server updated, secure, and functioning correctly. You can have excellent hosting and still have a poorly maintained, vulnerable website.
For a straightforward brochure site, 1 3 hours per month is typically sufficient to cover updates, a backup check, and a quick content accuracy review though the consequences of skipping it accumulate over a longer time horizon than that monthly time investment might suggest.
Significant portions can automated backups, automated minor updates, automated uptime monitoring with alerts. But some judgment is still required: deciding whether a major update is safe to apply, reviewing whether content is still accurate, and investigating any alerts that automated monitoring surfaces.