Somewhere on your invoice, there's a line item called "website maintenance." Maybe it's $50 a month. Maybe it's $400. You have no idea what it actually covers, and the person who sold it to you probably counted on that.
Here's the thing: there's no single right price for website maintenance, because "maintenance" isn't one thing. It's a bundle of very different services, some of which your site genuinely needs every month, and some of which are just a fee for someone to do nothing until something breaks. Before you can judge whether a plan is fair, you need to know what you're actually buying.
What "Website Maintenance" Actually Includes
Real maintenance covers four jobs. If a plan is missing more than one of these, you're not buying maintenance. You're buying a subscription.
Hosting and infrastructure. Your site lives on a server somewhere. Someone has to make sure that server is fast, backed up, and not shared with 400 other sites fighting for the same resources. Hosting can be bundled into a maintenance fee or billed separately, but either way it should be accounted for, not hidden.
Security updates. Software that runs your site, the CMS, plugins, themes, frameworks, gets patched constantly, often because someone found a vulnerability. If nobody applies those patches, your site is a sitting target. This is the least visible part of maintenance and the part most likely to get skipped by a cut-rate plan, because nothing looks broken until the day it very much is.
Content edits. Swapping a photo, updating a price, fixing a typo, adding a staff bio. Some plans include a set number of these per month. Others charge hourly. Neither approach is wrong, but you should know which one you signed up for before you need your fifth edit in a busy month.
Uptime monitoring. Something that actually watches whether your site is up and alerts a human when it isn't. Without this, "we'll fix it if it breaks" depends entirely on you noticing it broke, at 2am, on a Saturday.
A plan that only does one or two of these is not wrong to exist. It's just not full maintenance, and it shouldn't be priced like it is.
The Factors That Push a Maintenance Plan's Price Up or Down
Once you know what's in the bundle, the next question is why two plans covering the same four things can be priced so differently. A few honest factors:
- How the site was built. A site built on a heavily customized platform with a lot of moving parts takes longer to check, test, and patch safely than a simple, well-built site. More complexity means more hours, and more hours means a higher price. That's not padding, that's reality.
- How many hands touch the content. A five-page brochure site that changes twice a year costs less to maintain than a 40-page site with a blog, a store, and three people who need edits weekly.
- Response time promises. A plan that guarantees a fix within four hours costs more to run than one that says "within a few business days." Speed requires someone on call, and someone on call costs money.
- How much has been neglected already. If a site hasn't been updated in two years, the first month of "maintenance" is really cleanup. Expect that to cost more than steady-state upkeep.
- What's bundled versus billed separately. Hosting, backups, and a basic security scan bundled into one price will naturally read higher than a plan that bills those separately and only covers "checking in on things."
None of these factors have a universal dollar figure attached, and anyone who quotes you one without asking about your site first is guessing. What you can do is ask which of these five your quote reflects, and expect a straight answer.
Custom-Built Sites vs. Template Sites: Different Maintenance Realities
This is the part most pricing conversations skip, and it matters more than almost anything else on this list.
A template site, built on a mass-market theme with a stack of plugins bolted on, has more moving parts than it looks like from the outside. Every plugin is a separate piece of software with its own update schedule, its own security history, and its own chance of breaking something else when it updates. Maintaining a template site often means testing plugin updates against each other before they go live, because plugin A's latest version breaking plugin B's functionality is an extremely common Tuesday.
A custom-built site has fewer of those interdependencies. It was built to do exactly what your business needs and nothing else, so there's less surface area for something unrelated to break it. That doesn't mean custom sites need zero maintenance. The underlying framework and any integrations still need attention. But the maintenance work tends to be more predictable, because there isn't a stack of third-party plugins updating on their own schedules underneath you.
This is why a maintenance quote for a template site and a maintenance quote for a custom site shouldn't look the same, and why comparing them apples-to-apples is a mistake. If your site was built through our Custom Web Development approach, the maintenance conversation is about the framework and your integrations. If it's a template site, the conversation is really about managing a pile of third-party dependencies, and the plan should say so.
Signs You're Paying for Maintenance You're Not Getting
A few red flags worth checking against your current plan or a new quote:
- You've never received a report. Real maintenance leaves a trail: what was updated, what was backed up, what was checked. If you've been paying for a year and have zero record of anything happening, ask why.
- "Unlimited edits" with a two-week turnaround. Unlimited is a marketing word. Ask what the actual response time is for a content change.
- No mention of backups. If your maintenance plan doesn't explicitly say backups happen and how often, assume they don't.
- The price never changes even as your site grows. A flat fee that doesn't adjust as you add pages, features, or an online store isn't tracking the actual work involved. Someone's margin is quietly shrinking or the work is quietly getting skipped.
- Security updates are described as "as needed." Security patches aren't optional and they aren't occasional. If a plan treats them as a maybe, that's neglect wearing a maintenance label.
- Nobody can tell you what platform your site runs on. If your maintenance provider can't name the CMS or framework off the top of their head, they're not the one actually maintaining it.
If two or more of these describe your current plan, you're paying for a peace of mind you don't actually have.
How to Decide What Plan You Actually Need
Skip the search for a universal "right" number and start with your site instead.
- List what your site actually does. A five-page site with a contact form has different needs than a site with a store, a blog, and a client portal.
- Count how often you need content changes. If you touch your site monthly, pay for a plan with room for that. If you touch it twice a year, don't pay for weekly capacity you'll never use.
- Decide how much downtime you can tolerate. A restaurant that takes reservations online can't afford four days of "we'll get to it." A site that's mostly a digital business card has more room to breathe.
- Ask what happens if something breaks outside business hours. Get the actual answer, not the marketing answer.
- Match the plan to how the site was built. A template site with a dozen plugins needs closer, more frequent attention than a lean custom build. Don't buy a bare-bones plan for a complicated site, and don't overpay for heavy maintenance on a simple one.
If you're not sure which category your site falls into, run it through our free speed test first. A slow, bloated site is usually a preview of what its maintenance bill should look like, and it's a fast way to see how much is actually running under the hood.
And if maintenance keeps coming up because the site itself is the real problem, slow, hard to update, held together with plugins, it might be worth a conversation about rebuilding it right instead of maintaining it forever. That's a different conversation than this post, but it's often the more honest one. Pair a maintenance plan with real SEO & Analytics work and you'll actually know whether the upkeep is paying off, not just guess.
Next step: Pull your last three maintenance invoices or your current quote and check it against the four-part bundle at the top of this post: hosting, security updates, content edits, uptime monitoring. If one of those four is missing, that's the question to ask before you renew. If you want a second opinion on what your site actually needs, get started with a conversation, not a sales pitch.