Open on what needs attention, not on an alphabetical list
A grid of every site leaves the prioritizing to you. At forty sites that is a scanning exercise every morning. The portfolio view should already know what matters today.
Free during early access. No credit card required.
Updated
What is a WordPress maintenance dashboard?
A WordPress maintenance dashboard shows the state of many WordPress sites on one screen: which are online, which have updates waiting, which have a security or backup problem and how each one performs, so you see what needs attention without logging into each site.
WPCentrify's Websites list is that screen for every site you connect, whatever host it runs on. Each row shows the site's status and recent uptime, updates waiting, its security verdict, speed, traffic and new enquiries, and the list updates in place without reordering under your mouse. Sort it, pin the sites you watch most and choose the columns you want, and any site's detail or wp-admin is one click away.
WPCentrify Websites list at a glance
- Every connected site on one screen, on any host.
- Status, uptime, updates waiting, security, Core Web Vitals, visitors and enquiries per site.
- Updates in place with changed figures highlighted, and never reorders while you are reading it.
- Pinned sites stay at the top, and your sort and columns are remembered on your account.
- Each colleague sees only the sites and figures their permissions allow.
WordPress fleet management: a grid of sites is not risk
Every WordPress management tool shows you a list of connected sites with status indicators. At five sites this works perfectly. At forty it becomes a scanning problem, and at a hundred and forty it becomes unusable, because the information you need is distributed across a hundred and forty rows and organized alphabetically rather than by importance. What each row should be watching in the first place is set out in our guide to WordPress site monitoring.
The specific failure is that severity within a site is not the same as severity across a portfolio. A critical vulnerability on a decommissioned staging copy shows the same red indicator as a critical vulnerability on a store taking a thousand orders a week. The dashboard cannot tell the difference, so a human has to, every morning.
The second failure is that portfolio patterns are invisible entirely. When the same plugin is vulnerable on eleven client sites, a per-site view shows eleven separate problems rather than one problem with eleven instances, which is a completely different piece of work.
What the portfolio view leads with
- Vulnerabilities ranked by how many sites and which sites
- Updates that failed verification and were rolled back
- Backups that have never been restore-tested
- Clients approaching or breaching an SLA target
- Sites with certificates expiring inside thirty days
- Sites running end-of-life PHP or WordPress core
- Work assigned to the team and what is unassigned
Ranking by consequence, not by severity alone
The same technical finding gets a different priority depending on where it lands, which is the judgment the dashboard should be making for you.
Continuous state collection
Every connected site reports versions, plugins, certificates, backup status, job outcomes and uptime, continuously rather than on a scan schedule.
Consequence weighting
Findings are weighted by what the affected site actually is. A store, a site holding personal data, or a site under a strict SLA raises the priority of the same technical issue. For the sites holding personal data, consent status for every site sits in the same view.
Patterns grouped
One vulnerable plugin across eleven sites is presented as one item affecting eleven sites, with a single action, rather than as eleven separate rows.
Turned into work
Priorities become assignable work items with owners, so the morning question is what to pick up rather than what to look at. The same view carries traffic for every site you manage, next to the work each one needs.
What a WordPress maintenance dashboard should surface
Next best action
A ranked list of what the team should do first today, weighted by consequence rather than by alphabetical order.
Cross-portfolio exposure
One vulnerability affecting many sites presented as one problem, with the affected sites and their risk profile.
Backup confidence
Which sites have verified restore-tested backups and, more importantly, which do not.
SLA status
Clients approaching a response or resolution target, before the breach rather than in the post-mortem.
Trend view
Whether the portfolio is getting healthier or drifting, which is the number that tells you if your process works. Core Web Vitals across the portfolio trend in the same place.
Team workload
Who is working on what and where capacity is short this week.
The number that tells you whether your process works
Most agencies measure activity: updates applied, backups taken, tickets closed. These are easy to count and they tell you almost nothing about whether the portfolio is actually getting safer.
The more useful measures are lagging risk indicators. How long does a published security patch take to reach every affected site. What proportion of backups have been restore-tested in the last quarter. How many sites are running software past end of life. How many updates required rollback, and is that number falling.
Those figures move slowly and they are uncomfortable to look at initially, because the first honest measurement is usually worse than expected. They are also the only measures that distinguish an agency that is genuinely managing risk from one that is busy.
Activity metrics that mislead
- Number of updates applied, with no verification outcome
- Backups taken, with none ever restore-tested
- Uptime averaged across a portfolio rather than per client
- Tickets closed, without time or root cause recorded
- Sites connected, without knowing which are at risk
Questions about the fleet dashboard
Yes. Weighting is configurable, so if certificate expiry matters more to your operation than plugin vulnerabilities, you can rank it accordingly. The defaults reflect what causes the most incidents across agencies generally, not what necessarily matters most to you.
The view is designed for portfolios in the hundreds. It becomes more useful as site count rises, because the prioritization problem it solves barely exists at ten sites and dominates at two hundred.
Yes. WPCentrify is hosting-neutral and the connector works identically regardless of provider, so a portfolio spread across eight hosts appears as one estate.
Yes. Access is scoped by site and by action, so a technician assigned to certain clients sees the priorities for those clients, while managers see the whole portfolio including commercial data.
Yes, in machine-readable format, which agencies commonly pull into their own reporting or a client-facing dashboard. Pulling the same data through a public API is planned.
Yes. A WordPress management platform shows every site you look after on one screen. WPCentrify's Websites list shows each site's status, uptime, updates waiting, security, speed, traffic and enquiries, and opens any site's detail or wp-admin in one click.
Yes. You choose the columns, the sort order and the sites pinned to the top, and WPCentrify remembers them on your account so the list opens the way you left it.
Start the morning knowing what matters
A portfolio view that ranks by consequence, groups patterns across clients, and turns priorities into assigned work.
Free during early access. No credit card required.