Updated: 15 November 2026 · Applies to: DirectAdmin servers with Webalizer; Webalizer 2.23-08 tested
DirectAdmin runs Webalizer with its built-in defaults. To change what the reports show, an admin creates one custom file, /usr/local/directadmin/data/templates/custom/webalizer.conf, and DirectAdmin uses it for every domain on the server from the next statistics run. This is a server admin (root) task; on shared hosting, ask your provider.
Step 1: create the custom file
Log in to the server as root over SSH and open the file in an editor:
nano /usr/local/directadmin/data/templates/custom/webalizer.conf
According to DirectAdmin, the file must be domain independent, because the same file is used for all domains without changes. So put only options that make sense for every site in it, never a domain name or a per-domain path.
Step 2: add the options you want
A practical starting point, tested with Webalizer 2.23-08:
TopSites 10 TopURLs 20 TopReferrers 20 TopCountries 30 HideURL *.css HideURL *.js HideURL *.woff2 IgnoreSite 192.0.2.10 HTMLHead <meta name="robots" content="noindex, nofollow">
What the common options do:
TopSites,TopURLs,TopReferrers,TopAgents,TopCountries,TopSearch: how many rows each top table shows.AllSites yes,AllSearchStr yes: add an extra page that lists every entry, not just the top ones.HideURL,HideSite,HideReferrer,HideAgent: keep matching entries out of the top tables, but still count them in the totals. Use these for images, style sheets and fonts that crowd out real pages.IgnoreSite,IgnoreURL,IgnoreReferrer,IgnoreAgent: drop matching records completely, as if they were never in the log, so they are not counted at all. Use these for your own office IP or a monitoring service.GroupURL,GroupSite,GroupReferrer: combine matching entries into one line with an optional label, for exampleGroupURL /blog/* Blog.PageType: which file extensions count as pages (for examplephpandhtm*).HTMLHead: a line added to the head of every report page, useful for a noindex tag.
Match values may use a leading or trailing *. Without a wildcard, Webalizer matches the value anywhere in the string.
Optional: country lookups through reverse DNS
DirectAdmin's documentation gives an example that turns on reverse IP lookups with a DNS cache per domain, using the |DOMAIN| token, which DirectAdmin replaces with each domain name:
DNSCache /var/lib/webalizer/|DOMAIN|.dns_cache.db DNSChildren 10
The cache folder needs these permissions, according to DirectAdmin:
chown root:root /var/lib/webalizer chmod 1777 /var/lib/webalizer
Reverse lookups make each statistics run slower, so test on a quiet server first.
Step 3: rebuild the statistics
The new settings apply at the next run. To rebuild one account now, DirectAdmin recommends queuing a tally (replace USERNAME):
echo "action=tally&value=USERNAME&type=user" >> /usr/local/directadmin/data/task.queue
To test a configuration on one domain by hand first, run Webalizer directly with your file (replace USERNAME and example.com):
webalizer -c /usr/local/directadmin/data/templates/custom/webalizer.conf -p -n example.com -o /home/USERNAME/domains/example.com/stats /var/log/httpd/domains/example.com.log
In our lab test, an IgnoreSite line removed that visitor from the totals, and Webalizer reported it at the end of the run:
4 records (1 ignored) in 1 seconds, 4/sec
Related
- Make the reports viewable in a browser: How to allow webalizer stats to be viewable through the web in DirectAdmin?
- Reading the reports: How do I read my web stats on Webalizer?
- Prefer AWStats? See I want to have the DirectAdmin version of Awstats.
Official documentation: DirectAdmin, website statistics.