DD DevDome Track. Protect. Grow.
Site Care

The Monthly WordPress Maintenance Checklist (One Hour, Twelve Items)

Sites do not break on the day you neglect them. They break six months later, all at once. An hour a month is the price of never having that day.

On this page
  1. Keep it current (15 minutes)
  2. Keep it clean (20 minutes)
  3. Keep watch (15 minutes)
  4. Look at the numbers (10 minutes)
  5. When something is off
  6. The quarterly pass
  7. The notes
  8. If you have many sites

A WordPress maintenance checklist works when it fits in an hour and you actually run it. This one has twelve items in four groups: keep it current, keep it clean, keep watch, and look at the numbers. Most of the work is automated; the hour is reading what the automation produced and acting on it. Do it on the same day each month and write down what you did.

Keep it current (15 minutes)

1. Updates. Core, plugins, themes, PHP version. If automatic updates handle the trusted plugins, this is reviewing what ran and updating the rest one at a time with a check between. Check the Site Health screen for anything it flags.

2. Backup check. Confirm the scheduled backups ran, are stored off-site, and open one to see it is not empty. Once a quarter, restore one to a staging site. A backup you have never restored is a hope.

3. Licences and renewals. Premium plugins, the domain, the certificate. An expired licence stops updates quietly; an expired certificate stops visitors loudly.

Keep it clean (20 minutes)

4. Broken links and 404s. Run the content link scan and fix what is actually broken, not what was merely slow. Open the 404 log, human hits only, and add redirects for the real misses. DevDome Link Monitor does both, with a bot split on the 404 log so the list is short. We make it, so weigh that; the two checks matter whatever tool you use.

5. Media bloat. Quarterly rather than monthly on most sites: scan for unused media, trash the largest to a recycle bin, delete after a week. DevDome Media Cleaner handles the scan, sizes and recycle bin for free.

6. Admin clutter. Open the notice inbox, mute the marketing, act on the one notice that keeps coming back. Hide any new dashboard widgets. A quiet admin is where a real warning gets noticed; DevDome Admin Cleaner keeps it that way with a Notice Inbox and one-click widget and toolbar cleanup.

7. Plugins and users. Delete anything deactivated. Remove accounts that left. Check the default role is Subscriber.

Keep watch (15 minutes)

8. Malware scan summary. Read the scheduled scan’s results. Most months: nothing. Act on anything flagged with evidence, quarantine first.

9. Activity log. Filter to logins and user changes. Every success should be someone you know. Any new administrator you did not create is an incident.

10. Uptime and certificate. Check the monitor’s month: outages, response time trend, certificate expiry date. A site that is slowing down is on its way to an outage.

Look at the numbers (10 minutes)

11. Traffic, honestly. Human pageviews versus bots, top pages, top referrers, clicks on tracked links. Compare with last month. A jump in the bot share is worth a look at the 404 log and login attempts.

12. What worked. Which pages gained, which lost, where the clicks came from. One note about what to write or fix next month. This is the item that turns maintenance into growth.

When something is off

Most months every item is green and the hour is really forty minutes. The value of the routine shows the month something is not. A few patterns and what they usually mean:

  • The backup did not run. Cron stopped, the storage filled, or the credentials expired. Fix it the same day; everything else on the list assumes a backup exists.
  • The scan flagged a modified core file. Read the evidence. A host’s cache include is fine; anything else is a cleanup, and the activity log tells you when it started.
  • A login succeeded from an IP you do not know. Reset that password, end every session, enable two-factor, then look at what the account did since.
  • The bot share jumped. Check the 404 log and login attempts. A scanner network found you; bot protection in record mode shows what it is doing.
  • Response time doubled. A new plugin, a full database table, or a host problem. Compare with the activity log for what changed around the date it started.
  • Human traffic dropped on one page. Check whether the page still exists, still has its internal links, and still returns 200 for crawlers.

None of these needs panic. Each has a short, known fix, and finding it in the monthly hour means it is fixed before a visitor notices.

The quarterly pass

Once a quarter, add thirty minutes for the things that drift slowly: a plugin audit that asks whether each one still earns its place, a restore test of a backup to a staging site, a look at image sizes registered by the theme, a check that the privacy policy still describes what the site does, and a performance test of the three most important pages. Quarterly is enough; these change slowly and the monthly hour keeps the rest in order.

The notes

Keep a short log: date, what updated, what broke, what you fixed, what you noticed. Next month’s hour starts by reading it. After a year you have a history that explains every odd number and every incident, which is worth more than any single check.

If you have many sites

Standardise first: the same plugins, the same settings, the same checks on every site. Then use tools with a cross-site view so items 8 to 11 are one dashboard, not twenty logins. The hour stretches to two for a large portfolio, which is still less than one unplanned outage.

An hour a month, twelve items, the same day. The sites that never have the bad day are the ones that do this, not the ones with the most plugins.

Disclosure: DevDome publishes this blog and makes the products it mentions. We describe what they do rather than promise results.

Key takeaways

  • Twelve items, one hour, once a month. Updates and a tested backup are the two that cannot be skipped.
  • Three cleanups keep the site light: broken links and 404s, unused media, and the admin clutter that hides real warnings.
  • Three checks catch problems early: the malware scan summary, the activity log, and uptime and certificate status.
  • Three glances at the numbers keep you honest: human versus bot traffic, top pages, and the 404 log's human hits.
  • Write down what you did. Next month's hour starts from this month's notes.

Sources

  1. WordPress.org: Updating WordPress : the official update guidance
  2. WordPress.org: WordPress backups : what a backup must include
  3. WordPress.org: Site Health screen : the built-in checks worth reading monthly

Links last checked October 17, 2026.

Frequently asked questions

How often should WordPress maintenance be done?

Updates weekly, ideally with automatic updates for trusted plugins. The full checklist monthly. A deeper review, plugin audit and performance test, quarterly. Daily attention is only needed for shops and high-traffic sites, and that is monitoring, not maintenance.

Can I automate most of this?

A lot of it. Automatic updates, scheduled backups, scheduled malware scans, a 404 log and uptime alerts all run on their own. The monthly hour is reading what they produced and acting on it, which is the part automation cannot do.

What if I manage many sites?

Standardise the plugins and settings so every site looks the same, and use tools with a cross-site view: one analytics dashboard, one place for health. Then the monthly hour becomes a list you walk down rather than twenty separate logins.

Is a maintenance plugin worth it?

A single plugin that does everything tends to do several things badly. Small plugins that each do one job well, a scanner, a link monitor, a cleaner, a log, give you better results and you can replace any one of them.

DevDome Team WordPress plugin builders

The DevDome team builds lightweight, performance-first WordPress plugins and free tools for site owners, founders and marketers. We write about the exact problems our plugins solve, in plain language for people who run real sites.