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.
FAQ
Who is Web Plura Diagnostics for?
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.
What customer problems does it focus on?
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.
Does this plugin require an external account?
No. It works locally inside WordPress.
Will this slow down my website?
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.
Does this send my site data to Web Plura?
No. The free plugin is local-first and does not send diagnostics, logs, or telemetry to an external server by default.
Does it replace a firewall, malware scanner, or backup plugin?
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.
How is this different from Web Plura Operation Guard?
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.
Does it send emails automatically?
No. It only sends a manual test email when an admin explicitly clicks the button.
Does it perform updates automatically?
No. It only provides update-safety guidance.
Does it support Multisite?
Yes. It includes a multisite network dashboard surface for cross-site diagnostics visibility. Individual site access still follows WordPress capability checks.
Does it include WP-CLI support?
Yes. Admins can use wp web-plura-diagnostics scan, wp web-plura-diagnostics export, and wp web-plura-diagnostics cleanup for local operational workflows.
Does it integrate with WordPress Site Health?
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.
Does it collect telemetry?
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.
What data is removed on uninstall?
The plugin removes plugin-owned options, transients, scheduled scan hooks, local diagnostic history, and local action metadata during uninstall.
Where can I get support or product information?
Use the WordPress.org support forum, or visit https://wplura.com/products/web-plura-diagnostics.
Screenshots
Changelog
0.3.69
- Open New Dashboard by default, retain later Legacy choices, and align Free submenu presentation.
0.3.68
- Associated the three General Settings number and interval fields with their visible WordPress settings labels.
0.3.67
- Made New Dashboard workflow errors clearer and accessible while preserving existing checks and actions.
0.3.66
- Unified Settings navigation and reused the shared section-tab style where existing plugin pages use WordPress tabs. Routes, settings, data, and actions are unchanged.
0.3.65
- Standardized New Dashboard tabs as a consistent, keyboard-accessible horizontal strip across desktop and mobile. Dashboard data and actions are unchanged.
0.3.64
Embedded telemetry reporting in Settings with a bounded local delivery history, seven-day chart, and event details.
0.3.63
- Added a shared Web Plura Settings page with consent, telemetry data, and error reporting details, plus a WordPress.org plugin directory on About. Existing consent and local features remain unchanged.
0.3.62
- Refined New Dashboard links, tabs, buttons, table colors, and responsive presentation. Moved the review request to a dismissible admin notice.
0.3.61
- Kept the New Dashboard review button readable under alternate WordPress admin color schemes.
0.3.60
- Kept investigation area labels readable across New Dashboard widths.
0.3.59
- Kept investigation area labels readable in the New Dashboard mobile table.
0.3.58
- Kept compact New Dashboard donut values readable through the chart inspector without clipped labels.
- Improved the expanded New Dashboard check tables on narrow screens with clear horizontal scrolling.
0.3.57
- Improved New Dashboard KPI readability on narrow screens.
0.3.56
Kept a WordPress.org review link available in both dashboard views.
0.3.55
- Rebuilt the five-tab New Dashboard around real local health, issue, activity, and workflow data using a responsive mockup-inspired layout. The Old Dashboard remains unchanged.
0.3.54
- Restored New Dashboard action feedback, Priority Group details, and investigation change leads using existing local data. The Old Dashboard remains unchanged.
0.3.53
- Added more of the existing local diagnostic detail to the New Dashboard, including area counts, next-action context, and check-level findings. The Old Dashboard remains available.
0.3.52
- Short recorded signal and update comparisons now use columns; hosting strengths and weaknesses use a part-to-whole donut. Module score ranking remains horizontal for readable labels. Data, actions, Pro extensions, and Old Dashboard are unchanged.
0.3.51
- Refined New Dashboard card layout for available content width, preserving recorded values and Old Dashboard behavior.
0.3.50
- Added responsive New Dashboard column layouts with alternating graph widths and a compact featured insight.
0.3.49
- Made the New Dashboard score cards compact with current-value progress, and arranged update, hosting, investigation, and module-status graphs in an even two-column layout. The original dashboard and stored data are unchanged.
0.3.48
- Organized Diagnostics New Dashboard comparisons into a wide update chart and two side-by-side hosting and investigation charts. Chart cards now hold the relevant guidance and detail links without repeating the prior count cards.
0.3.47
- Added current-scan comparison charts for update readiness, investigation signals, and hosting findings on the New Dashboard. The original dashboard and stored data are unchanged.
0.3.46
- Added keyboard-accessible inspection of exact recorded chart values in the New Dashboard; the original dashboard and stored data are unchanged.
0.3.45
- The New Dashboard highlights an existing product workflow as its primary action, while retaining the original dashboard and its data.
0.3.44
- Added a shared, optional telemetry consent screen with explicit accept and decline choices and a session-scoped admin invitation. Local features remain available without consent.
0.3.43
- Optional telemetry now sends only documented event properties after administrator consent. Local features remain available with telemetry off.
0.3.42
- The new dashboard Overview groups four KPIs, a real-data featured ECharts chart, priorities, status, and operational context. The original dashboard is unchanged.
0.3.41
- The new dashboard now shows a link-style “Switch to Old” control matching the existing “Switch to New” control.
0.3.40
- New-dashboard tabs now honor section links and browser history while retaining keyboard navigation and activity pagination.
0.3.39
- The new dashboard now explains when a trend needs another retained result and shows an honest empty Workflows state when no task or page is available.
0.3.38
- The new dashboard now shows clear section-specific messages for missing results and history while preserving real zero values and chart data alternatives.
0.3.37
- Added shared, page-scoped About and Upgrade presentation across the Free plugins while preserving product-specific content and routes.
0.3.36
- Added bounded priority, hosting, update, investigation, and failure-signal detail tables to the new dashboard.
- Kept the original dashboard unchanged and improved the shared mobile workflow layout.
0.3.33
- Updated the new dashboard score chart to an accessible semicircle gauge using existing local scores.
0.3.32
- Added a per-user Old/New dashboard switch with one visible Dashboard menu entry and refreshed the new dashboard header.
0.3.23
- Improved dashboard text contrast under WordPress Midnight admin colors; existing local features and actions remain available.
0.3.22
- Refreshed the local dashboard score-card layout while retaining existing checks, actions, and a legacy display fallback.
- Scoped the new dashboard styling to Diagnostics when other Web Plura plugins are active.
0.3.21
- Kept empty check-table guidance visible on narrow screens and clarified the empty Recommendations message.
0.3.20
- Removed a duplicate network dashboard display and made its status table keyboard scrollable on narrow screens.
0.3.19
- Improved the Site Health summary layout on narrow screens so the final count fills its row.
- Kept the Performance check page focused on local findings; service comparison remains on the Upgrade page.
0.3.18
- Made the About features table keyboard scrollable on narrow screens with visible guidance to its later columns.
0.3.17
- Made the existing narrow-screen checks tables keyboard scrollable and added visible guidance for reaching findings and actions in later columns.
0.3.16
- Grouped local investigation findings for easier review and added keyboard-accessible disclosure for nearby change leads. Diagnostic data and actions are unchanged.
0.3.15
- Clarified the local risk summary and next action, added readable score bars for nine diagnostic areas, and improved Scan and Priority Queue navigation.
0.3.14
- Keeps prior finding occurrences for 30 days, within the existing 30-row local limit, when a finding returns. Each occurrence retains its own incident ID and scan verification history.
0.3.13
- Added repeat-scan absence verification, recent finding details, and bounded local investigation metadata to the administrator JSON report. A clean scan does not confirm a cause or resolution.
0.3.12
- Added off-by-default, local JavaScript error counts for signed-in administrator browsing. Only coarse runtime and unhandled-promise categories are kept; messages, URLs, form values, and stacks are excluded.
0.3.11
- Added bounded local REST and AJAX server-failure counts to the conflict investigation view. Request paths, action names, and response content are not stored.
0.3.10
- Added scan-time WordPress core, active theme, and plugin activation change leads to the local conflict investigation view.
0.3.9
- Added bounded local PHP fatal-error signals to the conflict investigation view without storing messages or file paths.
0.3.8
- Added a local, bounded conflict investigation summary that groups scan findings and shows nearby plugin changes as leads to verify.
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.




