WordPress security for agencies

WordPress security for agencies and fleets of client sites

An agency is responsible for sites it did not always build, on hosting it does not always control, for clients who ask “are we secure?” and expect an answer. This is specialist security work delivered to the agency or alongside it: an audit across the fleet, a response when one client site is hacked and the others share the server, and monthly care with one report. Who speaks to the client, and who holds the access, is agreed in writing before anything starts.

Never send credentials, private keys, backup archives, or confidential source code through this website.

Best for
Agencies, resellers and freelancers responsible for ten or more client sites
Fleet record
130+ sites under Cloudflare management, a 30+ site malware incident, a 261-account WHM server
Reply
Same business day for an active incident; otherwise within 24 hours
Pricing
Fleet audits from $120 per site for ten or more sites, from $100 for 25 or more on shared hosting
Reports
Under the agency’s name for fleets of five or more sites, or under ours
Client contact
Agreed in the proposal: through the agency, or directly with a named contact

Why agencies bring in a specialist

Three moments an agency needs a WordPress security partner

A client asks “are we secure?”

A maintenance plan keeps plugins updated. It does not answer the question. An audit does: what was checked, what was found, what was fixed, and what remains, in a report the client can read.

One client site is hacked, and the others share the server

Cleaning the visible site is the smaller half. On shared hosting the first questions are which other accounts the web user could reach and what was left above the web root, and they have to be answered before any site is declared clean.

An insurer or enterprise client sends a questionnaire

Each answer has to be one the agency could evidence. A review maps every question to a control that was observed on the site and its server, and says which ones belong to the host.

Fleet engagements

WordPress security for a fleet of client sites: what each engagement delivers

The eight services are the same ones a single site owner buys. Across a fleet they are scoped together, so shared hosting, shared components and shared access are examined once rather than site by site.

SituationEngagementWhat the agency receives
Taking on a new client, or a fleet nobody has reviewedOne report: findings per site, findings common to the fleet, and who owns each fix
A client store takes paymentsCheckout, payment flow and customer-data findings for that store
A client site is hackedA cleaned and verified site, the likely entry point, and a statement of what was and was not established
Several sites on one server are flaggedA server-level sweep of every account, with per-account actions listed separately
The agency runs its own VPS or WHM serverHost findings mapped to who fixes them: the agency, the host, or the client
A flagship client has custom plugins or a membership platformReproducible findings with CVSS scores, and a retest after the fixes
Every client zone is configured differentlyOne documented baseline applied across the zones, with the exceptions written down
The fleet needs watching between projectsA monthly report covering exposure, updates, drift, access and backups

Client communication

Who talks to the client, who holds the access, and what carries whose name

These are settled in the written proposal, because they are where agency engagements go wrong.

  • Client communication runs through the agency by default. Direct contact with a client happens only where the proposal names the person and the reason, such as an incident that needs the site owner’s decision.
  • Written authorization comes from the party that owns the system. For a client’s site that is the client or a representative the client has authorized; an agency’s instruction alone is not authorization to test a site it does not own.
  • Access is named, temporary and least-privilege, created by whoever controls the hosting. Shared agency administrator accounts are not used for the work.
  • Reports are written for the agency. For a fleet of five or more sites they can be delivered white-label: the agency’s name and logo on the cover, and no mention of WP Server Guard in the document the client reads. Two things stay as they are. The written authorization to test names who does the testing, and the work may be cited in anonymized form, as in the published case studies, with nothing that identifies the agency or its client.
  • An NDA can be completed before detailed scoping. If the agency works under its own master services agreement or vendor terms, raise that at the proposal stage so the terms are settled before any access is exchanged.
  • When several clients share a server, each client’s findings are reported separately, and nothing from one client’s account is disclosed to another.

Fleet record

Fleet security work you can read before the first call

130+ websites behind Cloudflare

One security baseline kept consistent across a fleet: DNS and TLS posture, WAF rules, origin protection, member access and change discipline.

30+ WordPress sites, one ClickFix infection

A coordinated infection found in four persistence layers on every site, with a per-site checklist and a fleet retest protocol.

261 accounts on one WHM server

A backdoor above the web root that Wordfence, ImunifyAV and a clean database export all missed, and the sweep that followed.

A plugin built for multi-site triage

WPSecureOps Connector forwards completed Wordfence scan findings from every site to one dashboard, so alerts across a fleet are triaged in one place.

Fleet pricing

How WordPress security is priced across many client sites

A security audit across a fleet starts from $120 per site for ten or more sites, and from $100 per site for 25 or more sites on shared hosting, against $150–$500 for a single site. The lower figure applies where the fleet is large and uniform enough that most of the work is done once. The other published ranges are per site or server: $120–$500 for malware removal, $300–$750 for a server audit, $450–$1,500 for a penetration test, and from $75 a month per site for managed security. A fleet is scoped as one engagement: shared hosting, common themes and plugins, and one access model mean much of the work is done once.

The figure is a starting point, not a tier table, because two fleets of thirty sites can differ by a factor of five in work: thirty brochure sites on one managed host are not thirty stores on three servers. The proposal states the fixed fee for the fleet, what is included per site, and what would change it.

Tooling you keep

Free plugins for the agency’s own checks between engagements

Lockora Security Audit

A security-posture score with hardening and core-integrity checks, scan history and WP-CLI reporting, so the same check can be run across client sites and compared over time.

Who Changed It? – Activity Log & Audit Trail

A self-hosted activity log with field-level diffs and a tamper-evident hash chain: the record that settles “who changed this?” between an agency, a client and a contractor.

WPSecureOps Connector

Forwards completed Wordfence scan findings to a WPSecureOps dashboard for triage across every site the agency manages.

Getting started

How an agency engagement starts

  1. 01

    Describe the fleet

    How many sites, on which hosts, which are stores or membership sites, and what prompted the enquiry. No credentials and no client names are needed at this stage.

  2. 02

    Agree the ownership rules

    Who authorizes work on each client’s site, who speaks to the client, who creates access, and who approves fixes. These go into the proposal.

  3. 03

    Receive a grouped proposal

    One fixed fee for the defined scope, the deliverables per site and for the fleet, and the retest that is included.

  4. 04

    Work, report, retest

    Findings are validated by hand, reported per site and across the fleet, and retested after the agreed fixes.

Common questions

Questions about this engagement

Do you offer white-label WordPress security for agencies?

Yes, for fleets of five or more sites. Reports are delivered with the agency’s name and logo and without ours, and client communication runs through the agency unless the proposal says otherwise. The written authorization to test still names who performs the testing, and the work may be cited in anonymized form with nothing that identifies the agency or its client.

How much does a WordPress security audit cost for an agency?

From $120 per site for ten or more sites, and from $100 per site for 25 or more sites on shared hosting, against $150–$500 for a single site. The proposal states one fixed fee for the fleet; stores, membership sites, several servers and reporting requirements move it up.

Who has to authorize a security test on a client’s site?

The owner of the system, or a representative the owner has authorized in writing. An agency can arrange the engagement and hold the contract, but active testing of a client’s site starts only once that client’s authorization is on record.

One of our client sites was hacked. What do we tell the client?

What is known, what is being done, and what is not yet known, in that order, and nothing that has not been established. The incident response records which statements are confirmed, likely or undetermined, so the agency’s message to the client can use the same words.

Can you audit sites we did not build?

Yes. An inherited site is the usual case, and the audit records what was found without assigning blame to whoever built it.

Our client sites share one server. Does that change the work?

It changes the first question. If one site is compromised, the server’s account isolation decides whether the others are exposed, so the server is examined before any single site is declared clean.

Do you sign our MSA or NDA?

An NDA can be completed before detailed scoping. If your agency works under its own master services agreement or vendor terms, raise it at the proposal stage so the terms are settled before any access is exchanged.