A WordPress maintenance checklist is the short list of jobs that keep a website safe and working: updates, backups, security checks, monitoring and small repairs, each done on a schedule. Most of it takes minutes a week. This guide gives you the whole list and how often to do each task. It also shows which tasks you can do yourself, and the signs that it is time to hand the work to someone else.
It is written for owners and managers who run a business website on WordPress. Read it before you decide who should look after your site.
What does WordPress maintenance include?
WordPress maintenance includes six kinds of work: updates, backups, security, monitoring, small repairs and a regular review of the content. Each one protects something different, and skipping any one of them leaves a gap the others cannot cover.
| Area | What it means | What it protects |
|---|---|---|
| Updates | Installing new versions of WordPress, your plugins and your theme | Security, and plugins that keep working together |
| Backups | Regular copies of the files and the database, kept away from the site | Your ability to undo any mistake or attack |
| Security | Removing what you do not use, controlling who can log in, blocking attacks | Your data, your visitors and your name |
| Monitoring | Watching that the site is online, fast and that forms still send | Inquiries and sales you would otherwise lose without knowing |
| Small repairs | Fixing broken links, layout problems and errors after updates | The impression the site makes |
| Content review | Checking prices, dates, team members and legal pages | Trust, and the accuracy search engines reward |
A plugin is an add-on that gives WordPress a feature, such as a contact form or a booking calendar. A theme controls how the site looks. Most of the work in this checklist is about them, because that is where most problems start.
The WordPress maintenance checklist
Here is the full checklist, grouped by how often each task is done. The times are typical for a small business site once you know the routine. A large site or an online store takes longer.
Every week
- Open the home page and two or three important pages on your phone and on a computer. Check they load and look right.
- Send a test message through your contact form and check that it arrives.
- Install any security update that is waiting, after checking that last night's backup exists.
- Read the emails from your host, your backup tool and your security plugin. Act on anything marked as a warning.
Every month
- Make a fresh backup, then update plugins, your theme and WordPress itself.
- After updating, check the pages that matter most: the home page, the contact form, and the booking or checkout pages if you have them.
- Delete plugins and themes you no longer use. Deactivated plugins can still be attacked.
- Review the list of users. Remove people who have left and lower the access of anyone who does not need to be an administrator.
- Test the speed of your home page and your most visited page, and compare it with last month.
- Look for broken links and pages that show "not found", and fix or redirect them.
Every three months
- Restore a backup to a private copy of the site (a staging site) to prove your backups actually work.
- Check that every plugin you use is still being updated by its developer. Replace any that has not been updated for a long time.
- Ask your host which version of PHP (the language WordPress runs on) your site uses, and whether a newer one is available.
Every year
- Check that your domain name and your security certificate (the padlock in the browser) renew automatically, and who receives the renewal emails.
- Change important passwords and confirm that two-step login is on for every administrator.
- Read the whole site as a visitor would: old prices, past events, people who have left, an outdated privacy policy.
If this list feels like a lot, notice how much of it is checking rather than doing. The work itself is usually less than an hour a month for a small site. The value is in doing it on time, every time.
Keep a simple maintenance log
A maintenance log is a short record of what was done and when: the date, the updates installed, anything that broke and how it was fixed. It takes a minute per entry and saves hours later.
When something goes wrong weeks after an update, the log tells you what changed and when. When you hand the site to a new person or company, it shows them the site's history on day one. It also keeps you honest: a month with no entry is a month the checklist was skipped.
A shared spreadsheet is enough. Use one row per visit, with columns for the date, who did it, what was updated, the backup used, and notes. Some maintenance plugins keep a log for you, but a simple sheet you control works just as well.
How often should WordPress be updated?
Check for updates every week, install security updates as soon as they appear, and install the rest at least once a month, always after a backup. Waiting longer does not make updating safer; it only makes each update bigger and more likely to clash with something.
WordPress already does part of this for you. According to the WordPress.org documentation on updating WordPress, minor and security releases of WordPress itself are installed automatically. Major releases still need you to click "Update Now". Plugins and themes are different. Since WordPress 5.5 you can turn on automatic updates for each plugin and theme, but you have to choose to do it, one by one.
Automatic updates are useful for small, well-known plugins. Some plugins carry your business: the shop, the booking system, the page builder. Many site owners update those by hand, so they can check the site straight afterwards. WordPress.org's own advice is the same in both cases: make sure you can go back to a previous version before you update.
When an update breaks something
- Do not keep clicking. Note which update you installed last.
- Restore the backup you made before the update. Your site is back as it was.
- Find the cause on a staging site, or wait a few days for the plugin's developer to release a fix.
- Update again once the fix is out, and check the same pages again.
This is why the backup always comes first. With a fresh copy in place, a broken update costs you a few minutes. Without one, it can cost days.
Backups that actually save you
A backup only helps if it is recent, kept somewhere other than your website's server, and has been tested. Many site owners discover during an emergency that their backup was old, incomplete or stored on the same server that just failed.
A backup routine that works
- A full backup (files and database) every day for a site that changes often, at least every week for a site that rarely changes.
- An extra backup right before every update.
- Copies kept in a second place, such as cloud storage, away from your hosting account.
- Several copies kept, so you can go back further than yesterday. A problem is sometimes noticed only weeks later.
- A test restore every three months, on a staging site.
Your host may already make backups. Ask how often, how long they are kept, where they are stored, and how you restore one. If the answer to the last question is "open a support ticket and wait", keep your own backups as well.
The WordPress security tasks that matter most
Most WordPress security problems start in plugins, not in WordPress itself. Keeping plugins updated, removing the ones you do not use and controlling who can log in prevents most of the attacks small business sites face.
The numbers explain why. In its State of WordPress Security in 2026 report, the security company Patchstack counted 11,334 new vulnerabilities (security flaws) in the WordPress world in 2025. 91% were found in plugins and 9% in themes, with only 6, all low priority, in WordPress itself.
In plugins
Of 11,334 new vulnerabilities found in 2025, 91% were in plugins and 9% in themes.
91%of new vulnerabilities
No fix in time
The developer had not released a fix by the time the flaw was made public.
46%of vulnerabilities
Used within a day
Attackers exploited them within 24 hours of disclosure.
About halfof high-impact flaws
Two lessons follow. First, every plugin you install is something you have to keep watching, so fewer plugins means less risk. Second, attackers move fast: an update that fixes a known flaw is worth installing the same day.
The short security list
- Keep only the plugins and themes you use, from developers who still update them.
- Give administrator access only to people who need it, and turn on two-step login for them.
- Use a firewall: your host may provide one, or a security plugin can.
- Limit repeated login attempts, so bots cannot guess passwords endlessly.
- Know the signs of a hack: pages you did not create, redirects to other sites, a warning from Google or your browser, or a sudden email from your host. If you see one, restore a clean backup and change every password.
Monitoring your site before your visitors notice
Monitoring means tools that warn you when something goes wrong, so you hear about a problem from an alert and not from a customer. Four things are worth watching on any business site.
- Uptime: a free or low-cost uptime service checks your site every few minutes and emails you when it stops answering.
- Forms: forms can stop sending without any error on the page, for example after an email setting changes. The weekly test message catches this.
- Speed: a site that slowly gets slower loses visitors before anyone complains. A monthly test of your key pages with Google's PageSpeed Insights shows the trend. Our speed optimization page lists the usual causes when it keeps dropping.
- Search Console: Google's free Search Console tells you when pages drop out of Google, when your site has errors, and when Google suspects a hack.
What your host may already do
Hosting and maintenance are different jobs. Hosting keeps the server running; maintenance keeps the website on that server updated, backed up and working. Some hosts do part of the maintenance too, so check before you pay twice.
| Task | A basic host | A managed WordPress host | You or a maintenance plan |
|---|---|---|---|
| Server and network | Yes | Yes | No |
| Backups | Sometimes, ask how often | Usually daily | Your own copies as well |
| WordPress core updates | Minor ones (automatic in WordPress) | Usually | Major ones, checked afterwards |
| Plugin and theme updates | No | Sometimes | Yes |
| Checking the site after updates | No | Rarely | Yes |
| Firewall and malware scan | Sometimes | Usually | Yes, if the host does not |
| Fixing what breaks on your site | No | Rarely | Yes |
| Content and links | No | No | Yes |
Questions worth asking your host: How often do you back up my site, and for how long do you keep the copies? Do you update plugins, or only WordPress itself? If my site is hacked, do you clean it, or only tell me? What happens if an update you install breaks my site?
Write the answers in your maintenance log. If your host changes its terms, or you move to another host, you will know exactly which tasks you have to take back.
Do it yourself or get help?
You can maintain a WordPress site yourself if it is small and does not take payments or bookings. You also need about an hour a month that you will not skip. Getting help makes sense when a day offline would cost you money, or when nobody on your team will reliably do the checklist.
Your site takes payments, bookings or a steady flow of inquiries
Someone responsible for itA day offline costs real money
It relies on many plugins or a page builder, and nobody tests after updates
Get helpUpdates are more likely to clash
It relies on many plugins or a page builder, and you test after every update
Do it yourselfCheck the key pages each time
A small site, and someone will do the weekly and monthly tasks
Do it yourselfWith a host that keeps daily backups
Nobody will reliably do the checklist
Get helpA site nobody updates is an easy target
If you decide to pay for maintenance, compare plans by what happens when something goes wrong, not only by the list of tasks. Ask who checks the site after updates and how fast they start work when it is down. Ask whether fixing a hacked site is included, and whether you can have a full copy of your website if you leave. We describe how we handle each of these on our WordPress maintenance page, if you want an example to compare against.
Questions about WordPress maintenance
Check for updates every week and install security updates as soon as they appear. Install the rest at least once a month. Always make a backup first, and check your most important pages after updating.
Yes, if the site is small and does not take payments or bookings, and someone will reliably do the weekly and monthly tasks. It usually takes less than an hour a month once you know the routine. Use a host that keeps daily backups.
Known security flaws stay open, and attackers often use them within a day of being published. Plugins also stop working well together over time. A site left for a year can need a costly repair instead of a quick update.
Hosting keeps the server your site lives on running. Maintenance keeps the website itself updated, backed up, secure and working. Some hosts include parts of maintenance, such as backups, so ask yours what it covers.
Doing it yourself costs only your time, usually under an hour a month for a small site. Paid plans vary widely in what they include, so compare them by how fast problems are fixed and what is covered when something breaks.
Published . Filed under Websites.


