Muhammad Ismail Khalid

WordPress Website Maintenance Checklist: Weekly, Monthly, Quarterly and Yearly Tasks

By , Full Stack Developer and AI Automation Engineer. . 9 min read.

Topic: WordPress Speed, SEO and Security

On this page
  1. The WordPress website maintenance checklist at a glance
  2. Before you start: backups and a staging site
  3. Weekly maintenance tasks
  4. Monthly maintenance tasks
  5. Quarterly maintenance tasks
  6. Yearly maintenance tasks
  7. After every update: a 10-minute check
  8. Signs your maintenance isn't working
  9. Do it yourself or hand it off?
  10. The short answer
  11. Frequently asked questions

A WordPress website maintenance checklist comes down to six jobs done on a schedule: back up, update, secure, check speed, check search visibility, and test that forms and key pages still work. Weekly you confirm backups ran and apply updates. Monthly you review security, speed, Search Console and every form. Quarterly you clean out plugins, users and old content. Yearly you review hosting, PHP version, domain and licenses.

Most WordPress problems I see don't come from one big failure. They come from small things nobody checked: a backup that stopped running months ago, a plugin that hasn't been updated since the developer abandoned it, or a contact form that quietly stopped sending emails. The checklist below is built to catch those early, and it's the routine I'd recommend to any business that relies on its website for leads.

The WordPress website maintenance checklist at a glance

WordPress website maintenance checklist by frequency: weekly, monthly, quarterly and yearly tasks
The maintenance tasks grouped by how often to do them.
How often Tasks
Weekly Confirm backups ran, apply core, plugin and theme updates, check the site loads and forms submit
Monthly Run Site Health, review security logs and users, test speed and Core Web Vitals, check Search Console, test every form end to end
Quarterly Remove unused plugins and themes, audit user accounts, test a full restore, fix broken links, clean the database
Yearly Review hosting and PHP version, renew the domain and SSL, review plugin licenses, refresh old content
Before any change Take a fresh backup and use a staging site

Small sites with little traffic can stretch the weekly tasks to every two weeks. Online stores, membership sites and busy blogs should not, and they need daily backups.

Before you start: backups and a staging site

Two things make every other task on this list safe: a backup you can restore, and somewhere to test changes that isn't the live site.

Backups. WordPress's documentation is clear that you need both the files and the database to fully restore a site. The files include WordPress itself, plugins, themes, uploads and wp-config.php. The database is stored separately, so downloading the site folder alone doesn't capture it. It recommends:

  • Weekly backups for smaller sites with fewer posts
  • Daily backups for high-activity sites
  • At least 3 to 5 recent backups, stored in different locations, such as the hosting server, cloud storage and a local computer
  • A backup before every upgrade or move

A backup stored only on the same server as the website isn't enough. If the server fails or the account is compromised, the backup goes with it.

Staging. A staging site is a private copy of your website. Many hosts create one in a click. Use it to test major updates, a new theme or a PHP version change before you touch the live site. If your host doesn't offer staging, a fresh backup taken right before the change is the minimum.

Weekly maintenance tasks

These take minutes once you have the routine.

  1. Confirm the last backup completed. Don't assume the plugin or host ran it. Check the date and size of the latest backup, and that a copy exists off the server.
  2. Apply updates. Go to Dashboard, Updates. Update WordPress core, then plugins, then themes. For large plugins such as WooCommerce, page builders and form plugins, read the changelog first and update on staging if the release is a major one.
  3. Check the site after updating. Load the home page, a service page, a blog post and the contact page on desktop and mobile. Look for broken layouts and error messages.
  4. Submit your main form. A test submission confirms the form works and the notification email arrives.
  5. Look at uptime alerts. If you use an uptime monitor, check whether the site went down during the week and why.

Automatic updates: what WordPress does for you

WordPress installs minor core releases automatically by default. These are the maintenance and security releases, and WordPress's documentation strongly discourages turning them off. Since WordPress 5.6, new installs also get major core updates automatically, unless WordPress detects a version-control checkout.

Plugin and theme auto-updates arrived in WordPress 5.5. They are opt-in, set plugin by plugin and theme by theme. WordPress runs them twice a day using WP-Cron and emails the site owner when an update succeeds or fails.

My recommendation: turn on auto-updates for small, well-maintained plugins, and keep manual control over the plugins that run checkout, bookings, forms or your page builder. Those are the ones where a bad release costs you money, so update them after a backup and test right away.

Monthly maintenance tasks

Monthly WordPress website maintenance checklist: Site Health, security, speed, Search Console, forms and backups
Six checks to run every month.

Run Site Health

Go to Tools, Site Health. The Status tab lists critical issues, recommended improvements and passed tests. It flags things like an outdated PHP version, plugins waiting for updates, background updates that aren't working, and debug settings that show errors to visitors. The Info tab shows your WordPress, server and database details, which is useful when you contact your host or a developer.

Fix anything marked critical before you move on.

Review security

  • Users: check the list of administrator accounts. Remove anyone who no longer needs access, and lower roles for people who only write content.
  • Passwords and two-factor authentication: WordPress's hardening guide recommends strong passwords and two-step authentication. Make sure every administrator has both.
  • Logs: review your security plugin's activity log or your host's access and error logs for repeated failed logins or unusual changes.
  • Malware scan: run a scan with your security plugin or your host's scanner.

Check speed and Core Web Vitals

Run your main pages through PageSpeed Insights and check the Core Web Vitals report in Google Search Console. Google's "good" thresholds are:

Metric What it measures Good
Largest Contentful Paint (LCP) Loading speed 2.5 seconds or less
Interaction to Next Paint (INP) Responsiveness 200 milliseconds or less
Cumulative Layout Shift (CLS) Visual stability 0.1 or less

Google measures these at the 75th percentile of real visits, separately for mobile and desktop. A sudden drop after an update usually points to a new plugin, a theme change or images uploaded at full size.

Check Google Search Console

Look at the Pages report for new indexing errors, the Performance report for a sudden fall in clicks, and the Security and Manual Actions sections. A drop that lines up with an update date is your first clue.

Test every form end to end

Submit every form on the site, not just the main one. Confirm that the notification email arrives, the lead reaches your CRM if you use one, and any thank-you page or conversion tracking still fires. A form that looks fine on the page but sends nowhere is one of the most expensive failures a service business can have, because nothing tells you it's broken. Law firms can pair this with a full law firm website analysis, which also covers intake, practice pages and ethics rules.

Check that backups restore

Once a month, open a backup and confirm it contains both the database and the files. WordPress's documentation also suggests running a manual backup from time to time to check that automated backups are working.

Quarterly maintenance tasks

  • Remove unused plugins and themes. WordPress's hardening guide says to delete plugins you aren't using, because unused code is still an entry point. Deactivated isn't enough. Keep one default theme as a fallback and delete the rest you don't use.
  • Replace abandoned plugins. If a plugin hasn't been updated in a long time or has been closed on WordPress.org, plan a replacement before it becomes a problem. When no maintained plugin does the job, a small custom plugin is often the safer option, and our custom WordPress web development guide covers when that makes sense.
  • Test a full restore. Restore a backup to a staging site and check that it works. This is the only way to know your backups are usable.
  • Fix broken links and 404s. Use a crawler or the Search Console Pages report to find broken internal links and pages that return 404 errors, then fix the link or add a 301 redirect.
  • Clean the database. Remove spam comments, old post revisions and expired transients. Take a backup first.
  • Review the content that matters most. Check that service pages, prices, team members, phone numbers and addresses are still correct.

Yearly maintenance tasks

  • Review hosting and the PHP version. As of November 2026, WordPress.org recommends PHP 8.3 or greater, MySQL 8.0 or greater or MariaDB 10.11 or greater, and HTTPS support. Check what you're running under Tools, Site Health, Info, Server. Upgrade PHP on staging first, because older plugins and themes are the usual cause of problems.
  • Renew the domain and SSL certificate. Turn on auto-renew and make sure the renewal email goes to an inbox someone reads.
  • Review plugin licenses. A premium plugin with an expired license often stops receiving updates, which turns it into a security risk.
  • Review who has access. Check hosting, domain registrar, DNS, Google Search Console and analytics accounts, not just WordPress users.
  • Refresh old content. Update posts that still get traffic but have out-of-date facts, prices or screenshots.

After every update: a 10-minute check

WordPress website maintenance checklist steps to follow after every update, from backup to clearing cache
The steps to follow around every update.

This is the routine I'd recommend around any update, from a single plugin to a major WordPress release:

  1. Back up the files and database.
  2. Update core, then plugins, then themes.
  3. Clear the cache in your caching plugin, your host and your CDN.
  4. Load key pages on desktop and mobile.
  5. Submit a form and confirm the email and CRM entry.
  6. Check for errors in Site Health and your error log.

If something breaks, restore the backup or roll back the single plugin, and update again once the plugin author has released a fix.

Signs your maintenance isn't working

  • The latest backup is weeks old, or exists only on the same server
  • Plugins show updates waiting for more than a few weeks
  • Site Health shows critical issues nobody has looked at
  • Form submissions drop without a drop in traffic
  • Search Console reports new errors you didn't know about
  • You don't know who has administrator access

Any one of these is worth fixing this week. If the site is already down or hacked, the hacked or broken website rescue checklist in our ebook shop covers what to do first.

Do it yourself or hand it off?

A small brochure site with a handful of well-known plugins is reasonable to maintain yourself if you set aside time each week and month. Hand it off when the site makes you money directly, such as a store, a booking system or a lead-generation site, or when it has custom code that a careless update could break.

If you're moving platforms, maintenance starts on day one of the new site. Our guide to HubSpot to WordPress migration covers the launch checks, and this checklist covers everything after.

The short answer

Back up and update weekly, and test the site and its main form after each update. Monthly, run Site Health, review security and users, check Core Web Vitals and Search Console, and test every form end to end. Quarterly, delete unused plugins, test a full restore and fix broken links. Yearly, review hosting, PHP version, domain, SSL and licenses. Take a fresh backup before any change, and keep copies off the server.

Sources: WordPress.org: Requirements, WordPress: Upgrading WordPress, WordPress: Plugins and themes auto-updates, WordPress: Backups, WordPress: Hardening WordPress, WordPress: Site Health screen, web.dev: Web Vitals.

Frequently asked questions

How often should a WordPress website be maintained?

Check backups and updates every week, review security, speed, forms and Search Console every month, clean up plugins, users and content every quarter, and review hosting, PHP version, domain and licenses once a year. Busy sites that change daily need daily backups.

How often should I back up my WordPress site?

WordPress's own documentation suggests weekly backups for smaller sites with few posts and daily backups for high-activity sites. Back up both the files and the database, keep 3 to 5 recent copies in different locations, and always take a fresh backup before an update or a move.

Should I turn on automatic updates in WordPress?

Minor core releases, which include security fixes, update automatically by default and should stay on. Plugin and theme auto-updates are opt-in per plugin or theme. They are reasonable for small, well-maintained plugins, but for plugins that run checkout, forms or page building it is safer to update after a backup and test the site afterwards.

What PHP version should WordPress run on?

As of November 2026, WordPress.org recommends PHP 8.3 or greater, with MySQL 8.0 or greater or MariaDB 10.11 or greater, and HTTPS support. Check your current version under Tools, Site Health, Info, Server.

How long does WordPress maintenance take each month?

For a small business site with a sensible number of plugins, the weekly and monthly checks in this list usually fit in an hour or two a month. Sites with WooCommerce, memberships or many custom plugins take longer because each update needs more testing.

Get in touch

Have a question about my work or something I wrote? Send me an email.