Skip to content

TopNotch Site Health FAQ & Troubleshooting

Installation problems

WordPress says the plugin could not be installed

Confirm you uploaded the original ZIP file, not an extracted folder or nested ZIP. Also confirm your WordPress user can install plugins and that the host allows plugin uploads.

“Destination folder already exists”

An older copy may already be installed. Check Plugins → Installed Plugins. If an existing TopNotch Site Health installation is active, use the normal update process where possible instead of deleting it blindly.

License problems

The license will not activate

Check that the full key was copied without extra spaces, the site has outbound HTTPS access and the plan still has an available activation slot. If the license was previously used on another site, deactivate that site first.

The site count is full

Deactivate a site you no longer use. If a migration or cloned staging site consumed a slot, remove the obsolete activation before trying again.

Private updates are not enabled

Confirm the license shows Active. Then go to Dashboard → Updates → Check again. If it still fails, check firewall, security-plugin or host rules that might block outbound requests.

Audit problems

The audit is slow

Large sites, constrained hosting, large databases and live URL checks can increase run time. Keep the admin tab open and avoid starting multiple runs.

The audit times out

Check PHP memory and execution-time limits, recent server error logs and whether a security layer is terminating long admin requests. Do not disable unrelated plugins at random. Make one controlled change at a time and rerun.

A finding looks wrong

Review the evidence and the layer where the setting may actually be implemented. Caching, security headers and redirects can be handled by WordPress, a plugin, the web server, reverse proxy or CDN. A WordPress-level observation may therefore need contextual review.

Fixing problems safely

Back up the site before database cleanup, redirect changes, plugin removal or configuration edits. Test important pages, forms and checkout flows after each meaningful change. Do not aim to remove every informational notice simply to raise the score.

Still stuck?

Use the support checklist. Include the exact error, what you were doing when it happened and the relevant environment details. Do not send passwords or complete license keys.