Securing a WordPress site: the monthly maintenance checklist
Updates, tested backups, user accounts, monitoring and what to do after a hack: the monthly checklist to keep a WordPress site secure without losing your days.

A WordPress site is never “finished”. The core, the theme and the plugins change constantly, and every postponed update leaves a door ajar. Most of the hacked sites we see were not hit by a sophisticated attack. They were let down by a forgotten plugin, a reused password or a backup nobody had ever tested.
Here is the checklist we run every month on the sites we maintain. It takes one to two hours for a brochure site, a little more for a site with a shop or a members’ area. You can follow it yourself, or hand it over to a WordPress maintenance team.
Why monthly maintenance beats fixing things as they break
WordPress powers a very large share of the web. That is its strength, and it is also what makes it a target: bots scan sites around the clock looking for known vulnerable versions. As soon as a plugin vulnerability is made public, exploitation attempts follow, often very quickly.
A monthly routine, combined with security fixes applied as soon as they are released, keeps a site healthy without eating up your weeks. The principle is simple: a fixed slot in the calendar, the same list every time, and a written record of what was done. That record pays off the day you need to understand what changed.
1. Updates: core, theme and plugins
This is the step that prevents the most trouble. Since version 3.7, WordPress installs minor core updates on its own, the ones that fix security holes. Since version 5.5, you can also turn on automatic updates plugin by plugin. But automatic does not mean unchecked.
- Update a copy of the site (staging) first, then the live site.
- Read the changelog of sensitive plugins (forms, cache, e-commerce, SEO) before a major version.
- Delete deactivated plugins: even inactive, their files stay on the server.
- Replace any plugin that has not been updated for a long time or has been removed from the official directory.
- Check your host’s PHP version under Tools → Site Health.
Fewer plugins means a smaller attack surface. It is one of the reasons our WordPress themes are custom-coded without a page builder: many features that would need a plugin elsewhere are built straight into the theme.
2. Backups: have them, and know how to restore them
A backup that has never been restored is just a hypothesis. Every month, check three things.
- The backup really contains the files, including the wp-content/uploads folder, and the database.
- It is stored away from the site’s server, in remote storage, not only with the same host.
- A full restore works on a test environment, and you know how long it takes.
Set a retention period too. A site can be infected for weeks before anyone notices, so keep several restore points spread over time, not just the last seven days.
3. Accounts and passwords: who can access what
Access piles up over the years: a former contractor, an intern who left, an account created for a test. Every unnecessary account is one more door.
- List the users and delete those who no longer need access, reassigning their content.
- Give the lowest possible role: an editor does not need to be an administrator.
- Require long, unique passwords stored in a password manager.
- Turn on two-factor authentication for administrators. WordPress does not offer it natively, so use a well-established plugin.
- Revoke application passwords (Profile → Application Passwords) that are no longer used.
- When someone leaves the project, also change the hosting, SFTP and database credentials.
On the configuration side, add the DISALLOW_FILE_EDIT constant to wp-config.php to disable the file editor in the admin. A compromised account will no longer be able to change the theme’s code from the browser.
4. Monitoring and alerts: know before your visitors do
The worst case is learning about a hack from a customer or from Google. Simple monitoring prevents that.
- An uptime monitoring service that alerts you when the site stops responding.
- Search Console: the “Security issues” and “Manual actions” reports should stay empty. A sudden rise in indexed pages you do not recognise is a warning sign.
- A web application firewall and a limit on login attempts.
- Regular file scans to spot unexpected changes.
- WordPress’s Site Health tool, checked at every pass.
Use the monthly pass to look at speed as well. A page that suddenly slows down for no reason can hide an injected script. Our guide to speeding up a WordPress site and its Core Web Vitals gives the thresholds to watch.
5. What to do if your site is hacked
If the site is compromised despite everything (redirects to dubious sites, foreign-language pages in Google, an unknown administrator), follow a precise order.
- Isolate. Put the site in maintenance mode if needed and change every password at once: WordPress, hosting, database, SFTP.
- Copy. Make a copy of the infected site before touching anything. It will help you understand where the attack came from.
- Find the entry point. Vulnerable plugin, stolen account, modified file: skip this step and the attack will come back.
- Clean up or restore a clean backup from before the infection, then apply every update.
- Regenerate the security keys (salts) in wp-config.php to close every open session.
- Tell Google. If Search Console reports a security issue, request a review once the site is clean.
A hack also leaves traces in Google: spam pages in the index, hidden links. A technical SEO check after the clean-up gets those URLs out of the index and confirms your real pages are still in place.
The monthly checklist at a glance
- Full backup done, stored elsewhere, restore tested.
- Core, theme and plugins up to date, tested on staging.
- Unused plugins deleted.
- Users and roles reviewed, two-factor authentication on for administrators.
- Search Console free of security issues and manual actions.
- Site Health without critical alerts.
- Uptime and speed checked.
- Written report of what was done.
If you would rather not think about it any more, this is exactly what our maintenance and support service covers, with a single point of contact. Pricing is quoted after a free 30-minute audit. And if your site has become too heavy to maintain, our WordPress agency can rebuild it on a custom theme, with far fewer plugins to watch.
Frequently asked questions
How often should a WordPress site be updated?
Security fixes should be applied as soon as they are released, and WordPress already installs minor core updates on its own. Everything else (major versions, theme, plugins) can be grouped into a monthly pass, tested on a copy of the site first.
Is a security plugin enough to protect WordPress?
No. It helps (firewall, login limits, file scans), but it does not replace updates, tested backups or account management. Most intrusions come through an outdated plugin or a weak password.
How long should backups be kept?
Keep several restore points spread over several weeks, stored away from the site’s server. An infection can go unnoticed for a while: if you only keep the last few days, all your backups may already be affected.
How can I tell if my WordPress site has been hacked?
The most common signs: redirects to other sites, unknown pages in Google results, a new administrator you did not create, a Search Console alert or a sudden slowdown. At the slightest doubt, change the passwords and have the files scanned.
How much does WordPress maintenance cost at Nifty Link?
It depends on the site: number of plugins, whether there is a shop, how often we step in. We quote after a free 30-minute audit, which also flags the most urgent risks.



