A WordPress maintenance plan should cover four things: timely updates for core, plugins and themes, backups you have actually restored, security scanning with a defined response process, and uptime and error monitoring. It should also state who owns each task and how fast they respond. Without those details, it is only a list of tasks.
What a maintenance plan actually covers
Most plans you will find online are tier lists: bronze, silver, gold, each with a slightly longer list of tasks. The tasks themselves are rarely the problem. What differs between a good plan and a weak one is the detail behind each line: how often, who does it, and what happens when something goes wrong.
Think of a plan as five areas, each with a cadence and an owner. The table below is a practical baseline for a small business site or a freelancer's client site.
| Area | Typical cadence | What to define |
|---|---|---|
| Core, plugin and theme updates | Weekly, plus urgent security releases | Test method, rollback path |
| Backups | Daily for active sites, more often for stores | Storage location, restore test schedule |
| Security | Continuous scanning, monthly review | Triage steps, patch timing |
| Monitoring | Continuous | Alert recipients, response time |
| Reporting | Monthly | What the client receives |
If a plan you are reading cannot fill in the right-hand column, ask for it before you sign. If you are the one selling the plan, writing that column down is the quickest way to look more professional than competitors who only list tasks.
A plan also needs a boundary. Content edits, design changes and new features are usually separate work, and saying so up front prevents arguments later.
Updates: core, plugins and themes
Updates are the core of any plan, and the context has shifted. According to the WordPress.org releases listing, 2026 has seen several core security releases close together: September 22, October 6, October 28 and November 18. The November 18 release, 7.1.5, is flagged as a security release. The security announcements page tells users to update immediately. A plan that updates core once a month is too slow for that pace.
Minor core releases install automatically by default, while major releases are manual unless you opt in. Check the WP_AUTO_UPDATE_CORE constant in the WordPress developer documentation for the exact values before you change that behavior.
Plugins and themes are where most of the risk sits. Patchstack's 2026 report, as cited in secondary coverage, says 91% of the 11,334 vulnerabilities logged in 2025 were in plugins and 9% in themes. That is why plugin updates deserve more attention than anything else on the list.
On the question of automatic or manual, a sensible split works well:
- Auto-update low-risk plugins on simple brochure sites, with a backup taken first.
- Test updates for checkout, forms, page builders and membership plugins on a copy of the site first. Our staging site guide covers free and paid ways to do that.
- Always keep a rollback route, either a one-click restore or a stored copy of the previous version.
Backups you have actually tested
Every plan says backups are included. Far fewer say how they are verified. A backup that has never been restored is an assumption, not a safety net, so the plan should include a scheduled restore test, at least quarterly, onto a staging copy.
Decide three things in writing. First, frequency: daily is a reasonable baseline for a brochure site, while a store taking orders may need near real-time copies so no orders are lost. Second, location: copies stored only on the same server as the site disappear together with it, so keep at least one copy off-site. Third, retention: how many days or versions you keep, because malware is sometimes discovered weeks after infection.
A proper test checks more than whether the files unpack. Restore the database and files, load the homepage, log in to the admin area, submit a form and, on a store, place a test order. Note how long it took, because that number is your real recovery time.
For real-time backups with a visual activity log, Jetpack is one option worth evaluating. It suits owners who want backups managed outside their host and are comfortable with a hosted service. It is less suitable if you need every byte of data to stay on infrastructure you fully control, or if your host already provides tested off-site restores you trust.
Affiliate note: my Jetpack and Pressable links are affiliate links; if you buy through them I may earn a commission at no extra cost to you.
Security: scanning and what happens after a finding
The phrase routine vulnerability scans appears in nearly every plan, and it tells you very little. Scanning is the easy part. The valuable part is what happens when a scan finds something, and that is where plans should be specific.
A useful security section answers these questions:
- How is a finding triaged? A critical flaw in an active plugin on a public form is not the same as a low-severity issue in a deactivated one.
- How quickly is a patch applied after a fix is released? Same day for critical, within the week for the rest is a common pattern.
- What if no patch exists? Options include deactivating the plugin, blocking the vulnerable endpoint or replacing the plugin.
- Who cleans up if the site is hacked, and is that included or billed separately?
Hardening belongs here too: two-factor authentication for admins, removal of unused plugins and themes, and least-privilege user roles. Our security hardening checklist lists the settings, and the post on common vulnerabilities explains what attackers usually exploit.
If you add malware scanning, Jetpack Scan is one tool in that category. A scanner only reports, so the plan still needs a human who acts on the report.
Monitoring: uptime, errors and speed
Monitoring is what lets you find problems before the client does. A minimal setup checks the homepage and one critical page, such as checkout or contact, every one to five minutes from outside the server. Alerts go to a named person, not a shared inbox nobody reads.
Uptime alone misses a lot. A site can return a 200 status while the checkout is broken or the page shows a fatal error to logged-out visitors. Add a keyword check that looks for expected content on the page, and track PHP error logs so repeated warnings are noticed before they turn into outages. If errors do appear, the guide to common WordPress errors helps you diagnose them quickly.
Expiry dates are the cheapest wins and are forgotten surprisingly often. Track the domain, SSL certificate and any licensed plugins, and set reminders well ahead of each date.
Performance monitoring completes the picture. Re-check Core Web Vitals monthly, because new plugins, large uploads and tracking scripts erode speed gradually. The PageSpeed Insights guide explains what to look at, and the speed optimization guide covers the fixes. Unoptimized images are a frequent cause, and the free Erdo Image Optimizer can handle conversion and compression so that task does not recur every month.
Ownership, response times and credentials
This is the gap most plans leave open. A task list says what gets done, but not who is responsible when something breaks at 11 p.m. on a Friday. Put these points in writing:
- Owner per task: who updates, who tests, who approves, who talks to the client.
- Response times: separate the time to acknowledge an incident from the time to resolve it, and define severity levels such as site down, checkout broken and cosmetic issue.
- Access: who holds admin credentials, hosting login and DNS, and how those are shared. Use individual accounts and a password manager rather than one shared login.
- Exit terms: what the client receives if the arrangement ends, including backups and documentation.
The bottom line for freelancers is that the client should always own the domain, hosting account and licenses, with you added as a collaborator. That keeps the relationship clean and makes the plan easier to hand over.
If clients also review drafts and changes during maintenance, a defined sign-off process helps. See the client approval workflow for one way to structure that.
Choosing between DIY, tools and managed hosting
There are three practical ways to deliver a plan, and each fits a different situation.
Do it yourself with plugins and a checklist. This suits one or two sites you know well. It is not for anyone who cannot reliably check alerts or who travels without backup coverage.
Add hosted tools for backups, scanning and monitoring. This suits freelancers managing a handful of sites who want less manual work. The cost is another subscription per site and another dashboard to watch.
Move sites to managed hosting. Pressable, managed by Automattic, targets agencies with many client sites. It fits when you want hosting, backups and infrastructure handled in one place. It is a poor match for a single small site on a tight budget, or for projects that need server-level customization beyond what a managed platform allows.
In short, managed hosting reduces the plan's workload but does not remove it. You still need to confirm what the host covers: some handle server-level updates and backups but leave plugin updates, vulnerability response and content recovery to you. Our guide to choosing hosting for agencies and freelancers goes through the criteria, and the list of plugins agencies need can help you pick supporting tools.


