• Insights uses available cPanel access-log, AWStats and bandwidth information.
• Performance history depends on collected monitoring samples.
• Speed score requires the configured Google PageSpeed API key.
• Automatic backups from the server backup integration require JetBackup 5.
• Supported malware scanning and cleanup actions require Imunify360 and appropriate permissions.

1. Confirm the relevant server component is installed, working and available to the test hosting account.
2. Configure any required provider key through the module's protected settings. Restrict and maintain that key according to the provider's supported controls.
3. Enable the relevant product tool and open an active test website.
4. Run a suitable test, such as loading a speed score or requesting a supported scan. Inspect its completion result and safe error details.
5. For historical information, allow monitoring samples to accumulate and verify that later visits show a developing history.
6. Document which plans and servers have the integration, including any limits imposed by its provider.

Server logs and AWStats are operational data sources. Requests, bandwidth and live activity are not automatically unique human visitors or a complete record of every visitor's device. Bots, caching and logging behaviour can affect the numbers.

Country information uses a downloaded geolocation database and should be treated as an estimate. A performance score is a measurement under particular test conditions, not a guaranteed experience for every visitor. Use trends and supporting evidence when investigating a customer's report.

A clean scan is useful but does not prove a website cannot be compromised. If malware is reported, preserve the relevant evidence, check the scope and create an appropriate recovery copy before using a supported cleanup action. Fix the entry point, credentials or vulnerable software as part of the incident response.

Do not repeatedly run cleanup against an unexplained false positive. Compare the report with the website's legitimate files and escalate through your security procedure when necessary.

Check provider credentials, quota, permissions, cron health and the account's eligibility. Distinguish unavailable data from a successful result of zero visits, no threats or no backups. Your customer article should say when a feature depends on the plan or server instead of presenting every optional integration as universal.

• Configure scheduled WordPress maintenance and verify its history
• Define and test the backup scope of managed WordPress plans
• Configure and interpret Hosting Suite site-health monitoring
• Collect useful Hosting Suite diagnostics without exposing credentials

• cPanel: manage WordPress with WP Toolkit