Updates are the number one way WordPress sites break. A plugin, theme or WordPress update – often an automatic one, overnight – quietly changes a layout, removes a checkout button or sets a page to “noindex”. Usually a customer notices before you do, and nobody knows which update did it.

MyKavo fixes that. It watches the pages that matter on your site and tells you when something important changes or breaks. This plugin brings that monitoring into WordPress, and adds Safe Updates: every time WordPress updates anything, MyKavo checks your pages straight away and tells you whether the update broke something – and exactly which update it was.

Safe Updates

Every update is checked. Plugins, themes, WordPress itself and translations, whether you clicked Update or WordPress did it automatically.
Every plugin switch too. Activating or deactivating a plugin, or switching theme, breaks sites as often as updates do. Those are checked the same way.
A clear verdict. “Verified – nothing changed”, or “3 changes found after this update”, with the before-and-after evidence one click away.
The culprit, named. Changes found after an update say so: “Appeared after: Updated WooCommerce 8.1.0 8.2.0”.
A history of every update, with versions, kept on your site.
Know before you press Update. On the Plugins screen, a plugin whose last update changed things on your site is flagged: “Last time this plugin updated, 2 things changed on your site.”
Roll back in one click. In the update history, any plugin from WordPress.org has a “Roll back to 8.1.0” button that reinstalls the version you had before, keeps the plugin active, and asks MyKavo to check the site again. This works on every plan, including free. Plugins from other sources cannot be rolled back here.
Update checks are included in every paid plan, from Starter. On the free plan, updates are still listed so you know what changed and when, and one-click rollback works.

Safe Update All, snapshots and “did it crash?” (free)

A saved copy of everything you update. Right before WordPress updates a plugin or theme, MyKavo zips the folder in wp-content/mykavo-snapshots (closed to the web). Any plugin or theme – premium ones too – can then be rolled back for seven days. The last two copies per plugin are kept, folders over 200 MB are skipped, and nothing is saved when the disk is low. MyKavo never snapshots or rolls back itself.
“Did it crash?” About ten seconds after an update, the site loads its own home page and up to three monitored pages and looks for a server error, WordPress’s “critical error” page, a PHP fatal error or an empty page. If it finds one, the update history says so with a “Roll back now” button.
Safe Update All. One button: optionally start an UpdraftPlus backup first, update the plugins one at a time, check the site after each, and roll back any update that breaks it, then one verdict: “7 updated, 6 verified, 1 rolled back”. On paid plans MyKavo also takes a fresh baseline first and checks the pages afterwards.
Silent-disaster alerts. “Discourage search engines” switched on, the site or WordPress address changed, the permalinks changed, the admin email changed, or a new administrator appeared: a red notice on every wp-admin screen until someone dismisses it. Paid plans also get an instant email or Slack alert from MyKavo.
Email check. Optional: WordPress sends one short test email a day to the admin address, and MyKavo shows whether it went out.
For agencies and their clients. A “MyKavo viewer” role lets a client see the MyKavo screen without being able to change anything. On multisite, Network Admin > MyKavo lists every site’s status.

Automatic rollback, update windows and plugin health

These come from MyKavo’s service on paid plans. MyKavo makes the decision (whether an update broke something, when updates may run, which plugins are abandoned); the plugin shows the result and carries out what MyKavo says.

Automatic rollback (Pro and Agency). When MyKavo’s check after a plugin update finds a critical change, the plugins from that update are put back to their previous version from WordPress.org automatically, and MyKavo checks the site again. You can switch it off on the Safe Updates screen. MyKavo never rolls itself back, never rolls back a rollback, and WordPress will not automatically update a rolled back plugin straight back to the version that broke.
Update windows (Agency). Choose the days and hours, in your time zone, when WordPress may install automatic updates. Outside the window, automatic plugin, theme and core updates wait for the next one, so they happen when someone is around.
Plugin health (paid plans, from Starter). Once a day the plugin sends MyKavo the list of installed plugins, and MyKavo flags the ones that were closed on WordPress.org or have not been updated in two years.
Known security issues. Every plan sees how many installed plugins have a known vulnerability. Paid plans, from Starter, see which plugin, what the issue is and the version that fixes it; Pro and Agency can have vulnerable plugins updated automatically as soon as the fix is out.
Update risk. On the Plugins screen, next to “Update now”: “Updated on 214 MyKavo sites, 3% saw changes” (anonymous results of Safe Updates across MyKavo). On Pro and Agency, an automatic update MyKavo marks risky waits 48 hours.
Watch buttons and forms. On the Pages tab, open a page, click the button, link or form that matters, and MyKavo alerts you if it disappears or changes. In the block editor, a MyKavo panel warns before you save an edit that removes a watched element or changes the page title or SEO description. The free plan watches one element; more come with Pro and Agency.
Contact forms (paid). Pages with a Contact Form 7, Gravity Forms or WPForms form are checked by MyKavo (from Starter), and on Pro and Agency MyKavo also sends a labelled test entry.
Your site report (Agency). A Site report tab with the last 30 days on one page – updates, rollbacks, uptime, SSL, changes caught and AI crawler visits – with your logo and brand colour, ready to share or print as a PDF.
Your plan at a glance. The plan medal (Free steel, Starter bronze, Pro silver, Agency gold) in the top bar, a Plan tab with everything your plan includes, a Site audit card that opens your MyKavo site audit, and, on Pro and Agency, the address to connect ChatGPT, Claude or any MCP app to MyKavo.

See which AI reads your site

ChatGPT, Claude, Perplexity and other AI systems send crawlers to read your pages before they quote or recommend them. The AI crawlers screen shows:

Who visits. Visits from OAI-SearchBot, ChatGPT-User, GPTBot, Claude-SearchBot, Claude-User, ClaudeBot, PerplexityBot, Perplexity-User, Amazonbot, DuckAssistBot, Meta-ExternalAgent, MistralAI-User, CCBot and Bytespider, and why each one visits (AI search answers, a person asking about your page, or training).
Which pages AI reads most, and visits per day for the last 30 days.
Errors served to AI. Pages that answered a crawler with 404 or 5xx – pages AI cannot quote.
Block AI training, allow AI search (free). One switch adds rules to your robots.txt that ask crawlers collecting AI training data (GPTBot, ClaudeBot, CCBot, Google-Extended, Applebot-Extended, Bytespider and Meta-ExternalAgent) to stay away, while the crawlers that read pages for AI search answers or open a page someone asked about (OAI-SearchBot, ChatGPT-User, Claude-SearchBot, Claude-User, PerplexityBot and Perplexity-User) are left alone. It works with the robots.txt WordPress generates; if your site has its own robots.txt file, the screen shows the rules to copy into it.
Last 12 months (paid plans, from Starter). Twelve months of AI crawler visits kept by MyKavo, by month and by crawler, with the day each crawler first visited.
Allow or block each AI crawler (free). A table with every known AI crawler, each allowed or blocked in robots.txt, plus a “Block training, allow search” button.
Real or fake? (free). Anyone can call themselves GPTBot. Visits from OpenAI and Perplexity crawlers are checked against the IP ranges those companies publish, and Amazonbot by reverse DNS, so fakes are counted separately. Only a salted hash of the address is cached for six hours; addresses are never stored. Requests that come through a proxy or CDN are not checked.
Fix errors served to AI (free). Addresses that answered an AI crawler with 404 get a “Create redirect” button. The redirect only runs on requests that would otherwise be a 404. Paid plans, from Starter, also get a suggested target page from MyKavo.
llms.txt (free). Switch on a /llms.txt for AI assistants: your site’s name, description and important pages. Paid plans, from Starter, add a one-line summary of each page written by MyKavo.

Crawlers are counted by the name they send in the User-Agent header. No IP addresses, no cookies and nothing about human visitors are ever recorded. You can switch counting off on that screen.

Built for WooCommerce stores

A broken cart or checkout loses sales every minute it stays broken. If WooCommerce is active, MyKavo shows whether your Shop, Cart, Checkout and My account pages are monitored, and adds the missing ones in one click.

On Pro and Agency, Guard checkout goes further: MyKavo also watches the Place order, Proceed to checkout and Add to cart buttons on your cart, checkout and a product page, and sends a critical alert the moment one goes missing.

What you see in WordPress

Safe Updates: a check and a verdict after every update, with the update named.
One clear status. “All clear”, or exactly how many important changes need attention, at the top of the screen and as a badge in the admin menu.
Before-and-after screenshots. Drag a slider across the old and new version of a page, or switch to the highlighted differences.
The exact values that changed. Old and new title, meta description, robots tag, canonical URL, button text and more, side by side.
Severity you can trust. Every change is ranked Critical, High, Medium, Low or Info. Ad slots and other noise are filtered out, so alerts mean something.
One-click decisions. Accept an intentional change as the new baseline, mark it fixed, or ignore it.
Run a scan on demand. Check the site right after an update and watch the progress live.
Uptime, response time and SSL expiry at a glance.
Scan history and monitored pages, with a link to each page.
A small Dashboard widget with the current status.
Monitor any page from WordPress. A “Monitor with MyKavo” link under every published page and post, or paste an address on the Pages tab.
Site Health. MyKavo’s status appears in Tools > Site Health, and its details in the Info tab for support requests.
WP-CLI. wp mykavo status, wp mykavo changes, wp mykavo scan --wait, wp mykavo monitor, wp mykavo updates and more, for scripted maintenance runs.

What MyKavo detects

Pages that go down or return errors (404, 500)
Visual changes, measured against an approved baseline
SEO changes: title, meta description, canonical, robots / noindex, headings, structured data
Broken internal links
Tracking and third-party scripts added or removed (Google Analytics, Tag Manager, Meta Pixel and others)
Performance regressions: page weight, request count, response time
Missing or changed buttons and forms you choose to watch (conversion elements)

Built to never slow your site down

Many plugins get deleted because they make a site slower. MyKavo is built so that cannot happen:

Nothing on the public site. No scripts, no styles, no database queries and no remote requests on the pages your visitors load. The only things that run are two text matches – the User-Agent header, to spot AI crawlers, and the request path, to answer /llms.txt – and human visitors stop there. A redirect is looked up only on a request that is already a 404.
AI crawler counting is one counter update. A request from an AI crawler adds one row update to a small table, after the page has been built. Rows older than 35 days are deleted.
No autoloaded options. The connection is stored in a single option that WordPress only reads on MyKavo’s own screens.
One small daily job. Once a day, WP-Cron sends the AI crawler totals and the list of installed plugins to MyKavo. The scanning itself runs on MyKavo’s servers, not yours.
Snapshots and checks run only during updates. A snapshot is taken while WordPress is already updating, and the “did it crash?” check is one WP-Cron job a few seconds later.
Automatic rollback waits quietly. On plans with automatic rollback, WP-Cron asks MyKavo every five minutes, for up to 40 minutes after a plugin update, how its check went. Nothing else runs between updates.
Admin screens only. Scripts load on the MyKavo screen alone (plus a 2 KB script for the Dashboard widget), using only libraries WordPress already includes.
Update checks cost nothing extra. The plugin notes versions while WordPress is updating, then sends one short report when the update finishes. Nothing runs between updates.
Cached and time-limited. Answers from MyKavo are cached for a minute, and every request has a short timeout.

Secure by design

Connecting uses an OAuth-style approval with PKCE. You approve on mykavo.app, and your site receives a key that only works for this one website.
The key stays on your server. Your browser never sees it.
Only administrators can act on monitoring. Users with the “MyKavo viewer” role can see it, read-only.
Disconnect at any time, from WordPress or from your MyKavo account.

Plans

MyKavo has a free plan: 1 website, 5 monitored pages and weekly scans, with no card required. Paid plans add daily scans, more websites and pages, manual scans and more. See mykavo.app/pricing.

External services

This plugin connects your site to MyKavo (https://mykavo.app), a website monitoring service operated by MyKavo. It does not work without a MyKavo account.

What is sent, and when:

When you press “Connect to MyKavo”: your browser is sent to mykavo.app with your site’s address, its name, its WordPress admin address, the plugin and WordPress version numbers, and one-time security values for the connection. Your site’s server then sends a one-time code and your site’s address to mykavo.app to finish connecting.
After WordPress updates plugins, themes, translations or itself, and after a plugin is activated or deactivated or the theme is switched: your site’s server sends the names and version numbers of what changed, and whether the update was automatic, so MyKavo can check the site. You can switch this …

MyKavo – Website Change Monitoring