WordPress Maintenance Checklist: Weekly, Monthly and Quarterly Tasks

Last updated November 16, 2026.

Your site loads slower than it used to. A backup nobody has checked in months. A plugin you stopped using years ago, still sitting there. Nothing dramatic has happened, and that is the point: a WordPress site goes wrong quietly, one small job at a time, until visitors notice what the owner did not.

A wordpress maintenance checklist exists to catch those problems while they are still small. It is not a one-time project. It is a short routine you repeat on a schedule, the same way you service a car. Below is the wordpress maintenance schedule I recommend to every WordPress site owner: what to check every week, every month, and every quarter, and roughly how long each session takes.

Work through it in order, one session at a time. The weekly part takes about fifteen minutes once you have done it twice.

Three Ground Rules Before You Start

Before any routine works, agree with yourself on three rules. They take five minutes to set up and they save you from nearly every maintenance disaster.

Rule 1: back up first, update second. Not a backup your host might have. A copy you made yourself, stored somewhere other than your own server, that you have restored at least once. That copy is what turns a broken update into a five-minute fix instead of a lost weekend.

Rule 2: make one change at a time. Update one thing, check the site, then update the next. If you change everything in one go and the site breaks, you have to undo everything to find the cause.

Rule 3: write down what you did. A short note with the date, the task, and what happened is the record that proves the routine ran, and it is the first thing you reach for when something goes wrong later. Any text file or shared document works. If your site was ever compromised, our WordPress security services cover the deeper hardening work that a checklist alone cannot.

These three rules apply to every section below.

TaskHow oftenTime
Confirm backups, apply updates, review security alerts, visual check, clear spamWeeklyAbout 15 minutes
Security scan, broken links, database cleanup, speed test, Search Console and 404s, user reviewMonthlyAbout 45 to 60 minutes
Plugin and theme audit, restore test, PHP, SSL and hosting check, content refresh, performance reviewQuarterlyAbout 2 to 3 hours
Domain, hosting, theme, legal pages, content auditYearlyHalf a day

Weekly Tasks (About 15 Minutes)

Weekly tasks are the light, frequent checks. They keep the site current and catch problems early.

1. Confirm your backups ran

Open your backup tool or hosting panel and confirm that the most recent scheduled backup completed successfully. Check that the backup file actually exists and that it was stored offsite or in a separate location, not only on the same server. If your backup tool shows a failed or missing run, fix the schedule before doing anything else. Back up before every update, not just on the weekly schedule. A backup that might not work is not a safety net.Hand holding an external backup drive plugged into a laptop.

2. Apply WordPress updates

Go to Dashboard, then Updates. Apply WordPress core updates, then plugin updates, then the theme update. Do this one item at a time and reload the site after each round. Security releases should go on as soon as you see them. If your site takes payments or bookings, consider testing the update on a staging copy first; most decent hosts provide one-click staging, and it is made for exactly this.

3. Review security alerts

If you use a security plugin, glance at its dashboard or email reports for the week: login attempts blocked, files changed, or any warning about a vulnerable plugin. You do not need to read every log entry. You are looking for anything that changed or spiked compared to a normal week.

4. Do a quick visual check

Open the homepage and one or two key pages (for example, your services page and contact page) in a browser. Look for broken layouts, missing images, or anything that shifted after an update. Then submit your contact form the way a visitor would, and confirm the message actually arrives in your inbox. Forms break silently, and this thirty-second test catches it.

5. Clear pending comments and spam

If your site accepts comments, delete the spam and reply to or approve the real ones. Spam comments left sitting on posts are not just ugly; on some themes they can carry links you do not want pointing to or from your site.

6. Set up uptime monitoring and read its alerts

Nothing on your site can tell you the site is down, because a plugin on a dead site cannot send you a message. An uptime monitor checks your site from outside the server every few minutes and alerts you by email or text when it stops responding. Set one up once, then read its alerts in the weekly session the same way you read your security alerts. If the site was down at the same hour on several nights, that pattern is worth telling your host about.

Monthly Tasks (About 45 to 60 Minutes)

Monthly tasks go one layer deeper. They deal with the slow accumulation of clutter and the first signs of performance or visibility problems.

1. Run a full security scan

Once a month, run a complete malware scan, not just the quick daily one. Review the results and act on anything flagged. This is also a good time to change your admin password if you have not done it in a while, and to remove any admin accounts that no longer need access. Old contractor accounts and unused admin users are one of the most common weak points on real sites. If you find malware, our emergency recovery guide for hacked WordPress sites walks through the cleanup in order. If the scan finds malware, the cleanup is a separate job with its own cost: our guide to WordPress malware removal cost explains what a cleanup includes and what changes the price.

2. Check for broken links

Run a broken-link scan across the site. Fix internal links that point to pages you moved or deleted, and update or remove external links that no longer work. Broken links frustrate visitors and make a site look neglected, and they are cheap to fix when you catch them monthly instead of discovering them a year later.

3. Clean the database

Over a month, the database collects post revisions, spam comments, transient records, and orphaned data from deleted plugins. A database cleanup plugin can clear this safely, but take a fresh backup first. After cleanup, most owners notice the admin area feeling a little faster, especially on sites with hundreds of posts. One part of the database that quietly grows is the autoloaded options table: options WordPress loads on every page, including ones left behind by deleted plugins. Our guide to cleaning up autoloaded options explains what to check and what is safe to remove.

4. Test your site speed

Once a month, run your homepage and one inner page through a speed test and write down the results. You are not chasing a perfect score. You are watching for change. If load time creeps up month after month, something is growing: images getting heavier, a plugin adding scripts, a database getting slower. Catching the trend early is much cheaper than fixing a site that has become visibly slow. While you are checking, open Tools, then Site Health: it groups problems into critical issues, recommended improvements and passed tests, and it flags an outdated PHP version, plugins waiting for updates, and background updates that are not working. Our speed optimization service page explains what usually causes the slowdown on WordPress sites.

5. Review Search Console and 404 errors

Open Google Search Console and check the coverage and Core Web Vitals reports for new errors. Look at the list of 404 pages visitors are hitting. A 404 that gets traffic every week deserves a redirect to the right page, which takes a minute and keeps visitors from bouncing.

6. Review users and roles

Go to Users and confirm every account still belongs there, with the right role. Downgrade anyone who only needed temporary access. This is quick and it closes one of the simplest ways a site gets compromised. Turn on two-factor authentication for every administrator account, and do the same for your hosting, domain registrar and email accounts, because an attacker who controls your email can reset the WordPress password.Woman reviewing printed site reports beside her laptop.

Quarterly Tasks (About 2 to 3 Hours)

Quarterly tasks are the deeper audits. They take a little longer, but they are the ones that prevent the expensive failures.

1. Audit every plugin and theme

Open the plugins list and ask about each one: do we still use this, and is it still maintained? Remove plugins that are deactivated, abandoned by their developers, or duplicated by something else you installed. Do the same for themes: keep your active theme and one default WordPress theme as a fallback, and delete the rest. A plugin you never open still runs code on your server, and code nobody watches is code nobody patches.

2. Test a full backup restore

Most owners never test a restore until the day they need one. Once a quarter, restore your latest backup to a staging site or a test folder and confirm the site actually works. Until you have restored it once, a backup is a file you are trusting, not a recovery you have proven. You do not want to discover a corrupt backup on the day you actually need it.

3. Check PHP, SSL, and hosting health

Look at Tools, then Site Health, and check which PHP version your host runs. Outdated PHP is both a security risk and a performance drag; most hosts let you switch versions in their panel, and testing the new version on staging first avoids surprises. WordPress recommends PHP 8.3 or greater. If your site is still on PHP 8.2, plan the move now, because its security support ends on 31 December 2026, and PHP 8.1 and older receive no security fixes at all. Confirm your SSL certificate is valid and that your domain registration is not expiring soon. While you are there, glance at disk usage in your hosting panel; backups and image libraries quietly fill up space.

4. Refresh stale content

Read your key pages with fresh eyes once a quarter. Update anything that changed: services you no longer offer, team members who moved on, old statistics, seasonal references, contact details. Then check your contact page and footer for the same. Stale content tells visitors the business behind the site might be stale too.

5. Review performance against the monthly log

Compare this quarter’s speed test numbers with the previous ones. If the trend is worse, dig into the cause before it becomes a visitor complaint. Common culprits are uncompressed images uploaded during the quarter, new tracking scripts, or a plugin that quietly added a heavy feature in an update.

Yearly Tasks (Half a Day)

Once a year, step back and review the whole setup rather than the pieces:

  • Domain and renewals: confirm the domain is renewed for another year and that the renewal goes to an email address you still check. Losing a domain to an expired registration is embarrassing and entirely preventable. Public SSL certificates are getting shorter: certificates issued from 15 March 2026 last at most 200 days, so confirm that automatic renewal actually works rather than relying on a reminder email.
  • Hosting plan: is your current plan still right for your traffic? A plan that was perfect three years ago may be underpowered now, or you may be paying for capacity you never use.
  • Theme review: check whether your theme is still maintained and compatible with the current WordPress version. If the theme author has gone quiet, plan a replacement before it becomes an emergency.
  • Legal pages: review the privacy policy, terms, and any cookie notice. Regulations change, and so do the tools your site uses.
  • Full content audit: walk through every page and ask whether it still deserves to exist. Merge thin pages, update the popular ones, and remove what no longer serves a purpose.

When an Update Breaks Something

Undo first, restore second, investigate last. When an update breaks the site, that order is what gets you back online fastest:

  1. Start with the last thing you changed, and check your notes for what it was.
  2. If you can reach the dashboard, switch the plugin off from the dashboard and check whether the site comes back.
  3. If you cannot reach the dashboard, rename its folder through your hosting file manager or FTP. WordPress will switch it off automatically and the site should load.
  4. If the site is still broken, put the backup back, then investigate the conflict on a staging copy.

Do not start changing three things at once in a panic. Your notes and your backup exist precisely for this moment.

Frequently Asked Questions

How much time does WordPress maintenance actually take?

For a typical small business site, plan on about fifteen minutes a week, an hour a month, and a few hours each quarter. The first few sessions take longer while you set up backups, monitoring, and your log. After that it becomes routine. Larger or more complex sites, especially shops with daily orders, need more time or a dedicated routine.

Can I automate all of this?

Parts of it, yes. Backups, security scans, uptime monitoring, and update notifications can all run automatically. But automation still needs a human watching it. Scheduled backups that silently fail, update emails that go to an unchecked inbox, and scans nobody reads are some of the most common causes of the disasters maintenance is supposed to prevent. Automate the work, but keep the weekly check on a human.

What happens if I skip maintenance entirely?

Nothing dramatic at first, which is exactly why people skip it. Updates pile up, backups age, and small problems accumulate. The bill arrives later, usually all at once: a hacked site, a broken update chain that cannot be resolved cleanly, or a site so slow that visitors leave. Regular maintenance spreads that cost into small, manageable pieces instead of one large emergency.

Do I really need a staging site?

For a simple blog or brochure site, you can often get by without one if your backups are solid and you update carefully. For any site that takes orders, bookings, or payments, a staging site is strongly recommended. It lets you test updates where a mistake costs you nothing instead of where a mistake costs you customers.

Should I update plugins the moment new versions appear?

Security releases, yes, apply them promptly. Feature updates can wait for your weekly session. The middle ground that causes trouble is updating twelve plugins at once on a live site without a backup. One at a time, with the site checked between rounds, is the safe pattern.

What is the difference between doing this myself and a maintenance plan?

The tasks are the same either way. Doing it yourself costs your time and attention every week. A WordPress maintenance plan hands the routine to someone who does it daily across many sites, including the unglamorous parts like testing backups and watching security logs. What a plan usually covers, and what moves a quote, is explained in our guide to WordPress maintenance cost factors. The right choice depends on how much your time is worth and how much you enjoy this kind of work. If you would rather focus on running your business, see the full list of services we offer.

Should I turn on automatic updates for everything?

Not for everything. Minor WordPress core releases and small, well-maintained plugins are safe to update automatically. For the plugins your business depends on, WooCommerce, payment gateways, page builders and anything that touches checkout, update manually after testing on a staging copy. Since WordPress 6.6, a plugin auto-update that causes a fatal error is rolled back automatically, but that only catches crashes: it will not notice a broken layout or a payment button that stopped working, so the weekly check still matters.

How often should I back up my WordPress site?

Back up before every update, without exception. Beyond that, weekly backups suit a smaller site that changes rarely, and daily backups suit a busy site or a shop that takes orders every day. Keep at least three recent backups stored in different places, for example on the server, in cloud storage and on your own computer. A backup that lives only on the same server as the site disappears with the server, so the offsite copy is the one that matters.

What is uptime monitoring, and do I need it?

Uptime monitoring is a service outside your site that checks whether the site loads, every few minutes, and alerts you by email or text when it does not. You need it because nothing on the site itself can tell you the site is down: a plugin on a dead site cannot send you a message. Free monitors exist, and one alert that catches a night of downtime is worth the setup. Add your contact page or checkout as a second check if the homepage alone would not show a broken form.

Should I turn on two-factor authentication for my admin accounts?

Yes, for every administrator account. A password alone is one thing to steal; two-factor authentication means a stolen password is not enough on its own. Turn it on for hosting, your domain registrar and your email as well as WordPress, because an attacker who controls your email can reset the WordPress password. While you are there, remove any admin account that no longer belongs to a real person on your team.

Start With This Week

You do not need to do everything on this wordpress maintenance checklist today. Do this one thing this week: confirm that your site has a recent backup you can actually restore, and write down the date. Then run your updates one at a time. That single habit covers most of what goes wrong on WordPress sites.

After that, work through the weekly wordpress maintenance tasks until they feel automatic, then add the monthly tasks. By the end of your first quarter, you will have a site that stays fast, stays secure, and never surprises you.

If maintaining the site yourself sounds like a chore you will keep postponing, that is worth being honest about. A neglected site costs more than a maintained one. You can message us on WhatsApp, reach us through the contact page, or email [email protected] and we will take the whole routine off your hands.

Scroll to Top