WPShift — monitoring
WordPress uptime monitoring and health checks, in one dashboard.
WordPress uptime monitoring on WPShift watches three things most tools treat separately: whether the site is up, how fast it is, and whether WordPress itself is healthy. Per-site uptime checks run with a configurable interval, expected status code, string match, timeout and failure thresholds. Google PageSpeed Insights runs on a schedule with thresholds you set, and the native WordPress Site Health checks are surfaced for every install you operate, without opening wp-admin. It is built for agencies and operators who are on the hook when a client site goes down, and for teams where the person on call is not always a sysadmin. Monitoring is included on every plan, from Personal at €5.99/mo to Agency at €29.99/mo; the only limits are the plan’s server and site counts.
Checks that match how WordPress actually fails.
The difference is in the alerts: each one arrives with a plain-English explanation of the likely cause, generated by AI from the actual signals, and paired alerts auto-resolve when the underlying issue clears.
A 200 status is not the same as a working site. The string match option answers the real question, is the homepage actually serving the right content, and the consecutive-failure threshold stops one flaky network hop from waking anyone up. Incidents are kept per site with timestamps, so the was-it-down-at-03:14 question gets answered without digging through logs.
PageSpeed runs on a schedule, which turns performance from an occasional audit into a trend line. A regression in LCP or CLS shows up in the dashboard before it shows up in Search Console, and the history lets you correlate a slow-down with a specific plugin or theme update.
Site Health closes the loop on the WordPress layer: outdated PHP, missing recommended modules, REST API access and loopback requests are surfaced at workspace level for every install, so the warnings do not hide inside each site’s wp-admin.
What you get.
Uptime monitoring
Per-site checks with configurable interval, expected status, string match, timeout and failure thresholds. Incident history kept for every site.
PageSpeed monitoring
Google PageSpeed Insights run on a schedule with thresholds you set per metric. Track regressions before they hit Core Web Vitals.
WordPress Site Health
The native Site Health checks surfaced at workspace level for every install you operate, no wp-admin round trips.
Disk and bandwidth tracking
Disk usage and monthly bandwidth tracked per server and per site, so you plan capacity before it runs out.
AI-explained alerts
Every alert ships with a plain-English paragraph naming the likely cause, generated from the actual signals. No cryptic warnings to decode.
Smart deduplication
Paired alerts auto-resolve when the underlying issue clears. Less noise in the inbox, more signal in the dashboard.
Alerts that do the triage for you.
Each alert ships with a paragraph that names the likely cause based on the actual signals: load average paired with PHP-FPM saturation, disk pressure correlated with a cron-job spike, that sort of thing. You still get the raw data, but the triage step is already done, so the on-call person can jump to the fix.
Deduplication keeps the channel worth reading. Paired alerts auto-resolve when the underlying issue clears, so you do not get a follow-up telling you something already came back. Fewer is-this-still-happening pings at 02:00, and a cleaner incident history.
Disk and bandwidth tracking round it out: you can see which install is eating storage, whether it is uploads, logs or a runaway backup retention policy, and spot a runaway crawler or a hotlinked image going viral from the bandwidth roll-up.
Who it’s for.
Everyone who would rather hear it from the dashboard than from the client.
- 01
Agencies
Uptime, performance and health for the whole client portfolio in one place, with incident history to show for it when the SLA question comes up.
- 02
Freelancers
Be the one who reports the outage, not the one who hears about it. The AI explanation means less time decoding and more time fixing.
- 03
Teams with non-developers
A plain-English cause in every alert means whoever sees it first can act on it, or route it to the right person, without a sysadmin translating.
How it works.
- 01
Set the checks
Per site, choose the interval, the expected status code, an optional string match, a timeout, and how many consecutive failures fire an alert.
- 02
Schedule the performance runs
PageSpeed Insights runs against the URLs you care about, with per-metric thresholds, while Site Health results roll up across every install.
- 03
Alerts arrive triaged
When something fires, it comes with an AI-written explanation of the likely cause based on the actual signals, plus the raw data.
- 04
Noise resolves itself
Paired alerts auto-resolve when the issue clears, and incidents are kept per site with timestamps for a clean history.
How it’s priced.
Monitoring is included on every plan. There is no separate monitoring tier or per-check fee.
See all plans and pricing- Uptime checks, PageSpeed runs, Site Health, disk and bandwidth tracking, AI-explained alerts and deduplication ship on Personal (€5.99/mo), Professional (€14.99/mo) and Agency (€29.99/mo) alike.
- The only limits that apply are the plan’s server and site counts: 1 server and 3 sites on Personal, 5 and 15 on Professional, unlimited on Agency.
- The 7-day free trial runs full Professional features, no credit card required.
Questions, answered.
What does WPShift monitor?
Uptime per site, Google PageSpeed scores on a schedule, the native WordPress Site Health checks, and disk and bandwidth per server and per site.
What are AI-explained alerts?
Every alert ships with a plain-English paragraph naming the likely cause, generated by AI from the actual signals, for example load average paired with PHP-FPM saturation. The raw data is still attached.
Can I tune when an alert fires?
Yes. Per site you set the check interval, expected status code, an optional string match, a timeout, and the number of consecutive failures before an alert fires.
Will I get flooded with duplicate alerts?
No. Paired alerts auto-resolve when the underlying issue clears, so you are not notified that something already recovered.
Do I need to log into each site to see Site Health?
No. The same checks WordPress runs internally are surfaced at workspace level for every install you operate.
Spot trouble before customers do.
Start your 7-day free trial with full Professional features. No credit card required, cancel anytime.