AWStats is a server-side web traffic analysis tool that reads data directly from your web server's access log files (Apache or Nginx), unlike JavaScript-based trackers such as Google Analytics which require browser execution. AWStats runs automatically on the server every hour or daily, analyzing and organizing log data without depending on user browsers or JavaScript tracking code. This makes it capable of capturing bot activity, crawlers, and all HTTP requests—even those that block JavaScript trackers. For shared hosting users on DirectAdmin who do not have root SSH access, AWStats is an effective solution to monitor baseline traffic without additional setup or installation.
In short: AWStats reads server logs to record unique visitors, page views, bandwidth, referrers, search keywords, and bot activity without JavaScript. Numbers are typically higher than Google Analytics because bots, crawlers, and all requests are counted, whereas GA only sees real users who load pages with the tracking script.
What is AWStats and How Does It Differ from Google Analytics
AWStats (Advanced Web Statistics) is a Perl-based program running on your server that reads and analyzes the access log file, which records every HTTP request. After processing, AWStats generates organized summary reports. Here are the key differences from Google Analytics:
- Google Analytics Requires JavaScript: You must insert GA tracking code on every page and wait for browsers to load the GA library before counting visits. Users with ad blockers or disabled JavaScript are not tracked by GA.
- AWStats Reads Raw Log Files: Every HTTP request reaching the server (from humans, bots, webhooks, scanners) is automatically recorded in the access log. AWStats simply reads this raw data.
- Bots and Crawlers Are Counted in AWStats: Google bot, Bingbot, Facebook crawler, and malicious scanners all have IP addresses and send HTTP requests that are logged. For example, a blog receiving heavy bot traffic will show much higher "Unique Visitors" in AWStats than in GA because each bot IP is counted as a separate visitor.
- Google Analytics Tracks User Behavior: GA records scroll depth, time on page, event tracking, and link clicks—data that AWStats cannot capture because AWStats only sees that an HTTP request was made, not what the user did after the page loaded.
- Data Delay: AWStats processes log files overnight, so data may lag 1-2 days. Google Analytics is typically real-time or 24-hour delay.
Finding and Accessing AWStats in DirectAdmin
DirectAdmin includes a "Site Summary" or "Statistics" section that lets you choose an analytics tool. AWStats is often the default option, though Webalizer (a simpler alternative) may also be available. Here's how to access it:
- Log into your DirectAdmin Control Panel using your hosting account username and password.
- Look for a menu labeled "Site Summary" or "Your Account," typically shown with a dashboard or graph icon.
- Click "Site Statistics" or "View Statistics" from the left menu.
- If given a choice, select "AWStats" (Webalizer or Analog may be alternatives).
- If your domain is brand new or has no traffic yet, wait 24 hours. AWStats processes logs overnight via a scheduled cron job.
- Once data is available, click "View AWStats" or your domain name to open the full report.
Tip: At some hosts, AWStats may be under "Traffic," "Reports," or "Statistics" menus. If you cannot find it, look for links mentioning log analysis or analytics in the left sidebar. If your account is brand new, AWStats may not have data yet, which is normal. Also check whether your hosting provider has included AWStats in your package; some shared hosting plans may offer only Webalizer.
Understanding the AWStats Dashboard
When you open an AWStats report, you will see a summary page displaying key metrics:
- Unique Visitors: The count of distinct users, identified by IP address, not the total page views.
- Pages Viewed: Total HTTP requests (which may include HTML pages, CSS, JavaScript, images, depending on AWStats configuration).
- Hits: Total number of HTTP requests, equivalent to "Pages Viewed."
- Bandwidth: Total data size (bytes or MB) sent from your server.
- Visit Duration: Average session length (if recorded in logs).
- Top Pages: URL paths that received the most requests. Click "Top Pages" to view the top 20 or 50.
- Top Referrers: External websites that sent traffic to your site (Google, Facebook, Twitter, blogs, etc.).
- Top Search Keywords: Search keywords users entered in Google before clicking to your site (only visible if referrer is a search engine).
- Robots/Spiders: A list of bots and crawlers that visited your site, including request count and bandwidth consumed (e.g., Googlebot, Bingbot, FacebookExternalHit).
Interpreting AWStats Data Correctly and Comparing with Google Analytics
A common mistake is comparing AWStats numbers directly with Google Analytics, because the two tools count different things:
| Factor | AWStats (Server Log) | Google Analytics (JavaScript) |
|---|---|---|
| Bot/Crawler Counting | All bots counted (Googlebot, Bingbot, Facebook crawler, malicious scanners) | Typically not counted (GA filters them by default) |
| Ad Blocker Impact | Not affected (reads log independent of browser) | Visitors with ad blockers are not recorded (JavaScript is blocked) |
| Static File Requests (CSS, JS, images) | Counted as "hits" or "requests" | Not counted (GA tracks page views, not assets) |
| Real-Time Data | Delayed 1-2 days (waits for log processing) | Real-time or 24-hour delay |
| Behavioral Events | None available (only sees page requests) | Available (scroll, click, custom events, goals) |
| User Journey Tracking | Not available (raw log data only) | Available (flow analysis, landing pages, behavior) |
Warning: Never directly compare AWStats "Unique Visitors" with Google Analytics "Users." AWStats will always be significantly higher—sometimes 2 to 10 times higher—because it counts bots, crawlers, health checks, and scanners. A malicious bot scanning for vulnerabilities may even appear as multiple visitors if using different IP addresses. This makes direct comparison meaningless.
How to Interpret Each Section of AWStats Usefully
Unique Visitors vs Pages Viewed
If you see "Unique Visitors: 500" but "Pages Viewed: 2500," it means the average visitor viewed 5 pages (2500 ÷ 500 = 5 pages per visitor). This metric helps gauge basic user engagement without having to rely on JavaScript behavioral data.
Unusual Top Pages
If you notice "/robots.txt," "/wp-admin/," "/admin/," or "/xmlrpc.php" appearing with unusually high request counts, it may indicate a bot or attacker scanning for vulnerabilities or admin panels. Check the request frequency and IP addresses of these requests.
Referrers to Monitor
If you see strange referrers like "http://some-spam-site.ru" or "http://gambling-site.tk" appearing repeatedly, this is likely referrer spam—fake traffic with no real users behind it. While not harmful to your site, it does pollute your AWStats data.
Search Keywords as Insights
If your top search keywords align with your site's topic, you've found genuine user interest. Conversely, if you notice repeated misspelled keywords (e.g., "hostingg" instead of "hosting"), consider writing content targeting those variations to capture additional organic traffic.
Robots/Spiders Section
Check which bots visit most frequently. High traffic from Googlebot or Bingbot is positive (search engines actively crawl your site), but unknown or suspicious bots that consume excessive bandwidth are candidates for blocking.
Blocking Bad Bots and Malicious Scanners via .htaccess
If you identify a bot in the Robots/Spiders section that consumes excessive bandwidth or performs suspicious scans, you can block its IP address or User-Agent string using a .htaccess file (which DirectAdmin allows you to create and edit).
Method 1: Block a Single IP Address
<Files *> order allow,deny deny from 192.168.1.100 allow from all </Files>
Method 2: Block Bots by User-Agent String
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{HTTP_USER_AGENT} ^.*[Ss]pider.*$ [OR]
RewriteCond %{HTTP_USER_AGENT} ^.*[Ss]craper.*$ [OR]
RewriteCond %{HTTP_USER_AGENT} ^.*[Gg]rabber.*$ [OR]
RewriteCond %{HTTP_USER_AGENT} ^MJ12bot.*$
RewriteRule ^.*$ - [F,L]
</IfModule>
Tip: If a .htaccess file does not already exist in your domain's root directory (public_html), you can create one and upload it via FTP or DirectAdmin's File Manager. Always back up your existing .htaccess before making changes, as syntax errors can cause 500 errors on your site. Test changes carefully on a non-critical URL first.
Warning: Do not block legitimate bots like Googlebot or Bingbot. Blocking them prevents Google and Bing from crawling and indexing your pages. Before blocking any bot, verify its identity through Google and Bing's official bot verification documentation to ensure you are not blocking a legitimate crawler.
Privacy and GDPR Considerations Regarding Access Logs
Your server's access log file (which AWStats analyzes) records IP addresses, user agents, HTTP headers, and other visitor information. Under GDPR (Europe) and similar data protection laws (including Thailand's PDPA), IP addresses are classified as "personal data." Therefore:
- Include a Privacy Policy: Inform visitors that you collect and store access logs and state the retention period.
- Set a Retention Window: Do not keep logs indefinitely. A typical retention is 30-90 days, with deletion afterward. High-traffic sites may retain logs for 180 days but must document the business justification.
- Anonymize Sensitive Reports: If sharing AWStats reports with staff or third parties, remove or mask IP addresses (e.g., display "192.168.x.x" instead of the full address).
- Review Your Hosting Provider's Policy: If using shared hosting such as AsiaGB, check their log retention policy and whether they allow you to request log deletion.
- Protect URLs Containing Sensitive Data: Avoid placing tokens, session IDs, or passwords in URLs, as they will be logged in the access log and visible to anyone with access to AWStats.
Summary and Best Practices for Using AWStats
AWStats is a standard, free tool included in most shared hosting packages, including DirectAdmin. It is ideal for users seeking server-side traffic insights without complex setup. AWStats captures bot activity, crawlers, and static file requests that Google Analytics does not see, making it useful for understanding raw traffic patterns and identifying malicious scanning activity. For basic traffic monitoring, AWStats is sufficient. However, if you need to understand real user behavior (scroll depth, time on page, conversion goals), you should use Google Analytics or Matomo alongside AWStats.
In practice, using AWStats and Google Analytics together provides a complete picture: AWStats reveals bot and crawler activity, while GA shows what real users actually do on your site. This guide covers accessing AWStats on DirectAdmin shared hosting, reading the dashboard, and distinguishing legitimate traffic from bots. For further questions or troubleshooting, contact your hosting provider's support team or consult the official AWStats documentation.
Frequently Asked Questions
My AWStats numbers are much higher than Google Analytics. Does this mean my site gets real traffic?
Not necessarily. AWStats counts bots, crawlers, and scanners—often 70–80% of your "Unique Visitors" may be non-human traffic. To gauge real traffic, look at your Google Analytics numbers or examine the "Top Pages" and "Top Referrers" sections to see which pages receive genuine user visits.
Can I delete or reset AWStats data?
AWStats is a server-level tool; shared hosting users typically cannot delete or disable it. Some hosts may allow you to reset the current month's data, but historical data usually cannot be deleted. Contact your hosting support if you need assistance with data management.
Why does AWStats show less mobile traffic than I expect?
AWStats displays all traffic sources. If mobile numbers appear low, the likely cause is that most of your traffic comes from bots and crawlers rather than real mobile users. Check the User-Agent section in AWStats to distinguish between mobile devices and non-human traffic.
Can I import AWStats data into Google Analytics?
Not directly. Google Analytics requires a tracking script installed on your pages to collect data. AWStats is simply a server log report; importing it into GA would require manual processing and is not practical. Instead, use AWStats and GA as complementary tools, viewing each as a separate data source that together provide a fuller picture of your traffic.
Start Your AsiaGB Hosting Today
AsiaGB Hosting runs on SSD storage, managed through the easy-to-use DirectAdmin control panel, with multi-PHP support and 99% uptime — affordable plans backed by a Thai support team.
See Hosting Plans