Description

Most WordPress sites don’t go down all at once. They drift — a core update skipped because nobody wanted to risk breaking something, a plugin left three versions behind, a backup job that failed silently two months ago and nobody checked. None of it looks urgent on any single day. Then a plugin conflict takes the site offline, or a vulnerability that was patched months ago finally gets exploited, and the owner realizes the last backup that actually completed is older than they thought. By the time any of this becomes visible, it’s already the expensive version of the problem — a site down during business hours, or a rebuild from a backup that turns out to be six weeks stale.

This happens because WordPress maintenance is invisible work. Nobody sees weekly updates the way they see a new page or a redesign, so it’s the first thing that gets deprioritized when a business owner is busy running the business — which is most of the time. The trouble is that WordPress core, themes and plugins release security patches constantly, and every week a site runs on outdated versions is a week its attack surface grows — and it cuts both ways, since even a routine-looking release can occasionally change behaviour in ways that catch site owners off guard, as when a recent WordPress accessibility change risked breaking some plugins outright. Backups are the same story in reverse: they matter enormously the one day something goes wrong, and mean nothing every other day, which is exactly why they’re easy to forget until it’s too late. A site owner checking in occasionally has no reliable way to tell whether the backup plugin they installed two years ago is still actually completing its job, or whether it quietly started failing after a hosting change nobody connected to it.

The other part of the problem is that “assumed fine” and “actually fine” look identical from the outside, right up until they don’t. A brochure site that hasn’t been touched in months can look perfectly normal in a browser while running a version of a plugin with a known, published vulnerability, or while its last successful backup sits three months in the past. Nothing about the front end tells you that. The only way to know the real state of a WordPress site is to actually check the versions, the update history and the backup logs — which is exactly the kind of routine, unglamorous checking that’s easy to keep meaning to do and easy to keep not doing.

Essential Care Plan exists to make that upkeep something that just happens, on a schedule, without you having to remember it. Weekly core, theme and plugin updates keep the site patched against known vulnerabilities instead of accumulating months of unapplied fixes. Daily off-site backups — stored away from your hosting account, not just in a folder on the same server — are kept on a 30-day rolling retention, so if something needs to be rolled back, you have a month’s worth of restore points to choose from, not just whatever the last manual backup happened to catch. Uptime monitoring checks that the site is actually reachable, so a server issue or fatal error gets flagged to us directly instead of waiting for a customer to tell you the site is down.

What makes this different from just installing a backup plugin and hoping for the best is that a person is actually watching the output. A monthly health report tells you what was updated, that backups completed successfully, and what your uptime looked like — real information instead of a dashboard you have to remember to check. And it starts before you even commit: every plan opens with a free site health check covering WordPress and PHP versions, plugin conflicts, security exposure and backup status, so you see the actual condition of the site before deciding anything.

How it works

1. Free site health check. Before anything is touched, we review your WordPress and PHP versions, check for plugin conflicts, look at your current security exposure, and confirm whether backups are actually running. You get these findings regardless of whether you sign up.
2. Onboarding and baseline setup. Once you’re on the plan, we connect the site to our backup and monitoring systems and confirm the update schedule. Nothing about this requires downtime or disruption to how the site currently runs — visitors and search engines see no interruption while onboarding happens in the background.
3. Weekly update cycle. Core, theme and plugin updates are applied on a set weekly cadence rather than an ad hoc basis, so patches don’t sit unapplied for weeks at a time waiting for someone to get around to it. Each update happens on the same schedule every week, so there’s a consistent, predictable rhythm behind the site instead of maintenance that only happens when something prompts it.
4. Daily backups and continuous uptime checks. Every day, a fresh off-site backup is taken and the oldest one past 30 days rolls off, so the retention window is always a full rolling month. In parallel, uptime monitoring runs continuously in the background, watching for the site going unreachable rather than relying on someone happening to notice.
5. Monthly health report and ongoing support. At the end of each month you get a written report covering what was updated, backup status, and uptime over the period — plain information about what actually happened, not a vague “all good” summary. If anything comes up in between reports, email support responds within 24 hours.

Who this is for: This fits small business and brochure sites that just need essential upkeep handled reliably every month, without security scanning or edit time bundled in. If your site is a straightforward informational or lead-generation site rather than a store, and nobody is regularly asking for small content changes, this plan covers exactly what you need and nothing you don’t.

What’s included

• ✓Weekly core, theme & plugin updates
• ✓Daily off-site backups (30-day retention)
• ✓Uptime monitoring
• ✓Monthly health report
• ✓Email support — 24h response

The two bullets doing the most work here are the backups and the update cadence. Off-site storage matters because a backup sitting on the same server as your site does you no good if that server has a problem — the backup and the thing it’s protecting fail together. Thirty days of retention means you’re not limited to restoring “the last good version,” you can go back to any of the last thirty daily snapshots if an issue isn’t noticed right away. The weekly update cycle matters for a similar reason: security patches are only useful if they’re actually applied, and a fixed weekly schedule means updates don’t quietly slip for a month because nobody had time.

Every plan begins with the free site health check described above — WordPress and PHP versions, plugin conflicts, security exposure and backup status — and you receive those findings whether or not you go on to sign up. There’s no sales pressure baked into the audit; it’s meant to tell you the truth about where the site currently stands, so if you decide not to sign up, you still walk away knowing more than you did before.

Billing is month to month with no long-term contract attached. You can cancel at any time, and there’s no penalty or minimum term to work around — no annual commitment disguised as a “discount,” no cancellation fee buried in the fine print. Email support responds within 24 hours if something comes up between your scheduled updates and monthly report, so you’re not waiting a full month to flag a problem or get a question answered.

The monthly health report is a real accounting of the month, not a marketing summary — what was updated, whether every scheduled backup completed, and what uptime looked like over the period, including any incidents. If a backup fails or an update needs to be rolled back for compatibility reasons, that gets flagged rather than quietly retried and left unmentioned.

If your needs grow past this — you want security scanning and malware removal, database optimisation, speed and Core Web Vitals monitoring, or an hour of edit time included each month so small changes don’t need a separate invoice — Business Care Plan is the next tier up and includes everything in this plan as its foundation, so nothing about upgrading means starting over.

How soon does maintenance actually start? Onboarding begins with the free site health check, so the very first thing that happens is a clear picture of your site’s current state — versions, conflicts, security exposure and backup status. Once you’re on the plan, backups start running daily and the weekly update cycle begins on its set schedule, so ongoing protection is in place from the first week rather than phased in slowly.

What if I want to cancel? There’s no long-term contract on this plan. It’s billed monthly, and you can cancel at any time without a penalty or a minimum commitment to work through first.

What if my site actually needs security scanning or someone to make small edits each month? Essential Care is intentionally scoped to core upkeep — updates, backups, uptime and reporting — without security scanning or edit time included, because plenty of brochure sites genuinely don’t need those. If yours does, Business Care Plan builds on this same foundation and adds security scanning and malware removal, database optimisation, speed and Core Web Vitals monitoring, and an hour of edits included every month.

Does this plan cover a site that’s already having problems? The free health check will surface issues that already exist — an outdated PHP version, a plugin conflict, backups that aren’t actually running — so you’ll know about them regardless of whether you sign up. Essential Care then keeps the baseline from slipping again going forward: current updates, current backups, and monitoring that catches the next issue early instead of months later.

Billed monthly. Cancel any time. Your free site health check and first backup run start right after checkout, with nothing to sign beyond that. Secure checkout — payments processed via Stripe, bank transfer, or crypto (Mercuryo). Questions before ordering? Talk to us first.