Docs
Relvato documentation
Product how-tos and reference for using Relvato — connecting your site, configuring monitors, and reviewing results.
Get started
Prove a site is yours, connect your code and your AI builder, and get the first runs going.
Lovable monitoring: re-check speed from the Lovable chat
Connect Relvato's MCP server to Lovable, run Core Web Vitals on the published app after each change, and let Lovable fix what got slower.
Bolt.new performance: a speed budget Bolt checks itself
Add Relvato as a custom MCP connector in Bolt, measure the published site's Core Web Vitals in a real browser, and turn the diagnostics into code changes.
Verify site ownership
The ways to prove a site is yours — the WordPress plugin, a domain record, or Google Search Console / Bing — how each is re-checked, and what makes proof lapse.
Connect your site to GitHub: re-check on every deploy
Wire your repo to Relvato so every push re-runs your site’s monitors automatically — step by step.
Alerts and integrations
Send what Relvato finds to the place your team already looks.
Alert severity levels: how Relvato decides what's critical
The five levels, the rules that give every failure its level, what never counts as a failure, and how to choose which alerts reach you.
Send alerts to a webhook
Send website monitoring alerts to your own tools as signed JSON — set up the webhook, verify the signature, and route alerts anywhere.
Send alerts to Slack
Connect a Slack channel so your monitors' alerts post there — set it up, test it, and fix it if alerts stop.
WordPress updates and security
Update plugins safely, undo a bad update, harden the site and watch it after a clean-up.
WooCommerce test orders
What happens to the real order a “Full order” checkout monitor places — and how it stays out of your stock, analytics and ad platforms.
WordPress Abilities API: what Relvato adds and what it checks
The four abilities the Relvato plugin registers for AI assistants, who can use them, and how the exposure scan checks every other plugin's.
Why WordPress didn't update itself
Auto-updates on, but WordPress is still on an old version? The usual causes — a wp-config setting, WP-Cron, a plugin, the host — and how to fix each.
Quarantine mode after a clean-up
Watch a just-cleaned WordPress site for 48 hours: start quarantine, read the change log, pause auto-updates, and what each alert means.
Update a vulnerable plugin safely
Update to the fixed version in WordPress, re-run every monitor, and undo it with one click if one breaks — or deactivate and verify.
Roll back a plugin update
Reinstall the version you had before, and keep WordPress from reinstalling the one that broke your site.
Fix security findings in one click
Turn off XML-RPC, hide the user list, remove version leaks and more — one click per exposure-scan finding, with Undo.
Firewalls and access
When a firewall, a bot check or a blocked plugin stands between Relvato and your site.
“Please wait while your request is being verified”
Imunify360 and Cloudflare fighting over cookies puts visitors in an endless verification loop. Here's the fix.
Bypass the Vercel firewall
Vercel's Security Checkpoint blocking your monitors with a 403? One Firewall rule lets Relvato through.
Allowlist Relvato behind a firewall
If Cloudflare or a WAF blocks Relvato’s monitors with a 403, add one rule to let Relvato through.
Fix “Plugin not responding”
The three things that stop Relvato's plugin from answering — an inactive plugin, a security/WAF block, or edge caching — and how to fix each.
Results and data
Decide what counts as the normal look of a page, and control what Relvato collects.
Remove the real-user beacon
Turned real-user monitoring off? Take the beacon off your site too — one tick in the WordPress plugin, or delete the snippet from your code.
Managing baselines: accept, ignore, undo & reset
Review flagged changes on the visual and structure-drift monitors — and revert a decision.