← Blog

WordPress maintenance plan cost: what a good plan includes

For owners and directors comparing care plans: what a WordPress maintenance plan must include, how to check backups and response times, and what each price band should cover.

Get a summary withChatGPT Claude Google AI Mode
A glass lantern lighting a row of calm dials, picturing a WordPress maintenance plan cost and coverage at a glance
On this page

You want a WordPress site that stays up, stays updated and never asks for your attention. A good care plan delivers that. The difficulty is that proposals look alike, and the WordPress maintenance plan cost varies widely for reasons the quote rarely explains.

This guide is for owners, directors and heads of marketing or operations who run a brochure site, a WooCommerce store or a membership site and are comparing plans. You will learn what a complete plan includes, five checks that let you compare any proposal line by line (scope, tested backups, response times, the monthly report and price), and what moves the price.

The short answer: a complete WordPress care plan covers updates, backups that have been restored in a test, uptime and security monitoring, fixes after a bad update and a written monthly report. The price follows your site type and how much revenue depends on the site.

Key takeaways

  • A complete plan has five parts: updates, tested backups, uptime and security monitoring, fixes and a monthly report.
  • A backup only counts once someone has restored it, so ask for the date and result of the last restore test.
  • A reply in two hours and a fix in two hours are different promises, so ask for both in writing.
  • Price follows site type, revenue at risk, response window and plugin count, which lets you place any quote.
  • The monthly report is your proof that the plan is working, so ask for a sample before you sign.

What a WordPress maintenance plan includes

A WordPress maintenance plan is a monthly service that keeps your site updated, backed up, watched and repaired, and tells you in writing what it did. Each part protects something you care about: the enquiries your forms bring, the orders your store takes, the members who log in. When one part is missing, the gap shows on the worst day.

The five parts of a complete plan

Updates come first. WordPress core, your theme and each plugin release new versions, often to close security holes. A plan applies them on a schedule, so your site never falls months behind and each change is checked before visitors see it.

Backups come second. A backup is a copy of your database and files that lets you go back to an earlier day. A good plan stores copies away from the server that runs your site and proves they restore.

Monitoring is the third part. Uptime monitoring checks every few minutes that your site answers. Security monitoring watches for changed files, malware and suspicious logins. You hear about a problem from an alert, not from a customer.

Fixes are the fourth part. When an update breaks a form, a menu or a checkout, a named person repairs it. Cheap plans often leave this out, and it is the part you will want most.

The report is the fifth. A written monthly report lists what was updated, restored, blocked and flagged, and what needs your decision. You can see what a monthly report contains before you sign anything.

Use this list as a filter on any proposal. If an item is missing, ask whether it is included, billed apart or not offered.

  • Core, theme and plugin updates, applied on a staging copy first
  • Backups stored off the server, with a restore test you can see
  • Uptime and security monitoring with alerts that reach a named person
  • Fixes after a bad update, inside the plan or at a stated hourly rate
  • A reply time and a fix time, in writing
  • A written monthly report
  • A named person who knows your site

Think of the plan as a night watchman: it walks the same rounds every day, and you hear from it only when something needs you.

A lantern glowing over a row of small house-shaped windows, picturing a site watched around the clock
A watchman's lantern over a row of lit windows

Plan types side by side

Three kinds of offer share the same name. A WordPress website monitoring service watches your site and alerts you. An updates-only plan applies new versions. A full WordPress care plan does both, then adds restores, fixes and reporting. The table shows what each one covers.

PartMonitoring onlyUpdates onlyFull care plan
BackupsRarely includedSometimes, taken before updatesScheduled, off the server, restore tested
UpdatesNot includedCore, themes and plugins appliedApplied on a staging copy first, then live
MonitoringUptime alerts, sometimes security scansNot includedUptime, security and speed
FixesAlert only, you find a developerBilled apartInside the plan or at a rate stated in writing
ReportAlert logRarelyWritten monthly report

Monitoring alone suits you if a developer is already on call. Updates alone suit a site with little revenue at stake. When the site brings in enquiries or orders, the full column is the one to compare.

Backups you have seen restored

A backup is worth what it restores. Many sites learn that a backup file is incomplete on the day they need it. Ask for a restore test and its result, and a hope becomes a date.

The WordPress backup documentation (opens in a new tab) explains that a site has two parts to protect: the database, which holds posts, pages, orders and settings, and the files, which hold themes, plugins and uploads. A plan has to copy both.

How often and where backups are stored

Frequency follows how often your site changes. A brochure site edited weekly is covered by a daily backup. A store or membership site writes to its database all day, so backups run more often.

Storage matters as much. Keep at least one copy away from the server that runs your site, because a server failure or an attack can take a backup stored beside it. Ask how many days of copies are kept: thirty days lets you go back past a problem that went unnoticed for a week.

Hosting backups are a useful base. Check what they cover, how long they are kept and who restores them, since many are restored by you through a control panel and come without a test. A plan for WordPress backups and monitoring adds the person and the proof.

A restore test in four steps

A restore test proves the copy works. It runs on a staging copy, a private duplicate of your site that visitors cannot see, so your live site stays untouched.

  1. Take the latest backup

    Pick the most recent copy from the off-server storage, the one you would really use on a bad day.

  2. Restore it to staging

    Load the files and the database into the private copy, never into the live site.

  3. Check what earns money

    Open the home page, send your main form, place a test order or log in as a member.

  4. Write down the result

    Record how long the restore took and any gap, such as missing images or lost orders, then fix the cause.

Ask how often the test runs. Quarterly is a reasonable rhythm for a brochure site, and monthly suits a store. The result should reach you in writing, with the time it took, because that number is how long you would wait on a bad day.

What WooCommerce and membership sites add

Restoring a backup from yesterday removes today's orders and sign-ups from your site, although your payment provider still holds the charges. For these sites, ask three extra questions. How often is the database alone copied? How are orders written between backups recovered? Does the restore test include a test order or a login?

Updates on staging and monitoring that watches

Updates are where most breakages start, and monitoring is how you learn fast when one slips through. Together they decide whether you hear about a problem from an alert or from a customer.

Why updates go to a staging copy first

Plugins are written by many independent authors, and the WordPress Plugin Handbook (opens in a new tab) shows how each release is versioned and maintained on its own schedule. One plugin's update can change how another behaves. On a staging copy, the agency applies the update where visitors cannot see it and checks the pages that earn money before anything reaches your live site.

The order matters: backup first, update on staging, check key pages and your checkout or login, then go live with monitoring watching and a rollback ready. The diagram shows the path of one update.

One update's path

  1. 01Backup takenA restore point before anything changes
  2. 02Update on stagingApplied where visitors cannot see it
  3. 03Key pages checkedCheckout and login still work
  4. 04Goes liveReleased once checks pass
  5. 05Monitoring watchesAn alert fires if something slips
  6. 06Monthly reportYou see what was updated

Flow of one WordPress update: backup, staging update, key page checks, go live, monitoring and report, with a rollback if a check fails

How one update reaches your live site safely

Ask which pages are checked. A good answer names them: your home page, your main form, the cart and checkout, the login. An answer such as "we test it" tells you little.

What uptime and security monitoring should watch

A WordPress website monitoring service is only as useful as what it watches. Look for these items in the proposal:

  • Uptime checks every few minutes on the pages that matter, looking for the content you expect, and not only for a reply from the server.
  • Certificate and domain expiry, because an expired certificate shows visitors a warning page.
  • Security signals: changed files, malware scans and bursts of failed logins. The WordPress hardening guide (opens in a new tab) lists protections such as updated software, strong credentials and limited user permissions, and a plan should apply them.
  • Speed on key pages, so a slowdown at checkout shows up before your sales do.
  • Alerts that reach a named person who acts, rather than an inbox nobody reads.

Abandoned plugins and what to do about them

Some plugins stop receiving updates when their author moves on. No schedule can patch that, so a good plan flags the plugin in the report. The plugin's page in the WordPress.org directory shows when it was last updated and which WordPress versions it was tested with.

You then have three options: a maintained replacement, a small custom plugin for the one feature you use, or removal if the feature no longer earns its place. Your agency should bring the options and a cost, and you choose.

Response times and who fixes a breakage

Response time decides whether a breakage costs you an hour or a day. Plans use the same words for different promises, so read them closely.

Reply time versus fix time

A reply time is how fast a person acknowledges your message. A fix time is how fast the problem is resolved. Many plans promise the first and leave the second open.

Two promises

A reply in two hours and a fix in two hours are different promises. Ask for both in writing, and ask whether a repair after an update is inside the plan.

Ask how each changes between business hours and nights or weekends. A store that sells around the clock may justify out-of-hours cover. A brochure site whose enquiries arrive by form usually does well with business-hours cover, since a form can wait until morning. Cover at all hours costs more because someone has to be on call.

Also ask who answers: a named person who knows your site, or a ticket queue. For the broken-update case in detail, see who fixes broken updates.

Fixes inside the plan or billed by the hour

The most important price question is whether repairing a bad update is included. Plans fall into three groups: repairs inside the plan, repairs from a monthly pool of hours, and repairs billed apart at an hourly rate. None is wrong, but each changes your real monthly cost.

A low sticker price with hourly repairs can cost more in the month an update breaks your checkout. Ask for the hourly rate in writing. Ask what counts as a repair and what counts as a new request, such as a new page or feature, which is usually quoted separately.

WordPress maintenance plan cost by site type

WordPress maintenance plan cost follows what your site earns and how much work it takes to look after, more than its page count. This section gives relative bands, because market ranges shift by region and scope and we will not hand you a figure we cannot source. For current werun.dev prices, see plans and pricing.

Place your site in one of three groups, then read the proposal against it.

Lower band

Brochure site

Few plugins, a contact form and perhaps a blog. A breakage costs enquiries, not orders. Expect updates, backups, uptime monitoring and a report, with business-hours replies.

Middle to upper band

WooCommerce store

More plugins for payments, shipping and taxes, and orders written all day. Expect frequent database backups, staging checks on cart and checkout, and a tighter response window.

Upper band

Membership site

Logins, protected content, payments and often custom code. Expect restore tests that include a login, checks on member areas and clear terms for fixing custom plugins.

What moves the price up or down

Two plans for the same type of site can differ because of these factors:

  • Revenue at risk: the more orders or enquiries depend on the site, the tighter the checks and replies.
  • Response window: business hours cost less than round-the-clock cover.
  • Plugin count and kind: custom, heavily configured or abandoned plugins add work.
  • Backup frequency and retention: hourly database copies and long retention cost more than daily copies.
  • Included hours: a pool of repair hours raises the price and lowers the surprise bills.
  • Depth of testing: five key pages checked on staging take less time than a full checkout and login routine.

A worked example with illustrative numbers

Take a store that takes $1,500 a day in orders. An update breaks checkout at 9 in the morning and nobody notices until mid-afternoon. About half a day of orders, roughly $750, is at risk, before counting ad spend sent to a broken page and customers who do not return. These numbers are illustrative.

The method is real: divide your daily revenue by the hours you trade, and you see what an hour of downtime costs. A plan that catches the break within minutes is priced against that figure, not against the cheapest line on a roundup.

When a smaller plan is enough

If your site has a few pages and a contact form, rarely changes and brings occasional enquiries, a lighter setup can be the better buy. A host with daily backups kept off-site, automatic minor updates, a basic uptime alert and a quarterly check by someone you trust may be all you need.

Step up to a full plan when the site starts to feed sales, when you add a plugin that handles payments or personal data, or when nobody on your team can restore the site. If you are unsure which side of that line you are on, the questions in the next section settle it.

Questions and red flags before you sign

The five checks are scope, tested backups, response times, the monthly report and price. The ten questions below cover all five. Send them to every WordPress maintenance agency you consider, and compare the written answers in one afternoon.

Ten questions to put in writing

  1. Which parts are included: updates, backups, monitoring, fixes and a report?
  2. How often are backups taken, where are they stored and for how many days?
  3. When was the last restore test, and can I see the result?
  4. Are updates applied on a staging copy first, and which pages are checked?
  5. What are the reply time and the fix time, in business hours and outside them?
  6. Who answers: a named person or a queue?
  7. Is repairing a bad update inside the plan or billed apart, and at what hourly rate?
  8. What does the monthly report contain, and can I see a sample?
  9. Who owns the site, the code and the accounts if I leave?
  10. How are abandoned or conflicting plugins handled?

A short written answer beats a long call. If you are still deciding who should run the plan, see freelancer vs agency for website maintenance.

Red flags in a proposal

These signs mean the plan promises more than it delivers:

  • Backups are listed without saying where they are stored or whether they are tested.
  • Fixes are unlimited, with no definition of what counts as a fix.
  • Round-the-clock cover is promised with no named person and no phone path.
  • Updates go straight to the live site.
  • There is no report, or the report is only a list of alerts.
  • Security is guaranteed, although no plan can promise that nothing will ever go wrong.
  • You would have no access to your own site, accounts or code.

A red flag is a reason to ask, and a clear written answer can settle it.

How the werun.dev Care plan works

The werun.dev Care plan is our monthly maintenance plan for WordPress sites. We look after 200+ sites and have kept sites up for 12+ years, and the plan follows the five checks in this guide. To see how it sits next to one-off projects, read how engagements work.

What is watched and fixed each month

Your site is watched for downtime and security signals. Updates are tried on a copy first and then applied to the live site. Backups are checked, so going back to yesterday takes minutes.

When an update breaks something, a person you know by name repairs it. When you want a change, you click the element on your site with Client Feedback and describe it, and the request reaches the team. Our tools cost $0 on the sites we run.

The monthly report you receive

When the month closes, you get a written report: what was updated, what was fixed, what was flagged and what we recommend next. Requests and invoices sit in the Client Portal, so you check progress without asking.

The report is your proof. If a month was quiet, it says so. If a plugin is abandoned, it says that too, with options and a cost.

Replies in under 2 hours on business days

You get a reply in under 2 hours on business days, from a person you know by name. For a repair, we tell you in writing what we found and what it takes.

If you already have a plan, send it to us. We read it against the five checks and tell you what we find, whether or not you move. Sometimes the answer is that your current plan is fine.

Where to start this week

Start with two numbers and one email. They take under an hour and tell you more than any proposal.

  1. Write down what your site earns per day: orders, or enquiries multiplied by what each is worth.
  2. Email your current provider and ask for the date and result of the last restore test and the last monthly report.
  3. Send the ten questions to each agency you are comparing, and line up the answers.

If the answers are thin, tell us your goal: more orders, fewer outages or fewer hours spent on the site. We read your setup and tell you what a fair plan looks like. See plans and pricing for the Care plan, or get in touch and a person answers in under 2 hours on business days.

Frequently asked questions

How much does a WordPress maintenance plan cost?

It depends on site type, revenue at risk, response window and plugin count. A brochure site sits in the lower band, a WooCommerce store in the middle to upper band and a membership site in the upper band. Ask each agency for the price in writing, with included repair hours and the hourly rate stated.

What should a WordPress maintenance plan include?

Core, theme and plugin updates, off-server backups with restore tests, uptime and security monitoring, fixes after a bad update and a written monthly report. A named person who knows your site should answer when something breaks.

Is a WordPress maintenance plan worth it for a small business site?

If the site brings enquiries or sales, usually yes, because one outage or a failed update can cost more than a lighter plan. A site of a few static pages can do with host backups, automatic minor updates and a quarterly check.

What is the difference between WordPress hosting backups and a maintenance plan?

Hosting backups copy your site on a schedule, often on the same infrastructure, and you restore them yourself. A maintenance plan adds off-server copies, restore tests, updates, monitoring and a person who fixes problems.

How often should a WordPress site be backed up and tested?

Back up a brochure site daily and a store or membership site more often, with the database copied several times a day. Test a restore quarterly for a brochure site and monthly for a store, and ask for the result in writing.

What response time should I expect from a WordPress maintenance agency?

A reply within hours on business days is a fair expectation. Ask for the fix time separately, and pay for out-of-hours cover only if your site earns overnight. werun.dev replies in under 2 hours on business days.

Do I need a maintenance plan for a WooCommerce store?

In most cases, yes. Orders are written all day, payment and shipping plugins update often and a broken checkout stops revenue. Choose a plan with frequent database backups, staging checks on checkout and a short response window.

Running into this on your own stack?

Tell us the platform and the problem. We'll tell you what it takes and who does it.

Start a conversation No commitment. Just a conversation.