Title: Site Remedy AI Author: Xpert Developerz Published: September 9, 2026 Last modified: September 9, 2026 --- Search plugins ![](https://ps.w.org/site-remedy-ai/assets/banner-772x250.png?rev=3688115) ![](https://ps.w.org/site-remedy-ai/assets/icon-256x256.png?rev=3688115) # Site Remedy AI By [Xpert Developerz](https://profiles.wordpress.org/xpertdeveloperz/) [Download](https://downloads.wordpress.org/plugin/site-remedy-ai.1.57.1.zip) * [Details](https://wordpress.org/plugins/site-remedy-ai/#description) * [Reviews](https://wordpress.org/plugins/site-remedy-ai/#reviews) * [Installation](https://wordpress.org/plugins/site-remedy-ai/#installation) * [Development](https://wordpress.org/plugins/site-remedy-ai/#developers) [Support](https://wordpress.org/support/plugin/site-remedy-ai/) ## Description Developed by Xpert Developerz — https://xpertdeveloperz.com/ Site Remedy AI is a local-first WordPress maintenance and diagnostic platform for site health, errors, request/API/database failures, performance evidence, change tracking, incident correlation, recovery verification, maintenance planning, reporting, support snapshots and privacy-safe diagnostic handoff. Safety model: * Evidence and deterministic analysis remain local by default. * Plugin/theme maintenance and recovery actions require administrator confirmation.* No unattended plugin/theme updates are performed. * Diagnostic exports are administrator initiated and exclude credentials, API tokens, raw payloads and other sensitive fields. * Deactivation preserves evidence. Uninstall removes data only when the administrator explicitly selected full data removal in Site Remedy Settings. ### Production rollout * Take a normal site/database backup before first deployment or maintenance changes. * Start on a staging or controlled production site and review Dashboard, Action Center and Settings before broader rollout. * Site Remedy recommendations remain administrator-controlled; review evidence before applying maintenance or recovery actions. * Emergency Recovery Bridge requires HTTPS outside localhost and should only be enabled when standalone recovery access is required. * Development test helpers and the RC uninstall validator are separate tools and are not included in the production package. ### Data lifecycle * Deactivation preserves Site Remedy evidence and configuration. * With Retain Site Remedy data selected, uninstall removes Site Remedy runtime schedules and the Emergency Recovery Bridge while retaining Site Remedy data for a later reinstall. * With Delete all Site Remedy data selected, uninstall removes Site Remedy tables, options, transients, schedules and Recovery Bridge state. * The uninstall policy can be reviewed in Site Remedy AI > Settings before removing the plugin. ### Privacy and external services Site Remedy does not send telemetry, diagnostics, site content, credentials, or usage data to Xpert or to a Site Remedy-hosted service. Core monitoring and diagnostic analysis run on the WordPress site. Site Remedy observes WordPress HTTP API activity so it can record failures made by WordPress, plugins, or themes. It does not create those third-party requests itself. The destination and privacy terms of those requests are controlled by the component that initiated them. If an administrator explicitly enables scheduled report delivery or sends a test report, Site Remedy uses the site’s configured WordPress mail system (`wp_mail`) to send the selected report summary to the email address entered by the administrator. No report is sent to Xpert by default. Diagnostic downloads are created only after an administrator requests them. They are designed to omit credentials, API tokens, raw request payloads, database queries, stack traces, and free-form sensitive content. Administrators should still review exported files before sharing them with a third party. ### Source code All PHP, JavaScript, CSS, and Recovery Bridge runtime source distributed with Site Remedy AI is included in human-readable source form in the plugin package. No JavaScript build step is required for this release. In particular, `admin/assets/js/changes. js` is the maintained source file used directly by WordPress and is not a generated or minified artifact. ### Emergency Recovery Bridge The optional Emergency Recovery Bridge is disabled by default. When an administrator enables it, Site Remedy creates a standalone recovery directory under the site’s WordPress content directory so limited recovery access can remain available if normal WordPress bootstrap fails. The bridge code is shipped with this plugin; Site Remedy does not download or execute remote code. It uses a one-time recovery key, stores only a password hash, requires HTTPS outside localhost, rate-limits authentication attempts, and restricts plugin file disable/restore actions to the last-known plugin snapshot. The bridge is removed when Site Remedy is uninstalled. ## Screenshots [[ [[ [[ [[ [[ ## Installation 1. Upload and activate Site Remedy AI from WordPress Plugins. 2. Open Site Remedy AI > Settings and confirm the Release Readiness checks pass for the site environment. 3. Keep the default Retain Site Remedy data uninstall policy unless permanent data removal is explicitly required. 4. The Emergency Recovery Bridge is optional and disabled by default. If enabled, store its one-time recovery key securely and verify Bridge Health from Settings. ## FAQ ### Does Site Remedy send site data to an AI or cloud service? No. This release performs local deterministic analysis and does not contact an external Site Remedy AI service. ### Does Site Remedy automatically update plugins or themes? No unattended plugin or theme updates are performed. Component maintenance actions require administrator confirmation. ### Does Site Remedy make third-party API requests? Site Remedy monitors WordPress HTTP API failures, but it does not create the monitored third-party requests. Other plugins, themes, or WordPress itself may make those requests. ### What happens to data when I deactivate or uninstall Site Remedy? Deactivation preserves Site Remedy data. Uninstall retains diagnostic data by default while removing runtime schedules and the Emergency Recovery Bridge. Administrators can explicitly select full data removal in Site Remedy Settings before uninstalling. ### Is the Emergency Recovery Bridge required? No. It is optional and disabled by default. Normal monitoring, diagnostics, reports, and maintenance guidance work without it. ### Can I use Site Remedy on multisite? The current release is designed and tested primarily for standard single-site WordPress installations. Multisite-specific behavior is not advertised as supported in this release. ## Reviews There are no reviews for this plugin. ## Contributors & Developers “Site Remedy AI” is open source software. The following people have contributed to this plugin. Contributors * [ Xpert Developerz ](https://profiles.wordpress.org/xpertdeveloperz/) [Translate “Site Remedy AI” into your language.](https://translate.wordpress.org/projects/wp-plugins/site-remedy-ai) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/site-remedy-ai/), check out the [SVN repository](https://plugins.svn.wordpress.org/site-remedy-ai/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/site-remedy-ai/) by [RSS](https://plugins.trac.wordpress.org/log/site-remedy-ai/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 1.57.1 * Replaced the nonstandard Recovery Bridge `.template` distribution file with a documented `.txt` runtime source file that is copied to `index.php` only when an administrator enables the bridge. * Removed the direct `error_reporting()` call from the PHP error monitor while preserving respect for the site’s configured PHP error mask. * No feature scope changes. #### 1.57.0 * Renamed the plugin to Site Remedy AI and aligned the WordPress.org text domain with the proposed `site-remedy-ai` repository slug. * Updated developer attribution and the WordPress.org contributor username. * Completed the repository security review of state-changing requests, retaining capability and nonce verification for protected actions. * Replaced the compressed Changes screen JavaScript with the maintained human-readable source used directly by the plugin. * No new feature scope added. #### 1.56.1 * WordPress.org submission header correction: removed duplicate Plugin URI while retaining the Xpert Developerz Author URI. * No functional behavior changes. #### 1.56.0 * WordPress.org submission-candidate compliance hardening. * Clarified nonce-analysis exceptions for read-only navigation and diagnostic request classification while preserving capability checks on protected actions. * Documented intentional production diagnostics hooks used for PHP error and source attribution monitoring. * Finalized repository metadata, developer attribution, and short description. * No new feature scope added. #### 1.54.0 * WordPress.org repository compatibility pass with the public plugin name and slug changed to Site Remedy AI / site-remedy-ai. * Text domain aligned to the repository slug for translation compatibility. * Restored and verified the non-executable Emergency Recovery Bridge runtime template; no standalone executable PHP runtime is shipped inside the plugin directory. * Documented intentional uncached queries against Site Remedy’s own diagnostic tables for WordPress Coding Standards. * Reduced repository-check noise around internally controlled table identifiers while preserving prepared values and current diagnostic evidence. * Kept Xpert Developerz attribution and https://xpertdeveloperz.com/ in plugin metadata. * No new monitoring, incident, maintenance, or recovery feature behavior was added. #### 1.53.0 * WordPress.org submission-candidate hardening based on Plugin Check findings. * Improved repository metadata, escaping, nonce/input handling, date handling and prepared LIKE queries. * Recovery Bridge runtime moved to a non-executable template that is materialized only when explicitly enabled by an administrator. #### 1.52.0 * WordPress.org repository-preparation release with expanded licensing, privacy, external-service, FAQ, and recovery documentation. * Added GPLv2 license file and retained administrator-controlled maintenance/recovery and no-telemetry defaults. #### 1.51.0 * First production release after the validated v1.50.0 regression cycle. * Finalized production packaging, installation guidance, rollout guidance, and data-lifecycle documentation. ## Meta * Version **1.57.1** * Last updated **1 day ago** * Active installations **Fewer than 10** * WordPress version ** 6.0 or higher ** * Tested up to **7.1** * PHP version ** 7.4 or higher ** * Tags * [diagnostics](https://wordpress.org/plugins/tags/diagnostics/)[maintenance](https://wordpress.org/plugins/tags/maintenance/) [monitoring](https://wordpress.org/plugins/tags/monitoring/)[site health](https://wordpress.org/plugins/tags/site-health/) [troubleshooting](https://wordpress.org/plugins/tags/troubleshooting/) * [Advanced View](https://wordpress.org/plugins/site-remedy-ai/advanced/) ## Ratings No reviews have been submitted yet. [Your review](https://wordpress.org/support/plugin/site-remedy-ai/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/site-remedy-ai/reviews/) ## Contributors * [ Xpert Developerz ](https://profiles.wordpress.org/xpertdeveloperz/) ## Support Got something to say? Need help? [View support forum](https://wordpress.org/support/plugin/site-remedy-ai/)