---
title: "WordPress Care Plan: What It Should Include"
url: https://hostmy.blog/wordpress-care-plan/
date: 2026-10-19
modified: 2026-10-19
lang: en
author: "Aditya Sharma"
description: "What a WordPress care plan should include, what each line should mean in practice, the wording that needs a follow-up question, and ten questions to ask before you sign."
categories:
  - "WordPress"
image: https://hostmy.blog/wp-content/uploads/2026/10/hmb-card-2554-1024x538.jpg
word_count: 1499
---

# WordPress Care Plan: What It Should Include

A WordPress care plan is a list of things someone agrees to do for your site every month, plus a promise about what happens when something breaks. The list is easy to write. The promise is where plans differ, and where most of them say the least.

This post is the checklist: what a plan should include and what each line should mean in practice. It also gives the questions that show whether a plan is real or only a long list of nouns. It is for blog and small business owners who are comparing plans, or deciding whether to buy one at all. For what a month of the work looks like on the inside, see [what a WordPress maintenance month actually contains](/wordpress-maintenance-service/).

## What a care plan is, and what it is not

A care plan is ongoing maintenance, monitoring and support for a site that already exists, paid for monthly or yearly. It is not hosting, which is where the site runs, although some providers bundle the two. It is not a redesign, and it is not content or SEO work. It is also not insurance. A plan lowers the chance and the cost of trouble, and it cannot remove either. If you are still deciding where the site should live, [what managed WordPress hosting actually buys you](/managed-wordpress-hosting/) is the better place to start.

## The ten things a plan should include

Most plans list some version of these ten. The middle column is what each one should mean in practice, and the right column is the question that shows whether it does.

| Line | What it should mean | What to ask |
| ---- | ------------------- | ----------- |
| Updates | Core, plugins and themes updated in a planned order, and the site checked afterwards | Do you test on staging first, and apply major updates one at a time? |
| Backups | Copies kept off the server, with a test restore on a schedule | When did you last restore one, and from where? |
| Uptime monitoring | The site checked from outside every few minutes, with an alert that reaches a person | Who gets the alert, and at what hours? |
| Security | Malware scanning, login protection and file change monitoring | What happens when a scan finds something? |
| Error and 404 review | A person reads the PHP error log and the 404 log | Do you read the logs, or only watch up and down? |
| Performance | Response time tracked over time, not only whether the site is up | What do you do if response time doubles? |
| Incident response | A named person who diagnoses and fixes what breaks | How fast do you respond, and does that include fixing? |
| Restore on failure | Recovery from a backup when the site breaks, without a separate bill | Is a restore included, or charged by the hour? |
| Reporting | A short note on what was done and what was found | Can I see a sample report? |
| Support | A person you can write to, who answers in plain English | Who replies, and how quickly? |

None of these is exotic. A plan that covers all ten is not doing anything special, it is doing the ordinary job. What separates plans is how specific the answer is to the right-hand column.

## The line most plans leave vague: what happens when it breaks

Updates and backups are easy to promise because they happen on a schedule. Incident response is harder, because it depends on a person being available on a day you did not plan for. That makes it the line to read most carefully.

Two words cause most of the confusion. Response time often means the time until someone acknowledges your message, not the time until the problem is fixed. Ask for both. And fixing is sometimes billed separately, as emergency work at an hourly rate. That is a legitimate way to run a plan. It does mean the plan covers maintenance and not the outcome, and you should know which one you are buying before the site is down.

If you want to see what a good message looks like when something does go wrong, [our website down message wording](/website-down-message-customers/) is free to copy.

## Backups that have been restored

Every plan says it takes backups. The useful question is whether anyone has restored one. A backup that has never been restored is a hope, and the gap between the two is the story in [the WordPress backup that did not restore](/wordpress-backup/).

Two more details are worth asking. Where are the copies stored? A backup that lives on the same server as the site goes down with it. And how long are they kept? A problem noticed three weeks late needs a copy from three weeks ago.

## Monitoring that reads more than up or down

An uptime check tells you the site answered. It does not tell you that the checkout form stopped sending, that response time has tripled, or that a plugin update changed an asset path. Those failures are quiet, and they are the ones a plan exists to catch. What to watch, and what is only noise, is covered in [what to actually monitor on a WordPress site](/wordpress-monitoring/). The failures that nobody sees coming are in [what breaks when nobody is watching](/what-breaks-when-nobody-is-watching/).

The simplest test of a plan is to ask what it looks at besides up or down. If the answer is only up or down, the plan watches whether the site is alive, not whether it is working.

## Wording that should make you ask more

Some phrases are not wrong, but they are incomplete. Each one needs a follow-up question.

| If the plan says | Ask |
| ---------------- | --- |
| Unlimited support | Unlimited by what measure, and with what response time? |
| Daily backups | Stored where, kept how long, and restored when? |
| Security hardening | Which specific measures, and who reviews the alerts? |
| 24/7 monitoring | Is there a person on call to act on an alert, or only a tool to send one? |
| Automatic updates | Is each update checked afterwards, or applied and left? |
| Priority support | Priority over whom, and what is the stated time? |

A vague answer to one of these is not a reason to walk away. A vague answer to most of them is.

## What you can do yourself

You do not need a plan to cover the basics. Update on a schedule, using a staging copy for anything that changes how the site looks ([WordPress staging done properly](/wordpress-staging/) covers the traps). Keep backups off the server and restore one to check it. Set up a free uptime monitor with an alert on your phone. Read your 404 log once a month. If you want the security side without a plugin that fights your host, [WordPress security without a plugin that fights your host](/wordpress-security/) sets out the approach.

The cost is your time, and the real cost is the day something breaks while you are away or asleep. A plan is a way of paying someone else to be the person who finds out first. Whether that is worth it depends on what an hour of downtime costs your blog, not on the price of the plan.

## Questions to ask before you sign

Copy these into an email to any provider you are comparing. The answers matter more than the price.

`1. What exactly is checked every month, and can I see a sample report?
2. Are updates tested on staging first, and applied one major update at a time?
3. Where are backups stored, how long are they kept, and when did you last restore one?
4. Who is alerted when the site goes down, and at what hours?
5. What is your response time, and what is your time to fix?
6. Is fixing a broken site included, or billed separately?
7. Do you read error and 404 logs, or only watch uptime?
8. What is not covered, and what happens if the cause is my host or a plugin?
9. Who actually does the work, and can I write to that person?
10. How do I leave, and do I keep the backups and the reports?`

## When a plan is not the answer

A plan sits on top of hosting. If the host is the problem, because the server is slow, oversold or restarting under load, no plan on top of it fixes that. The reasons are in [the uncomfortable economics of cheap shared hosting](/cheap-shared-hosting-economics/). A plan also adds little to a site that rarely changes and that you are comfortable looking after yourself. It earns its place when the site makes money or carries your reputation, and when nobody on your side is watching it.

## Where Host My Blog fits

Everything above is a checklist you can use with any provider, including us. If you compare us against it, we would rather you did.

On the blogs we look after, we watch the site around the clock, verify backups with a test restore, and a named person replies in hours, in plain English, when something breaks. We also turn some sites down, and [what we check before taking on a client blog](/what-we-check-before-taking-a-client-blog/) says why. If you would rather not be the person who gets the alert, [our care for bloggers](/for-bloggers/) is built for that.

If your site broke tonight, could you name the person who would fix it, and how long they have promised?