Forum Moderators: DixonJones
The new server is Apache/Plesk/Unix.
The problem is that the log files have the referrer string in the 'wrong' location. In previous log files the referrer string was a the end of the entry - with the new ones it appears before the 'server status code' and 'bytes transferred' figures.
This is preventing Webalizer or any of my other log file analysis software from providing referrer info.
Q. Does anyone know if there is an easy fix for this? (We have 100+ sites to transfer over, so a 'one time' fix would be nice rather than 100 separate fixes!)
The other solution I considered is Traxis, which I have installed on one of our sites.
Q. I would have to use .shtm to run SSI with our server - is this still a problem with search engines, or are they OK now?
Q. Am I right in assuming that Traxis can be used to measure stats on different domains on the same server? My server 'expert' said that allowing the other domains to call the counter.cgi as an SSI was a security risk, is this right, or would I have to install multiple instances of Traxis.
(Brett - when you release Traxis as a commercial package, you have one customer here for sure !)
You log software should be configurable to interp the log format. FastStats, Webtrends, and Analog can all be configured for that.
..and I guess any feedback on the shtml ranking issues would be appreciated.
I have Faststats and it cannot be congigured with these logs - their support is all about re-configuring my server to produce logs that are acceptable - not an easy option for me, unfortunately.
I have read a couple of comments here and there (sorry didn't try to locate) that .shtml is not the best for SEO.
However, you can configure your server to handle .html, and/or .htm as .shtml if you like.
Instructions here [webmasterworld.com].
I have read that shtml was bad for SEO - but also read contradictory info on another forum - thought perhaps it was OK now.
Will try the htaccess solution and see whether the server can take the strain.
