WordPress maintenance checklist: what to do every month

A monthly WordPress checklist: backups, updates, security, speed, forms, search and housekeeping, plus quarterly and yearly checks. About two hours.

By Sohail Hussain21 November 20265 min read

Once a month, a WordPress site needs about two hours of attention: confirm backups ran, apply and test updates, review users and security alerts, check speed and the forms that bring in enquiries, look at Search Console, and tidy the database. Some checks belong every week or as alerts, and a few belong every quarter or year. The list below is the one we work through on WordPress sites we look after under website care and maintenance. Copy it, put a name next to each section, and tick it every month.

What should run every week, or as alerts?

These should not wait for the monthly check. Set them up once so they run, or alert you, without anyone remembering.

  • Uptime monitoring checks the homepage and the contact page every few minutes and alerts by email or message. Uptime monitoring covers the options.
  • Backups run daily and email on failure.
  • Minor WordPress releases install automatically, which is the default.
  • Security releases for plugins are applied within the week, either automatically or by hand.
  • Search Console sends you its emails. Check that the address it uses is one somebody reads.

Monthly: are backups and updates in order?

  • Open the backup log or dashboard and confirm a successful backup for every day this month, with a copy stored off-site.
  • List pending updates for core, plugins and themes. With WP-CLI, wp core check-update and wp plugin list --update=available show them.
  • Read the changelogs of any major releases.
  • Apply updates on staging first, plugins then theme then core, and test. How to update WordPress without breaking anything has the full routine.
  • Apply the same updates on live, at a quiet hour, and run the same tests.
  • Check that the PHP version is still supported. As of October 2026, WordPress.org recommends PHP 8.3 or newer.

Monthly: is the site still secure?

  • Review the list of administrators. Remove anyone who has left or no longer needs that role:
bash
wp user list --role=administrator --fields=ID,user_login,user_email,user_registered
  • Confirm two-factor login is on for every administrator and editor.
  • Check core and plugin files against the official copies on WordPress.org. Anything listed as changed or added needs explaining:
bash
wp core verify-checksums
wp plugin verify-checksums --all
  • Read the security plugin or host firewall report for anything beyond the usual login attempts.
  • Check for plugins that have been closed on WordPress.org or not updated in a year, and plan a replacement.

The WP-CLI commands are documented in the WP-CLI command reference. WordPress security: the ten things that stop most attacks explains the reasoning behind each check.

Monthly: is the site still fast, findable and working?

  • Run the homepage and one key inner page through PageSpeed Insights on mobile, and record LCP, INP and CLS. Our Core Web Vitals calculator shows which pass. Compare with last month; a sudden drop usually means a new plugin, script or image.
  • Submit every form on the site. Confirm the email arrives at the right inbox and any CRM or spreadsheet entry is created. Forms break silently more often than anything else.
  • For a store: place a test order through checkout, including the payment and the confirmation email.
  • In Search Console, check the Pages report for new "not indexed" problems, the Core Web Vitals report, and the Security Issues and Manual Actions reports.
  • Click through the main menu and footer on a phone. Look for broken links, missing images and layout problems.
  • Check that the SSL certificate renews automatically and has more than two weeks left.

Monthly: what housekeeping keeps it tidy?

  • Empty the spam comments and form spam, or turn comments off if the site does not use them.
  • Delete expired transients with wp transient delete --expired.
  • Remove drafts, test pages and unused media that editors have finished with, after checking with them.
  • Clear old revisions if the database has grown, and cap future ones with WP_POST_REVISIONS in wp-config.php.
  • Write a short log of what changed this month: updates applied, issues found, anything left open.

Do not install a "database optimisation" plugin just to run this once a month. Most of it is a few commands or a few clicks, and every plugin is another thing to update.

What should you check every quarter or year?

Every quarter:

  • Restore a backup to staging and check it works. Note how long it took. How to back up a WordPress site properly covers the test.
  • Audit the plugin list: why each is there, whether it overlaps another, and who holds the licence. How many WordPress plugins is too many has the method.
  • Review every user account, not only administrators.
  • Check that the contact details, prices, team and opening hours on the site are still true.

Every year:

  • Renew the domain, or confirm it renews automatically on a card that has not expired. Check who holds the registrar login.
  • Review premium plugin and theme licences: renew what you use, cancel what you do not.
  • Review hosting: price, PHP versions offered, backups, and whether the plan still fits your traffic.
  • Re-read the privacy policy and cookie consent against what the site now collects.
  • Do a quick accessibility check: keyboard navigation, image alt text, colour contrast.

How long does this take, and should you outsource it?

For a typical company site with 10 to 15 plugins, the monthly check takes one to three hours once the alerts and backups are in place. The first month takes longer, because that is when the problems surface.

Doing it yourself is reasonable if someone on the team is comfortable with staging, updates and reading an error log, and will block out the time every month. The failure mode is not difficulty. It is the month nobody does it, then the next, until the site is a year behind.

Outsourcing makes sense when nobody owns the site internally, or when the site brings in enough business that a broken form for a week would cost more than a year of care. As of October 2026, outsourced WordPress maintenance typically costs about ₹3,000 to ₹15,000 a month in India or $50 to $300 elsewhere. How much does website maintenance cost breaks that down by tier, and website maintenance explains what the money should buy. For how maintenance fits into running WordPress overall, see WordPress for business websites.

Was this guide useful?

Questions

Frequently asked.

Can I automate WordPress maintenance?

Partly. Backups, minor core updates, updates for simple plugins, uptime monitoring and malware scans can all run automatically. What cannot be automated is judgement: testing major updates, noticing a form that quietly stopped sending, deciding whether a plugin should go. Automation covers most of the weekly work; the monthly review still needs a person.

How much does WordPress maintenance cost if I outsource it?

As of October 2026, roughly ₹3,000 to ₹15,000 a month in India, or $50 to $300 elsewhere, for a typical company site. The low end covers updates, backups and monitoring; the high end adds staged testing, content changes and a monthly report. Stores and membership sites cost more.

Sohail Hussain

Founder, MSH Technologies

Sohail has designed and built websites, web apps and AI products for over 12 years, for clients from Singapore-based industrial groups to early-stage SaaS startups. He writes about what actually worked.

Keep reading

Related guides.

All posts

Your next move

Like what you see? Tell us about it.

A process that takes too long, a website that undersells you, or an idea ready to take shape. Tell us where you are and we will suggest a useful next step.

India · Working with clients worldwide

Sohail, Founder, replies within 1 working day (Mon–Sat, IST). Free and no obligation.