Your WordPress site broke.
See what changed.
WPTrace is being built for WordPress developers, agencies, and technical teams who are tired of debugging blind. It connects failures to recent WordPress, environment, and runtime changes so teams can understand what likely caused a site to break.
Coming soon for WordPress developers, agencies, freelancers, and technical site owners.
- [13:42:08]OKsite.healthcheckhomepage reachable · 200 OK · 384ms
- [13:42:12]Unauthorized Changeplugin_updatedwoo-checkout v4.2.1 → v4.3.0
- [13:42:14]Trackedconfig.diff3 options changed
- [13:42:19]Runtime Failuresite.healthcheckhomepage failed · 500 · timeout 7.4s
- [13:42:19]Degradedrest.api.failure/wp-json/wc/v3/*
- [13:42:20]Attribution Engineculprit_detectedconfidence 0.94
- [13:42:21]Recovery Availablerecovery.suggestedrollback woo-checkout → v4.2.1
Most WordPress debugging starts blind.
A client says “it was working yesterday.” The site is down. Logs are scattered. Someone updated something, but nobody knows what changed, when it changed, or whether it caused the issue.
Something broke.
No one knows what changed. Logs are scattered. The team starts guessing.
Hours lost to manual debugging.
Developers waste time checking plugins, themes, updates, users, logs, and hosting issues by hand.
Monitoring says it is down, not why.
Traditional monitoring tells you a site failed. WPTrace is being built to help explain what likely caused it.
WPTrace is being built to reconstruct incidents automatically.
WPTrace watches key WordPress changes and runtime signals, then builds a structured incident timeline so developers can see the sequence of events around a failure.
Change Intelligence
Tracks meaningful WordPress changes including plugin updates, theme switches, plugin activations, plugin deactivations, PHP version changes, memory limit changes, upload limit changes, and other operational events.
Incident Timeline
Shows what happened before, during, and after a break so teams can investigate from evidence instead of guessing.
Attribution Engine
Designed to connect failures to recent changes and highlight likely causes with confidence scoring.
Runtime Visibility
Designed to detect frontend failures, fatal errors, degraded pages, REST API issues, and other symptoms that indicate something is broken.
Recovery Layer
Planned to support practical recovery actions such as deactivating a problematic plugin, switching theme, or rolling back changes where possible.
Built for real WordPress operational chaos.
Managing client sites.
Quickly understand what changed before a client reports a broken website.
Debugging production issues.
Replace guesswork with a timeline of events, symptoms, and likely causes.
Catch risky changes early.
Build better evidence around incidents and reduce repeat failures across client sites.
Spot environment changes.
See when PHP versions, memory limits, upload limits, or runtime settings change before a failure.
Not another WordPress monitor.
Monitoring tells you a site is down. WPTrace is being built to help answer the harder question: what changed before it broke?
What WPTrace is being built to do.
These features are being developed and prioritised based on real WordPress agency and developer feedback. Not all of them are live yet.
Reconstruct the sequence of events around a WordPress failure.
Track plugin updates, activations, deactivations, theme switches, and related changes.
Detect PHP version changes, memory limit changes, upload limit changes, and key runtime configuration changes.
Detect when the public-facing site changes from healthy to broken.
Capture fatal errors that appear around the time of an incident.
Connect failures to recent WordPress or environment changes.
Show how strongly WPTrace believes a change caused the issue.
Give agencies one place to monitor incident signals across client sites.
Organise incidents by client, website, and operational priority.
Planned integration for agencies already managing sites through MainWP.
Help support teams understand what changed before a ticket was opened.
Summarise important changes, failures, and risks across managed sites.
Allow different access levels for developers, support teams, and clients.
Suggest practical next steps based on the detected incident pattern.
Planned workflows for plugin/theme rollback and recovery verification.
Compare site state before and after key changes.
Future SaaS-side checks to detect when a site is unreachable from outside WordPress.
Notify teams when important incidents or risky changes are detected.
Future assistance for summarising incidents and suggesting next steps.
Future workflows for hosting providers and technical support teams.
Want to test WPTrace when it is ready?
WPTrace is still in development. We are collecting interest from WordPress developers, agencies, freelancers, and technical teams who want to be notified when testing opens.
Coming soon · No spam · Testing opens when the product is ready
Stop debugging blind.
Join the testing waitlist and get notified when WPTrace is ready for real WordPress testing.