You are paying somewhere between $50 and $500 a month for website maintenance and you cannot name a single thing that happened last month. The site looks the same. Nobody sent you anything. The invoice arrives anyway, and asking what it covers has produced answers like "updates and monitoring" that tell you nothing you can check. So you have started to suspect you are paying rent on something that does not change. Before anyone defends that fee, including us, you should know that the industry itself does not agree it should exist. In one public thread on this exact question, two people who both build websites for a living gave completely opposite answers, and one of them charges nothing at all. That disagreement is the honest starting point, and it is a lot more useful to you than another price range.
Key Takeaways
In one public small-business thread on maintenance costs, one agency owner listed $195 a month for monthly maintenance, $295 for biweekly and $595 for a higher tier. Another replied that they also build websites and do not charge a monthly maintenance fee at all. Both are running real businesses.
Five of the eight page-one sources on this question are platforms or hosts. For reference, AWS Lightsail's cheapest published instance is $3.50 a month. That is a server, not a person doing anything.
It suggests checking for updates "at least every three months, six months at the most", housekeeping every three to six months, and backups three to twelve times a year. Minor and security updates have applied automatically in the background since version 3.7.
A plugin-heavy site has many moving parts that update independently and can break each other, so it genuinely needs watching. A statically exported site has no database and no plugins to conflict, so it genuinely does not.
A $300 fee with six named tasks and a cadence is judgeable. A $99 fee described as "updates and monitoring" is not, and that is the one to question first.
Start From the Fact That the Industry Cannot Agree This Fee Should Exist
When we ran this search, the discussions block surfaced a small-business thread about maintenance and management costs where two agency owners contradicted each other in the same conversation.
The first laid out a price list: "We charge $195/mo. for monthly maintenance, $295/mo. for biweekly maintenance, and $595/mo." The second replied: "I also run a business that builds websites. We do not charge a monthly fee for website maintenance."
Neither of them is a cowboy. They are describing different products for different kinds of site, and neither one said so, because on their own pricing pages they would each present their approach as the normal one. If you have only ever read one of those pages, you have only ever seen half of a genuine professional disagreement.
We build websites too, and we sell maintenance, so treat our opinion accordingly. What we can do is show you the mechanics that decide which of those two answers is right for your site, so you can work it out without trusting either of us.
Separate Your Hosting Bill From Your Maintenance Bill and the Floor Disappears
Here is the single most useful thing in this post, and it explains why the published ranges are so absurdly wide.
Of the eight sources on page one for this question, five are platform vendors or hosting companies. Their bottom figure, the "$5 a month" that anchors every range you have read, is the price of a server. It is not the price of anybody doing anything. For a sense of the real floor, AWS Lightsail's published pricing starts at $3.50 a month for its smallest instance and $5 with a public IPv4 address. That is raw compute. Nobody is watching it.
So when a range reads "$5 to $5,000 a month," that is not a distribution with an average in the middle. It is a hosting price and an enterprise support contract printed on the same line.
| The bill | What it actually pays for | Rough real cost | Who can do it |
|---|---|---|---|
| Hosting | A server, or a static host, keeping the files reachable | $0 to $25 a month for most small business sites | Anyone, once. It runs itself. |
| Domain and email | Your address, and a mailbox at it | $10 to $20 a year for the domain, plus mail if you use it | You. This one should be in your name, always. |
| Maintenance | A person doing named tasks on a stated cadence | $0 to $600 a month, depending entirely on what the site is | Somebody with access and a checklist |
Ask which of those three lines your monthly fee covers. If the answer is all of them and the number is $49, you are paying for hosting with a small margin and calling it maintenance. That is not fraud, but it is not maintenance either.
Know What Actually Has to Happen, and How Often
This is checkable, and the answer is less dramatic than most maintenance pages suggest. WordPress's own site maintenance documentation sets out a recommended cadence, and it is worth reading because it is the platform's own advice rather than a vendor's.
It recommends checking in for updates and upgrades "at least every three months, six months at the most." It suggests the housekeeping routine, cleaning out old plugins and similar, "typically every three to six months." It suggests scheduling backups "three to twelve times a year." Dead link checks it puts at every six months to a year. The one thing it says to do monthly is check your site statistics.
Notice what that is not. It is not a monthly emergency. And on the update question specifically, the updating WordPress documentation is explicit that since version 3.7, "you don't have to lift a finger to apply minor and security updates," because most sites apply them automatically in the background. You still click for major feature releases, and you should still back up before you do.
Two honest caveats, because that documentation is general and your site is specific. First, its cadence assumes a fairly plain site; a plugin-heavy one with a shop, a booking system and a form builder has far more that can break, and those break each other. Second, "updates apply automatically" is exactly why some sites break without anybody touching them: an automatic update to one component can conflict with a plugin that has not been maintained in two years. That is the real argument for someone watching, and it is a much better argument than "hackers."
Find Out Whether Your Site Needs Monthly Attention At All
This is the question Google's own suggested questions surface on this search, and the honest answer is that it depends almost entirely on what your site is built from.
A site assembled from a content system, a theme and fifteen plugins has fifteen independent vendors shipping code into it on their own schedules. Any one of them can change something that breaks something else, the database can accumulate junk, and a plugin whose author quietly stopped maintaining it becomes a genuine problem rather than a theoretical one. That site needs somebody looking at it monthly, and $195 for that is a fair price for real work.
A site exported to static files has no database, no plugins, no admin login and no server-side code running when a visitor arrives. There is nothing for an automatic update to break, because there is nothing updating. Sites like that need a backup of the source, a domain renewal you must not forget, and somebody available when you want a change. Charging a monthly retainer for watching a site that cannot break is the thing the second agency owner in that thread was refusing to do, and they were right to refuse it.
So work out which one you have before judging the fee. If you are on a plugin-driven site, a monthly retainer is buying you something. If you are not, ask what the monthly work consists of, and be prepared for the answer to be thin. This is one of the practical, unglamorous differences behind the platform versus custom build question, and it shows up on your bank statement every month for years.
Get an Itemised Fee So You Can Judge the Price Yourself
The reason a maintenance fee feels arbitrary is almost never the amount. It is that "updates and monitoring" is not a thing you can check happened. Here is what a fee should name, so that you can.
What a fair maintenance fee names, and what it should tell you
Which components were updated and when. On a plugin site this is the core of the work. Ask for the log, not the reassurance.
A backup nobody has ever restored is a hope, not a backup. The question to ask is when they last restored one and how long it took.
Knowing the site is down at 2am is only worth something if somebody is going to do something about it. Ask what happens next, and how fast.
On a plugin site, promptly applying security releases and removing logins for people who left. This is where most real incidents actually come from.
The most valuable line for most owners. An hour or two a month of actual changes, with unused time either rolling over or not, stated either way.
Two paragraphs saying what was done and what needs deciding. Not a 14-page automated PDF nobody opens.
Add up what that would take on your site in hours and multiply by a rate you would consider fair. That is your own estimate, and you can now compare it with the invoice. If your estimate comes out at twenty minutes a month, you have your answer, and if it comes out at three hours, you have a different one.
Keep the Ability to Leave, Whatever You Decide to Pay
There is one thing worth more than getting the fee right, and it is not price at all.
Check whose name the domain is registered in. Check whether you have an administrator login to your own site and your own hosting. Check whether you could get a copy of the site and the content today if you asked. And check what the notice period is on the arrangement.
A maintenance retainer becomes something else entirely when leaving it means losing your site. If the domain is in the provider's account, if there is no login in your name, or if the only copy of the site lives somewhere you cannot reach, then the monthly fee is not really buying maintenance. It is buying continued access to your own property, and that is the arrangement worth ending regardless of the number on it.
A provider who is doing real work has no reason to hold any of that, and will hand it over without a conversation. Ours ends up in accounts registered to you as a matter of course, because a fee that survives only because leaving is hard is not a fee we would want to defend.
Is your maintenance fee buying anything?
1. Can you name three things your provider did to your site last month?
2. What is your site built on?
3. When was a backup of your site last restored, as a test?
4. Does your monthly fee include any actual edit or content time?
5. Is your domain registered in your name, with a login you hold?
Pick an answer to begin.
If you answered the second question with "a lot of plugins and a shop," a monthly fee is probably fair and the thing to fix is the reporting. If you answered it with "static files" and the rest of your answers were in the lower options, you are paying for watching that nobody needs to do.
Frequently Asked Questions About Website Maintenance Costs
Is it costly to maintain a website?
For most small business sites, genuinely not. Hosting can be under $25 a month and is sometimes free for a static site, a domain is $10 to $20 a year, and the labour depends entirely on what the site is built from. The expensive version is a plugin-heavy site that needs monthly human attention, and even then $195 to $300 a month covers real work. If you are being quoted more than that for a brochure site, ask what the hours are going into.
How much does it cost to hire someone to maintain a website?
Published figures run from $75 to $300 a month for small business care plans, with the public example in that agency thread at $195 for monthly and $295 for biweekly attention. Above roughly $600 a month you are usually paying for development time rather than maintenance, which is fine as long as it is labelled that way. Below about $75 you are usually paying for hosting plus automated update software.
Do websites need monthly maintenance?
Some genuinely do and some genuinely do not, and it comes down to how many independently updating parts the site has. WordPress's own documentation recommends checking for updates every three to six months rather than monthly, and applies minor and security updates automatically. A site with a shop, a booking tool and a dozen plugins needs more than that. A statically exported site with no database and no plugins needs a backup and a renewal reminder.
What does website maintenance include?
It should include a named list: updates with a log, backups that have been restore-tested, uptime monitoring with a response commitment, security patching, a stated amount of edit time, and a short readable report. If a plan will not name those, the price is not the problem with it. Anything beyond that list, like content writing or design changes, is separate work and should be priced separately.
Can I just not pay for maintenance?
On a static site, largely yes, provided you keep the domain renewed and hold a copy of the source. On a plugin-driven site it is a real gamble, because the failure mode is not a slow decline but a site that stops working after an update conflict, usually at an inconvenient moment. The cheapest honest middle ground is paying for updates and backups only, and buying changes hourly when you need them.
Is a website maintenance plan worth it if I never change anything?
If you never change anything and your site is static, no. If you never change anything and your site runs on plugins, yes, and the reason is the opposite of what you would expect: a site nobody touches is more likely to break, because its components keep updating around unmaintained parts. The never-changing site is the one where nobody notices the problem for three weeks.
Moving Forward
The industry does not agree that a monthly maintenance fee should exist, and that is the most honest thing anybody can tell you about the price. One agency owner charges $195 to $595 a month, another charges nothing, and both are right about the sites they build. The published range of $5 to $5,000 collapses the moment you separate the three bills, because the floor is a server at $3.50 a month and the ceiling is an enterprise support contract. WordPress's own documentation recommends a slower cadence than most retainers imply, and applies security updates by itself. What is left as real work depends on how many independently updating parts your site has, and that is something you can find out today.
Once you can name the six things a fee should cover, this stops being a leap of faith. You can hold any plan against your own estimate of the hours, ask for the update log instead of the reassurance, and either agree the price or renegotiate it with something specific to point at. Owners who can do that pay less and get more, not because they haggled, but because a specific question gets a specific answer.
If you want a straight read on what you are paying now, send us the plan and tell us what your site is built on, and we will tell you honestly whether it needs monthly attention or a renewal reminder. At Web Leveling we build static, hand-coded sites precisely because there is less to maintain, and our maintenance is an itemised list with edit time in it rather than a watching fee. Tell us what is happening and we will reply in plain English within one business day. Your domain, your hosting and your site stay in accounts registered to you, so nothing you pay us each month is payment for continued access to your own property.
Terms
What the words on a maintenance plan mean
Tap a term to see what it means.
Hosting. The server or service that keeps your files reachable. A cost of existing online, not a service anybody performs monthly.
Core update. An update to the content system itself. Minor and security ones apply automatically on WordPress; feature releases need a click and a backup first.
Restore test. Actually restoring a backup to check that it works. The difference between having backups and having recoverable backups.
Uptime monitoring. Automated checking that the site responds. Worth only as much as the response commitment attached to it.
Static export. A site delivered as plain files with no database or plugins running. Far less to maintain, and far less that can break on its own.
Care plan. A common name for a maintenance retainer. Look for the task list underneath the name, because the name means nothing on its own.