Read the evidence before changing anything
Each useful finding should be interpreted in context: what was detected, why it matters, how confident the signal is and what the recommended next step actually asks you to review. Do not treat every notice as a reason to install another plugin or make an immediate database change.
A practical order for fixing issues
- Confirmed breakage or exposure: broken internal destinations, clearly unsafe production settings or failed compatibility requirements deserve attention first.
- Operational problems: overdue cron work, update problems, cache conflicts, excessive autoload or other maintenance issues can affect reliability and speed.
- Content architecture: duplicate or near-duplicate pages, weak internal linking and possible orphan candidates should be reviewed with editorial context before consolidation.
- Informational observations: useful context may require no action at all.
Common finding types
Plugin overlap
Two plugins appearing to cover the same responsibility is a review signal, not proof that one must be removed. Confirm which features are enabled before deactivating anything.
Broken or redirected internal links
Open the source and destination manually. If a URL is genuinely broken, correct the internal link or restore the intended destination. For redirect chains, link directly to the final canonical destination when practical.
Database and maintenance findings
Back up the database before deleting rows, revisions, transients or plugin data. If you do not know which plugin owns a table or option, identify it first rather than cleaning by size alone.
Security posture
A missing hardening signal is not automatically evidence of compromise. Review the finding against your host, reverse proxy, CDN and security-plugin setup. Some headers or controls may be implemented outside WordPress.
Performance findings
Do not stack multiple cache/minification systems just to clear a warning. Confirm which layer owns page cache, object cache, CDN behavior and frontend optimization, then avoid duplicated responsibilities.
Content and orphan candidates
A page that appears weakly connected in the stored content graph may still be reachable through templates, dynamic navigation or other generated elements. Review before deleting, redirecting or merging it.
After a fix
Clear only the caches relevant to the change, test the site as a visitor, confirm important forms and checkout flows still work, then rerun TopNotch Site Health to see whether the evidence changed. Avoid making ten unrelated changes at once; smaller batches make regressions easier to identify.
When not to fix a finding
If the evidence is informational, context-dependent or already handled correctly at the server/CDN layer, leaving it unchanged can be the right decision. The goal is a healthier site, not a cosmetically perfect report.
For technical problems that persist, use the FAQ & Troubleshooting guide.