Observability is the ability to understand the internal state of your WordPress site from the signals it emits — not just whether it is up. Automation is acting on that understanding without introducing new risk. WP SelfOps treats both as one loop: observe, explain, act, verify.
Signals WP SelfOps observes
- Site health and performance indicators, WordPress and PHP versions.
- Plugin and theme inventory, available updates, known conflicts.
- Cache layers and conflicts between caching plugins and hosting caches.
- Database storage: table sizes, post meta, expired transients, reclaimable space.
- Background jobs (Action Scheduler): pending, failed and past-due actions and their storage footprint.
- Selected configuration files, on request, for diagnosis.
- Business signals from WooCommerce, GA4 and Search Console when connected.
Evidence you can check
Every answer states whether it came from a live query, a verified snapshot (with its age) or could not be produced. Recommendations reference the signals that triggered them. Nothing is inferred silently.
Safe automation
WRITE operations are allow-listed and classified by risk and reversibility. The flow is always preview → your confirmation → backup or restore point where the environment allows → execution → verification → undo when reversible. Autopilot can run predefined low-risk categories within the scope you enable, and can be switched off at any time. WP SelfOps never claims a rollback it cannot perform.
Where the WordPress plugin fits
The plugin is the on-site connector that collects signals and executes confirmed operations. WP SelfOps — the SaaS platform — is where correlation, reasoning, safety gates and your conversation live. Updates to the plugin are delivered through the normal WordPress update flow.