<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: The Best Free Website Analytics Tools</title>
	<atom:link href="http://www.thedailyanchor.com/2009/01/13/the-best-free-website-analytics-tools/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.thedailyanchor.com/2009/01/13/the-best-free-website-analytics-tools/</link>
	<description>Online Marketing Blog</description>
	<lastBuildDate>Sun, 07 Mar 2010 20:44:23 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jon Combe</title>
		<link>http://www.thedailyanchor.com/2009/01/13/the-best-free-website-analytics-tools/comment-page-1/#comment-1742</link>
		<dc:creator>Jon Combe</dc:creator>
		<pubDate>Thu, 19 Mar 2009 10:20:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.thedailyanchor.com/?p=2375#comment-1742</guid>
		<description>Thanks for the link to my JAWStats project, it is much appreciated.

Your write-up implies JAWStats was created by the people who created AWStats but this is not the case. JAWStats was created purely as a &quot;web2.0&quot; (how I hate that expression) interface for a product that many, many web hosting companies do provide out of the box for their customers. JAWStats wouldn&#039;t exist at all if the AWStats interface was nicer, but it isn&#039;t so I opted to step in.

You should mention that &quot;front end&quot; stats packages (ala Google Analytics, Piwik) and &quot;back end&quot; stats packages (ala AWStats, Woopra, Analog) base their information on fundamentally different data. A webmaster should use one front end system and one back end system in conjunction with each other for the most complete view. Let me know if you want to know more about this.

A good article, Andrew, thank you. It&#039;s really good to see such healthy competition in the analytics market.</description>
		<content:encoded><![CDATA[<p>Thanks for the link to my JAWStats project, it is much appreciated.</p>
<p>Your write-up implies JAWStats was created by the people who created AWStats but this is not the case. JAWStats was created purely as a &#8220;web2.0&#8243; (how I hate that expression) interface for a product that many, many web hosting companies do provide out of the box for their customers. JAWStats wouldn&#8217;t exist at all if the AWStats interface was nicer, but it isn&#8217;t so I opted to step in.</p>
<p>You should mention that &#8220;front end&#8221; stats packages (ala Google Analytics, Piwik) and &#8220;back end&#8221; stats packages (ala AWStats, Woopra, Analog) base their information on fundamentally different data. A webmaster should use one front end system and one back end system in conjunction with each other for the most complete view. Let me know if you want to know more about this.</p>
<p>A good article, Andrew, thank you. It&#8217;s really good to see such healthy competition in the analytics market.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin Lock</title>
		<link>http://www.thedailyanchor.com/2009/01/13/the-best-free-website-analytics-tools/comment-page-1/#comment-420</link>
		<dc:creator>Martin Lock</dc:creator>
		<pubDate>Wed, 28 Jan 2009 07:14:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.thedailyanchor.com/?p=2375#comment-420</guid>
		<description>In the face of the tough competition, Alexa is coming up with more and more user friendly and unique features. Ability to create own search engine by giving access to the crawler is quite a novel feature in itself.</description>
		<content:encoded><![CDATA[<p>In the face of the tough competition, Alexa is coming up with more and more user friendly and unique features. Ability to create own search engine by giving access to the crawler is quite a novel feature in itself.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
