After a new website launches, there’s a question that many businesses don’t think about until something goes wrong: who looks after it now? WordPress, its plugins and its theme need regular updates. Backups need to run and be tested. Security needs watching. Small changes come up every month. A WordPress care plan is the usual answer.
Care plans, also called maintenance plans or support retainers, are the usual answer. A developer or agency takes responsibility for keeping the site healthy in exchange for a monthly or annual fee.
I’ve been on both sides of this, selling care plans to clients and reviewing plans clients were paying for elsewhere. The quality varies enormously. Some plans are excellent value. Others charge a monthly fee for little more than clicking “update all” once a month. This article explains what a good plan includes, so whether you’re buying or selling, you can judge one properly.
What a care plan is for
A good care plan does three things:
- Prevents problems, through updates, security measures and monitoring.
- Limits damage when problems happen, through backups, fast response and clear responsibility.
- Keeps the site improving, through small changes and advice.
A plan that only does the first part is maintenance. A plan that does all three is a partnership.
The core services
Updates
WordPress core, plugins and themes should be updated regularly. That means more than clicking a button. A proper update process includes:
- A backup before updating
- Reading changelogs for major updates
- Testing significant updates on staging first
- Checking the site after updating
- Rolling back if something breaks
Security updates should be applied quickly, often within a day or two of release. Routine updates can be weekly or fortnightly. Ask how updates are handled, not just how often.
Backups
Daily backups are standard, stored off-site, with a retention period of at least 30 days. Stores and busy sites may need more frequent backups. Just as important: backups should be tested. A plan should include periodic test restores to confirm backups actually work.
Security
Security measures commonly include:
- Firewall and malware scanning
- Login protection and two-factor authentication
- Monitoring for vulnerabilities in installed plugins
- Hardening of WordPress configuration
- Malware cleanup if the site is compromised
That last point varies a lot between plans. Some include cleanup at no extra cost. Others charge separately, sometimes heavily. Check before signing.
Monitoring
Uptime monitoring checks the site every few minutes and alerts someone if it goes down. Some plans also monitor performance, SSL certificate expiry, domain expiry and broken links.
The question to ask is: what happens when an alert fires? Monitoring is only useful if someone responds.
Support and small changes
Most plans include a set amount of time each month for content updates, small design changes and help. Typical allowances range from 30 minutes to several hours, depending on the plan level.
Clarify:
- How requests are made: email, a ticket system, a form
- Response times for normal requests and emergencies
- Whether unused time rolls over
- What happens when a request exceeds the allowance
Reporting
A monthly report showing what was done builds trust and makes the value visible. Good reports include updates applied, backups completed, uptime, security events, performance metrics and any work done, in plain language rather than technical jargon.
Valuable extras
Higher-tier plans often add:
- Performance optimisation, with regular speed reviews and Core Web Vitals monitoring
- SEO health checks, such as broken links, indexing issues and Search Console monitoring
- Accessibility checks against common issues
- Analytics reviews with recommendations
- Strategy calls, quarterly or monthly, to plan improvements
- WooCommerce-specific care, including checkout testing after updates and payment gateway monitoring
For businesses that depend on their website for revenue, these extras often matter more than the core maintenance.
What care plans usually exclude
Clear exclusions prevent arguments later. Common exclusions:
- New features or significant redesigns, usually quoted separately
- Content writing and large content uploads
- Third-party service costs such as premium plugin licences, hosting and email services
- Problems caused by changes the client or another developer made
- Recovery from issues outside the provider’s control, such as hosting failures
A good contract lists exclusions plainly. A vague contract creates misunderstandings on both sides.
Hosting: included or separate?
Some care plans include hosting. Others work with whatever hosting the client already has.
Included hosting simplifies responsibility: one provider handles everything, and they can tune the server. The downside is dependency. If you leave the provider, you also need to move hosting.
If hosting is separate, make sure the care plan provider has the access they need and that someone is clearly responsible for server-level issues.
Pricing models
Care plan pricing varies widely by region, provider and scope. Rather than quoting figures that will date quickly, here’s how pricing generally works:
- Tiered plans: basic, standard and premium, with increasing support time and services.
- Per-site pricing for agencies managing many similar sites.
- Custom retainers for larger sites, based on estimated hours.
- Pay-as-you-go support, without a monthly fee, but with no proactive maintenance.
When comparing prices, compare what’s actually included. A cheap plan that charges separately for malware cleanup, updates on staging and anything over 15 minutes of support may cost more over a year than a more expensive inclusive plan.
Also consider the value of the website to the business. A site generating significant revenue each month justifies a more comprehensive plan than a simple brochure site.
Questions to ask before signing
- How are updates tested before they’re applied to the live site?
- Where are backups stored, how long are they kept and how often are restores tested?
- Is malware cleanup included, and are there limits?
- What’s the response time for an emergency, such as the site being down?
- How much support time is included, and what happens beyond that?
- What does the monthly report include?
- Who owns the site’s accounts, licences and domain?
- How much notice is needed to cancel, and what happens on cancellation?
The ownership question is important. The client should own their domain, hosting account and licences, or at least be able to take them over easily. A care plan shouldn’t become a hostage situation.
For providers: making plans sustainable
If you sell care plans, a few lessons from experience:
- Standardise your stack where possible. Managing fifty sites with the same tools is much easier than fifty different setups.
- Automate monitoring, backups and reporting, so your time goes into judgement rather than routine.
- Be clear about exclusions in writing from the start.
- Review pricing annually. Plans priced too low lead to rushed work and resentment.
- Communicate proactively. Clients value hearing “we noticed and fixed this” far more than silence.
Signs a care plan isn’t working
Whether you’re the client or the provider, a few warning signs suggest a plan isn’t delivering value. Updates are applied but nobody can say when the last backup restore was tested. Reports arrive but are identical every month, generated automatically without anyone reviewing them. The site goes down and the client finds out before the provider does. Small requests take weeks. Plugins pile up because nobody questions whether they’re still needed.
A good plan feels active. The provider notices things before the client does, suggests improvements and explains what they’ve done in plain language. If that isn’t happening, it’s worth a frank conversation about scope, price or fit.
Care plans for WooCommerce stores
Stores need more attention than brochure sites, because problems directly cost money and updates are riskier. A store care plan should include testing the checkout after every significant update, monitoring payment gateway webhooks, checking order emails, reviewing failed orders and keeping an eye on performance during sales. Backups should be frequent enough that a restore never loses a day’s orders, and restores should be planned carefully so new orders placed since the backup aren’t overwritten. Expect store plans to cost more than brochure site plans, and be wary of any that don’t. Choose a WordPress care plan by what it actually does each month, not by the length of its feature list.
Frequently asked questions
Can I maintain my WordPress site myself?
Yes, if you’re comfortable with updates, backups and troubleshooting, and you have time each month. Many small sites are maintained by their owners. The risk is that maintenance gets postponed when you’re busy.
Is a care plan necessary for a small brochure site?
Not always, but the site still needs updates and backups. A basic plan or managed hosting with automatic updates and backups may be enough.
What happens if my site gets hacked while on a care plan?
That depends entirely on the contract. Good plans include cleanup and explain how they’ll respond. Check this before you need it.
How do I switch care plan providers?
Ask the current provider for a handover: credentials, licences, backups and documentation. Change passwords after the handover and make sure the new provider has everything they need before the old plan ends.




