WordPress maintenance

WordPress Maintenance: What’s Actually Happening Behind the Scenes

wordpress-maintance-featured-image
WordPress now runs well over 40% of all websites online — which is exactly why keeping on top of it matters more than most businesses realise.

WordPress now runs more than 43% of all websites online, and accounts for well over 60% of every content management system in use — somewhere north of 810 million sites. That scale is exactly why it’s such a constant target: the bigger the platform, the more automated attacks are written specifically to find weaknesses in it. WordPress itself is a genuinely secure platform when it’s looked after properly, but “looked after properly” is doing a lot of work in that sentence.

Key takeaways

  • Maintenance isn’t only about security — it’s also what keeps a site fast, current and ready to grow.
  • Hosting is the foundation everything else sits on, and it’s the one area where cutting cost often costs more later.
  • Roughly 70% of live WordPress sites are running a version with a known vulnerability.
  • Every plugin you add is a trade-off between functionality and risk — fewer, well-chosen plugins beat many convenient ones.
  • Weak or reused passwords are still the single biggest reason WordPress sites get compromised.

Why it’s not optional

It’s easy to think of WordPress maintenance as purely a security exercise, and security is a big part of it — but it isn’t the whole picture. A properly maintained site also runs faster, takes advantage of genuine technical improvements as they arrive, and keeps a stable foundation under it as the business grows. A site that’s never maintained doesn’t usually fail all at once; it just gets slower, clunkier and more fragile until something finally breaks at the worst possible moment.

Hosting

It sounds like an obvious starting point, but a surprising number of businesses still choose cost over security and performance when picking a host. A proper hosting provider does more than just keep a site technically online — the better ones include firewalls, malware scanning and genuine WordPress-specific protection as standard.

We work with two preferred hosting partners, WP Engine and SiteGround, both built specifically around hosting WordPress well rather than hosting everything adequately. Which one suits a given site depends on its size and needs, but the principle is the same either way: think of it less like a server and more like a dedicated technical assistant sitting behind your site — threat detection and blocking, daily backups, WordPress core updates, and caching that genuinely improves page speed, all handled as part of the plan rather than left to chance.

WordPress and PHP versions

Keeping WordPress current

This sounds basic, but recent figures suggest as many as 70% of live WordPress sites are running a version with a known vulnerability in it. Staying current is genuinely straightforward if you do it regularly — the jump from one minor version to the next is trivial, but the jump from a version three years old to the current one is a much bigger, riskier leap. The longer a site goes unupdated, the harder catching up becomes, which is exactly why it’s worth never letting that gap open in the first place.

PHP, underneath it all

Even a fully up-to-date WordPress install can still be exposed through weaknesses in PHP, the programming language WordPress itself runs on. PHP runs server-side, generating the page a visitor’s browser actually receives, and it’s usually paired with a database to power anything dynamic — which is most of what a modern website does. At an absolute minimum, a site should be running PHP 7.4 or later; newer is better where your plugins and theme support it. This is genuinely a developer-side task rather than something a business owner needs to action themselves, but it’s worth knowing it exists and asking whether it’s being kept current.

Plugins

Yes, more updates — but plugins are also one of WordPress’s biggest strengths, letting a site add real functionality without a custom build for every feature. The trade-off is that every plugin added increases a site’s overall complexity, and each one is additional code that can become a weak point if it’s left unmaintained.

Before adding any plugin, it’s worth asking a few quick questions: do you actually need it, or does something close to it already exist in WordPress core or your hosting? How actively is it maintained — who’s the developer, and do they have a track record? Is there a recent update history and solid documentation behind it?

We generally recommend running the fewest plugins that genuinely do the job, since every one you don’t install is one less thing to maintain and one less thing that can go wrong. For whatever you do keep, treat updates like a recurring task rather than an occasional one — a quarterly check works well for most sites, with the same logic as WordPress core: the longer an update is left, the bigger and riskier the eventual jump becomes.

“A site that’s never maintained doesn’t usually fail all at once — it just gets slower and more fragile until something finally breaks.”

Passwords and user access

This one sounds obvious too, and yet weak password habits remain one of the single biggest reasons WordPress sites get compromised. A simple, memorable password, a password shared casually between colleagues, or one that’s never been changed since the site launched — these are far more common than most businesses would admit, and they’re exactly what a brute-force attack is built to exploit: automated software simply guessing passwords until one happens to work.

Good password and access practice looks like:

  • Complex passwords, at least 16 characters, mixing upper and lower case, numbers and symbols
  • Nothing drawn from a dictionary word, name or obvious pattern
  • Changed regularly — worth tying to the same quarterly check as plugin updates
  • Never shared between colleagues, however convenient it seems
  • Each user given only the access level they actually need, not automatically made an admin
  • Two-factor or multi-factor authentication enabled as an extra layer
  • Old user accounts removed promptly once someone leaves the business

What a support plan actually covers

This is the part of maintenance most business owners never see directly, which is rather the point — a plan handling all of this well is one you rarely have to think about. Beyond the core updates, hosting and password practices covered above, a proper support plan typically includes 24/7 uptime monitoring, security scanning, hosting liaison, crisis resolution if something does go wrong, server migrations, general website audits, and small ongoing design or development requests that come up along the way.

It’s worth being honest: none of this is especially glamorous work. But it’s the difference between a website that quietly keeps working in the background for years, and one that eventually becomes a problem nobody saw coming — usually at a moment with real cost attached, whether that’s lost sales during downtime or the much larger bill that follows a genuine security breach.

Want someone else handling all of this for you?

Frequently asked questions

If I don’t have a support plan, how often should I be updating WordPress myself?

At a minimum, check monthly — but security-critical updates should be applied as soon as they’re released, not left for your next scheduled check. The gap between “known vulnerability published” and “automated attacks start targeting it” can be a matter of days.

What happens if a plugin update breaks something on my site?

This is exactly why updates should be tested on a staging copy first, not applied directly to a live site. If something does break, a recent backup means rolling back is usually a quick fix rather than a crisis — another reason daily backups matter more than they might seem to.

Is PHP something I need to worry about as a business owner?

Not directly — it’s genuinely a developer-side task. But it’s worth asking whoever manages your site which PHP version it’s running, since an outdated one can quietly undermine even a fully updated WordPress install.

Do I really need two-factor authentication on a small site?

Yes. Automated attacks don’t care how small your business is — they’re scanning for weak logins at scale, not targeting you specifically. Two-factor authentication is one of the cheapest, easiest security improvements available, regardless of site size.

How is WP Engine or SiteGround different from a normal web host?

A normal host keeps your site online. A WordPress-specific host like WP Engine or SiteGround is built around WordPress’s particular needs — automatic core updates, WordPress-aware caching, built-in threat detection and daily backups all handled as standard, rather than added on separately or left to you. We choose between the two depending on what a particular site needs.