MyKavo - Website Change Monitoring

No. The plugin adds no scripts, styles, queries or remote requests to the pages your visitors load. The only public-side work is a text match on the User-Agent header; when the visitor is an AI crawler, one counter is updated after the page is built. Everything else runs inside wp-admin, and the scanning happens on MyKavo's servers.

AI search is a growing way people find websites. If ChatGPT, Claude or Perplexity never read your pages, they cannot cite them. The AI crawlers screen shows which ones do, which pages they read, and which pages give them errors. It records crawler names only - never IP addresses or anything about people - and you can switch it off.

Yes. The plugin shows the monitoring MyKavo does for your site. The free plan covers one website with five pages, with no card required.

Administrators (users who can manage options) can see and do everything. Give a client the "MyKavo viewer" role (or any role the mykavo_view capability) and they can see the MyKavo screen and its Dashboard widget, read-only: they cannot approve changes, run scans, roll back, connect or change settings.

Right before WordPress updates a plugin or theme, MyKavo zips its folder into wp-content/mykavo-snapshots. That folder has an index.php, an .htaccess and a web.config that close it to the web, and the file names are random. The last two snapshots per plugin or theme are kept, for seven days at most, and deleting the plugin deletes them all.

It loads the site from the site's own server, like WordPress's own Site Health loopback test. If the host blocks those requests, the check says nothing rather than raising a false alarm.

Disconnecting revokes this site's key. Deleting the plugin removes everything it stored. Monitoring in your MyKavo account is not affected, and you can connect again at any time.

When WordPress finishes updating anything, the plugin tells MyKavo what changed (for example "WooCommerce 8.1.0 → 8.2.0"). MyKavo scans your monitored pages against your approved baseline and reports back: nothing changed, or exactly what did. It works for automatic background updates too.

No. The plugin reads version numbers while WordPress is already updating, and sends one small report at the end of the request. The scan itself runs on MyKavo's servers.

Yes. With WP-CLI: wp mykavo status shows the site's status, wp mykavo changes lists changes, and wp plugin update --all && wp mykavo scan --wait updates everything and then waits for MyKavo's verdict, exiting with an error if something important changed. Run wp help mykavo for every command.

Yes. Switching a plugin on or off, or changing the theme, is checked the same way as an update, and named in the result: "Deactivated WP Rocket - 2 changes found".

Everything that runs only inside WordPress is free, on every plan: the whole MyKavo screen, the update history, snapshots and one-click rollback of any plugin or theme, the "did it crash?" check, Safe Update All (with an UpdraftPlus backup first), silent-disaster notices, the critical-change notice, the MyKavo viewer role, suggested pages, the multisite network screen, the block editor panel, AI crawler counts for the last 30 days with real-or-fake checks, per-crawler robots.txt rules, 404 redirects, llms.txt, the daily email test, the number of plugins with a known security issue, and the update-risk line on the Plugins screen. One watched element is included on the free plan. Paid plans, from Starter, add MyKavo's automatic checks after every update, instant email and Slack alerts for silent disasters, a fresh baseline before Safe Update All, plugin health and vulnerability details, 12 months of AI crawler history, llms.txt page summaries, redirect suggestions and contact form checks. Pro and Agency add automatic rollback, holding back risky automatic updates for 48 hours, automatic updates for vulnerable plugins, more watched elements, test entries through contact forms, the WooCommerce checkout guard and ChatGPT and Claude (MCP). Agency adds update windows and your branded site report. Paid features are provided by MyKavo's service: the plugin contains no locked code.

The update history offers "Roll back to" the version you had before. For a plugin from WordPress.org, WordPress downloads that exact version from WordPress.org; for any other plugin or theme (premium ones too), the snapshot taken just before the update is put back. Either way the plugin stays active if it was, MyKavo is told about it and checks your site again. Snapshots are kept for seven days, and MyKavo never rolls itself back.

Yes. Install the plugin on each site and connect each one to its own website in MyKavo.

Your server needs to be able to make outbound HTTPS requests to mykavo.app, which almost every host allows. MyKavo also needs to be able to reach your public pages to scan them.