You pay for website maintenance every month, and the amount depends less on the number of pages than on what an outage would cost you. A stable presentation site and a site that takes bookings need different cover and different budgets. This page sets out the levels, what each one covers, and how to read a quote before you sign.
How much does website maintenance cost?
The market is organised around five levels. Work out which one you are on, and the budget follows.
| Level | For which site | What it covers | Monthly budget |
|---|---|---|---|
| Light maintenance | Stable showcase site, few publications | Updates, backups, occasional checks | On quote |
| Maintenance and support | Active site, lead generation | The base, plus a block of hours for fixes | On quote |
| Monitoring and fixes | Commercial site, several contributors | Continuous monitoring, alerts, tracked fixes | On quote |
| Critical maintenance | Online sales, booking, business-critical activity | Extended supervision, guaranteed response time, recovery procedure | On quote |
| One-off call-out | Isolated bug, single update | Billed for the time it takes, diagnosis included | On quote |
Three things decide where you sit: how often the site changes, how many people work on it, and what an interruption costs your business. You can count the first two. You have to price the third, and it is the one that settles the level.
What the price includes, line by line
A monthly budget rarely covers one thing, and it is separate from the build budget, which we cover in our article on the cost of a website and, for a showcase site, in the one on the cost of a showcase website. Four families of expenses add up, and they do not all come from the same provider.
| Item | Frequency | What makes it vary |
|---|---|---|
| Hosting | Monthly or yearly | A shared plan, which pools resources and supervision, or a managed plan, which bills dedicated operations |
| Domain name | Yearly | The extension chosen, and nothing else |
| Technical upkeep | Monthly | Frequency of updates, level of monitoring, block of hours included |
| Call-outs | As needed | Number of tickets, diagnosis time as much as fixing time |
Hosting is the most stable line. The domain name weighs little per month but counts over the year. The genuinely variable line is the last one, and it is also the one quotes detail the least. A plan may include part of the hosting or none of it, so when the offer says nothing, ask what belongs to the site, what belongs to the infrastructure and what belongs to support.
Why two comparable sites do not pay the same
At equal size, the gap between two invoices comes from four drivers. They add up, and none of them depends on the number of pages.
| Driver | Effect on the budget | Why |
|---|---|---|
| Type of hosting | Fixed line, highly variable by plan | Shared hosting pools resources and supervision, managed hosting bills dedicated operations |
| How often work is needed | Rises fast once something needs fixing every week | Each ticket takes a diagnosis, a fix and a check afterwards |
| Level of monitoring | Paid even without an incident | Monitoring and handling alerts take up time continuously |
| Number of contributors | Increases the support load | The more people publish, the more configurations and mistakes there are to put right |
The third driver is the one that surprises people when the invoice arrives. Most of us accept paying for a fix and resist paying for monitoring whose best possible outcome is that nothing happens. That is exactly what keeps an incident from turning into an emergency.
Maintenance, fixes and changes: do not put everything in the same place
A website budget works better when routine upkeep, one-off fixes and product changes stay separate. That keeps you from funding a full transformation out of a maintenance plan, or from treating a simple fault as a major project. It also makes a quote readable: a backup is not a new page, a bug is not a change, and a plan is not an open-ended development budget.
What belongs to routine upkeep
Updates, checks, backups, small fixes and basic monitoring. On a WordPress base, this is the scope a standard maintenance service covers. It is the repetitive work that keeps the site stable and limits the incidents your teams notice.
What triggers a one-off call-out
The incident falls outside the routine scope, or the request has to be handled immediately. This kind of work is billed for the time it takes, and the real duration depends as much on the diagnosis as on the fix.
- Blocking bug on a page or a journey.
- Urgent fix after an update.
- Content change that needs technical work too.
- Broken display on desktop or mobile.
What should be treated as a change
A change starts when the scope of the site changes, not when a detail is corrected. A new page, a new template, a design system, front-end work or structured content belong to a separate project, and so to a separate budget. That boundary keeps maintenance and redesign apart.
Which level of maintenance for which site
The right level comes from what one hour of downtime costs, not from the number of pages. Find your site in the first column.
| Role of the site | Cost of an interruption | Level of cover that fits | Point not to overlook |
|---|---|---|---|
| Presence and credibility | Low, deferred | Light maintenance | Backups that are actually tested |
| Regular editorial publishing | Low, but visible | Maintenance and support | Autonomy of the team that publishes |
| Lead generation | Direct: a broken form means lost enquiries | Monitoring and fixes | Monitoring of forms and conversion tracking |
| Booking or availability | Immediate and quantifiable | Critical maintenance | Recovery time after an incident |
| Online sales | Immediate, with an effect on the customer relationship | Critical maintenance | Payment, security, rollback procedure |
Read it this way and you avoid the two usual mistakes: paying for extended supervision on a presentation site, or running a commercial business on an entry-level plan. A budget that is too low does not make the cost disappear, it moves it to emergency fixes billed by the hour.
Monthly plan or one-off call-out?
For a site that changes little, hourly billing can be enough. For a site that publishes, sells or changes often, a plan smooths the cost and saves you negotiating every request. That is especially true when several people work on the same site.
Security, backups and availability
Keeping a site running costs money because you have to be able to roll back, update without breaking anything and react fast when an incident happens. ANSSI, the French national cybersecurity agency, recommends multi-factor authentication for administration accounts and backups of information systems, and cybermalveillance.gouv.fr, the French public cybercrime assistance service, sets out what to do in the face of ransomware. This line stays invisible until the day it matters more than any other.
Back up and be able to roll back
A backup is only worth something if the copy is recent and actually usable. Off-site copies keep recovery possible if the main environment goes down. Without a tested backup there is very little left to do once an incident is declared, which is the scenario those public guidance sheets describe.
Update without breaking the site
- Apply security patches without delay.
- Test on a staging environment.
- Check key pages and forms after each update.
- Review dependencies before going to production.
Monitor, alert, react
A critical site needs monitoring, alerts, sometimes a web application firewall and stronger authentication for administrators, which means keeping a developer or a technical provider available. When availability matters, response time and recovery time become budget lines of their own. You do not pay for comfort, you pay to shorten the outage.
Reading a maintenance quote line by line
Two plans at the same monthly price can cover very different scopes. Compare them on six lines the quote has to spell out, not on the amount.
| Quote line | What to read into it | Warning sign |
|---|---|---|
| Scope covered | What is included, and above all what moves to hourly billing | A mention of "site maintenance" with no detail |
| Frequency of work | How often updates and scheduled checks happen | No schedule stated |
| Backups | Frequency, retention period, and whether restoration is tested | "Backups included" with no frequency or recovery test |
| Response time | A written commitment, graded by the severity of the incident | A response "as soon as possible" or "subject to availability" |
| Block of hours | Number of hours included, and whether they roll over from one month to the next | Included hours that expire without warning |
| Taking your site elsewhere | Access, backups and documentation handed over if you leave | The subject is not addressed at all |
Two questions asked before you sign are worth the whole document. First, what happens if the site goes down on a Saturday, who works on it and how fast. Second, if you end the contract in six months, what you get back and in what form. The answers tell you more about the provider than the price list does.
The kind of provider matters too. With a freelancer, you pay for the work and you carry the continuity. With a larger team, you also pay for coordination, which covers absences and the skills you do not have. An in-house skill only looks free: someone still has to follow the updates, test before publishing and know how to roll back.
Webflow, WordPress or custom: maintenance is not the same
The technical base changes the nature of the upkeep more than its principle.
- Webflow: hosting included and fewer layers to maintain, so lighter technical upkeep. The spend moves towards content and changes.
- WordPress: updates to the core, the theme and the plugins, with the risk of conflicts that comes with them. This is where a maintenance plan earns its keep.
- Custom front-end: few updates forced on you, but dependencies to watch and a skill to call on whenever work is needed.
On Stockly, the CEO edited and published himself after delivery, without coming back to us. That kind of editorial autonomy keeps the call-out line down for good. On the sites we deliver, a consistent class convention noticeably reduces rework and the cost of fixes after launch.
Content, SEO and accessibility: the costs people forget
A website budget does not stop at the technical side. Copy, campaign pages, recurring SEO and accessibility all add costs that are rarely priced at signing time.
Update content without rewriting everything
Editorial updates cost money as soon as copy, visuals or the structure of a campaign page have to be reworked, and landing page creation follows the same cost logic. A one-off correction stays a one-off. Once the template and the hierarchy have to be reviewed, it is a change. The more the site publishes, the more this item shows.
The SEO adjustments that keep coming back
- Update internal links.
- Check the tags on every published page.
- Track indexing in Search Console, the foundation of any Webflow SEO engagement.
- Check performance after launch.
Accessibility as an upgrade cost
The RGAA, the French accessibility standard, is published by DINUM, the French government digital directorate. Its method provides for an audit run either by the organisation itself or by a third party, on a sample of pages representative of the service. The accessibility statement follows from a real compliance assessment, full or partial depending on the criteria met. The size of that sample, more than the number of pages on the site, determines the workload.