The short answer
WordPress maintenance is usually sold as a monthly plan, and the price depends on how much the plan covers, how complex the site is, and how quickly someone has to respond when something breaks. Our own WordPress website cost guide puts typical ongoing care at $75 to $300 per month for updates, backups, security monitoring and small changes. A store, a membership site or a site with custom code sits above that because there is more to test and more that can go wrong.
The mistake most buyers make is comparing two monthly prices without comparing what each one covers. A cheap plan that only runs updates and a fuller plan that includes a support allowance, uptime monitoring and a restore guarantee are not the same product, so the rest of this article is about what to look for behind the number.
What a maintenance plan includes
A complete WordPress maintenance plan covers six things: updates, backups, security, monitoring, performance checks and a way to request small changes. If a plan is missing any of these, the price may look good but you are still carrying the risk yourself.
- Updates. WordPress core, the theme and every plugin, applied on a schedule and tested afterwards, ideally on a staging copy first.
- Backups. Daily or more often for stores, stored somewhere other than the web server, with a tested restore process. Our guide on backing up a WordPress website explains what a good backup looks like.
- Security. Malware scanning, a firewall or login protection, and a plan for clean-up if the site is compromised. The WordPress security guide covers the basics a plan should enforce.
- Monitoring. Uptime checks that alert a person, plus a check that forms, checkout and other key pages still work after updates.
- Performance. A periodic speed check and clean-up of the database, unused plugins and oversized images.
- Support. A defined amount of developer time each month for small changes and fixes, with a stated response time.
For a task-by-task view of what maintenance involves, see the WordPress website maintenance checklist.
Basic, standard and full-care packages
Most providers, including us, group these tasks into three levels. The names differ but the pattern is the same: the more the plan promises to notice and fix without being asked, the more it costs.
| What is covered | Basic | Standard | Full care |
|---|---|---|---|
| Core, theme and plugin updates | Monthly | Weekly, tested on staging | Weekly, tested on staging |
| Backups | Weekly, off-server | Daily, off-server | Daily or hourly for stores, with restore drills |
| Security scanning and firewall | Included | Included | Included, plus clean-up if the site is hacked |
| Uptime monitoring | No | Yes | Yes, with checks on forms and checkout |
| Performance check | No | Quarterly | Monthly |
| Support time for changes | None, billed separately | A small monthly allowance | A larger allowance and priority response |
| Reporting | None | Monthly summary | Monthly report with recommendations |
| Best for | Brochure sites with few plugins | Most business sites | Stores, membership sites, custom builds |
A basic plan is genuinely enough for a small, simple site. The trouble starts when a store or a lead-generating site is put on a basic plan because it was cheapest; nobody notices the checkout error until a customer complains.
What moves the price
The price of a maintenance plan is driven by the amount of work needed to keep the site safe and the cost of being wrong, not by the size of your company. These are the factors that change the quote:
- Number of plugins. Every plugin is another update to test. A site with forty plugins takes several times longer to check than a site with ten.
- Custom code. A custom theme or plugin has to be checked against each WordPress release. Well-built code needs little; hastily built code needs a lot.
- WooCommerce or memberships. Payment, tax and shipping extensions update often and break loudly. These sites need staging tests and more frequent backups.
- Traffic and hosting. High-traffic sites need closer performance monitoring, and cheap shared hosting creates problems a plan has to work around.
- Response time. A promise to respond within hours costs more than a promise to respond within days, because someone has to be available.
- Included support time. Plans that bundle developer hours cost more but usually work out cheaper than paying for small jobs one at a time.
- Compliance needs. Sites handling health, legal or donor data need tighter logging, access control and update discipline.
Monthly plan, hourly or pay-as-you-go
A monthly plan is the right model for any site that earns money or collects personal information; pay-as-you-go only makes sense for a site you would not mind being offline for a few days. The table compares the three ways people pay for maintenance.
| Model | How it works | Where it fits | The catch |
|---|---|---|---|
| Monthly plan | A fixed fee covers scheduled work plus a support allowance | Business sites, stores, anything that must stay up | You pay in quiet months too |
| Hourly retainer | You pre-buy a block of hours and use them as needed | Sites with frequent changes and an in-house admin | Nobody is watching between requests |
| Pay-as-you-go | You call when something breaks | Hobby sites and low-value brochure sites | Emergency work costs the most and comes with downtime |
Some businesses combine a monthly plan with a separate budget for larger improvements. That keeps the routine work predictable while bigger jobs are quoted on their own.
The cost of no maintenance
Skipping maintenance does not save the money; it moves the bill to a worse moment. The three costs that show up on unmaintained sites are a hacked site clean-up, an emergency rebuild after a failed update with no backup, and lost business while the site is down or slow.
Clean-up after a compromise is quoted as a project, often costs more than a year of a standard plan, and comes with a period where search engines may warn visitors away from the site. A failed update with no backup can mean rebuilding pages from scratch. Neither is rare; almost every emergency we take on starts with a site that had not been updated in months. If you are already in that situation, our guide to fixing a hacked WordPress site explains what to do first.
How to compare two quotes
Put the two quotes side by side and answer these questions for each. The cheaper plan is only cheaper if it answers them the same way.
- How often are updates applied, and are they tested on a staging site before going live?
- Where are backups stored, how long are they kept, and when was a restore last tested?
- Is uptime monitored, and who is alerted at 2 a.m.?
- What exactly happens if the site is hacked, and is clean-up included or extra?
- How much support time is included each month, and what is the hourly rate beyond it?
- What is the promised response time for an outage versus a routine request?
- Is hosting included, and if so, what kind?
- Can you cancel monthly, and do you keep all logins, backups and code if you leave?
That last point matters more than it seems. A plan should never make it harder to leave. You should own the hosting account, the domain, the backups and every password, and a good provider will say so in writing. Our guide to WordPress maintenance services goes deeper on what to expect from a provider.
One more practical tip: ask what happens during planned downtime. A provider who uses WordPress maintenance mode properly, with a staging copy for anything risky, is showing you how carefully they work.
Next step
If you want a number for your own site, tell us the platform, roughly how many plugins it runs, whether it sells anything, and how quickly you need a response when something breaks. We will recommend the lightest plan that covers the real risk and give you a fixed monthly price in writing. See our WordPress maintenance and support service or start on the contact page.