WordPress powers most UK business websites. That is a strength — until an outdated plugin, a shared admin password, or a backup nobody has tested leaves orders, client data, or unpublished strategy on the open internet.
Security vendors often publish “publication checklists” aimed at enterprises. You do not need a compliance team to benefit from the same thinking. This post is a self-audit you can run in an afternoon: work through each section, tick what you have verified, and note what still needs fixing before your next important update goes live.
How to use this audit
- Block an hour with someone who can log into WordPress and the hosting control panel.
- Do not change everything at once. Mark gaps first, then fix the highest-risk items (access, updates, backups).
- Re-run quarterly, or before a redesign, a WooCommerce peak, or any project that touches customer data.
Everything below is written for site owners and agencies — not security researchers. Where we mention a setting, it is the kind of thing you can check without reading PHP source code.
1. Know what is “business-critical” on your site
Before you harden the perimeter, be clear what you are protecting. On a typical WordPress site that might include:
- Customer and order records (WooCommerce, forms, memberships)
- Unpublished pages, pricing drafts, and embargoed news
- Mailbox addresses harvested through contact forms
- API keys or webhook URLs stored in options tables or page builder modules
- Back-office integrations (CRM, stock, accounting)
Audit question: Could you list, in one screen, every place that data enters or leaves WordPress? If not, map it before you publish the next big change.
2. Accounts, roles, and sign-in
Most compromises still start with a password that worked. WordPress makes it easy to add editors; it is equally easy to forget they still have admin rights from a project three years ago.
Checklist
- Every user has a named work email — no shared “office@” administrator.
- Two-factor authentication is enabled for every Administrator and Shop Manager account.
- Roles follow least privilege: authors publish posts; only trusted people get Administrator.
- Remove dormant accounts (former staff, old agencies, demo users).
- The hosting control panel uses different credentials from WordPress, with 2FA where available.
- You have rotated the database and FTP/SFTP passwords after any agency handover.
3. Core, themes, and plugins
WordPress core is actively maintained. The long tail of plugins and bespoke themes is where attackers look first. An audit is not “is everything on the latest version?” — it is “is everything we rely on still maintained, and can we remove the rest?”
Checklist
- WordPress core is on a supported release and auto-updates (or a documented patch process) are enabled.
- Every active plugin has an update within the last 12 months — or a plan to replace it.
- Deactivate and delete unused plugins; they still contain code on disk.
- Premium and nulled themes are avoided; child themes are used for custom CSS where possible.
- File editing from the dashboard is disabled (
DISALLOW_FILE_EDITinwp-config.phpwhere appropriate). - You maintain a staging copy (or a trusted backup) to test plugin updates before production.
4. Publishing workflow and content leakage
“Protect business-critical information” is not only about hackers. It is also about the draft press release that went live early, or the PDF indexed by Google before launch.
Checklist
- Draft and private content is not linked from public menus or sitemaps.
- Search-engine visibility is set deliberately per post (public, noindex for staging clones).
- Only senior roles can publish; others submit for review where your workflow allows.
- Revision history is understood — old drafts may still contain superseded pricing.
- Media library uploads (PDFs, spreadsheets) are checked for sensitive metadata before upload.
- Forms that collect personal data record a privacy notice and retention approach.
5. Backups you can actually restore
A backup that has never been restored is a hope, not a plan. Business-critical sites need backups that are off-server, encrypted in transit, and tested at least once a year.
Checklist
- Daily automated backups include files and the database (not just “home directory”).
- Backups are stored off the live server (object storage, remote vault, or host-provided off-site).
- You know how to restore without opening a support ticket at 2 a.m.
- Backups run before major plugin updates and theme changes.
- For shops, you can recover orders and customer data to a point in time that satisfies your policy.
6. Transport, hosting, and the edge
WordPress security does not stop at the login screen. TLS, PHP version, and server-level hardening matter — especially when you handle payments or personal data.
Checklist
- HTTPS is enforced site-wide; mixed-content warnings are resolved.
- PHP is on a supported, patched version (your host should have applied recent security releases).
wp-config.phpand uploads are not world-writable; directory listing is off.- A Web Application Firewall or host-level rules block obvious exploit paths.
- XML-RPC is disabled if you do not need it (reduces brute-force noise).
- Email sending uses SMTP or a reputable relay — not bare
mail()on a shared IP that burns reputation.
Our WordPress hosting UK stacks include LiteSpeed, NVMe storage, free SSL, daily backups, and UK-based support — the same platform described in WordPress hosting UK: what you actually need.
7. Monitoring and when things go wrong
No checklist prevents every incident. What separates a bad afternoon from a business-ending week is noticing early and knowing the playbook.
Checklist
- Uptime and SSL expiry monitoring alerts a human — not only an inbox nobody reads.
- File-change or malware scanning runs on a schedule (plugin or host-provided).
- You have a single incident contact and a rough order of operations: contain, restore from clean backup, rotate secrets, notify if required.
- Google Search Console is verified so you see indexing anomalies.
- You know where DNS is managed and can roll back a hijack.
If you are cleaning up after an infection, pair this audit with our guides on defending against backdoors and malware and how attackers reach WordPress sites.
Score your site
Count how many checklist items you could honestly tick today (34 in total across sections 2–7):
- 30–34: Strong baseline — schedule the next audit and keep staging discipline.
- 20–29: Usable but exposed — prioritise access control, updates, and backup testing this month.
- Below 20: Treat security as a project, not a setting — consider professional help before the next major publish.
Print the list or copy it into your project tracker; the goal is evidence, not a perfect score on day one.
When you want a second pair of eyes
Self-audits catch most preventable issues. When you are migrating, launching a shop, or recovering from a compromise, talk to us — we help UK businesses with hosting hardening, malware clean-up, and migrations that do not leave DNS in limbo.
Agencies managing many installs can pair this checklist with a Care Plan so updates and backups are not left to whoever is least busy.
Next step: block time this week, run the checklist, and fix the three red items that would hurt most if tomorrow morning’s traffic met last year’s plugin.