<?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: What Will *Really* Break If Google Switches To AJAX&#8230;?</title>
	<atom:link href="http://smackdown.blogsblogsblogs.com/2009/02/02/what-will-really-break-if-google-switches-to-ajax/feed/" rel="self" type="application/rss+xml" />
	<link>http://smackdown.blogsblogsblogs.com/2009/02/02/what-will-really-break-if-google-switches-to-ajax/</link>
	<description>Smackdown!</description>
	<lastBuildDate>Mon, 15 Mar 2010 20:42:03 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Maqbool Ahmad</title>
		<link>http://smackdown.blogsblogsblogs.com/2009/02/02/what-will-really-break-if-google-switches-to-ajax/comment-page-2/#comment-33097</link>
		<dc:creator>Maqbool Ahmad</dc:creator>
		<pubDate>Fri, 29 Jan 2010 10:29:25 +0000</pubDate>
		<guid isPermaLink="false">http://smackdown.blogsblogsblogs.com/?p=256#comment-33097</guid>
		<description>For this idea to work, it&#039;s first of all got to be an opt-in program. Hopefully, Yahoo will learn that lesson from the current Yahoo Search Marketing &quot;&lt;a&gt;web promotion&lt;/a&gt;&quot; issues.</description>
		<content:encoded><![CDATA[<p>For this idea to work, it&#8217;s first of all got to be an opt-in program. Hopefully, Yahoo will learn that lesson from the current Yahoo Search Marketing &#8220;<a>web promotion</a>&#8221; issues.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kent Davidson</title>
		<link>http://smackdown.blogsblogsblogs.com/2009/02/02/what-will-really-break-if-google-switches-to-ajax/comment-page-2/#comment-11585</link>
		<dc:creator>Kent Davidson</dc:creator>
		<pubDate>Thu, 12 Feb 2009 17:52:20 +0000</pubDate>
		<guid isPermaLink="false">http://smackdown.blogsblogsblogs.com/?p=256#comment-11585</guid>
		<description>And one more note for the conspiratorial minded: If Chrome chooses to pass the &quot;fragment&quot; to browsers, this would likely break a variety of sites (web servers, specifically) which don&#039;t know how to handle them. 

&lt;a href=&quot;http://www.w3.org/DesignIssues/Fragment.html&quot; rel=&quot;nofollow&quot;&gt;It&#039;s against the standard&lt;/a&gt; and I have seen many a web server which just plain &lt;strong&gt;break&lt;/strong&gt; when given anything outside of a normal URL (Java web servers pop to mind, in particular.) 

So, would Google risk having their browser break on some web servers? Doubtful.</description>
		<content:encoded><![CDATA[<p>And one more note for the conspiratorial minded: If Chrome chooses to pass the &#8220;fragment&#8221; to browsers, this would likely break a variety of sites (web servers, specifically) which don&#8217;t know how to handle them. </p>
<p><a href="http://www.w3.org/DesignIssues/Fragment.html" rel="nofollow">It&#8217;s against the standard</a> and I have seen many a web server which just plain <strong>break</strong> when given anything outside of a normal URL (Java web servers pop to mind, in particular.) </p>
<p>So, would Google risk having their browser break on some web servers? Doubtful.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kent Davidson</title>
		<link>http://smackdown.blogsblogsblogs.com/2009/02/02/what-will-really-break-if-google-switches-to-ajax/comment-page-2/#comment-11584</link>
		<dc:creator>Kent Davidson</dc:creator>
		<pubDate>Thu, 12 Feb 2009 17:43:59 +0000</pubDate>
		<guid isPermaLink="false">http://smackdown.blogsblogsblogs.com/?p=256#comment-11584</guid>
		<description>From a technical perspective, there&#039;s really nothing *preventing* Google from passing the actual referrer and search string from SERPs. 

Some may have noticed recently (within the last 2-3 months, I would say) that Google modified their tracking which links you click as you exit their site. As I often do right-click &quot;Copy this link&quot; on SERP pages to bookmark things for my blog, I noticed a lot of them redirected through Google. Checking today, this has been changed, again.

For a brief period (after I checked again) they were redirecting organic search links through google.com in order to track them for a short period. Now it appears that they are tracking exit links using Javascript (what, no GA?). Look at each organic link on the page&#039;s source:

onclick=&quot;return clk(this.href,&#039;&#039;,&#039;&#039;,&#039;res&#039;,&#039;4&#039;,&#039;&#039;)&quot;

I offer a detailed analysis of this internal tracking over at my &lt;a href=&quot;http://www.razzed.com/2009/02/12/analysis-of-google-outbound-link-tracking/?_cr=web&#124;smackdown&#124;what-will-really-break-google-ajax&#124;personal blog&quot; rel=&quot;nofollow&quot;&gt;personal blog&lt;/a&gt;, as this in particular is off-topic, but it reminds me of the quick technical solution which lets Google use AJAX and analytics to continue peacefully is:

- Use AJAX to perform their search using the URL fragment to &quot;hone in&quot; on results (http://www.google.com/#q=roi+tracking)

- Upon the outbound click, redirect through Google.com without using a referrer-killing HTTP status

(that is, Google.com servers would NOT use a 3xx HTTP status so the referrer is preserved as the outbound page containing the query string)

- Everybody wins.

If Google chooses to kill referrers, and the main source of SEO goodness, then I think it&#039;s best to rethink their &quot;Do no evil&quot; mantra.</description>
		<content:encoded><![CDATA[<p>From a technical perspective, there&#8217;s really nothing *preventing* Google from passing the actual referrer and search string from SERPs. </p>
<p>Some may have noticed recently (within the last 2-3 months, I would say) that Google modified their tracking which links you click as you exit their site. As I often do right-click &#8220;Copy this link&#8221; on SERP pages to bookmark things for my blog, I noticed a lot of them redirected through Google. Checking today, this has been changed, again.</p>
<p>For a brief period (after I checked again) they were redirecting organic search links through google.com in order to track them for a short period. Now it appears that they are tracking exit links using Javascript (what, no GA?). Look at each organic link on the page&#8217;s source:</p>
<p>onclick=&#8221;return clk(this.href,&#8221;,&#8221;,&#8217;res&#8217;,'4&#8242;,&#8221;)&#8221;</p>
<p>I offer a detailed analysis of this internal tracking over at my <a href="http://www.razzed.com/2009/02/12/analysis-of-google-outbound-link-tracking/?_cr=web|smackdown|what-will-really-break-google-ajax|personal blog" rel="nofollow">personal blog</a>, as this in particular is off-topic, but it reminds me of the quick technical solution which lets Google use AJAX and analytics to continue peacefully is:</p>
<p>- Use AJAX to perform their search using the URL fragment to &#8220;hone in&#8221; on results (<a href="http://www.google.com/#q=roi+tracking" rel="nofollow">http://www.google.com/#q=roi+tracking</a>)</p>
<p>- Upon the outbound click, redirect through Google.com without using a referrer-killing HTTP status</p>
<p>(that is, Google.com servers would NOT use a 3xx HTTP status so the referrer is preserved as the outbound page containing the query string)</p>
<p>- Everybody wins.</p>
<p>If Google chooses to kill referrers, and the main source of SEO goodness, then I think it&#8217;s best to rethink their &#8220;Do no evil&#8221; mantra.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Uh-oh. AJAX-powered search kills keywords in referrers</title>
		<link>http://smackdown.blogsblogsblogs.com/2009/02/02/what-will-really-break-if-google-switches-to-ajax/comment-page-2/#comment-11574</link>
		<dc:creator>Uh-oh. AJAX-powered search kills keywords in referrers</dc:creator>
		<pubDate>Thu, 12 Feb 2009 15:22:45 +0000</pubDate>
		<guid isPermaLink="false">http://smackdown.blogsblogsblogs.com/?p=256#comment-11574</guid>
		<description>[...] according to Clicky, Smackdown and a discussion forum on Webmaster World, many webmasters are fearful of AJAX-only search from [...]</description>
		<content:encoded><![CDATA[<p>[...] according to Clicky, Smackdown and a discussion forum on Webmaster World, many webmasters are fearful of AJAX-only search from [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael VanDeMar</title>
		<link>http://smackdown.blogsblogsblogs.com/2009/02/02/what-will-really-break-if-google-switches-to-ajax/comment-page-1/#comment-11491</link>
		<dc:creator>Michael VanDeMar</dc:creator>
		<pubDate>Tue, 10 Feb 2009 14:38:54 +0000</pubDate>
		<guid isPermaLink="false">http://smackdown.blogsblogsblogs.com/?p=256#comment-11491</guid>
		<description>Melanie, it&#039;s from Traffic Sources -&gt; All Traffic Sources. Google Search referrals look like &quot;google / organic&quot;, whereas referrals from Google that are supposedly not searches look like &quot;google.com / referral&quot;.

Just so you know though, it looks like they have cut way down on the testing it right now. It might be related to the fact that they were only testing one browser, and Firefox updated last week to a newer version. Or they may have just slowed way down because it drew too much attention. Not sure. You should still be able to see what I was talking about though if you restrict your stats report to Feb 1st through Feb 5th. For that period a little more than 25% of my Google traffic was direct, without keywords passed.</description>
		<content:encoded><![CDATA[<p>Melanie, it&#8217;s from Traffic Sources -> All Traffic Sources. Google Search referrals look like &#8220;google / organic&#8221;, whereas referrals from Google that are supposedly not searches look like &#8220;google.com / referral&#8221;.</p>
<p>Just so you know though, it looks like they have cut way down on the testing it right now. It might be related to the fact that they were only testing one browser, and Firefox updated last week to a newer version. Or they may have just slowed way down because it drew too much attention. Not sure. You should still be able to see what I was talking about though if you restrict your stats report to Feb 1st through Feb 5th. For that period a little more than 25% of my Google traffic was direct, without keywords passed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Melanie</title>
		<link>http://smackdown.blogsblogsblogs.com/2009/02/02/what-will-really-break-if-google-switches-to-ajax/comment-page-1/#comment-11489</link>
		<dc:creator>Melanie</dc:creator>
		<pubDate>Tue, 10 Feb 2009 14:25:53 +0000</pubDate>
		<guid isPermaLink="false">http://smackdown.blogsblogsblogs.com/?p=256#comment-11489</guid>
		<description>Michael,

Which Google Analytics report did your screen shot come from? Was that the Keywords report under Traffic Sources? I just want to check and see if there is something similar showing for our accounts. As you can probably tell, my knowledge on all this is a little limited. And I apologize if this question already arose; I didn&#039;t take the time to read through all the comments.</description>
		<content:encoded><![CDATA[<p>Michael,</p>
<p>Which Google Analytics report did your screen shot come from? Was that the Keywords report under Traffic Sources? I just want to check and see if there is something similar showing for our accounts. As you can probably tell, my knowledge on all this is a little limited. And I apologize if this question already arose; I didn&#8217;t take the time to read through all the comments.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Keith Holloway</title>
		<link>http://smackdown.blogsblogsblogs.com/2009/02/02/what-will-really-break-if-google-switches-to-ajax/comment-page-1/#comment-11437</link>
		<dc:creator>Keith Holloway</dc:creator>
		<pubDate>Mon, 09 Feb 2009 18:18:09 +0000</pubDate>
		<guid isPermaLink="false">http://smackdown.blogsblogsblogs.com/?p=256#comment-11437</guid>
		<description>It seems disingenuous of Google to say that they&#039;re doing it to &quot;provide a faster experience for our users&quot;. There must be another reason.

I do hope they&#039;re being honest about the fact that they have no intention of disrupting referrer tracking and they are continuing to iterate, because if they do roll this out they are going to break a lot of successful business models.

However, I suppose we can take some solace in the fact that rolling out this change would in fact break Urchin, because, I agree with Cristi, it seems unlikely that Google would do that.</description>
		<content:encoded><![CDATA[<p>It seems disingenuous of Google to say that they&#8217;re doing it to &#8220;provide a faster experience for our users&#8221;. There must be another reason.</p>
<p>I do hope they&#8217;re being honest about the fact that they have no intention of disrupting referrer tracking and they are continuing to iterate, because if they do roll this out they are going to break a lot of successful business models.</p>
<p>However, I suppose we can take some solace in the fact that rolling out this change would in fact break Urchin, because, I agree with Cristi, it seems unlikely that Google would do that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AJAX w googielowej szukajce</title>
		<link>http://smackdown.blogsblogsblogs.com/2009/02/02/what-will-really-break-if-google-switches-to-ajax/comment-page-1/#comment-11432</link>
		<dc:creator>AJAX w googielowej szukajce</dc:creator>
		<pubDate>Mon, 09 Feb 2009 17:06:47 +0000</pubDate>
		<guid isPermaLink="false">http://smackdown.blogsblogsblogs.com/?p=256#comment-11432</guid>
		<description>[...] Polecam równie? zapozna? si? z artyku?em &#8220;Co si? naprawd? zepsuje, kiedy Google przejdzie na AJAX&#8220;, w którym poruszana jest niezwykle wa?ne zagadnienie: adresy AJAX&#8217;owe (czyli #q=) [...]</description>
		<content:encoded><![CDATA[<p>[...] Polecam równie? zapozna? si? z artyku?em &#8220;Co si? naprawd? zepsuje, kiedy Google przejdzie na AJAX&#8220;, w którym poruszana jest niezwykle wa?ne zagadnienie: adresy AJAX&#8217;owe (czyli #q=) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mattias Geniar</title>
		<link>http://smackdown.blogsblogsblogs.com/2009/02/02/what-will-really-break-if-google-switches-to-ajax/comment-page-1/#comment-11301</link>
		<dc:creator>Mattias Geniar</dc:creator>
		<pubDate>Sat, 07 Feb 2009 10:23:44 +0000</pubDate>
		<guid isPermaLink="false">http://smackdown.blogsblogsblogs.com/?p=256#comment-11301</guid>
		<description>I&#039;ll bet Google will find some workaround for this, especially if it &quot;breaks&quot; their own Google Analytics tool. Either add in an additional URL parameter (which would be in direct contract to their AJAX-experimenting, since it would require a page reload), or attach an extra parameter for any SERP-item followed. Something in line of www&lt;nobr&gt;.site.com/mypage/?__google_search=my+site+in+google.

Or perhaps a more ugly solution, having a form of redirect before being sent to your final search-result page.</description>
		<content:encoded><![CDATA[<p>I&#8217;ll bet Google will find some workaround for this, especially if it &#8220;breaks&#8221; their own Google Analytics tool. Either add in an additional URL parameter (which would be in direct contract to their AJAX-experimenting, since it would require a page reload), or attach an extra parameter for any SERP-item followed. Something in line of www<nobr>.site.com/mypage/?__google_search=my+site+in+google.</p>
<p>Or perhaps a more ugly solution, having a form of redirect before being sent to your final search-result page.</nobr></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: CoolSeo</title>
		<link>http://smackdown.blogsblogsblogs.com/2009/02/02/what-will-really-break-if-google-switches-to-ajax/comment-page-1/#comment-11251</link>
		<dc:creator>CoolSeo</dc:creator>
		<pubDate>Fri, 06 Feb 2009 01:35:47 +0000</pubDate>
		<guid isPermaLink="false">http://smackdown.blogsblogsblogs.com/?p=256#comment-11251</guid>
		<description>Thanks for letting us know..</description>
		<content:encoded><![CDATA[<p>Thanks for letting us know..</p>
]]></content:encoded>
	</item>
</channel>
</rss>
