Web Plura Diagnostics is a free admin-only plugin that helps site owners understand:<\/p>\n\n
What it includes:<\/p>\n\n
Fix First<\/code>, Fix Soon<\/code>, Optional Improvements<\/code>)<\/li>\n- Dashboard action center (
Recommended Actions<\/code>)<\/li>\n- WordPress Site Health-style grouped advisor view for critical issues, recommended improvements, checks needing review, and passed tests<\/li>\n
- Beginner vs Advanced Explain Mode (stored in WordPress option)<\/li>\n
- Beginner-friendly
What is this?<\/code> explanations<\/li>\n- Hosting Quality Advisor with score, strengths, weaknesses, improvements, and copyable host-support message<\/li>\n
- Update Safety Advisor (
Safe To Update<\/code>, Backup Recommended Before Updating<\/code>, High Impact Updates<\/code>)<\/li>\n- Recovery Readiness indicator score<\/li>\n
- Lightweight historical change tracking (
Recently Changed<\/code>)<\/li>\n- Settings page for retention policy, visible history count, and scheduled diagnostics scan interval<\/li>\n
- Downloadable diagnostics exports (JSON and CSV)<\/li>\n
- Optional scheduled diagnostics scans via WP-Cron<\/li>\n
- WP-CLI command support for scan\/export\/cleanup workflows<\/li>\n
- Multisite network dashboard surface for cross-site scan visibility<\/li>\n
- Site health, email, performance, plugin impact, hosting, and update-risk modules<\/li>\n
- Expanded local server checks for database version, PHP limits, timezone, URL alignment, cache signals, and key file permissions<\/li>\n
- Plugin\/theme diagnostics for inactive plugins, theme update backlog, commerce plugins, builders, and cache plugins<\/li>\n
- Passive manual email test readiness check based on the last admin-triggered test email result<\/li>\n
- Lead Capture Health module for local form plugin, contact page, SMTP, privacy, and form-plugin update signals<\/li>\n
- WordPress privacy tooling compatibility for test-email metadata<\/li>\n<\/ul>\n\n
Principles:<\/p>\n\n
\n- No cloud requirement<\/li>\n
- No tracking<\/li>\n
- No aggressive popups<\/li>\n
- No frontend impact<\/li>\n
- Admin-only behavior<\/li>\n<\/ul>\n\n
The admin dashboard includes a non-blocking WPlura Cloud benefits notice for automated monitoring and alerts. Free local checks remain available without cloud connection or a paid plan.<\/p>\n\n
Product page: https:\/\/wplura.com\/products\/web-plura-diagnostics\nTerms: https:\/\/wplura.com\/terms\nPrivacy: https:\/\/wplura.com\/privacy<\/p>\n\n
Admin menu counters may show locally cached actionable findings or jobs. Counters are local-only and do not trigger scans, cloud calls, tracking, or paid gating during menu rendering.<\/p>\n\n
Automatic update checks use WordPress.org by default for public packages. Direct\/private WPlura builds may use signed WPlura release manifests; those checks send only the plugin slug, current version, and release channel.<\/p>\n\n
External Services<\/h3>\n\n
This plugin does not require external services for core functionality.<\/p>\n\n
The manual test email feature uses WordPress mail transport (wp_mail<\/code>) configured by your environment.<\/p>\n\nPrivacy<\/h3>\n\n
Web Plura Diagnostics stores local diagnostic cache, explain-mode preference, and local action metadata in WordPress options\/transients.<\/p>\n\n
No user tracking or telemetry is sent by default.<\/p>\n\n\n
\n- Upload the
web-plura-diagnostics<\/code> folder to \/wp-content\/plugins\/<\/code>.<\/li>\n- Activate the plugin through the
Plugins<\/code> menu in WordPress.<\/li>\n- Go to
Web Plura Diagnostics<\/code> in the admin sidebar.<\/li>\n- Click
Run Diagnostics<\/code>.<\/li>\n<\/ol>\n\n\n\nDoes this plugin require a cloud account?<\/h3><\/dt>\nNo. It works locally inside WordPress.<\/p><\/dd>\n
Does it send emails automatically?<\/h3><\/dt>\nNo. It only sends a manual test email when an admin explicitly clicks the button.<\/p><\/dd>\n
Does it perform updates automatically?<\/h3><\/dt>\nNo. It only provides update-safety guidance.<\/p><\/dd>\n
Does it collect telemetry?<\/h3><\/dt>\nNo. It stores local diagnostics cache and limited local metadata only.<\/p><\/dd>\n\n<\/dl>\n\n\n
0.2.6<\/h4>\n\n\n- Improved Diagnostics check presentation so healthy results, findings, review-needed items, and active problems use clearer status-aware labels.<\/li>\n
- Refined Lead Capture Health update-status copy so current form plugins are presented as a professional maintenance result, not as a problem.<\/li>\n
- Added contextual WordPress Help Tabs and shared WPlura admin wrapper support across Diagnostics admin and network views.<\/li>\n
- Added native WordPress heading and header-divider markup to Diagnostics admin views, including the network dashboard.<\/li>\n
- Added WordPress-native postbox foundations to dashboard, settings, export, hosting, updates, and Lead Capture Health panels while preserving existing Diagnostics styling and local-only behavior.<\/li>\n<\/ul>\n\n
0.2.5<\/h4>\n\n\n- Updated the Site Health Advisor page with a WordPress-native grouped presentation for critical issues, recommended improvements, checks needing review, and passed tests.<\/li>\n
- Added accessible expandable check details so admins can scan the summary first and open only the problem, impact, and action guidance they need.<\/li>\n
- Kept the Diagnostics Health Advisor local-only with no cloud sync, tracking, paid gating, or scan work during page rendering.<\/li>\n
- Hardened the WordPress.org-ready package so public builds rely on native WordPress.org updates and helper acceleration uses the configured local socket path only.<\/li>\n<\/ul>\n\n
0.2.4<\/h4>\n\n\n- Added local core\/server diagnostics for database version, upload\/post limits, max execution time, key file permissions, URL alignment, timezone, object cache, and page cache signals.<\/li>\n
- Added passive manual email test readiness reporting based on the last admin-triggered test email result; diagnostics scans do not send email automatically.<\/li>\n
- Added plugin\/theme diagnostics for inactive plugin inventory, theme update backlog, commerce plugin detection, major builder detection, and cache plugin detection.<\/li>\n
- Refreshed diagnostics result cache version so expanded local checks appear after upgrade.<\/li>\n<\/ul>\n\n
0.2.3<\/h4>\n\n\n- Added local-only Lead Capture Health diagnostics for form plugin detection, likely contact\/lead pages, SMTP readiness, privacy policy setup, and form plugin update signals.<\/li>\n
- Added a Lead Capture Health admin page and dashboard module score card.<\/li>\n
- Added a basic local lead capture risk score without submitting forms, collecting leads, calling cloud APIs, or sending telemetry.<\/li>\n
- Refreshed diagnostics result cache version so the new module appears after upgrade.<\/li>\n<\/ul>\n\n
0.2.2<\/h4>\n\n\n- Simplified dashboard microcopy and action labels for faster operator understanding (
Run Scan<\/code>, Save View<\/code>).<\/li>\n- Added a recommendation-driven \u201cWhat To Do Next\u201d priority callout on the main diagnostics surface.<\/li>\n
- Improved dashboard presentation hierarchy with a critical-issues-first summary panel and cleaner module cards.<\/li>\n
- Refined table readability with improved spacing, sticky headers, and zebra row scanning.<\/li>\n
- Added AJAX-based report export downloads (JSON\/CSV) for smoother in-page workflow, while preserving secure nonce\/cookie admin-post handling.<\/li>\n
- Restored Web Plura Diagnostics admin colors to WordPress-default-oriented behavior and removed plugin-forced dark-mode palette overrides.<\/li>\n
- Kept plugin styles scoped to
.web-plura-diagnostics-wrap<\/code> so WordPress admin\/global color scheme behavior remains primary.<\/li>\n- Added forced-colors compatibility handling while preserving
prefers-reduced-motion<\/code> behavior.<\/li>\n- Improved network dashboard status labels and number rendering for translation and locale safety.<\/li>\n
- Added subtle, scoped admin CSS animations across cards, notices, tables, buttons, and score counters for clearer UI feedback.<\/li>\n
- Added
prefers-reduced-motion<\/code> safeguards so motion is automatically reduced for users who prefer minimal animation.<\/li>\n- Added Settings API-based admin settings page for retention, history visibility, and scheduled scan control.<\/li>\n
- Added scheduled diagnostics scan cron workflow with configurable interval.<\/li>\n
- Added diagnostics export actions (JSON and CSV) from WP admin.<\/li>\n
- Added multisite network dashboard for site-level diagnostics status visibility.<\/li>\n
- Added WP-CLI command surface:
wp web-plura-diagnostics scan<\/code>, wp web-plura-diagnostics export<\/code>, wp web-plura-diagnostics cleanup<\/code>.<\/li>\n- Added richer test-email failure details capture from
wp_mail_failed<\/code> for troubleshooting.<\/li>\n<\/ul>\n\n0.2.1<\/h4>\n\n\n- Replaced guidance-only email DNS checks with real local SPF\/DKIM\/DMARC DNS verification attempts.<\/li>\n
- Replaced legacy plugin abandonment guidance with local plugin maintenance backlog signals.<\/li>\n
- Expanded compatibility baseline to broader supported WordPress and PHP versions.<\/li>\n<\/ul>\n\n
0.2.0<\/h4>\n\n\n- Repositioned plugin as WordPress Problem Advisor.<\/li>\n
- Added universal advisor check format (severity, impact, causes, actions, ownership, urgency).<\/li>\n
- Added Why This Matters and Business Impact sections for warning\/critical findings.<\/li>\n
- Added priority queues and action center recommendations.<\/li>\n
- Added Explain Mode (Beginner\/Advanced) persisted in WordPress options.<\/li>\n
- Added hosting advisor score\/strengths\/weaknesses\/recommendations and copyable provider message.<\/li>\n
- Added update safety categories and recovery readiness score.<\/li>\n
- Added lightweight historical diagnostics change tracking.<\/li>\n
- Added dark-mode-aware admin styling via
prefers-color-scheme<\/code>.<\/li>\n<\/ul>\n\n0.1.0<\/h4>\n\n\n- Initial release.<\/li>\n
- Added diagnostics runner with transient caching.<\/li>\n
- Added health, email, performance, plugin impact, hosting, and update-risk modules.<\/li>\n
- Added recommendations page and secure admin actions.<\/li>\n<\/ul>","raw_excerpt":"Business-first diagnostics and prioritized actions for site admins.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/321408","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=321408"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/wplura"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=321408"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=321408"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=321408"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=321408"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=321408"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=321408"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}