Welcome to Mike's Pub -> Tools -> aWebVisit 0.1.6

You will be redirected to the new site for Mike's Pub in a few seconds...



What is aWebVisit ?

It's a Perl5 script that analyses WWW logfiles for visitor information like the :

- most commonly used ENTRY points into the website
- most commonly used EXIT points from the website
- most commonly used TRANSIT points in the website
- most commonly used HIT & RUN points of the website
- most frequently followed internal LINKS
- average DURATION of each visit
- average number of PAGES viewed PER VISIT
- average TIME SPENT on each page
- path of the LONGEST VISIT (in time and/or hits)
- ...

The reports are generated in HTML format for easy viewing (sample reports).

What is aWebVisit-Map ?

It's a companion program for aWebVisit that allows you to walk through your website and examine the links followed by your visitors to and from each web page. Have a look at some sample web maps, or at the real on-line CGI (not always available !).

How much does it cost ?

It's free, as long as you send some feedback !
Well, okay, donations are always welcome too :-)

Help other people find this site

Rate this Script @ The CGI Resource Index!
Script Rating:

Downloading the latest versions

If you want the complete package (.zip file) at once, get it here (70 KB). Note : you still need to download the fly program separately...

aWebVisit 0.1.6b by itself can be downloaded from here (120 KB). It was released on 18/Feb/1999. (version 0.1.6b contains a minor bug fix for version 0.1.6, which was released on 17/Feb/1999.)

Last changes are the configurable exclusion/inclusion of URLs, hosts, entry points (e.g. for robots), partial removal or replacement of URLs, ... And last but not least, the adaptation of the statistics file for use with aWebVisit-Map 0.1.6. You can download the CGI script separately from here (100 KB).

Note : if you have problems downloading this software, please try again first. If the problem remains, please contact me at feedback@mikespub.net with the symptoms and your browser version.

Installation and Configuration

Nothing is easier :
  1. copy awebvisit to any directory
  2. find out where your web server logfiles are located
  3. run 'perl awebvisit <logfile(s)>' (you need perl5, not perl4)
  4. have a look at the HTML output reports : awebvisitf.html
No need to change your pages or webserver (no SSI, CGI, referer log, cookies, ...). If you do not have a command line interface to your webserver (telnet, DOS box, ...), you can either download the logfiles to a local PC/workstation and run aWebVisit there, use some kind of CGI wrapper (coming soon), or ask your webmaster to run it for you...

In order to get the graphical web maps, you'll also need the fly program (free). It's just three little steps :

  1. find out what operating system your webserver is running on - ask your webmaster or hosting company
  2. install the right version of fly (Windows 95/NT, various UNIXes, ...), and
  3. tell aWebVisit where to find it.
You'll see the difference...

If you want to use the companion program aWebVisit-Map, you'll need to configure at least some parameters since it's a CGI program (hint : ask your webmaster to install it for you). Don't worry, it's not very difficult : everything is explained at the beginning of the script. And the results are worth it...

Changing the default settings

You can modify the default configuration of aWebVisit in the script itself, e.g. : And same thing for aWebVisit-Map...

Why use aWebVisit (instead of ...) ?

There are hundreds of logfile analysers in the world, but most of them concentrate on 'basic' statistics like the number of hits per hour, day, week or month, the pages with the most hits, the originating domains etc. For a list of common tools, have a look at DaveCentral or at CGI-Resources for instance.
These tools are great, but something is still missing : how do you know what your visitors are actually DOING on your website ? How do they navigate inside your website : do they just 'hit-and-run', or do they walk through the site as you intended ? Which pages tend to 'put off' your visitors so that they leave your website ?

Getting reliable visitor information has always been tricky. Some tools rely on a specific SSI (server-side include) or CGI for each page to keep track of visits, others use the referer log information, while others work with cookies to keep track of sessions.
All of this is fine, but what of the logfiles you collected in the last few months/years ? And do you even want to change your pages or server for this ? The only non-intrusive way is to use referrer information, which is often standard on webservers, but this does not really work for frames inside your website. And some browsers don't send the referrer, while others might send anything...

So, here we are with aWebVisit and aWebVisit-Map. It's easy, it's free, and it's yours for a try-out. It may not be perfect (especially with AOL), but it'll give you a good idea of what people might do on your website. Just don't forget to send some feedback !
If you're also interested in getting the 'standard' web statistics, try Analog. If you want to find out which search engines led to your website, try Relax. They're free too...

What do the numbers mean ?

Anyone who tells you he can extract 100% reliable 'visit' information directly from webserver logfiles is a liar - or a fool. The only thing a webserver logfile can really tell you is the 'hits' that the webserver saw, but not what people actually did.

So, if aWebVisit tells you that the average time spent on a particular page is 75.1 seconds, this does NOT mean that people actually spent 75.1 (or even 70) seconds on that page on average.

What it does mean is that - for pages where aWebVisit counted a significant number of hits as entry pages and/or transit pages - those people who can be identified by a unique IP address during a visit are probably spending more time on a page with an average of 75.1 seconds than on a page with an average of 49.3 seconds. If they are not all taking a coffee break at that page, that is...

And if aWebVisit tells you that the link from /abc.html to /def.html was followed 14 times, this does NOT mean that 14 people actually followed that link. The link might not even exist, except as random noise in the sequence of webserver hits.

But if the link from /abc.html to /def.html was followed 12514 times, and the link from /abc.html to /ghi.html was followed only 3501 times according to aWebVisit, well, you might consider making that link on page /abc.html a bit more attractive to people. Maybe you'll see a difference next month...

Plans for the future

This is as far as I go on my own. If you want more, give some feedback to feedback@mikespub.net first...

You can have a sneak preview of some of the features that may become part of the next release (if there is sufficient feedback).

About aWebVisit 0.1.6

See the aWebVisit help file...

Would you care to give me some feedback on this ?
It's your last chance...before the end of this page :-)


1