What website maintenance actually includes, and what it doesn't

“Website maintenance” is a phrase that survives on being vague. Two providers can both use it in a proposal and mean almost nothing in common: one is checking that plugin updates don’t break the contact form, the other is rewriting your service pages every month. Before you pay for it, work out which version you’re buying.

Here’s what usually sits inside the phrase, and what usually doesn’t.

Keeping the site online

The unglamorous half of maintenance is making sure the thing loads. That covers the hosting itself, the SSL certificate that stops browsers flagging your site as insecure, the DNS records that point your domain at the right server, and the renewal dates attached to all of it.

Most small business sites that go down do so for boring reasons. A domain lapses because the renewal notice went to an email address nobody checks. A certificate expires. A card on file gets replaced and the hosting invoice fails silently. None of these are technical failures. They’re calendar failures, and a maintenance plan should be absorbing them.

Uptime monitoring belongs in this bucket too. Someone or something should notice your site is down before your customers do.

Keeping the site safe

Security work on a small business site is mostly patching. If you’re on WordPress, Joomla, Drupal, or anything else with a plugin ecosystem, the core software and every extension you’ve installed ship updates, and a good share of those updates close security holes. Sites get compromised because nobody applied them for eighteen months.

Applying updates is the easy part. The part people underestimate is checking that the update didn’t break anything, which is why a plan that includes updates but no testing is worth less than it sounds. Booking form stops submitting after a plugin bump, nobody notices for three weeks, you lose three weeks of inquiries.

Backups sit alongside this. Ask two questions of any backup arrangement: how far back does it go, and has anyone ever restored from it? An untested backup is a promise, not a safety net.

Keeping the content current

This is the part business owners actually feel. Prices change. You drop a service, add another, hire someone, move premises, change your business hours over the holidays. Your phone number changes and it’s still wrong in the footer eleven months later.

Content maintenance usually covers text edits, swapping photos, updating contact details, adding or retiring a service, and small page additions. Where providers differ enormously is volume and turnaround. Some plans give you a fixed number of change requests a month. Some give you a fixed number of hours, which is not the same thing. Some quote a turnaround in business days, some don’t quote one at all.

Ask for the turnaround in writing. “We’ll get to it” is not a commitment, and the gap between a same-week edit and a same-day edit matters when you’ve just changed your prices.

Keeping it working properly

The last bucket is the routine checking nobody enjoys. Links that now 404 because you deleted a page. Forms that stopped delivering because an email provider tightened its rules. Images that were uploaded at full camera resolution and now cost your visitors four seconds of load time. Search Console errors that have been accumulating quietly.

This work rarely produces a visible change, which is exactly why it gets skipped when nobody is being paid to do it.

What maintenance usually doesn’t cover

Here’s where quotes diverge, and where people get surprised by an invoice.

Marketing is normally separate. Running ads, sending campaigns, managing your social accounts, and doing keyword research are different jobs with different skills, even when the same company sells both.

A redesign is separate. Maintenance keeps the site you have in good order. It doesn’t fund a new one. If your site looks dated, that’s a build conversation, not a maintenance one.

New functionality is separate. Adding a booking system, a payment flow, a members area, or a multi-language version is development work. Some plans include a small allowance of development hours; most don’t.

Bulk content production is separate. Editing your existing about page is maintenance. Writing twelve blog posts is a content service.

Legal compliance is usually yours. A provider can put a cookie banner and a privacy policy page on the site. Whether the policy accurately describes what your business does with customer data is a question about your business, not your website.

Third-party costs are usually passed through. Domain registration, premium plugin licenses, stock photo licenses, and paid integrations get billed separately unless the quote explicitly says otherwise.

Reading a maintenance quote

Three things tell you most of what you need to know.

First, is the scope described as work or as outcomes? “Two hours per month” tells you what you’re renting. “Your site stays online, patched, backed up, and current” tells you what you’re getting. The second is harder to sell and better to buy.

Second, what happens when something breaks at an awkward time? A plan with no answer to that question is a plan you’ll be very unhappy with at 8am on a Monday.

Third, what happens to your content if you leave? You should be able to get an export of everything on your site. Ask before you sign, not after.

The version worth paying for

The maintenance arrangement that works for a small business is the one where you stop thinking about your website except when you want to change something on it. You send a message, the change happens, and the rest of it stays invisible because it’s being handled.

If you’re comparing plans and one of them lists eleven technical tasks while another says “message us and it’s done within a day”, the second is not less thorough. It’s just describing the same work from your side of the fence.