<?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: More on afr.com &#8211; a quick traffic analysis</title>
	<atom:link href="http://www.lawfont.com/2007/06/18/more-on-afrcom-a-quick-traffic-analysis/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.lawfont.com/2007/06/18/more-on-afrcom-a-quick-traffic-analysis/</link>
	<description>an analysis of law, technology, economics, and policy</description>
	<lastBuildDate>Thu, 29 Dec 2011 19:59:43 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: David Nachman</title>
		<link>http://www.lawfont.com/2007/06/18/more-on-afrcom-a-quick-traffic-analysis/comment-page-1/#comment-55709</link>
		<dc:creator>David Nachman</dc:creator>
		<pubDate>Thu, 28 Jun 2007 21:26:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.lawfont.com/2007/06/18/more-on-afrcom-a-quick-traffic-analysis/#comment-55709</guid>
		<description>Ben, sorry to contradict you but you have made a bit of a stuff up here, although in fairness you allude to the problem with Alexa yourself.
Firstly, the decline in afr.com pages coincides with the launch of afraccess. You have tracked the wrong site so what you are really seeing is the migration of traffic from one site to the other. Secondly and more importantly, alexa can not track afraccess (which in April this year effectively replaced AFR.com) because it can&#039;t track flex. So if you track afraccess on Alexa all its measures its the home page. It doesn&#039;t measure the page impressions inside the application where most of the activity is generated. In fact if you go to the alexa link you mention, click on the link to afr.com on Alexa and look at the AFR.com thumbnail you will see the evidence for yourself.
Finally if you&#039;re so concerned about what&#039;s been happening to traffic its very easy to find out. afr.com (afraccess) is tracked by Nielsens, which all of us in advertising land have access to. Its traffic has been growing very strongly and consistently now for 6 months.</description>
		<content:encoded><![CDATA[<p>Ben, sorry to contradict you but you have made a bit of a stuff up here, although in fairness you allude to the problem with Alexa yourself.<br />
Firstly, the decline in afr.com pages coincides with the launch of afraccess. You have tracked the wrong site so what you are really seeing is the migration of traffic from one site to the other. Secondly and more importantly, alexa can not track afraccess (which in April this year effectively replaced AFR.com) because it can&#8217;t track flex. So if you track afraccess on Alexa all its measures its the home page. It doesn&#8217;t measure the page impressions inside the application where most of the activity is generated. In fact if you go to the alexa link you mention, click on the link to afr.com on Alexa and look at the AFR.com thumbnail you will see the evidence for yourself.<br />
Finally if you&#8217;re so concerned about what&#8217;s been happening to traffic its very easy to find out. afr.com (afraccess) is tracked by Nielsens, which all of us in advertising land have access to. Its traffic has been growing very strongly and consistently now for 6 months.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patricia Connelan</title>
		<link>http://www.lawfont.com/2007/06/18/more-on-afrcom-a-quick-traffic-analysis/comment-page-1/#comment-55707</link>
		<dc:creator>Patricia Connelan</dc:creator>
		<pubDate>Thu, 28 Jun 2007 07:09:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.lawfont.com/2007/06/18/more-on-afrcom-a-quick-traffic-analysis/#comment-55707</guid>
		<description>As someone was directly involved in the &#039;afr.com fiasco&#039;, I have to tell you that you&#039;re missing the point.

The fact is that Glenn Burge, the afr&#039;s editor, WANTED the website to fail, because he sees the web as a threat to print circulation.

Hence, the project was nobbled from the start.</description>
		<content:encoded><![CDATA[<p>As someone was directly involved in the &#8216;afr.com fiasco&#8217;, I have to tell you that you&#8217;re missing the point.</p>
<p>The fact is that Glenn Burge, the afr&#8217;s editor, WANTED the website to fail, because he sees the web as a threat to print circulation.</p>
<p>Hence, the project was nobbled from the start.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

