Confirm the domain you want to analyse and the reporting period. Statistics must be enabled on the server, and recently added domains may need a scheduled processing cycle before meaningful history appears.

1. Open Statistics > AWStats in SiteWorx and select the intended domain or available report.
2. Check the displayed month, year and last-update time before interpreting a sudden rise or fall.
3. Compare visits and pages with hits and bandwidth. One page can request many assets, so a high hit count is not the same as that many people visiting.
4. Review the most requested URLs, status codes, referrers and robot activity to understand the source of traffic.
5. For a specific incident, compare the report with current or archived access logs and the relevant application or CDN analytics. Export or record the useful period before retention removes older data.

If the origin records one HTML request plus a stylesheet and two image requests, that page load contributes four recorded requests. It does not prove that four people visited. Compare the report's visits and pages separately, then inspect robot activity and the reporting period before attributing a higher hit count to audience growth.

A plausible report should correspond to the correct domain and time window. Use it to identify patterns and questions, then confirm individual errors or unusual requests in logs.

If the report is empty or stale, check whether requests reached this origin and whether statistics processing is enabled. CDN-served cache hits may not reach the origin at all. Ask support about processing failures rather than deleting statistics directories or forcing repeated jobs.

• Where did Webalizer go after an InterWorx upgrade?
• Creating and downloading a full SiteWorx backup
• Checking whether Cloudflare is active for a hostname
• Changing a SiteWorx FTP user password

• InterWorx documentation