Web Plura Diagnostics – Site Health, Email & Update Readiness
Web Plura Diagnostics – Site Health, Email & Update Readiness
Description
Web Plura Diagnostics helps WordPress site owners, agencies, and support teams find problems that quietly hurt leads, sales, trust, and maintenance time. It runs inside wp-admin and turns local site signals into clear, prioritized action items.
Use it when you need to answer practical questions before an update, launch, client handoff, or support call:
- Are forms, password resets, store emails, and lead notifications likely to work?
- Is the site showing health, hosting, cache, cron, or PHP warning signs?
- Which plugin, theme, or update risks should be checked before making changes?
- What should a business owner, developer, host, or support team fix first?
- What can be exported or shared without sending diagnostics to an external service?
For every finding, the plugin focuses on:
- What is wrong
- Why it matters
- What business impact it may cause
- Who should fix it
- What to fix first
No external account, no tracking, and no frontend scripts are required for the core diagnostics workflow.
No external service requirement: core diagnostics, dashboard rendering, exports, and scheduled scans run locally in WordPress.
No tracking by default: diagnostics scans do not send telemetry or site diagnostics to Web Plura unless a site administrator enables optional telemetry categories in settings.
Free local checks remain available without an external account.
Customer Problems It Helps Solve
- Missed leads from broken contact forms, weak email setup, or untested notification paths.
- Risky updates when a site has stale plugins, inactive code, commerce dependencies, or no clear pre-update checklist.
- Slow or unstable sites caused by cache gaps, low memory, cron pressure, upload limits, or hosting constraints.
- Confusing support handoffs where clients, developers, and hosts need the same problem summary.
- Reactive maintenance where issues are discovered only after checkout, login, email, or lead capture fails.
Key Checks
- Fix First dashboard with score, priority groups, recommended actions, and recent-change history.
- Site Health-style checks for WordPress, database version, PHP limits, timezone, URL alignment, cache signals, and key file permissions.
- Email readiness checks for local mail transport, SPF, DKIM, DMARC, domain alignment, manual admin-triggered test email results, and optional bounded metadata-only test history. Diagnostics scans do not send email automatically.
- Lead Capture Health checks for form plugins, contact pages, SMTP readiness, privacy-page status, and form-plugin updates.
- Pre-update Safety checks for inactive plugins, theme update backlog, commerce plugins, builders, and cache plugins.
- Hosting Advisor checks for memory, cache, cron pressure, upload limits, execution limits, and host-support guidance.
- Cron & Background Jobs checks for WP-Cron configuration, overdue events, orphaned callbacks, repeated hooks, Action Scheduler presence, and WooCommerce queue backlog signals.
- Front-end Response checks for home URL HTTPS, response code, redirect signal, cache-control, compression header, and REST API response.
- Support-safe diagnostics snapshot with redacted environment, module scores, and top findings for support handoffs.
- Client-ready diagnostics with problem, impact, owner, urgency, next action, JSON/CSV exports, WP-CLI commands, and multisite network visibility.
Good Fit For
- Site owners who want a clear first-pass health, email, performance, and update-readiness review.
- Agencies preparing client reports, maintenance checks, launch reviews, or pre-update safety notes.
- Support teams collecting safe local diagnostics before deeper troubleshooting.
- WordPress admins who want prioritized actions without telemetry or a required external account.
Product page: https://wplura.com/products/web-plura-diagnostics
Terms: https://wplura.com/terms
Privacy: https://wplura.com/privacy
External Services
Web Plura Diagnostics is local-first. Diagnostics scans, dashboard rendering, exports, and scheduled scans run inside WordPress by default.
Optional telemetry can be enabled by a site administrator from the plugin settings. It is disabled by default and is not required for local diagnostics. When enabled, the plugin may send selected categories to Web Plura at https://api.wplura.com/v1/plugin/telemetry/events:
- Usage analytics: plugin lifecycle events such as activation, deactivation, update observation, and health snapshot events.
- Error diagnostics: sanitized Web Plura Diagnostics error category, severity, component, message code, and fingerprint.
- Environment diagnostics: coarse WordPress version, PHP version, plugin version, multisite state, and locale.
The recipient is Web Plura. The data is used to understand plugin reliability, compatibility, and consented diagnostic health signals. The plugin does not send passwords, API secrets, JWTs, authentication headers, email content, customer records, payment information, raw request bodies, full file paths, raw stack traces, or unrelated personal information. Consent can be withdrawn later from the plugin settings, and local diagnostics continue working when telemetry is disabled or unavailable.
The plugin links to Web Plura product, terms, and privacy pages for support and product information:
- Product page: https://wplura.com/products/web-plura-diagnostics
- Terms: https://wplura.com/terms
- Privacy: https://wplura.com/privacy
The public WordPress.org package uses WordPress.org update checks.
Data, retention, and uninstall behavior:
- Diagnostics results, history snapshots, explain-mode preference, scheduled-scan settings, export metadata, and manual test-email metadata are stored locally in WordPress options/transients.
- Retention settings allow site admins to control how long local diagnostic history and email-test metadata are kept.
- Uninstall cleanup removes plugin-owned options, transients, scheduled scan hooks, and local diagnostic metadata.
Installation
- Upload the
web-plura-diagnosticsfolder to/wp-content/plugins/. - Activate the plugin through the
Pluginsmenu in WordPress. - Go to
Web Plura Diagnosticsin the admin sidebar. - Click
Run Diagnostics.
Screenshots

Main dashboard showing site score, risk level, and Fix First issues.

Business-friendly diagnostics with problem, impact, owner, and next action.

Email Delivery Readiness for forms, password resets, and store emails.

Lead Capture Health for contact forms and silent lead-loss risks.

Hosting Advisor with copyable message for hosting support.

Cron, front-end response, and support handoff views for scheduled-job pressure, HTTP response signals, and redacted diagnostics snapshots.
Faq
It is for WordPress site owners, agencies, support teams, and administrators who need a local health, email, performance, hosting, and update-readiness review before deeper troubleshooting.
It focuses on practical operational problems: missed form leads, unreliable WordPress email, risky updates, weak hosting readiness, slow or unstable sites, unclear fix priorities, and support handoffs that need a client-readable summary.
No. It works locally inside WordPress.
No frontend scripts or frontend monitoring are added by default. Diagnostics run inside wp-admin, scheduled scans are optional, and the plugin does not automatically change public content.
No. The free plugin is local-first and does not send diagnostics, logs, or telemetry to an external server by default.
No. It provides local diagnostic insights and prioritized guidance. Use a dedicated firewall, malware response process, and backup/restore system where those protections are required.
Diagnostics focuses on broad site health, email readiness, hosting, performance, update risk, and support handoff snapshots. Operation Guard focuses on operational workflow readiness such as forms, lead capture, digital products, marketplace signals, cron/REST/site systems, update readiness, and manual Flow Contracts.
No. It only sends a manual test email when an admin explicitly clicks the button.
No. It only provides update-safety guidance.
Yes. It includes a multisite network dashboard surface for cross-site diagnostics visibility. Individual site access still follows WordPress capability checks.
Yes. Admins can use wp web-plura-diagnostics scan, wp web-plura-diagnostics export, and wp web-plura-diagnostics cleanup for local operational workflows.
Yes. WordPress Site Health can show a cached Web Plura Diagnostics score after diagnostics have run. The Site Health test reads cached local results and does not start a fresh scan.
No telemetry is collected or sent by default. A site administrator may optionally enable usage analytics, error diagnostics, or environment diagnostics in settings. Local diagnostics continue working if every telemetry option remains off.
The plugin removes plugin-owned options, transients, scheduled scan hooks, local diagnostic history, and local action metadata during uninstall.
Use the WordPress.org support forum, or visit https://wplura.com/products/web-plura-diagnostics.
Reviews
Changelog
0.3.7
- Fixed first-time telemetry opt-in so the consent event queues only after an administrator enables that category.
0.3.6
- Made the Upgrade comparison readable on narrow screens without horizontal scrolling.
0.3.5
- Added a Free-owned settings cloud delivery extension surface with contextual upsell fallback.
0.3.4
- Added a Free-owned recommendations cloud intelligence extension surface with local fallback rendering.
0.3.3
- Added a Free-owned dashboard action guidance extension surface with local fallback rendering.
0.3.1
- Hardened local report exports with sanitized JSON and CSV payloads, support-safe metadata, and redaction for URLs and email addresses.
- Added localized export status messages and refreshed the free-plugin feature summary for the current local diagnostics scope.
0.3.0
- Added read-only Cron & Background Jobs diagnostics.
- Added Front-end Response diagnostics for home URL, REST API, cache, compression, and redirect signals.
- Added optional metadata-only manual email test history and a redacted support snapshot export.
- Added plugin-conflict risk guidance without automated plugin deactivation.
0.2.9
- Improved the WordPress.org title, tags, and problem-focused readme copy for site health, email, performance, hosting, update risk, and lead capture diagnostics.
- Kept the public package local-first with no external service requirement for diagnostics, exports, and scheduled scans.
0.2.8
- Updated the WordPress.org release package with the current local diagnostics admin UI, assets, uninstall cleanup, and readme metadata.
- Kept diagnostics local-first with no telemetry or required external account for core checks.
0.2.7
- Improved dashboard Recommended Actions with ordered action rows, priority badges, source context, and module links.
- Improved dashboard Recently Changed history with a compact timeline and previous/current value chips.
- Kept the public package local-first and streamlined the admin workflow.
0.2.6
- Improved WordPress.org listing copy, screenshots, Site Health integration, scheduled scans, retention cleanup, email dependency checks, cache checks, OPcache readiness, exports, and admin UI clarity.
Earlier releases
- Added the local diagnostics runner, health checks, email checks, performance checks, plugin impact checks, hosting checks, lead capture checks, update-risk checks, recommendations, exports, WP-CLI commands, scheduled scans, and WordPress-native admin UI improvements.