Every client site. One console. Plain language.
Choose your fleet size
Pick the plan that matches your client list.
Every plan includes the multi-site console, uptime monitoring and backups. AI messages are the plain-language commands you issue per month.
All plans start with a 14-day free trial. No card required to connect your first site.
How it connects
A small connector on each site. Everything else happens here.
WPControl doesn't replace wp-admin — it sits above all of them. Install the connector plugin on a client site, paste the pairing key, and the site joins your fleet within one heartbeat.
Install the connector
A 40 KB plugin from the WordPress directory. It adds one settings screen and nothing else — no dashboard widgets, no admin notices, no front-end footprint.
Pair it with your workspace
Copy the pairing key from /settings/connector, paste it into the plugin, done. The connector self-updates, so clients never see a maintenance chore.
The site joins the fleet
Within one heartbeat you see health, WP and PHP versions, pending plugin/theme/core updates, uptime and backup state — next to every other site you maintain.
Command it in plain language
“Update Yoast SEO everywhere except the stores” — the agent resolves which sites match, shows you the list, asks before anything destructive, and reports back per site.
What the console does
Built for the maintenance hour you repeat every week.
Every site, one row of evidence each.
Health verdict, WP/PHP version, pending updates, last heartbeat and uptime — per site, sortable, filterable. Select any set of rows and act on all of them at once: update, back up, flush cache, toggle maintenance mode.
Explore the consoleBack up every site before Friday's WooCommerce update
2 stores match. Backup window: tonight 02:00–04:00.
State the intent. The agent does the clicking.
Type what you want in plain language. The agent resolves which sites match, shows you exactly what will change per site, and asks for explicit confirmation before anything destructive. Results come back per site — success and failure clearly separated.
See the command surfaceThe routine you'd write a script for, without the script.
WordPress triggers and actions across many sites, from seeded templates: auto-update minor core releases, snapshot before plugin updates, alert when uptime dips, compile the Monday client report. Runs while you sleep; reports when you wake.
Browse automation templatesMinor core auto-update · 18 sites · nightly
ActiveSnapshot before plugin update · all sites · on trigger
ActiveMonday client report · 12 clients · weekly
PausedWhy it pays for itself
Maintenance stops being the invisible line item.
Twenty sites at fifteen minutes each is five hours a week of wp-admin tab-hopping. The same round as one fleet command is one message and a confirmation.
Fleet uptime · trailing 30 days
200
sites on the largest plan
340ms
median heartbeat round-trip
5,000
AI messages on Scale, monthly
Illustrative figures from a representative agency fleet — not a live reading of your account.
Questions agencies ask
Straight answers.
No. The connector is a 40 KB plugin with no front-end footprint — it enqueues nothing on public pages. It answers signed requests from your workspace and sends one heartbeat; on a typical shared host its overhead is below what a single admin-ajax call costs.
One command you send to the agent — regardless of how many sites it touches. “Update all plugins on the sites that are behind” against 60 sites is one message. Manual console actions (bulk select, single-site clicks) never consume messages.
Destructive or costly operations never run on the first message. The agent resolves the affected sites, shows you the exact list with what will change per site, and waits for an explicit scope confirmation — selected rows, first N, or save without running. Restore points are created before update runs.
Nothing gets disconnected. At the message cap the agent pauses and tells you — the console, bulk actions, automations and monitoring keep working. At the site cap you can't pair new sites until you upgrade or remove one. Current usage is always visible under /usage.
Yes. Stores are flagged automatically, so commands can exclude or target them (“…except the ecommerce ones”). On Pro and above, a read-only WooCommerce view aggregates revenue, orders and products across your stores — it never writes to a store.
That's what scheduled reports are for: per-client email or PDF summaries of updates applied, uptime and backup state, on a weekly or monthly cadence. On Agency and Scale they're white-labeled with your studio's name, not ours.
Connect your first site before lunch.
Install the connector, pair the key, watch the fleet assemble. 14 days free on every plan.
By starting a trial you agree to the terms of service. No card required.