The site is live. Somebody has put a monthly number in front of you, or nobody has and you are trying to decide whether paying one at all is the right move. Either way the question underneath is the same, and it is the one people type: how much does it cost to maintain a website, and what does that money buy that you could not do yourself on a Sunday afternoon.
The published answer is narrower than the search makes it look. Website care plans exist, they are sold under their own names, and the sellers that publish a price publish it plainly. What those plans cover is a content management system: updates on a schedule, backups, a malware scan, an uptime check, and a fixed slice of somebody’s attention. What they do not cover is the upkeep a site generates because of what it does. If people sign in, if the database changes shape when a feature changes, if money moves through the thing, none of the plan lists read for this page names any of that work.
Every figure here was taken on 1 September 2026 from the seller’s own plan page: two website care sellers and one site-tools vendor publish a monthly number, two more render no plan price even when the page source is read directly, and one refused an automated read altogether, which is why the published market on this search is smaller than a page full of ranges makes it look.
Published website care plans read on 1 September 2026 start at $69 a month on FixRunner’s small-site ladder and reach $359 a month at the top of WP Buffs’ four tiers, with FixRunner’s enterprise tier at $500 above that range. That buys updates, backups, monitoring and a fixed slice of somebody’s time. On the published plan lists, none of it is described as the upkeep a site with logins and payments generates, so treat that coverage as unconfirmed until a seller puts it in writing.
What the published plans actually cost, and what each one buys
Website maintenance cost, taken from the plan pages themselves, runs from FixRunner’s “$69/month” entry plan to WP Buffs’ “$359.00 USD / Month” top tier for small-site plans, both read 1 September 2026, with FixRunner’s “$500/month” enterprise tier above that. The spread tracks how much of a person each plan includes rather than site size.
That is the whole shape of it: a few scheduled tasks at the bottom of the market, named support hours and a staging environment at the top. Prices and plan contents below were read on 1 September 2026 from each seller’s own plan page. Where a seller sets a price out in separate pieces, the quotation reassembles it the way the page displays it and changes no figure. Every one of them is volatile and every one of them is worth reopening before you sign anything.
| Seller and plan | Published monthly | What the list names | What it does not name |
|---|---|---|---|
| WP Buffs, Maintain | ”$89.00 USD / Month”, read 1 Sep 2026 | Weekly WP Updates, 24/7 Emergency Support, 24/7 Uptime Monitoring, Cloud Backups (4x Daily) | Edits to the site |
| WP Buffs, Protect | ”$179.00 USD / Month”, read 1 Sep 2026 | Everything above, plus 24/7 Unlimited Website Edits and Security Optimization | Speed or store work |
| WP Buffs, Perform | ”$239.00 USD / Month”, read 1 Sep 2026 | Adds Speed Optimization, e-Commerce Plugin Management, Complete Malware Removal | Staging, hosting |
| WP Buffs, Custom | ”$359.00 USD / Month”, read 1 Sep 2026 | Adds Safe Updates on Staging, Custom Functionality Monitoring, Pantheon, AWS or VPS Hosting | Changes to code you wrote yourself |
| FixRunner, Premium | ”$69/month”, minimum 3 months, read 1 Sep 2026 | ”90 minutes support”, core, plugin and theme updates, cloud backups, security scan | Phone support, a named contact |
| FixRunner, Advance | ”$169/month”, minimum 3 months, read 1 Sep 2026 | ”240 minutes support”, a dedicated account manager, phone support | Anything past the minutes |
| FixRunner, Small (enterprise) | “$300/month”, minimum 3 months, read 1 Sep 2026 | ”8 hours support”, priority support, two cloud backups a day | Anything past the hours |
| FixRunner, Medium (enterprise) | “$500/month”, minimum 3 months, read 1 Sep 2026 | ”12 hours support”, four cloud backups a day, advanced speed optimization | Anything past the hours |
| Jetpack, Security | ”$19.95 /mo” billed yearly, “$9.95” for the first year, read 1 Sep 2026 | Real-time cloud backups, unlimited restores, website firewall, real-time malware scanning, 30-day activity log | Anybody’s time |
| Jetpack, Complete | ”$49.95 /mo” billed yearly, “$24.95” for the first year, read 1 Sep 2026 | VaultPress Backup with 1TB storage, Scan with WAF, and the rest of the bundle | Anybody’s time |
| Elementor, care plans | No plan price rendered, read 1 Sep 2026 | Tier names and per-feature value labels | A price anybody is charged |
| WP Tech Support | No price rendered, read 1 Sep 2026 | Three tier names and a route to a quote form | Any currency figure at all |
Read the four rows at the top as one ladder and the shape of the market shows. WP Buffs’ bottom tier at wpbuffs.com/plans/ is scheduled work with an emergency line attached. Its second tier adds unlimited website edits, which is the first moment on that page where you are buying a person rather than a job queue. FixRunner, at fixrunner.com/plans/, does the same thing in the opposite order: it publishes the person first, as a number of minutes, and lets the scheduled work ride along behind. Its small-site ladder runs across three tiers, from $69 a month to $169 a month on the 1 September 2026 read, and the two ends are the ones named in the table.
Jetpack is in the table for contrast rather than as a competitor. Jetpack’s pricing page sells backups, malware scanning and a firewall as software you switch on, at “$19.95 /mo” billed yearly for Security with the first year marked at “$9.95”, and “$49.95 /mo” for Complete with the first year at “$24.95”. Nobody is included. When a care seller charges more than that for a list of similar-sounding features, the difference is a human being, and that is the only comparison between the two rows that means anything.
Then there is the average cost of website maintenance, which three separate searches ask for and which would be the least useful number on this page. The cost of website maintenance does not average well. Each seller is pricing a different amount of a person, in units of its own choosing, against a site type of its own definition. An average of a minutes-based plan, an unlimited-edits promise and a software bundle produces a figure that describes none of them and predicts nothing about your bill. The useful comparison is narrower and it is in the next section.
How much website maintenance costs per month, and what the month contains
Monthly website maintenance cost runs from $69 on FixRunner’s entry plan to $359 on WP Buffs’ top tier, read 1 September 2026. The number itself matters less than its unit. Some plans sell tasks done on a schedule. Others sell minutes of somebody’s attention. Only one of those two runs out.
Every seller on this search quotes website maintenance cost per month rather than per year or per job, so the monthly figure is the one you will be handed to compare. What that month contains is published in three different units by three sellers. FixRunner counts minutes: “90 minutes support” on its entry small-site plan, “240 minutes support” on the top one, then “8 hours support” and “12 hours support” on its two named enterprise tiers. WP Buffs counts nothing at the bottom and then promises “24/7 Unlimited Website Edits” from its second tier upward, which is a different kind of commitment and a harder one to compare. Jetpack counts no labour whatsoever, because it is selling software.
If you are holding two quotes, the thing worth comparing is the time. A plan with a published minute count tells you exactly where the month ends. A plan without one is either more generous or less, and the page will not say which. Ask any seller who publishes neither how a month is measured on their side, and what happens on the day it runs out.
A note on the minutes, since it is tempting: dividing a plan price by its published minutes does not produce a rate you can hold anybody to. The minutes are what the plan includes, not what an hour costs, and the two answer different questions.
There is also the month where the number is zero. Nothing expired, nobody updated anything, no customer wrote in. On a site that changed last in March, that is most months. A plan charges the same in those months as in the one where a payment path stopped working on a Friday, which is the actual argument for and against paying monthly at all. Whether a monthly arrangement beats paying for each job is a decision with its own rule, and it is not settled by the size of the site.
One frame you will meet on the ranked pages cannot be made to work here. A share of what the site cost to build cannot answer this, because nobody who does the work prices it that way. The plans read for this page charge per site and per task, and the person doing the work charges for the hour they spend, so a bill that was settled a year ago has no vote in either.
The upkeep a site with logins, a database and payments generates
One owner runs the customer side of a property services business on software they built themselves. The word they use for it is website, and every plan page above would sell them one. What none of those pages would cover is the part that makes their site worth money to them: accounts that belong to different customers, records that have to stay apart, and a way to take payment that works on the third try as well as the first.
Below is one row per recurring job, marked against the three plan lists that publish their contents: WP Buffs, FixRunner and Jetpack.
| Recurring job | Named in a plan list read here | Free to do yourself | What it actually takes |
|---|---|---|---|
| CMS, plugin and theme updates | Yes, on the two care sellers | Yes, if you watch for them | Minutes, until one of them breaks a page |
| Certificate renewal | No, on none of the three | Yes, automatic on most hosts | Nothing, until a renewal job stops quietly |
| Backups | Yes, on all three | Yes, most hosts include them | The restore is the part nobody tries |
| Uptime checking | Yes, on the two care sellers | Yes, free tiers cover a small site | Minutes to set up, then nothing |
| Framework version bump that closes a known hole | Partly, as updates and a scan | Sometimes, if you read the notice | One version number, or a week |
| A database change that arrives with a feature | No | No | Somebody who can move data without losing it |
| A login rule that keeps one account out of another’s records | No | No | Somebody who can prove the rule holds |
| A payment path that still works on a refund and on a second attempt | No | No | Somebody who can test the cases that fail |
| An outside key or token that expires on somebody else’s calendar | No | No | A calendar note, and then a person |
As of 1 September 2026, none of the three plan lists read for this page names any of the last four rows. Not in a feature bullet, not in a tier description, not as an optional extra. A bullet that is absent does not prove the work is excluded, since WP Buffs lists e-Commerce Plugin Management and Custom Functionality Monitoring and FixRunner sells support hours that could be spent on anything, so read it as coverage that is unconfirmed and ask the seller, in writing, which stack and which custom code and payment work the plan covers. The sellers deserve no criticism for that: they publish plans for a content management system and describe what those plans do, accurately. The gap is a mismatch between what is on sale and what a site with customers in it actually generates.
Certificate renewal is missing from all three lists as well, which surprises people who assume it is the first thing a care plan does. The only place it turns up on any of those pages is inside one seller’s optional hosting extra, where a hosting partner supplies the certificate rather than the plan doing anything about it.
The fifth row is the one that moves between the halves. AxonBuild audited 26 real AI-built applications across June and July 2026, checking every finding against the code as written rather than pattern-matching it, and in 8 of the 21 applications built by other people, the framework version in use carried a publicly documented hole that the application’s own code could reach. The repair in most of those cases was moving a single version number. How the 26 were selected and how each finding was confirmed is set out separately. A care plan’s weekly update run would close some of those, silently, on somebody else’s schedule, which is the honest argument for paying for one.
It is also the argument against doing it casually. An update that closes a hole and an update that takes the site down look identical the day before. What to do when the routine update is the thing that broke the site is a recovery sequence rather than a budget line, and it is the reason the top tier on one of the plan pages above charges extra for staging.
Which of these jobs turn up whether or not anybody touches the thing is a list worth reading before agreeing to any monthly figure, and it is written out in full elsewhere.
What you can do yourself for nothing, and what you cannot
Four of the nine rows above are genuinely free for a small site. Certificate renewal happens on its own on most hosts and has done for years. Checking that the site is still answering costs nothing on a free tier, and what an outside check is worth to a founder-sized site, and which free tiers cover one is settled elsewhere rather than priced again here. Backups are usually included with the hosting you already pay for. Updates are a button, on a schedule you set.
If your site is a set of pages that tell people what you do, that list is close to the whole job. Paying anybody a monthly figure for it is a convenience purchase, and a defensible one if you would otherwise never open the dashboard, but it is a convenience purchase.
What does not go to zero is the judgement. On an AI-builder community thread, somebody explained why they were considering moving their site onto something else, and the reason had nothing to do with what either option charges:
I am planning to migrate my old WordPress site to Base 44 so I can manage it easily in the future… Any pitfalls or caveats that I should be aware of before I migrate?
What they are pricing there is the work rather than the invoice. That is the half of this question no plan page answers, because the amount of your own week a site consumes is not a line item anybody sells.
Two things in particular refuse to be free. The first is the hour somebody spends when a payment path stops working at the wrong time, which is always the wrong time. Nobody talks their way through that with a plugin update. The second is the update a bot opened overnight that nobody on your side can safely approve. The change looks small, the notes are written for people who already know the system, and merging it is either five minutes or the start of a bad week. Deciding which costs the same either way, and the deciding is the expensive part.
A reasonable middle exists and almost nobody describes it: do the four free rows yourself, and pay a person by the job for the rest, when the rest happens.
What the packages sold as website maintenance services cost
Packages sold as website maintenance services cost from FixRunner’s “$69/month” entry plan up to WP Buffs’ “$359.00 USD / Month” top tier, both read 1 September 2026. Some of what is inside them is software you could buy directly. The rest is somebody’s time, and the time explains the gaps.
Take the software half first. Backups, malware scanning and a firewall are all products with their own published prices, which is exactly what Jetpack’s two plans in the table above are. Both care sellers on this page put some version of that list inside their plans. That does not mean the care plans are overpriced, but it does mean that when two packages sit far apart on price and both feature lists mention backups and scanning, the backups are not where the difference went.
The time half is where the packages actually differ, and it is described in three incompatible ways: published minutes, an unlimited-edits promise, and named support hours at the enterprise tiers. A package that names hours is telling you the truth about its own limits. A package that names none is asking you to trust a queue.
Then there is the part of the market that publishes nothing. As of 1 September 2026, Elementor’s care plans page does not render a plan price to an automated read; the page at elementor.com/care/ carries per-feature value labels inside its feature lists and no plan price anywhere, including in the page source. As of 1 September 2026, WP Tech Support’s plans page does not render a price to an automated read either; wp-techsupport.com/ names three tiers and routes to a quote form, with no currency figure in the source at all. A third seller’s plans page, at wpsitecare.com/plans/, refused an automated read on 1 September 2026 both rendered and raw, so nothing here is claimed about what it charges. Of the six pages opened for this article, three publish a monthly number and three do not. When a buyer’s guide hands you a tidy range for this market, ask which pages it actually read.
When the design and the upkeep are sold together
Website design and maintenance cost is usually quoted as one figure, and the single figure is the problem. Two of the sellers read here fold hosting into their upper tiers: WP Buffs names “Pantheon, AWS or VPS Hosting” only at its top tier, and FixRunner offers premium hosting and one-click staging as options on its upper small-site plans. Once hosting is inside the number, the number stops being comparable to anything.
A bundled quote hides which half of the money is the site and which half is the person. That matters because the two halves renew on completely different clocks. The site is made once and then only changes when you ask. The person is paid every month whether you ask or not, and the day you stop asking is the day the monthly figure starts buying scheduled tasks you could have run yourself.
Ask any bundled quote to split into three lines: what it costs to make, what it costs to keep somewhere, and what it costs to have a person available. The three move independently. If the seller will not split them, that is information too.
Making the site in the first place is a separate market with its own published packages, and no figure from it is repeated on this page. If the site is not published anywhere yet, getting one to a real address that other people can open comes before any of this.
Four charges people file under maintenance that are counted somewhere else
Four costs turn up in maintenance conversations and belong to other invoices. Sorting them out first is usually worth more than negotiating the monthly figure.
The machines send an invoice of their own every month, the hosting plan and the database and every outside service the site calls, and not one dollar of it is counted anywhere on this page.
The build is the second. The build invoice and the upkeep invoice are written by different people on different clocks, and what a site costs to have made in the first place is priced from package bands that appear nowhere here.
The third is a single repair. When the job is one repair rather than a month of cover, it is priced by the hour or by the finished piece of work, and those published rates are collected on their own page. That is the arrangement most small sites actually need, a few times a year, rather than a standing monthly charge.
The fourth is not a website at all. Something people install from a phone store keeps a different upkeep calendar, because the two stores set the deadlines and nobody who owns the thing gets a vote, and that bill is counted on its own page.
One more thing, and it is not a charge at all. Finding the person is a different exercise from pricing the month, and what to have ready before anybody quotes is set out where that search lands.
Where all of this ends up for most owners of a small live site is a short list of real problems rather than a subscription. AxonBuild works that way: a free 20-minute video call with Bilal about the problem, then, if you want it fixed, a fixed quote after he checks the site, and payment after you see it working. Further fixes can follow the same way. For most small sites the honest pattern is a change now and then rather than a standing monthly bill.
Common questions about website maintenance cost
How much does website maintenance cost per year?
Neither care seller on this search publishes an annual price, so for them the yearly number is whichever monthly plan you picked, taken twelve times; Jetpack is the exception, sold as a monthly figure billed yearly with a lower first year. The published monthly figures read on 1 September 2026 were “$69/month” at FixRunner’s entry small-site plan and “$359.00 USD / Month” at the top of WP Buffs’ ladder, and FixRunner attaches a three-month minimum to its plans, so the shortest commitment on offer is a quarter rather than a year. Whatever the yearly total comes to, it covers no domain and no work outside the plan’s own list, and hosting only where a top tier names it, as WP Buffs’ Custom tier does.
What is a fair monthly price for looking after a small business site?
For a site that mostly sits still, fair is whatever the cheapest published plan costs, and often less than that, because most of what those plans do is already automatic on modern hosting. FixRunner publishes “$69/month” with a three-month minimum for its entry small-site plan, read 1 September 2026, and that is the floor of the published market on this search. Anything above it is buying a person’s availability, so the question becomes how often you actually need one.
Is a maintenance plan worth paying for if nothing on the site changes?
Usually not, with one exception. A site nobody edits still needs its software updated and its certificate renewed, and both of those happen on their own on most hosting. The exception is the site you would never check: if you would not open the dashboard for months at a time, a plan is buying you the fact that somebody else will.
Can I maintain my own site for nothing?
Mostly, for a site made of pages. Updates, certificate renewal, backups and an uptime check are all either automatic or covered by free tiers, which is four of the nine recurring jobs listed above. What you cannot do for nothing is the work that arrives once customers are inside the thing: a database change, a rule about who can read what, a payment that failed halfway. Those need a person, and they are bought by the job.
Does website maintenance include hosting and the domain?
On the ranked cost guides, yes, and that is why their numbers look large. GoDaddy’s guide at godaddy.com/resources/skills/website-maintenance-cost, dated 13 April 2026, and Network Solutions’ guide at networksolutions.com/blog/website-maintenance-cost/, dated 15 May 2026, both count domain renewal, hosting and an SSL certificate inside the maintenance figure, alongside updates and content work. The care plans in this article mostly do not: they price labour and leave the machines to whoever you already pay, with two exceptions, WP Buffs’ Custom tier, which names Pantheon, AWS or VPS hosting, and FixRunner’s optional hosting extra. What those lines add up to each month is worked out separately, and no small-site figure on this page includes any of them.
I call mine a website, but people sign in and pay through it. Which number applies?
Neither cleanly, and that is worth knowing before you sign. Every plan price on this page is written for a content management system holding pages, so it covers the updating and the backing up of your site and none of the work your accounts and payments generate. Price the plan for what it covers, then price the rest by the job. If yours is submitted to a store rather than published at a web address, the deadlines come from somewhere else again, and so does the number.
Why is website maintenance quoted by the hour on some pages and by the month on others?
Because they are selling two different things. A monthly plan sells availability and a set of scheduled tasks, priced per site. Buying by the hour sells a named piece of work, priced by how long it takes. Sellers who publish monthly plans tend to publish included time as well, which is the closest the two models come to being comparable: FixRunner publishes “90 minutes support” on its entry small-site plan and “12 hours support” on its larger enterprise tier, read 1 September 2026.
What happens if I stop paying for maintenance?
On a plan that sells labour only, the site keeps working, and then it stops being tended. Updates queue up, the backup schedule ends with the plan on most sellers, and any monitoring the plan provided goes with it. Nothing breaks that afternoon on that kind of plan. If the plan also supplied the hosting or the certificate, as a top tier or hosting extra can, check what happens to those on the plan’s own cancellation terms before you stop paying, because then the site can go down with the invoice. What changes is that the next update, the next expired key and the next thing a customer reports become yours to notice, and the gap between something going wrong and somebody finding out gets longer. Rocket.net’s guide at rocket.net/blog/how-much-should-you-pay-someone-to-maintain-your-website/, dated 29 January 2025, prices the same list of tasks by site type; whoever does them, the tasks do not go away when the invoice does.
Built it with AI. Can’t get the last part right?
That’s the normal state of an AI-built app, and it’s fixable. I trace what the app actually does, explain what needs changing, and build it if you want me to.
Talk about your app →
Free 20-minute video call with Bilal.