Run A Baseline
Start with local site health, configuration, plugin/theme, environment, and operational signals that can be reviewed safely in wp-admin.
Product docs
Diagnostics Documentation
Use local WordPress diagnostics to review health, configuration, operational findings, and support context before escalating to deeper service work.
Editorial trust
- Publisher
- WPlura Editorial Team
- Updated
- Topics
- Doc, Product Documentation
- Verified sources
- 1 references
Problem, cause, fix, verify
Problem
Diagnostics should organize evidence and next steps without claiming to fix hosting, security, commerce, or deliverability problems automatically.
Why it matters
Diagnostics is an evidence-gathering workflow, not an automated repair guarantee.
Safe check
Install Web Plura Diagnostics on the WordPress site you want to review.
Verify
Use Fix First ordering and support summaries to separate urgent issues from routine improvements.
On this page
Scope
Diagnostics should organize evidence and next steps without claiming to fix hosting, security, commerce, or deliverability problems automatically.
For: Site owners, agencies, and support teams who need a repeatable first-pass diagnostic routine.
- Diagnostics is an evidence-gathering workflow, not an automated repair guarantee.
- Avoid publishing private environment details in public pages or shared reports.
- Use product-specific docs when a finding belongs to security, backups, commerce, or search visibility.
Quick Start
Set up the workflow in a safe order
- Step 1
Install Web Plura Diagnostics on the WordPress site you want to review.
- Step 2
Run a local diagnostics baseline from wp-admin.
- Step 3
Read the Fix First items before lower-priority improvements.
- Step 4
Export or share support-safe context when a host, developer, or agency needs evidence.
- Step 5
Escalate security, backup, checkout, catalog, or discovery findings to the matching WPlura product workflow.
Workflow
Setup and operating notes
Share Support Context
Use summaries and exports to help support teams understand symptoms, environment details, and likely next checks.
Escalate By Domain
Move security, backup, checkout, email, catalog, or search-discovery questions into the product built for that workflow.
Tutorials
Detailed product walkthroughs
Run a first-pass WordPress health review
FreeUse Diagnostics to separate urgent site-health signals from general improvement ideas.
- 1Open Diagnostics and run the local review.
- 2Start with urgent findings around environment, updates, email readiness, REST, cron, and operational signals.
- 3Read the explanation for each issue before changing settings.
- 4Export the support context when another team owns the next action.
- 5Rerun the review after changes to confirm the evidence changed.
Prepare a support handoff without leaking private details
FreeTurn site symptoms into a useful summary while keeping sensitive environment details controlled.
- 1Record the symptom, affected workflow, and when it started.
- 2Use Diagnostics to collect relevant local context.
- 3Remove secrets, private customer data, and raw stack traces before sharing.
- 4Send the support-safe summary to the host, developer, or product owner.
- 5Keep the final fix note with the site maintenance record.
Guides
How to use this documentation
Agency maintenance guide
Diagnostics fits well as the first pass before monthly care-plan work, launch checks, or support escalation.
Open related guidePre-launch diagnostics
Use Diagnostics before launch to check operational readiness beyond page design.
Open related guideCommon Problems
Issues this product helps organize
Site Health warnings feel confusing
Symptom: WordPress reports multiple warnings but the owner cannot tell what matters first.
Resolution: Use Fix First ordering and support summaries to separate urgent issues from routine improvements.
Email or forms appear unreliable
Symptom: Users report missing messages but the site looks normal.
Resolution: Review mail readiness and related operational findings before changing forms or SMTP settings.
Open related problemA developer needs context before debugging
Symptom: Support asks for environment details and recent changes.
Resolution: Use a diagnostics export or summary, then remove anything sensitive before sharing.
FAQ
Answers before installation or escalation
Does Diagnostics fix issues automatically?
No. Diagnostics organizes findings and next steps; administrators still choose and apply the fix.
Does it require a paid account?
Current Diagnostics behavior is local-first and does not require a cloud account.
Can agencies use it for client review?
Yes. It is useful for a first-pass site review and support handoff before deeper product-specific work.
Should raw diagnostics be public?
No. Keep private environment details, secrets, customer data, and stack traces out of public pages or support channels.
Free vs Pro
Capability boundaries
Free
Local site health guidance, priority review, and support context are the Diagnostics baseline.
Pro
Do not describe product-specific repairs or hosted automation as Diagnostics Pro unless a verified Pro source supports it.
Cloud
Escalate to product-specific cloud workflows only where the matching product and connector verify that behavior.
Planned
Avoid presenting future diagnostics automation, monitoring, or repair as available.
Verified Sources
Where these claims come from
Continue