{"id":384137,"date":"2026-10-15T10:59:21","date_gmt":"2026-10-15T10:59:21","guid":{"rendered":"https:\/\/wordpress.org\/plugins\/relvato-continuous-monitoring\/"},"modified":"2026-10-15T13:46:28","modified_gmt":"2026-10-15T13:46:28","slug":"relvato","status":"publish","type":"plugin","link":"https:\/\/wordpress.org\/plugins\/relvato\/","author":23579104,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"1.77.2","stable_tag":"1.77.2","tested":"7.1.3","requires":"6.5","requires_php":"7.4","requires_plugins":null,"header_name":"Relvato \u2014 Continuous Monitoring","header_author":"Relvato","header_description":"After every WordPress, plugin, theme or WooCommerce update, Relvato automatically re-tests key pages, checkout, forms, security and speed.","assets_banners_color":"0f1d24","last_updated":"2026-10-15 13:46:28","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"https:\/\/www.relvato.com\/platforms\/wordpress","header_author_uri":"https:\/\/www.relvato.com","rating":0,"author_block_rating":0,"active_installs":0,"downloads":41,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","faq","changelog"],"tags":{"1.77.1":{"tag":"1.77.1","author":"relvato","date":"2026-10-15 10:59:10","revision":3748240},"1.77.2":{"tag":"1.77.2","author":"relvato","date":"2026-10-15 13:46:28","revision":3748618}},"upgrade_notice":[],"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3748240,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3748240,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3748240,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3748240,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.77.1","1.77.2"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3748240,"resolution":"1","location":"assets","locale":"","width":1114,"height":861},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3748240,"resolution":"2","location":"assets","locale":"","width":1113,"height":882},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3748240,"resolution":"3","location":"assets","locale":"","width":1116,"height":735},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3748240,"resolution":"4","location":"assets","locale":"","width":1111,"height":669},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3748240,"resolution":"5","location":"assets","locale":"","width":1111,"height":714},"screenshot-6.png":{"filename":"screenshot-6.png","revision":3748240,"resolution":"6","location":"assets","locale":"","width":1104,"height":667},"screenshot-7.png":{"filename":"screenshot-7.png","revision":3748240,"resolution":"7","location":"assets","locale":"","width":1111,"height":784},"screenshot-8.png":{"filename":"screenshot-8.png","revision":3748240,"resolution":"8","location":"assets","locale":"","width":1063,"height":704}},"screenshots":{"1":"Once connected, Relvato can monitor your critical site flows, SEO \/ AEO readiness, site security, performance, domain, legal pages or accessibility.","2":"Choose when your monitors run: on a schedule, and again automatically after WordPress, theme or plugin updates.","3":"The Relvato dashboard in WordPress: every monitoring group at a glance \u2014 what passes, and what needs a look.","4":"Relvato suggests safe, reversible fixes. You apply each one in WordPress with one click, switch it back off any time, and Relvato re-runs its monitors to confirm.","5":"Performance in WordPress: lab Core Web Vitals against Google's \"good\" limits on one radar, with the biggest wins to fix first.","6":"Legal compliance: Relvato checks for a privacy policy, terms and an accessibility statement, and flags cookie consent and tracking problems \u2014 with a suggested fix for each.","7":"Every run in WordPress: what ran, what it found, and when \u2014 with the full details one click away in Relvato.","8":"The Relvato app: each site at a glance \u2014 monitors passing, what's ready to run, results over time and every run, for all your sites in one place."}},"plugin_section":[],"plugin_tags":[5603,247,600,29148,286],"plugin_category":[45,54],"plugin_contributors":[286923],"plugin_business_model":[],"class_list":["post-384137","plugin","type-plugin","status-publish","hentry","plugin_tags-monitoring","plugin_tags-performance","plugin_tags-security","plugin_tags-uptime","plugin_tags-woocommerce","plugin_category-ecommerce","plugin_category-security-and-spam-protection","plugin_contributors-relvato","plugin_committers-relvato"],"banners":{"banner":"https:\/\/ps.w.org\/relvato\/assets\/banner-772x250.png?rev=3748240","banner_2x":"https:\/\/ps.w.org\/relvato\/assets\/banner-1544x500.png?rev=3748240","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/relvato\/assets\/icon-128x128.png?rev=3748240","icon_2x":"https:\/\/ps.w.org\/relvato\/assets\/icon-256x256.png?rev=3748240","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/relvato\/assets\/screenshot-1.png?rev=3748240","caption":"Once connected, Relvato can monitor your critical site flows, SEO \/ AEO readiness, site security, performance, domain, legal pages or accessibility."},{"src":"https:\/\/ps.w.org\/relvato\/assets\/screenshot-2.png?rev=3748240","caption":"Choose when your monitors run: on a schedule, and again automatically after WordPress, theme or plugin updates."},{"src":"https:\/\/ps.w.org\/relvato\/assets\/screenshot-3.png?rev=3748240","caption":"The Relvato dashboard in WordPress: every monitoring group at a glance \u2014 what passes, and what needs a look."},{"src":"https:\/\/ps.w.org\/relvato\/assets\/screenshot-4.png?rev=3748240","caption":"Relvato suggests safe, reversible fixes. You apply each one in WordPress with one click, switch it back off any time, and Relvato re-runs its monitors to confirm."},{"src":"https:\/\/ps.w.org\/relvato\/assets\/screenshot-5.png?rev=3748240","caption":"Performance in WordPress: lab Core Web Vitals against Google's \"good\" limits on one radar, with the biggest wins to fix first."},{"src":"https:\/\/ps.w.org\/relvato\/assets\/screenshot-6.png?rev=3748240","caption":"Legal compliance: Relvato checks for a privacy policy, terms and an accessibility statement, and flags cookie consent and tracking problems \u2014 with a suggested fix for each."},{"src":"https:\/\/ps.w.org\/relvato\/assets\/screenshot-7.png?rev=3748240","caption":"Every run in WordPress: what ran, what it found, and when \u2014 with the full details one click away in Relvato."},{"src":"https:\/\/ps.w.org\/relvato\/assets\/screenshot-8.png?rev=3748240","caption":"The Relvato app: each site at a glance \u2014 monitors passing, what's ready to run, results over time and every run, for all your sites in one place."}],"raw_content":"<!--section=description-->\n<p><a href=\"https:\/\/www.relvato.com\">Relvato<\/a> is a website monitoring platform. It runs monitors against your site in a real browser: checkout, logins, sign-ups, contact forms, page speed, search visibility and security. This plugin connects your WordPress site to your Relvato account, so the monitors run again the moment something changes, and can see what a monitor running from outside can't.<\/p>\n\n<p>https:\/\/www.youtube.com\/watch?v=D6GfiDeb8nw<\/p>\n\n<p>What the plugin adds:<\/p>\n\n<ul>\n<li><strong>Runs after every change (Pro and up).<\/strong> A plugin, theme, WordPress or WooCommerce update tells Relvato to re-run the monitors that change can affect, so a broken checkout is caught minutes after the update, not days later. On the free plan you start the runs yourself, from WordPress or the Relvato app, or run them weekly.<\/li>\n<li><strong>Monitors that need to be inside.<\/strong> Logged-in checkout and account pages through a dedicated test customer, test orders that never touch your stock, stay out of your analytics and ad platforms (and move themselves to the Trash), form tests that don't email your team, WooCommerce health, backups, Site Health, PHP errors and failed emails.<\/li>\n<li><strong>Security from the inside.<\/strong> File integrity against WordPress.org checksums, signs of a hack in themes, uploads and options, new administrators, leftover backup files, and hardening you can switch on and off.<\/li>\n<li><strong>Fixes you apply.<\/strong> When a run proposes a fix (rolling back a plugin update, turning search indexing back on, clearing a cache\u2026), it appears under \"Relvato suggests\" in WordPress \u2192 Relvato, and an administrator applies it there with one click. Relvato then re-runs its monitors to verify it, and every fix can be undone. Relvato never applies a fix or changes a plugin on its own.<\/li>\n<li><strong>AI assistants.<\/strong> On WordPress 6.9+, Relvato's abilities (site status, monitors, the brief for fixing a failure) are available to AI assistants through the WordPress Abilities API, for administrators only.<\/li>\n<\/ul>\n\n<p>The plugin needs a Relvato account; there is a free plan (<a href=\"https:\/\/www.relvato.com\/pricing\">plans<\/a>). Nothing is sent to Relvato until you connect the plugin. Every request between your site and Relvato is signed with your site's own secret.<\/p>\n\n<p>Five features are off until you turn them on in <strong>Relvato \u2192 Settings<\/strong>: the activity log (sign-ins, key changes, PHP errors and failed emails), the test login, form tests, real-user Web Vitals and the outside-services map. When you set up monitoring in the plugin, its last step lists the ones your chosen monitors need, with what each does: test login and form tests are ticked, the activity log and real-user Web Vitals are not, and only the ticked ones go on with the monitors. A monitor that needs one that's off tells you which, in Relvato, instead of running.<\/p>\n\n<h3>External services<\/h3>\n\n<p>This plugin connects your site to Relvato, a website monitoring service run by Relvato (<a href=\"https:\/\/www.relvato.com\/terms\">terms<\/a>, <a href=\"https:\/\/www.relvato.com\/privacy\">privacy policy<\/a>). Nothing below happens until you connect the site, by clicking \"Connect with Relvato\" or pasting your connect token.<\/p>\n\n<p><strong>Relvato (app.relvato.com).<\/strong> Used to run your monitors and show their results.<\/p>\n\n<ul>\n<li><p>When you click <strong>Connect with Relvato<\/strong>, your browser goes to app.relvato.com with your site's address, the way back to your WordPress admin, a one-time check value, the active theme and the well-known plugins it runs, by name (for example WooCommerce, Yoast SEO, Wordfence, WP Rocket, Elementor), so you can sign in and confirm the site. When you come back, the plugin sends a one-time code, the matching secret and your site's address to app.relvato.com to receive your connect token.<\/p><\/li>\n<li><p>When something changes on the site, the plugin sends a signed event about the change: plugin, theme, WordPress and WooCommerce updates, activations and theme switches; new administrators and role changes; and, while quarantine mode is on after a hack, new scheduled tasks and uploaded executable files. Each event names the WordPress user who made the change.<\/p><\/li>\n<li>While the <strong>activity log<\/strong> is on (off until you turn it on): administrator and editor logins (with the login name, role and the first part of the IP address) and counts of failed logins (never the usernames tried); changes to key settings (site address, registration, search visibility); edits made in the theme and plugin file editors; application passwords created or deleted; deleted administrators; and new PHP fatal errors and failed emails (the recipient's domain only). With it on, the plugin also keeps when each administrator last signed in (on the site) and includes that time in the security review of accounts below, so Relvato can point out administrators nobody uses; switching the activity log off deletes those times.<\/li>\n<li>While the <strong>outside-services map<\/strong> is on (off until you turn it on): for each server-side request a plugin or theme makes to another server, the plugin's or theme's folder name and the host name it called (never the full address, what was sent or what came back), with the day it was first and last seen. Kept in your site's options and read by Relvato's Exposure scan; switching it off deletes it.<\/li>\n<li>Every six hours the plugin sends its version, which well-known plugins are active, by name (for example Yoast SEO, Wordfence, WP Rocket, WooCommerce, a form or caching plugin), the active theme, the search visibility setting, whether its REST routes can be reached (and if not, which plugin blocks them) and which of the features above are on.<\/li>\n<li>When you open the Relvato pages in WordPress, the plugin fetches your monitors' status and Relvato's suggestions, and sends the actions you start there (such as running a monitor).<\/li>\n<li>When an administrator applies a suggestion there, the plugin first asks app.relvato.com to start a plugin update or deactivation (so Relvato can verify it), then reports what was applied: which suggestion, whether it worked (and WordPress's error if not), the hardening settings now on, and the WordPress user who applied it. A quarantine's auto-update pause, a released update hold and an undo are reported the same way.<\/li>\n<li>Relvato's monitors call the plugin's own REST routes, signed with your site's secret, to read results such as WooCommerce health, file checksums and installed plugin versions. None of them can change plugins, themes, settings or code; the only things they create or change are Relvato's own test data (the test customer below, test orders, form-test entries and test emails). The security review of accounts reads the administrator and other privileged accounts (login name, display name, roles, when the account was created, the domain of its email address and the names of its application passwords), and the ways in that skip the login form: WooCommerce REST API keys (their description, owner, access and the last characters WooCommerce shows) and OAuth clients. Administrator passwords and API keys are never sent.<\/li>\n<li>While <strong>Test login<\/strong> is on (off until you turn it on), the plugin keeps one dedicated test customer account (it creates it as a customer, or a subscriber without WooCommerce; never an administrator, and it refuses any account that can do more than shop). For logged-in monitors, a request signed by Relvato signs Relvato's browser in as that account (a session cookie, nothing stored). To test the real login form, Relvato can ask for that account's login: the plugin sets a new random password on it and returns the username and that password over the signed connection. Relvato can also have WordPress send that account's lost-password email (to the Relvato test inbox), to check the reset email goes out. No other account's password is set or sent.<\/li>\n<li>While <strong>AI assistant abilities<\/strong> are on, an AI assistant working in your WordPress admin (as an administrator) can ask the plugin for the site's status, its monitors or the fix brief for a run, or start monitors; each request goes to app.relvato.com, and nothing is sent until an assistant asks.<\/li>\n<li>While connected, your homepage carries <code>&lt;meta name=\"relvato-site\"&gt;<\/code> with your Relvato site's ID, so Relvato can confirm the connection from outside. It isn't a link and shows nothing to visitors.<\/li>\n<\/ul>\n\n<p><strong>Relvato real-user speed measurement (app.relvato.com).<\/strong> While real-user Web Vitals is on (off until you turn it on), a small script on your public pages measures how fast each page loads for a sample of visitors and sends the timings, the page type, whether the device is a phone or a computer, and (for slow pages) the slow element and resource to app.relvato.com\/api\/vitals. It sets no cookies and doesn't identify visitors. The script is part of the plugin (assets\/vitals-beacon.js); nothing is loaded from Relvato.<\/p>\n\n<p><strong>Relvato test inbox (verify.relvato.com).<\/strong> During a contact-form test (while form tests are on) or an email monitor, the test message goes to a Relvato address for your site instead of to your team, so Relvato can confirm it arrived.<\/p>\n\n<p><strong>WordPress.org (api.wordpress.org, downloads.wordpress.org).<\/strong> File integrity compares your WordPress core and plugin files with WordPress.org's published checksums. Rolling a plugin back or reinstalling it downloads that version from WordPress.org. See the <a href=\"https:\/\/wordpress.org\/about\/privacy\/\">WordPress.org privacy policy<\/a>.<\/p>\n\n<!--section=installation-->\n<ol>\n<li>Install and activate the plugin.<\/li>\n<li>In WordPress, open <strong>Relvato \u2192 Settings<\/strong> and click <strong>Connect with Relvato<\/strong>. Sign up or sign in (free, no card), confirm the site, and you come straight back to WordPress, connected.<\/li>\n<li>Or, if you already have a connect token from the Relvato app (the site's Settings \u2192 Connection), paste it on the same page and save.<\/li>\n<\/ol>\n\n<!--section=faq-->\n<dl>\n<dt id=\"is%20relvato%20free%3F%20what%20does%20the%20free%20plan%20include%3F\"><h3>Is Relvato free? What does the free plan include?<\/h3><\/dt>\n<dd><p>Yes, and it stays free: one site, 100 runs a month and every monitor except custom monitors and AI-feature monitors, with no card. On the free plan you start the runs, from WordPress or the Relvato app, or schedule them weekly. Paid plans re-run the monitors by themselves after every update, add daily and faster schedules and alerts, and cover more sites. See https:\/\/www.relvato.com\/pricing.<\/p><\/dd>\n<dt id=\"does%20relvato%20need%20my%20password%20or%20my%20customers%27%20passwords%3F\"><h3>Does Relvato need my password or my customers' passwords?<\/h3><\/dt>\n<dd><p>Never yours or your customers'. For logged-in monitors the plugin signs Relvato's browser in as a dedicated test customer it creates (never an administrator), using a short-lived signed token. To test the real login form, Relvato asks the plugin for that test customer's login: the plugin sets a new random password on that one account each time and returns it with the username, over the signed connection. This only happens while <strong>Test login<\/strong> is on in the plugin's settings.<\/p><\/dd>\n<dt id=\"will%20monitors%20change%20my%20stock%20or%20create%20real%20orders%3F\"><h3>Will monitors change my stock or create real orders?<\/h3><\/dt>\n<dd><p>A checkout monitor set to \"Full order\" places a real test order \u2014 that's how it proves your checkout works. The plugin marks it (order meta <code>_relvato_test<\/code>), doesn't reduce stock for it, doesn't email you about it, and moves it to the Trash a few minutes later. Monitors that stop before \"Place order\" create no order at all. Turning off \"Protect stock &amp; auto-remove\" in the plugin's settings keeps test orders (and their stock change) instead of removing them. So that stores taking only cards can be tested too, the plugin creates a 100% discount coupon that works only inside Relvato's signed test requests, never for a shopper; it is deleted when you deactivate the plugin.<\/p><\/dd>\n<dt id=\"will%20test%20orders%20show%20up%20in%20google%20analytics%2C%20google%20ads%20or%20meta%3F\"><h3>Will test orders show up in Google Analytics, Google Ads or Meta?<\/h3><\/dt>\n<dd><p>No. The plugin switches off the purchase event for test orders in Pixel Manager for WooCommerce (browser, conversion recovery and server-side), Google for WooCommerce, Google Analytics for WooCommerce, Site Kit, GTM4WP, Facebook for WooCommerce (pixel and Conversions API), PixelYourSite, Pinterest for WooCommerce and TikTok. Relvato's test browser also refuses analytics consent and blocks the ad and analytics collection addresses while it places the order. On WooCommerce 10.7 and later, test orders are also kept out of WooCommerce Analytics. For your own reports and conversion uploads, skip orders for which <code>relvato_is_test_order( $order )<\/code> returns true.<\/p><\/dd>\n<dt id=\"can%20relvato%20change%20my%20site%3F\"><h3>Can Relvato change my site?<\/h3><\/dt>\n<dd><p>Not on its own. Relvato suggests changes; an administrator applies each one in WordPress \u2192 Relvato, where the plugin makes it from a fixed list of reversible actions built into the plugin: for example rolling a plugin back to the version before an update, updating or switching off a vulnerable plugin, or turning search indexing back on. Each needs the matching WordPress permission (for example \"update plugins\"). No request from Relvato's service can install, update, activate or remove a plugin or theme, or change your settings or code. What it can ask for is limited to Relvato's own test data: while Test login is on, the dedicated test customer (the plugin creates that one account, never an administrator, signs Relvato's browser in as it, sets its password and sends its lost-password email to the Relvato inbox); the test orders, form entries and test emails its monitors make, and removing them. The plugin never runs code it receives, and every applied fix can be undone there.<\/p><\/dd>\n<dt id=\"does%20the%20plugin%20change%20wordpress%20updates%3F\"><h3>Does the plugin change WordPress updates?<\/h3><\/dt>\n<dd><p>Only when you ask it to. After you roll a plugin back, Relvato holds the version you left, so WordPress doesn't put it straight back: automatic updates skip it and installing it is refused until you release the hold (\"Release the hold\" on that plugin's row on the Plugins screen). While quarantine mode is on after a hack, an administrator can tick \"Pause plugin and theme auto-updates\" in WordPress \u2192 Relvato. Nothing else about WordPress's updates is changed.<\/p><\/dd>\n<dt id=\"does%20the%20plugin%20change%20how%20my%20forms%20handle%20spam%3F\"><h3>Does the plugin change how my forms handle spam?<\/h3><\/dt>\n<dd><p>Only for Relvato's own test submissions, and only while <strong>Form tests<\/strong> is on: for a submission carrying Relvato's marker in a request signed with your site's secret, the form plugin's CAPTCHA check and Akismet are skipped through the form plugin's own filters, its notification goes to your site's Relvato inbox instead of your team, and the test entry is deleted afterwards. Every other submission is handled exactly as before.<\/p><\/dd>\n<dt id=\"what%20does%20security%20hardening%20change%3F\"><h3>What does security hardening change?<\/h3><\/dt>\n<dd><p>Nothing until you switch an item on in Relvato, and each can be switched off again: XML-RPC off (not while Jetpack is active), the public user list and username lookups by number hidden, the WordPress version tag and the X-Powered-By header removed, the theme and plugin file editor turned off (the same as DISALLOW_FILE_EDIT; a value already set in wp-config.php wins), a few safe security headers added where the site sends none, and an empty index.php added to the uploads folders.<\/p><\/dd>\n<dt id=\"does%20the%20plugin%20keep%20backups%3F\"><h3>Does the plugin keep backups?<\/h3><\/dt>\n<dd><p>Only of plugins that aren't from WordPress.org, and only once the site is connected. When one of those updates, the plugin first zips the version being replaced into wp-content\/relvato-backups (closed to web visitors), so Relvato can roll the update back if it breaks the site; WordPress.org plugins are rolled back from WordPress.org instead. It keeps the two newest backups per plugin, for up to 60 days.<\/p><\/dd>\n<dt id=\"what%20happens%20when%20i%20remove%20the%20plugin%3F\"><h3>What happens when I remove the plugin?<\/h3><\/dt>\n<dd><p>Deactivating stops all communication with Relvato. Deleting the plugin also removes its settings, the test customer and Relvato's plugin backups.<\/p><\/dd>\n\n<\/dl>\n\n<!--section=changelog-->\n<h4>1.77.2 (2026-10-15)<\/h4>\n\n<ul>\n<li>Changed: Relvato is now on WordPress.org, and the plugin updates from there like any other. Sites that installed it from relvato.com move over with this version; nothing to do.<\/li>\n<\/ul>\n\n<h4>1.77.1 (2026-10-11)<\/h4>\n\n<ul>\n<li>Fixed: wp-config.php is checked for malware patterns again (only the pattern's name is reported; 1.77.0 skipped it along with its hash).<\/li>\n<li>Readme: says exactly what Relvato's requests can create or change \u2014 only its own test data, including how the test customer is signed in.<\/li>\n<\/ul>\n\n<h4>1.77.0 (2026-10-11)<\/h4>\n\n<ul>\n<li>Changed: Relvato never applies a fix or changes a plugin on its own. Fixes, plugin updates, rollbacks, deactivations and their undo are applied by an administrator under \"Relvato suggests\" in WordPress \u2192 Relvato (each needs the matching WordPress permission); the plugin then tells Relvato, which re-runs its monitors to verify the change. The routes Relvato's service used to apply them are removed.<\/li>\n<li>Changed: during quarantine mode, pausing plugin and theme auto-updates is a tick box in WordPress \u2192 Relvato, set by an administrator.<\/li>\n<li>Changed: Relvato's scheduled update window no longer runs on sites with this version; WordPress's own automatic updates keep working, and an update that breaks a monitor is offered as a one-click rollback in WordPress \u2192 Relvato.<\/li>\n<li>Security: the plugin no longer reads the values of your WordPress keys and salts, and wp-config.php is no longer part of the file fingerprint. Every admin page is escaped as it's printed. The activity log and quarantine record a file-editor save only with WordPress's own check for that save.<\/li>\n<\/ul>\n\n<h4>1.76.2 (2026-10-09)<\/h4>\n\n<ul>\n<li>Changed: \"Tested up to\" is declared only in this readme, no longer in the plugin file's header, as WordPress.org now requires.<\/li>\n<\/ul>\n\n<h4>1.76.1 (2026-10-09)<\/h4>\n\n<ul>\n<li>Fixed: the Runs list heading (\"The latest 5 runs\") now translates correctly in languages whose singular form also covers numbers like 21.<\/li>\n<\/ul>\n\n<h4>1.76.0 (2026-10-09)<\/h4>\n\n<ul>\n<li>Changed: on setup's last step, the activity log and real-user Web Vitals start unticked; only the switches you tick go on with your monitors. Test login and form tests stay ticked.<\/li>\n<li>Changed: backups of plugins that aren't from WordPress.org are kept only once the site is connected.<\/li>\n<li>Changed: the description and the dashboard group \"Legal &amp; accessibility\" no longer say \"legal compliance\": Relvato reports what it finds on your legal pages, cookie banner and accessibility; it doesn't certify anything.<\/li>\n<li>New: suggested privacy-policy text for the real-user speed script and the activity log (Settings \u2192 Privacy \u2192 Policy Guide).<\/li>\n<li>Fixed: with two copies of Relvato in two plugin folders, activating the second no longer stops with a fatal error.<\/li>\n<li>Readme: the FAQ and External services now say exactly what Test login sends, and when plugin backups are made.<\/li>\n<\/ul>\n\n<h4>1.75.1 (2026-10-09)<\/h4>\n\n<ul>\n<li>Fixed: a monitor still collecting data (Real-user Web Vitals before enough page views) no longer counts as \"couldn't run\" on the Overview's \"Monitors passing\" row. It's ready \u2014 Ready to run says so \u2014 and the row now shows it as \"1 collecting data\", with a note that it's counted once there's enough.<\/li>\n<\/ul>\n\n<h4>1.75.0 (2026-10-08)<\/h4>\n\n<ul>\n<li>New: the Overview's \"Monitors passing\" row now says how many monitors passed and how many it leaves out \u2014 e.g. \"26 of 27 passing \u00b7 3 couldn\u2019t run\". Monitors that couldn\u2019t run or haven\u2019t run yet aren't in the percentage, so a 100% that covers only part of your monitors now says so. \"Ready to run\" shows why each one is left out.<\/li>\n<\/ul>\n\n<h4>1.74.2 (2026-10-08)<\/h4>\n\n<ul>\n<li>Changed: the Overview's \"Site health\" card is now \"Monitors passing\" \u2014 it was always the share of your monitors whose latest run passed, not a score for the whole site. \"Health over time\" is now \"Passing over time\". Nothing about how it's counted changed.<\/li>\n<\/ul>\n\n<h4>1.74.1 (2026-10-08)<\/h4>\n\n<ul>\n<li>Fixed: switches ticked on setup's last step \u2014 Test login, form tests, the activity log \u2014 weren't saved (only Real-user Web Vitals was), so Customer login and Logged-in checkout still reported Test login as off. They're saved now. If you set up with 1.74.0, turn Test login on in Relvato \u2192 Settings.<\/li>\n<\/ul>\n\n<h4>1.74.0 (2026-10-08)<\/h4>\n\n<ul>\n<li>New: setup's \"When should they run?\" step lists the plugin switches your chosen monitors need \u2014 Test login, Real-user Web Vitals, form tests, the activity log \u2014 with what each does, ticked. They go on with your monitors (untick any first), so Customer login, Logged-in checkout and real-user Web Vitals run from the start instead of waiting for you in Settings.<\/li>\n<\/ul>\n\n<h4>Earlier versions<\/h4>\n\n<ul>\n<li>The full history is at https:\/\/www.relvato.com\/changelog<\/li>\n<\/ul>","raw_excerpt":"After every WordPress, plugin, theme or WooCommerce update, Relvato automatically re-tests key pages, checkout, forms, security and speed.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/384137","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=384137"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/relvato"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=384137"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=384137"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=384137"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=384137"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=384137"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=384137"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}