How Much Does Website Maintenance Cost? The Four Bills Hiding Under One Word

Every other cost guide we publish is about the number you pay once. This one is about the number you pay every month for years, which is the number that ends up larger. If you are still working out the build figure, that lives in our small business website cost guide, and this post deliberately does not restate it. The question here is what happens after launch, why the quotes you are comparing are so far apart, and which parts of a care plan are actually load-bearing.

Maintenance Is Four Different Bills Wearing One Name

This is the whole reason the market looks incoherent. Two vendors quote the same word and mean substantially different work, so the comparison is not a comparison at all until you separate the categories.

Keeping it alive. Hosting, the domain registration, the certificate that makes the padlock appear, backups, platform and plugin updates, security scanning. This is infrastructure. It is the cheapest of the four and the one most reliably included.

Keeping it accurate. Changing the hours, adding a staff member, swapping the seasonal banner, correcting a price, posting the new service. This is what most owners picture when they hear maintenance, and it is the category most often quoted vaguely.

Keeping it working. The form that stopped delivering. The booking widget that broke when the vendor pushed an update. The payment integration whose credentials expired. The layout that shifted on a browser version released last month. This is the category that produces emergencies, and the one whose absence you only discover during one.

Keeping it growing. New pages, search work, answer engine work, conversion improvements. This is not maintenance. It is search and content work with its own economics and its own timeline, and our SEO cost guide handles it separately. It gets bundled into maintenance retainers constantly, in both directions: businesses paying a growth-sized retainer and receiving only upkeep, and businesses paying an upkeep-sized retainer and wondering why nothing is growing.

Write those four down. Send them to each vendor. Ask which ones the number includes. A five-times gap between two proposals almost always resolves into one of them containing two categories and the other containing four.

What Each Tier Actually Buys

Under about $50 a month — self-managed

You are paying for hosting and a domain, and you are doing the rest. For a small site that changes a few times a year, this is a genuinely reasonable choice, and plenty of businesses run this way for years without incident. What makes it work is not the money saved, it is that a specific person has agreed to own it and has a recurring reminder in a calendar. What makes it fail is the far more common version, where the site was built two years ago by someone no longer involved and nobody has logged in since.

Roughly $75 to $300 a month — the standard care plan

Where most small businesses belong. Managed hosting, automatic certificate renewal, offsite backups on a stated schedule, updates applied on a staging copy rather than directly on the live site, uptime monitoring that alerts a person, security scanning, and a modest block of edit time — usually described as an hour or two, or as small changes within some stated turnaround. This tier is not exciting and it is not supposed to be. It buys you the reasonable expectation that the site is up, current, and recoverable.

Roughly $300 to $1,000 a month — a real service level

The jump here is not more of the same, it is commitments. A meaningful monthly edit allowance rather than a token one. A stated response time when something is broken, and a stated one for routine requests, which are different numbers. Performance monitoring rather than uptime monitoring, because a site that loads in eleven seconds is technically up. Upkeep of the integrations the site depends on, which matters enormously if bookings, payments, or a scheduling system are involved. Businesses that change their site weekly, run seasonal offers, or depend on the site for transactions belong here, and the money is usually justified by the third category rather than the second.

Above $1,000 a month — a growth retainer with maintenance inside it

At this level the maintenance is a rounding error and you are buying the fourth category. That is a legitimate purchase, but call it what it is, because the two things should be judged by completely different measures. Maintenance is judged by nothing bad happening. Growth work is judged by traffic, inquiries, and revenue, and if you are paying growth-retainer money you are entitled to a report that speaks in those terms.

Your Maintenance Bill Was Set Before the Site Existed

This is the part that belongs in a build conversation and almost never appears in one. How a site is constructed determines what it costs to keep, and the difference compounds for as long as you own it.

A site assembled from a large stack of third-party components carries a permanent compatibility burden. Every component is on its own release schedule, maintained by a different party with a different level of commitment, and any one of them can break the others or stop being updated entirely. That is not an argument against the approach — it buys enormous capability quickly — but the update work is real, it recurs forever, and it scales with how many components are in the stack. The most useful question to ask a vendor proposing one is how many of them the site will depend on.

A hosted platform moves most of that burden to the vendor. The updates happen without you, the security is theirs to worry about, and the monthly fee is predictable. You trade flexibility for that, and you accept that a platform decision made once is genuinely hard to reverse later. A cleanly built custom site sits at the other end: very little to update, very little to break on its own, but you need access to someone who can work on it when the requirement changes rather than adding a plugin.

None of the three is universally right, and our builder versus developer comparison works through which fits which business. The point for this post is narrower: when you are holding build proposals, ask every vendor what the site will cost to keep running in year two. A cheaper build with a heavier stack underneath it is frequently the more expensive purchase by month eighteen, and that arithmetic is invisible on the day you sign.

The Edit Allowance Is Where the Disappointment Lives

Almost every dispute we hear about a care plan is about this line rather than about the infrastructure. The infrastructure either worked or it did not, and it usually did. The edits are where expectation and contract quietly diverge.

Three questions settle it. What counts as a small edit, in examples rather than adjectives — is a new service page a small edit or a project? What is the turnaround, and is it different for something urgent, like a holiday closure going up on a Friday afternoon? And can you make routine changes yourself if you want to, which is less about saving money than about not being blocked at the moment something needs to be accurate.

That last one is worth more than it sounds. A site that the owner cannot update is a site that becomes wrong, gradually, in small ways, because every correction requires an email and a wait. Being unable to change your own hours is one of the six structural signals we list in signs you need a new website, and it is a maintenance problem long before it becomes a rebuild problem.

The Bill Nobody Quotes You

The case for maintenance is usually made emotionally, which is a shame, because the actual case is unglamorous and specific. Four things go wrong on unmaintained sites, and each has a real recovery cost.

A compromised site is the expensive one. An outdated component gets exploited, spam pages appear on your domain, and search engines flag the site with a warning that appears to anyone trying to visit. Cleanup is billable, and recovering search standing afterward takes longer than the cleanup does. Second, an expired certificate produces a browser warning that stops most visitors cold, and it always seems to happen on a weekend.

Third, and by far the most common, is silent delivery failure. A contact form keeps showing its thank-you message while the notification stops arriving, because a mail setting changed or a spam filter reclassified it. There is no error and no alert. Businesses discover this weeks later by accident, and the cost is every inquiry in between. If you take nothing else from this post: submit your own form once a month and confirm the message actually lands.

Fourth is drift. Nothing breaks, but the site slowly stops being true. Prices from two years ago, a staff page with people who left, a service you no longer offer, an address from before you moved. That is not only a customer problem now. Assistants and search engines read your pages as statements of fact about your business, and a site full of stale ones makes you unreliable to the systems people increasingly ask for recommendations, which is the entire subject of answer engine optimization. Accuracy became a ranking-adjacent concern rather than only a courtesy.

Recurring Costs That Are Not Maintenance but Arrive Anyway

Your monthly website spend is rarely just the care plan, and the surrounding items surprise people because each one arrived separately. The domain renews annually. Premium components and themes renew on their own licenses, often on different dates. Any third-party service the site depends on bills separately: booking, scheduling, email delivery, review collection, a chat widget, analytics beyond the standard tools.

Two of our other guides cover the versions of this that get genuinely large. For online stores, the app-marketplace accumulation and per-transaction processing described in the ecommerce cost guide routinely exceed the build cost within a year, which is a different mechanism from anything on this page. And if you are adding a conversational layer, the platform pricing models in the AI chatbot cost guide include one that scales with your success. Neither belongs inside a maintenance figure, and both should be listed beside it. The exercise worth doing once a year is opening the card statement and finding every line that exists because the website exists. Most owners are wrong about that total, usually low, occasionally by a lot.

Ownership: The Question to Ask on Day One, Not Day One Thousand

A maintenance relationship is the one where control quietly consolidates, because the whole arrangement is built on somebody else handling the parts you would rather not think about. That is fine, and it is the point. It becomes a problem only when the access consolidates along with the work.

Four things should be true regardless of who maintains the site. The domain is registered in your business name, billed to a card you control, and you can log into the registrar today. You hold administrator access to the hosting account and to the site itself. The code, or a complete export, is available to you on request. And the agreement says plainly what happens to all of it if the relationship ends, including how long you have to move.

This is a different problem from the one we describe in the real estate website cost guide, where the site is built on a brokerage subdomain and ownership was never the agent's to begin with. Here you own the asset and simply cannot reach it, which is more common and easier to prevent. Asking these four questions at the start costs nothing and reads as ordinary diligence. Asking them during a disagreement is a different conversation entirely.

The Care Plan Questions That Change the Price

Six, and they are all answerable in a sentence by anyone running a real service. Which of the four categories does this figure cover? What is the response time when the site is down, and what is it for a routine edit? What exactly counts as an included edit, in examples? Are backups offsite, on what schedule, and has a restore been tested rather than assumed? Who has the registrar and hosting logins, and can I see mine work right now? And what is not included that I will be billed for separately?

A sequencing note to finish on. Maintenance protects an asset; it does not grow one. If the site is current and reliable but nothing is arriving through it, the money belongs in the fourth category rather than a larger care plan, and the honest starting points are our guides to why a website gets no traffic and how long search work takes. If the site is fighting you every time it needs to change, a rebuild is frequently cheaper over two years than maintaining something that resists maintenance, which is the calculation in our redesign cost guide. We build with Claude Code, which shortens the build considerably and, more usefully here, keeps the underlying stack small enough that there is less to maintain in the first place. The cheapest maintenance is the work the site never generates.