<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Illuminati Karate, Inc. &#187; Analytics</title>
	<atom:link href="http://illuminatikarate.com/blog/category/analytics/feed/" rel="self" type="application/rss+xml" />
	<link>http://illuminatikarate.com</link>
	<description>creative web design, development and marketing</description>
	<lastBuildDate>Fri, 03 Feb 2012 20:13:42 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
		<item>
		<title>Exclude WordPress&#8217; Admin URLs from your AWStats Reports</title>
		<link>http://illuminatikarate.com/blog/exclude-wordpress-admin-urls-from-your-awstats-reports/</link>
		<comments>http://illuminatikarate.com/blog/exclude-wordpress-admin-urls-from-your-awstats-reports/#comments</comments>
		<pubDate>Tue, 10 Mar 2009 17:58:52 +0000</pubDate>
		<dc:creator>George Huger</dc:creator>
				<category><![CDATA[Analytics]]></category>
		<category><![CDATA[Wordpress]]></category>
		<category><![CDATA[awstats]]></category>

		<guid isPermaLink="false">http://illuminatikarate.com/blog/?p=18</guid>
		<description><![CDATA[After upgrading a friend&#8217;s blog to WordPress 2.7 we started noticing his pageview numbers in AWStats going through the roof, without a corresponding increase in visitors. Here&#8217;s a screenshot: Google Analytics was showing normal pageview numbers, so we knew something was amiss. When we looked at the most viewed [...]]]></description>
			<content:encoded><![CDATA[<p>After upgrading a friend&#8217;s blog to WordPress 2.7 we started noticing his pageview numbers in AWStats going through the roof, without a corresponding increase in visitors. Here&#8217;s a screenshot:</p>
<p><a href="http://illuminatikarate.com/wp-content/uploads/2009/03/aws-pageviews-feb-sic.png"><img class="aligncenter size-full wp-image-26" title="Screenshot of AWStats seemingly overreporting pageviews" src="http://illuminatikarate.com/wp-content/uploads/2009/03/aws-pageviews-feb-sic.png" alt="Screenshot of AWStats seemingly overreporting pageviews" width="430" height="69" /></a></p>
<p>Google Analytics was showing normal pageview numbers, so we knew something was amiss. When we looked at the most viewed pages in awstats, it became obvious:</p>
<p><a href="http://illuminatikarate.com/wp-content/uploads/2009/03/aws-pageviews-per-page-feb-sic1.png"><img src="http://illuminatikarate.com/wp-content/uploads/2009/03/aws-pageviews-per-page-feb-sic1.png" alt="Screenshot of AWStats views per page, showing 2228 hits on WP&#039;s admin-ajax.php file" title="Screenshot of AWStats views per page, showing 2228 hits on WP&#039;s admin-ajax.php file" width="500" height="38" class="aligncenter wp-image-28" /></a></p>
<p>AWStats has always counted pageviews on the WordPress backend, but compared to the total pageviews the impact was negligible. However, now that WordPress 2.7 makes so many AJAX calls to admin-ajax.php (primarily for saving drafts), we must exclude these pageviews from our reports to leave meaningful data. Thankfully its very easy.</p>
<p><span id="more-370"></span>We&#8217;re going to instruct awstats to ignore hits on any page in the wp-admin directory. Alternatively, we could have AWStats ignore our IP address, which has its own merits, but this approach becomes cumbersome when multiple authors and dynamic IPs come into play. </p>
<p>Instructions:</p>
<ol>
<li>Open the awstats .conf file which corresponds to your domain. On most shared hosting accounts this will be located in /tmp/awstats/. If you see more than one .conf file, choose the one which matches the domain of the site you are working on.</li>
<li>Look for the line which starts with:
<pre class="code">SkipFiles="</pre>
<p>AWStats is usually already configured to exclude robots.txt and favicon.ico, so the line probably looks like this:
<pre class="code">SkipFiles="robots.txt$ favicon.ico$"</pre>
</li>
<li>Append the following string after the last filename listed (make sure to leave a space), but before the quote:
<pre class="code"> REGEX[^/wp-admin/]</pre>
<p>If you&#8217;re file looks like mine, the line should now read:
<pre class="code">SkipFiles="robots.txt$ favicon.ico$ REGEX[^/wp-admin/]"</pre>
</li>
<li>Save and upload the file. If you&#8217;re on shared hosting, you&#8217;ll want to CHMOD the .conf file to 444, otherwise your changes are likely to be overwritten.</li>
</ol>
<p>That&#8217;s it! This change is not retroactive, but if all went well you should be able to write a new post in WordPress and the pageviews for admin-ajax.php will not increase.</p>
]]></content:encoded>
			<wfw:commentRss>http://illuminatikarate.com/blog/exclude-wordpress-admin-urls-from-your-awstats-reports/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
	</channel>
</rss>

