Error monitoring — no PHP warnings greeting your customers.
Relvato scans your key pages the way a logged-out visitor sees them and flags PHP and WordPress errors — a notice, a warning, a ‘critical error’ screen, a database connection error — uncaught JavaScript errors, and raw, unrendered code like shortcodes and block markup. It re-checks right after a plugin, theme or core update, or a push to your GitHub repository.
- ✓No PHP notices, warnings, deprecations or fatal/parse errors in the page
- ✓No WordPress ‘There has been a critical error’ or database connection error screen
- ✓No uncaught JavaScript errors while the page loads
- ✓No raw PHP, unrendered shortcodes or leftover block markup (<!-- wp:… -->)
- ✓Home, shop, category, product, cart, checkout and account pages — plus any URLs you add
- ✓Re-checked after plugin, theme, core and WooCommerce updates, and GitHub pushes
A plugin conflict or a bad update can splash a PHP warning across the top of your shop, replace checkout with a ‘critical error’ screen, or show [contact-form-7 id="42"] where a form should be. It often only appears to logged-out visitors or on templates you rarely open, so customers see it before you do. Relvato scans the rendered page and shows you exactly what they saw.
On WordPress, if the errors started right after a plugin update, Relvato suggests rolling that plugin back to the version you had before — from wordpress.org, and only when your copy is unmodified — and you apply it with one click in WordPress → Relvato. The plugin then holds the bad version so WordPress doesn't reinstall it. A newer release still installs normally.
- Relvato opens each key page logged-out in a real browser — home, shop, category, a product, cart, checkout and account, plus any URLs you add — and waits for late content like shortcode widgets to render.
- It scans what’s on screen for error signatures (PHP notices and fatals, WordPress critical-error and database screens, stack traces), uncaught JavaScript errors, and raw code outside code blocks. Code you show on purpose in <pre> or <code> is never flagged, and you can ignore a specific phrase.
- On a hit you get the page, the exact error text and a full-page screenshot of what visitors saw. It runs minutes after a plugin, theme, core or WooCommerce update reported by the Relvato plugin, after a push to a connected GitHub repository, and on a weekly schedule.
Do I need a plugin?
No — error scanning works on any site with a verified domain. The plugin adds a re-check right after WordPress updates; the GitHub App adds one right after a code push.
Why wouldn’t I see these myself?
Errors often show only to logged-out visitors, only on templates you don’t open, or only after an update you ran late at night. Relvato scans logged-out, across your key pages, right after changes.
Will it flag code I show on purpose, like a tutorial?
No. Code inside <pre> and <code> blocks is excluded before the raw-code scan, and you can add phrases to ignore — for example a shortcode you display deliberately.
Does it catch JavaScript errors?
Yes — an uncaught JavaScript exception while the page loads is reported alongside PHP and WordPress errors, with the error message.
Put this monitor on autopilot.
Free forever on one site — 100 runs a month, started by you or weekly, no card. Pro re-runs your monitors by itself after every update.