WordPress monitoring
WPFixAgent watches your WordPress sites from two directions at once: independent external HTTP checks that don't care whether the site itself is responding, and a connector that reports what's actually happening inside WordPress -- version drift, cron health, disk space, database errors. When something's wrong, that context feeds straight into the Issue Center instead of just paging you.
Every minute
External checks
Outbound-only
Connector
Live
Progress panel
Connected
To repair
From signal to resolved issue
External checks and connector heartbeats run continuously and independently of each other.
Health rules convert raw signals into severity-ranked issues on the affected website's Issue Center.
Each issue carries the evidence that triggered it, plus an optional AI-assisted explanation.
A supported issue queues a real repair; anything else stays visible for manual review.
A fresh check confirms whether the underlying problem is actually gone.
An external HTTP check runs every minute, completely independent of whether the WordPress connector itself can respond -- so a fully down site still gets detected and produces a real downtime window, not silence.
Heartbeat status, WordPress and PHP version, active theme, full plugin inventory, available updates, WP-Cron health, REST API health, disk capacity, database connectivity, and filesystem writability -- all reported on every sync.
Run a Google PageSpeed Insights test or an automated browser smoke test whenever you need one -- especially useful right after a repair, to confirm a real visitor's experience rather than just a connector status flag.
A scan of your own published posts and pages surfaces dead internal and external links, with one-click redirects for anything you control -- see the dedicated Broken Link Checker page.
Uptime checks, incidents, and repair runs stay attached to the website they happened on, so a recurring problem is visible as a pattern instead of a series of disconnected alerts.
External checks work even when the connector can't respond
Health signals are read, not just pinged
Every finding links to a specific website and moment
Monitoring feeds the same Issue Center as everything else
Practical guidance
Critical errors
Recover from the WordPress critical error screen with a controlled process that protects evidence, creates a restore point, isolates the cause, and verifies the result.
Read guideAuto repair
Automation should resolve known, reversible WordPress conditions while risky database, malware, and hosting failures remain review-driven.
Read guideBackups
Local restore points make repairs fast, while off-site copies protect against hosting and disk failure. A serious recovery plan needs clear roles for both.
Read guideFAQ
No -- external HTTP checks run independently once a website is added. The connector adds the deeper WordPress-internal signals (versions, cron, disk, database) on top of that.
Every minute, independent of connector heartbeat timing.
Yes, from a website's Monitoring tab, on demand -- useful for confirming a repair actually fixed the visible problem.
No. Monitoring detects and surfaces issues; repairs are queued separately (manually or via Safe Auto Fix) and always go through the same protect-then-verify workflow.
Free 14-day trial · no card required
Install the connector, pair with a one-time token, and start monitoring in minutes -- upgrade whenever you're ready.