<?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: Google Me This &#8211; Google’s 72 New Algorithms</title>
	<atom:link href="http://www.amalgamdesign.com/blog/archives/430/google-me-this-google%e2%80%99s-72-new-algorithms/feed" rel="self" type="application/rss+xml" />
	<link>http://www.amalgamdesign.com/blog/archives/430/google-me-this-google%e2%80%99s-72-new-algorithms</link>
	<description>The Official Blog of Amalgam Design</description>
	<lastBuildDate>Mon, 12 Mar 2012 01:54:21 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: SEO Steve</title>
		<link>http://www.amalgamdesign.com/blog/archives/430/google-me-this-google%e2%80%99s-72-new-algorithms/comment-page-1#comment-231</link>
		<dc:creator>SEO Steve</dc:creator>
		<pubDate>Wed, 24 Mar 2010 22:44:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.amalgamdesign.com/blog/?p=430#comment-231</guid>
		<description>A cookie is a small text file (non-encrypted) of persistent or temporary information shared between a server and a user.  If you view the cookies stored by your browser, you can see that they are named after the server that set them.  Web servers can only  and set read cookies that they have created themselves under the their server name.

Cookies can be hijacked by &quot;packet-sniffers&quot; on the Internet, in the same way that any data we send or receive can be detected, even emails.  This is dangerous is websites store sensitive personal data in their cookies such as passwords, or banking info.  

Third-party cookies are not malicious, however, and most modern browsers allow you to turn them off if you want.  When we visit a site such as blogs, there may be some google ads or some other &quot;third-party content&quot;.  This content is served by a different server (such as an ads server) which has the right to store its own cookie for its own use.  However, they cannot see the cookies of the hosting (or primary) server.

So, if the google ads server stores a cookie on our browser when we visit a site, anonymously identifying us as &quot;a specific user&quot;, it can make the connection to us when we visit another site with google ads.  So, if we are visiting a number of wedding-related sites, or even click-thru some of the google ads on weddings, it is able to conclude that we are interested in weddings and will gear the ad content to our preferences, hoping for more ad clicks.

My understanding, however, is that these google ad cookies are used only for &quot;sponsored links&quot; and not for organic search results.  While google search results are heavily influenced by geo-location (frustratingly so, suppose I am planning to travel away from my home town, G?), they are not so fluid as that.  Also, G recognizes which searches are &quot;global&quot; versus &quot;local&quot;, as well as favouring web servers hosted in our respective countries.  

Remember that google search and google ads are two separate arms of G using separate techniques and algorithms.  They don&#039;t really &quot;talk&quot; to each other.</description>
		<content:encoded><![CDATA[<p>A cookie is a small text file (non-encrypted) of persistent or temporary information shared between a server and a user.  If you view the cookies stored by your browser, you can see that they are named after the server that set them.  Web servers can only  and set read cookies that they have created themselves under the their server name.</p>
<p>Cookies can be hijacked by &#8220;packet-sniffers&#8221; on the Internet, in the same way that any data we send or receive can be detected, even emails.  This is dangerous is websites store sensitive personal data in their cookies such as passwords, or banking info.  </p>
<p>Third-party cookies are not malicious, however, and most modern browsers allow you to turn them off if you want.  When we visit a site such as blogs, there may be some google ads or some other &#8220;third-party content&#8221;.  This content is served by a different server (such as an ads server) which has the right to store its own cookie for its own use.  However, they cannot see the cookies of the hosting (or primary) server.</p>
<p>So, if the google ads server stores a cookie on our browser when we visit a site, anonymously identifying us as &#8220;a specific user&#8221;, it can make the connection to us when we visit another site with google ads.  So, if we are visiting a number of wedding-related sites, or even click-thru some of the google ads on weddings, it is able to conclude that we are interested in weddings and will gear the ad content to our preferences, hoping for more ad clicks.</p>
<p>My understanding, however, is that these google ad cookies are used only for &#8220;sponsored links&#8221; and not for organic search results.  While google search results are heavily influenced by geo-location (frustratingly so, suppose I am planning to travel away from my home town, G?), they are not so fluid as that.  Also, G recognizes which searches are &#8220;global&#8221; versus &#8220;local&#8221;, as well as favouring web servers hosted in our respective countries.  </p>
<p>Remember that google search and google ads are two separate arms of G using separate techniques and algorithms.  They don&#8217;t really &#8220;talk&#8221; to each other.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam</title>
		<link>http://www.amalgamdesign.com/blog/archives/430/google-me-this-google%e2%80%99s-72-new-algorithms/comment-page-1#comment-9</link>
		<dc:creator>Adam</dc:creator>
		<pubDate>Fri, 04 Dec 2009 15:27:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.amalgamdesign.com/blog/?p=430#comment-9</guid>
		<description>You mention third party cookies. &quot;That is, using third party cookies, my search results ...&quot; Does your research indicate Google is reading other sites&#039; cookies?

Is this a partnership thing?

Is this a privacy violation? I wonder how many privacy policies that contravenes?

It&#039;s not uncommon for a website&#039;s privacy policy to mention why cookies are being set  and how they will be used, but I&#039;ve never  seen a policy stating that &quot;Google will hijack our cookies and use them for their own purposes.&quot;

I thought cookies are supposed to be encrypted, Is Google hacking them or have they been given the code to open them up.

Or are they just setting/reading their own cookies based on users&#039; previous search behaviour?

One little blog post, so many questions.</description>
		<content:encoded><![CDATA[<p>You mention third party cookies. &#8220;That is, using third party cookies, my search results &#8230;&#8221; Does your research indicate Google is reading other sites&#8217; cookies?</p>
<p>Is this a partnership thing?</p>
<p>Is this a privacy violation? I wonder how many privacy policies that contravenes?</p>
<p>It&#8217;s not uncommon for a website&#8217;s privacy policy to mention why cookies are being set  and how they will be used, but I&#8217;ve never  seen a policy stating that &#8220;Google will hijack our cookies and use them for their own purposes.&#8221;</p>
<p>I thought cookies are supposed to be encrypted, Is Google hacking them or have they been given the code to open them up.</p>
<p>Or are they just setting/reading their own cookies based on users&#8217; previous search behaviour?</p>
<p>One little blog post, so many questions.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

