Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Setup & site building · Guide

What a WordPress Maintenance Plan Should Include

Short answer

A WordPress maintenance plan is a written schedule of weekly, monthly, quarterly and yearly jobs: backups, core, plugin and theme updates, security checks, speed and error monitoring, and clean-up. Each job names an owner and a frequency, and the plan forbids updates until a fresh backup exists. WordPress 7.1.4 is the latest version as of November 2026.

Key takeaways

  • A maintenance plan covers updates, backups, security, monitoring and clean-up on a weekly, monthly, quarterly and yearly schedule.
  • Back up files and the database together, weekly for small sites and daily for busy ones, and always before an upgrade.
  • WordPress.org recommends PHP 8.3 or greater, with MySQL 8.0 or MariaDB 10.11 or newer.
  • Site Health, under Tools in the dashboard, sorts issues into critical, recommended and passed tests.
  • A backup only counts once a restore has been tested on a staging copy.

What is a WordPress maintenance plan?

A WordPress maintenance plan is a written schedule of the routine jobs that keep a site updated, backed up and working.

The plan turns maintenance from a reaction into a routine. Instead of fixing a site after it breaks, you check the same short list on the same days each week, month and quarter. Each job has an owner, a frequency and a record of when it was last done.

A good plan covers five areas: updates, backups, security, monitoring and clean-up. WordPress.org's Site Health documentation describes a healthy site in similar terms: fully up to date, running supported software, well maintained and secure. Your plan is how you get there and stay there.

The plan should fit the site. A small blog that changes once a month needs less attention than a store that takes orders every day. The schedule below starts with weekly jobs and adds monthly, quarterly and yearly checks, so you can scale it up or down.

What should the plan cover each week?

Each week, check that the backup ran, run pending updates and test the pages that matter.

Start with the backup. Confirm the latest backup finished without errors and that a copy sits away from the web server. A backup that never ran is the same as no backup, and the weekly check is what catches it.

Next, update WordPress core, plugins and themes. WordPress.org's hardening guide states the rule plainly: always keep up to date with the latest version of WordPress, since older versions do not receive security updates. WordPress 7.1.4 is the latest version as of November 2026, and it shipped on October 28, 2026 as a security release.

Then open the site and test it. Click the contact form, the checkout and the login page, and confirm each one works. Site Health cannot see a form that quietly stopped working, so a human click is part of the plan.

Host backups alone may not be enough, so check what your host actually keeps.

How should backups work in the plan?

A backup must hold both parts of the site: the files and the database.

WordPress.org's backup guide states that a full restore needs both parts.

The files hold WordPress core, themes, plugins, uploads and settings files such as wp-config.php. The database holds posts, pages, comments, users and settings.

Downloading the files alone does not back up the database, since it lives in a separate MySQL or MariaDB system.

The same guide gives a frequency to start from: back up once a week for smaller sites, and daily for high-activity sites.

Always back up before an upgrade, so you can roll back if the update breaks something. Keep at least 3 to 5 recent backups, stored in different places, such as one copy on the server, one in cloud storage and one downloaded to your computer.

Learn WordPress repeats the same advice in its backing up lesson: back up before every update, and before installing new plugins.

Test the restore, not just the backup. A quarterly restore test on a staging copy proves the backup files are complete and the database import works. A backup you have never restored is a hope, not a plan.

Store backup copies in more than one place, and check where each copy lives.

How should updates be handled?

Update in this order: back up, update on staging first when you can, then update live and test.

Core updates come first, then plugins, then themes.

WordPress has offered automatic background updates since version 3.7, according to the WordPress.org hardening guide. You can switch on auto-updates for each plugin and theme from the Plugins and Themes screens.

Auto-updates suit simple sites, but a store or a site with many plugins is safer with controlled updates you run by hand.

Read the release notes before a major update.

WordPress 7.1.4, released October 28, 2026, was a security release, and WordPress recommended updating immediately.

Wordfence counted 22 vulnerabilities fixed in that release, including a flaw in the core update process itself. A maintenance plan that skips release notes misses that kind of warning.

After updating, check the site the same way you do each week. Open the home page, a post, the contact form and the checkout. If anything breaks, restore the backup you took before the update, then work out which update caused it.

Enable auto-updates per plugin when the site is simple enough for them.

What security checks belong in the plan?

Each week, review user accounts, login security and the results of a security scan.

Remove accounts that no longer need access, and check that no account has a role stronger than its job needs. A former contributor with an administrator role is a risk that costs nothing to fix. Turn on two-step login for every administrator account, and use a strong, unique password for each one.

Keep a security plugin or the host's scanner running, and read its results weekly. The WordPress.org hardening guide lists outdated plugins and software among the main ways sites get attacked. A scan that nobody reads is the same as no scan, so the plan should name who reads it and when.

Check the SSL certificate and the site address too. WordPress.org's requirements page lists HTTPS for every install, and a lapsed certificate breaks trust and logins at once. Confirm the certificate renews on its own, and check the site loads over HTTPS after each renewal.

Run a full security audit on a schedule, not only after a problem appears.

How do you monitor speed and errors?

Use Site Health weekly, and add uptime monitoring so you hear about outages first.

Site Health lives under “Tools” then “Site Health” in the dashboard. WordPress.org's Site Health documentation explains that the screen groups results into critical issues, recommended improvements and passed tests. The feature arrived in WordPress 5.2, and it checks updates, PHP versions, HTTPS, scheduled events and background updates.

Fix critical issues first. A critical issue can mean a security hole or a serious performance problem, while a recommended improvement is worth fixing but not urgent. The Info tab lists the technical details, such as the PHP version and the database version, which help when you ask a host or a developer for help.

Uptime monitoring is separate from Site Health. A monitor loads the home page every few minutes and emails you when it fails. That alert is often the first sign of a hosting outage or a fatal error, and it arrives before visitors start complaining.

Check which PHP version your site should run before you ask the host to change it.

What belongs in the monthly and quarterly checks?

Monthly jobs are clean-up and speed; quarterly jobs are restore tests and account reviews.

Each month, delete plugins and themes you no longer use, and clear spam comments. Unused code still needs updates, and an abandoned plugin can become a way in. Check broken links and 404 errors, and review search errors in Search Console if the site uses it.

Each month, also check the PHP version.

WordPress.org recommends PHP 8.3 or greater, with MariaDB 10.11 or newer, or MySQL 8.0 or newer.

PHP's own supported versions page shows PHP 8.3 receiving security fixes until December 31, 2027, and PHP 8.2 only until December 31, 2026. A version past its security support date should be on the plan to upgrade.

Each quarter, test a full backup restore on a staging copy. Review every user account and role again, and check that no plugin in use has been abandoned by its author. Re-test the contact form and checkout on a phone, since mobile breakage is easy to miss from a desktop.

FrequencyJobsWhy it matters
WeeklyBackup check, updates, form and checkout testCatches failures while they are small
MonthlyDelete unused code, broken links, PHP version checkStops old code and old software piling up
QuarterlyRestore test, user review, mobile testProves the backup works and access stays tight
YearlyDomain, hosting, SSL and licence renewalsStops the site expiring by accident

What should the yearly review cover?

Once a year, confirm every renewal, licence and legal page is current.

Check the domain name and hosting renewals first, and confirm the payment method on file still works. A domain that lapses can be registered by someone else, and a hosting account that lapses takes the site down. Note both dates in the plan, with reminders set weeks ahead.

Review premium plugin and theme licences next. A lapsed licence stops updates, which leaves known flaws unpatched. Renew the licences the site still needs, and drop the ones it does not.

Update the privacy page, the contact page and the site's busiest pages. Laws and contact details change, and a privacy page that names a service the site no longer uses is worse than no page at all. Refresh the busiest pages with current facts, and check their links still work.

Prove the backup restores before you need it, with a test on a staging copy.

What mistakes should you avoid?

The most common mistakes are updating without a backup, never testing a restore and letting software age.

First, never update core, a plugin or a theme without a fresh backup. Updates fix flaws, but a bad update can break a theme or a plugin the same day. The backup is the only fast way back, and the plan should forbid updates until it exists.

Second, do not trust a backup you have never restored. A backup file can be incomplete, corrupt or missing the database, and you only learn that when you need it. The quarterly restore test exists for that reason.

Third, do not let PHP or WordPress fall years behind. WordPress.org's hardening guide warns that once a fix is released, the details needed to attack old versions are usually public. A site three versions behind is an open target, not a stable site.

Fourth, do not give every user an administrator role. Each account should hold the weakest role that lets its owner do the job. Review the list every quarter, and remove accounts the day their owner leaves.

Frequently asked questions

How much time does a maintenance plan take each week?

For a small site, about one to two hours a week covers the backup check, updates and a quick test of the main pages. A store or a site that changes daily needs more, since it needs daily backups and faster checks after each change.

Can I automate all WordPress updates?

Yes, if the site is simple and the plugins are well maintained. You can switch on auto-updates per plugin and theme from the Plugins and Themes screens. Keep a backup before each update round, and test the site after major updates.

Do I still need my own backups if my host backs up the site?

Yes. The host backup protects the host, and restoring from it can take time and may need a support ticket. Keep your own backups too, stored away from the server, and test that they restore.

How do I know my backups are good enough?

Check that the backup ran, that the copy is stored off-site, and that a restore has been tested on staging in the last three months. If any of those three is missing, the backup part of the plan is not done.

Does a staging site replace the maintenance plan?

No. A staging copy is the safe place to test updates and restores, but the live site still needs its own backup, update and monitoring schedule. Use staging to rehearse, then apply the same checks to the live site.

Where do I start if the site has never had a plan?

Open Tools, then Site Health, in the dashboard and fix the critical issues first. Check the PHP version, the update status and whether scheduled events and background updates are working. The Info tab shows the technical details.

Sources

  1. Backups WordPress Developer Resources
  2. Hardening WordPress WordPress Developer Resources
  3. Site Health: keep your website healthy WordPress.org
  4. WordPress 7.1.4 WordPress.org
  5. PHP: Supported Versions PHP.net
  6. Requirements WordPress.org
  7. Backing Up Your WordPress Site Learn WordPress
  8. WordPress 7.1.4 Security Release Wordfence

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test