Three Rules Behind How We Look After WordPress Sites

Since June we have written 25 articles about how we look after WordPress sites. Read together, they keep coming back to three rules. This page lists every article under the rule it belongs to, so you can find them all in one place.

The two most-read articles were both about plugins. One asked why a plugin called Essential Addons is an add-on if it is essential. The other explained why many of our sites get one small custom plugin instead of several separate ones. Neither mentions price, servers or uptime.

Rule 1: Fewer Plugins, More Small Custom Code

Every plugin you install is a supplier you keep for the life of the site. Someone has to update it, check it still works with everything else, renew the licence if it is paid, and replace it when the author moves on. In most industries three to five plugins do the real work. Much of the rest is a few lines of code, and those are easier to look after in one custom file where the next developer will find them.

Article What it covers
WordPress Is the Lingua Franca of the Web Why WordPress: more developers know it than any other platform.
Open Source Guarantees Longevity That No Proprietary Platform Can Why the code outlives any single company.
Fewer Plugins, More Custom Code Our starting position on plugins.
Only 3-5 Plugins Per Vertical Actually Matter Which plugins are worth the upkeep.
Plugin Authors Burn Out: Plan For It What happens when the only maintainer stops.
Why Many WordPress Sites We Look After Get One mu-Plugin Where the small changes go instead.
WordPress Multisite Very Rarely Makes Sense Sharing one install ties every site to the same update day.
Static or CMS Is Usually Asked on the Wrong Desk Who should actually make that call.
If It Is Essential, Why Is It an Add-on? A plugin that fills gaps in a page builder, which itself sits on WordPress.

Rule 2: Updates on a Schedule, Critical Fixes Within Hours

Every site gets a monthly update window. Updates are tested on a staging copy first and only then go live. Critical security fixes don’t wait for the window. This year tested that rule twice: a WordPress security release in September, and PHP2Shell in October. The PHP2Shell fix came out at 3am New Zealand time, and every server we run was patched by 6:27.

Article What it covers
Updates Should Be Scheduled and Deliberate, Not Rushed The monthly window, and when we don’t wait for it.
Poor Passwords Were the Headline. The Server Had Four Other Ways In. Why a security review starts with a list of everything, not a password change.
Why Every Staging Site Gets a Popup Password Keeping test copies out of Google.
How We Patched PHP2Shell on a Backported PHP 8.1 The night of the release, hour by hour.
Security Updates Are a Schedule, Not a Button 255 site updates, with a median of 2 hours 14 minutes to live.
Where the Security Update Effort Actually Goes The 6% of updates that needed real work.
Four Ways to Approve a WordPress Security Update How clients approve an update, and what each choice means.

Rule 3: The Boring Parts Come With the Hosting

Tested backups, monitoring that doesn’t rely on a customer noticing, a CDN and a staging site are all part of running a website, so they come with the hosting. Things that are a different job, like email on staff phones, go to people who do that all day.

Article What it covers
Backups Must Be Automated, Frequent, Off-Site, and Tested Eight months of nightly backups that were missing the database, and the monthly restore test that would have caught it.
Monitoring Is Criminally Underused You shouldn’t hear about an outage from your customers.
The Real Cost of Cheap Hosting A site down for six days at a budget host, and what happens to the price at renewal.
On a VPS You Cannot Tell What Is Overloaded One processor, two suspects.
Nobody Configures Their VPS The default settings a server comes with.
On a VPS, the Server Backs Itself Up The backup runs on the same machine it is meant to protect.
A CDN Is Win-Win-Win, So Why Is It Sold as an Add-On? Why a CDN belongs in the hosting, not on the invoice as an extra.
Why We Don’t Host Email Spam filtering and phones are a job of their own.
We Don’t Charge for a Site Until It Goes Live Building a site is not the same as hosting it.

What Comes Next

Between now and Christmas, the articles look back over the year: how much security pressure there was, what we changed our minds about, and the update numbers so far. If you look after WordPress sites and want a second opinion on any of this for your own, I’m happy to take a look.

More Articles