At a distributor, a trade association, or a manufacturer with thirty people, the website usually belongs to whoever ended up with it: the marketing director because it's marketing, the operations lead or COO because the rest of the business runs through them, or the office manager because they hold the passwords. It runs on WordPress or a similar system, and each plugin, the theme, and the PHP version underneath them need updating on their own schedule. A security announcement doesn't wait for a quiet week, so the check gets the site current while there is time to test. I do the work myself, from the first backup to the written record.
In October 2026, a critical PHP security announcement went out in the middle of a workday. A member of a local nonprofit had flagged the old PHP version a while before, and another had already staged a server on the newer one, so that evening the nonprofit's WordPress site moved from PHP 5 to 8.4.27 in about an hour, with no disruption. The upgrade had been on the list for years, and it wasn't urgent until it was.
A safe copy, the logins, then the live site
- 01
Update a copy first
The site and its database are backed up off the host, then a staging copy gets the new WordPress core, plugins, theme, and PHP version. The pages that make you money get tested on the copy: the contact form, the quote request, the store checkout, and the booking page. A plugin that breaks there gets replaced or dropped before the live site changes.
- 02
Every login, checked against who should have it
The admin accounts in WordPress, the host, the domain registrar, the CRM connection, and the Google Workspace or Microsoft 365 admin are listed, with who holds each one. Former staff and finished contractors come off, unused application passwords are revoked, and two-factor sign-in goes on every admin login that remains.
- 03
Backups you've restored once, then the live update
Backups run on a schedule and are kept somewhere other than the host, and one of them is restored to prove it works. Then the update goes live in a window you choose, with the backup from that morning ready if anything needs to roll back.
What the check looks at
When a small site is broken into, the way in is often a known issue with a published fix: an old plugin, an old PHP version, or a login that should have been removed. The check covers each place those sit.
The website
WordPress core, every plugin and theme with its version and whether it's still maintained, the PHP version, unused plugins still on the server, the public login page, and what the site publishes about its own users and versions.
The host
Who is on the host's team list, the SSH keys and access tokens, how backups run, which PHP version each environment uses, and whether updates can run automatically.
Email and the domain
The registrar login and the email that receives renewal notices, the DNS records, and the SPF, DKIM, and DMARC records that stop someone sending mail as your domain. Whether the site itself can send mail, so a password reset arrives.
Forms and connections
Where the contact and quote forms send what visitors type, and the keys the HubSpot, payment, or shipping plugins hold, with the date each was last changed.
What you get
The site, up to date
Core, plugins, theme, and PHP updated and tested, or the exact change list if your own contractor will make the changes. Either way you get the list of what changed and why.
The access register
Every system, who has an admin login to it, and who should, so the next hire or contractor is added and removed from one list.
The setup record
Where the site is hosted, what each plugin is for, how backups run and how to restore one, and who to call for each piece, written so the next person can pick it up.
What should change
Which plugins and logins to retire, which updates can run on their own, and whether the site should stay on WordPress. A move to a smaller stack is a recommendation in writing, and a separate decision.
Proof
The check draws on account-takeover response at Uber, designed, built, and owned for North America, and on a 2026 security and systems audit for an international food ingredients importer.
Common questions
Will the updates break the site?
They can, which is why they go on a copy first. A plugin that doesn't support the new PHP version, or a theme that needs its license renewed before it will update, shows up on the copy, and the change list says what was replaced and why before the live site changes.
Our site isn't on WordPress. Does this apply?
The same check covers Joomla, Drupal, a WooCommerce or Magento store, and an older custom PHP site. On Squarespace, Wix, or Shopify the platform patches the software for you, so the check is shorter and spends its time on the logins, the domain, and email.
How is this different from the Ops Audit?
The Ops Audit follows how work moves through the business, from the first enquiry to the invoice. The security check stays on the website and the accounts around it, and it ends with the updates made, whereas the Ops Audit ends with a plan.
What if we think someone is already in?
Then start with the account security cleanup instead. An update can delete the evidence of how someone got in, so the cleanup keeps that evidence first and then closes every way in.
Do we need a monthly plan after this?
Often you don't. With automatic updates on, unused plugins gone, and two-factor sign-in on every admin login, a small site needs a person to look at it a few times a year. If yours needs more than that, the written record says so.