<?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: Watching a story, part II</title> <atom:link href="http://www.mattcutts.com/blog/watching-a-story-part-ii/feed/" rel="self" type="application/rss+xml" /><link>http://www.mattcutts.com/blog/watching-a-story-part-ii/</link> <description>neat fun stuff</description> <lastBuildDate>Wed, 08 Feb 2012 21:30:01 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.3.1</generator> <item><title>By: CPCcurmudgeon</title><link>http://www.mattcutts.com/blog/watching-a-story-part-ii/#comment-91431</link> <dc:creator>CPCcurmudgeon</dc:creator> <pubDate>Tue, 12 Dec 2006 01:55:57 +0000</pubDate> <guid isPermaLink="false">http://www.mattcutts.com/blog/watching-a-story-part-ii/#comment-91431</guid> <description>It does seem strange that Google would not know about IPs allocated to well-known ISPs such as Telstra.  However, I can imagine how this could happen.  IP address blocks change hands, and it is possible that a block came into Telstra&#039;s possession without a change to whatever databases Google was using at the time.  This is one among many reasons why I feel geotargeting shouldn&#039;t be relied on, because one cannot be sure that one&#039;s database correctly reflects allocations that are in use.In terms of actually determining if a geotargeted ad should be shown, unfortunately advertisers are not provided with enough information to make comparisons.  In the case where a request came in from an IP address with no mapping, but the query contained the targeted location, the ad could be shown, according to the AdWords documentation.  However, advertisers don&#039;t get a report of what comes in on the HTTP requests, so they have no way to determine what factors were applied in deciding whether an ad was shown.</description> <content:encoded><![CDATA[<p>It does seem strange that Google would not know about IPs allocated to well-known ISPs such as Telstra.  However, I can imagine how this could happen.  IP address blocks change hands, and it is possible that a block came into Telstra&#8217;s possession without a change to whatever databases Google was using at the time.  This is one among many reasons why I feel geotargeting shouldn&#8217;t be relied on, because one cannot be sure that one&#8217;s database correctly reflects allocations that are in use.</p><p>In terms of actually determining if a geotargeted ad should be shown, unfortunately advertisers are not provided with enough information to make comparisons.  In the case where a request came in from an IP address with no mapping, but the query contained the targeted location, the ad could be shown, according to the AdWords documentation.  However, advertisers don&#8217;t get a report of what comes in on the HTTP requests, so they have no way to determine what factors were applied in deciding whether an ad was shown.</p> ]]></content:encoded> </item> <item><title>By: Aeronautic</title><link>http://www.mattcutts.com/blog/watching-a-story-part-ii/#comment-91364</link> <dc:creator>Aeronautic</dc:creator> <pubDate>Mon, 11 Dec 2006 15:54:42 +0000</pubDate> <guid isPermaLink="false">http://www.mattcutts.com/blog/watching-a-story-part-ii/#comment-91364</guid> <description>Hello Everyone,Sorry to chime in here again but this hand wringing about the 100% &quot;promise&quot; of accuracy of geotargeting is irritating to say the least.When selecting regions the UI provides little in the way of warning or disclaimer about accuracy, but that is a classic problem of AdWords disclosure - like that of telling, or not telling, clients when their ads will run on parked pages. But I digress.As I think it&#039;s fair to infer from Mikkel&#039;s comment, I agree the issue is where in the world does Google get off charging for something they are uncertain meets the client&#039;s criteria?Why does the slop spill on the customer, not Google? If Google is not 100% sure of the visitor IP, by all means don&#039;t show the ad or don&#039;t charge for the click.Why is the burden on the customer to police Google? And to do so without detailed reporting of click IPs?In my case reported above in this thread the IP was 124.176.218.XX (last two munged for privacy of visitor)How long does it take to confirm it was not in the USA? Yah.Google could not handle that one?And again, most importantly, and in direct contradiction of public statements, irrespective of the issue of how accurate their look-ups are, how does Google really handle properly reported credit requests for bad geotargeting?Folks, this is a direct quote from an e-mail sent to me by AdWords Support:“Since our tests indicate that this targeting is accurate in the vast majority of cases, we do not credit for geographic targeting.” (quote here real)They keep the money. That is the only way that can be understood. If I order a salad and the waiter delivers a steak, charges my credit card and refuses to reverse the charge, I&#039;d view that as fraud. Especially if they tell me &quot;Our data suggests that folks who order salads really wanted steaks in the vast majority of cases, therefore we do not credit for steaks served you did not order.&quot;  (quote here fictional)As stated earlier, Google did finally reverse charge in this case, but it took a month, over 30 e-mails and hours of calls. That behavior, along with the real quote above, speaks volumes about Google&#039;s intent.They did not, in my case, quickly, easily, willingly or cooperatively reverse the charge and it was impeccably documented and politely requested at the outset. Read the response quote - they had no intention to reverse the click. None. And an official representative stated in writing (the quote) that this was official company policy. And if past is precedent that response was far from a personal message to me, it was pure boilerplate (template) text that reflected official approved policy.Frankly, the class actions don&#039;t seem as an appropriate a remedy as seeing a bunch of State Attorney Generals investigate this a la Microsoft.Part of why this irks me so much is the hypocrisy of it all.Yet another reason is this is doing significant harm to small AdSense publishers, like me, in the content network. When advertisers pull out of the content network for fear of being ripped off by who knows who, the little publishers also get hurt. And that&#039;s before the nightmare of so-called smart pricing.Thanks for the electrons Matt. I&#039;d be honored to meet you at an event.</description> <content:encoded><![CDATA[<p>Hello Everyone,</p><p>Sorry to chime in here again but this hand wringing about the 100% &#8220;promise&#8221; of accuracy of geotargeting is irritating to say the least.</p><p>When selecting regions the UI provides little in the way of warning or disclaimer about accuracy, but that is a classic problem of AdWords disclosure &#8211; like that of telling, or not telling, clients when their ads will run on parked pages. But I digress.</p><p>As I think it&#8217;s fair to infer from Mikkel&#8217;s comment, I agree the issue is where in the world does Google get off charging for something they are uncertain meets the client&#8217;s criteria?</p><p>Why does the slop spill on the customer, not Google? If Google is not 100% sure of the visitor IP, by all means don&#8217;t show the ad or don&#8217;t charge for the click.</p><p>Why is the burden on the customer to police Google? And to do so without detailed reporting of click IPs?</p><p>In my case reported above in this thread the IP was 124.176.218.XX (last two munged for privacy of visitor)</p><p>How long does it take to confirm it was not in the USA? Yah.</p><p>Google could not handle that one?</p><p>And again, most importantly, and in direct contradiction of public statements, irrespective of the issue of how accurate their look-ups are, how does Google really handle properly reported credit requests for bad geotargeting?</p><p>Folks, this is a direct quote from an e-mail sent to me by AdWords Support:</p><p>“Since our tests indicate that this targeting is accurate in the vast majority of cases, we do not credit for geographic targeting.” (quote here real)</p><p>They keep the money. That is the only way that can be understood. If I order a salad and the waiter delivers a steak, charges my credit card and refuses to reverse the charge, I&#8217;d view that as fraud. Especially if they tell me &#8220;Our data suggests that folks who order salads really wanted steaks in the vast majority of cases, therefore we do not credit for steaks served you did not order.&#8221;  (quote here fictional)</p><p>As stated earlier, Google did finally reverse charge in this case, but it took a month, over 30 e-mails and hours of calls. That behavior, along with the real quote above, speaks volumes about Google&#8217;s intent.</p><p>They did not, in my case, quickly, easily, willingly or cooperatively reverse the charge and it was impeccably documented and politely requested at the outset. Read the response quote &#8211; they had no intention to reverse the click. None. And an official representative stated in writing (the quote) that this was official company policy. And if past is precedent that response was far from a personal message to me, it was pure boilerplate (template) text that reflected official approved policy.</p><p>Frankly, the class actions don&#8217;t seem as an appropriate a remedy as seeing a bunch of State Attorney Generals investigate this a la Microsoft.</p><p>Part of why this irks me so much is the hypocrisy of it all.</p><p>Yet another reason is this is doing significant harm to small AdSense publishers, like me, in the content network. When advertisers pull out of the content network for fear of being ripped off by who knows who, the little publishers also get hurt. And that&#8217;s before the nightmare of so-called smart pricing.</p><p>Thanks for the electrons Matt. I&#8217;d be honored to meet you at an event.</p> ]]></content:encoded> </item> <item><title>By: Mikkel deMib Svendsen</title><link>http://www.mattcutts.com/blog/watching-a-story-part-ii/#comment-91353</link> <dc:creator>Mikkel deMib Svendsen</dc:creator> <pubDate>Mon, 11 Dec 2006 14:32:57 +0000</pubDate> <guid isPermaLink="false">http://www.mattcutts.com/blog/watching-a-story-part-ii/#comment-91353</guid> <description>The question is not weather the geo targeting is 100% accurate. Its not and I have never claimed it could be. The question is what do Google show when they do not know the origin of a user. Right now, as I have experienced, Google show ads to users they do NOT know where is coming from even for ads that have been targeted to one region only. That is just plain wrong to do, in my opinion. Google should only show global ads (non regional targeted) to users they do not know where is from.Where on Googles TOS does it say &quot;We will show you ads to users in the region you select + any other user we do not know where is coming from&quot;?Google have so far claimed, oh but thats just a small number. In most cases we do fine! How do you know? How do we, the advertisers, know? For all I know Google is indeed not doing very well on this given the fact that IPs Google should, and can find out about they apparently say they have not mapped. So, Matt, is Google&#039;s mapping bad or is Google not telling the truth when they claim that IPs from the biggest local ISPs (such as in my own case) are not in your IP database? Sorry, but as I said before, I simply do not believe that Google have data that is not as good as what I can pull of the web for a few bucks.The second claim from Google is, oh yes, we may have shown your ad outside the region you targeted but we never charged you for the clicks that came through. Does anyone really believe that Google will waste its inventory on commercial ads they do not get paid for? I don&#039;t! From a business as well as a technical point of view it dosn&#039;t make any sense. Why not give that inventory to ads that are either targeted to that region or no region at all - ads that Google could in fact legitimately charge for.</description> <content:encoded><![CDATA[<p>The question is not weather the geo targeting is 100% accurate. Its not and I have never claimed it could be. The question is what do Google show when they do not know the origin of a user. Right now, as I have experienced, Google show ads to users they do NOT know where is coming from even for ads that have been targeted to one region only. That is just plain wrong to do, in my opinion. Google should only show global ads (non regional targeted) to users they do not know where is from.</p><p>Where on Googles TOS does it say &#8220;We will show you ads to users in the region you select + any other user we do not know where is coming from&#8221;?</p><p>Google have so far claimed, oh but thats just a small number. In most cases we do fine! How do you know? How do we, the advertisers, know? For all I know Google is indeed not doing very well on this given the fact that IPs Google should, and can find out about they apparently say they have not mapped. So, Matt, is Google&#8217;s mapping bad or is Google not telling the truth when they claim that IPs from the biggest local ISPs (such as in my own case) are not in your IP database? Sorry, but as I said before, I simply do not believe that Google have data that is not as good as what I can pull of the web for a few bucks.</p><p>The second claim from Google is, oh yes, we may have shown your ad outside the region you targeted but we never charged you for the clicks that came through. Does anyone really believe that Google will waste its inventory on commercial ads they do not get paid for? I don&#8217;t! From a business as well as a technical point of view it dosn&#8217;t make any sense. Why not give that inventory to ads that are either targeted to that region or no region at all &#8211; ads that Google could in fact legitimately charge for.</p> ]]></content:encoded> </item> <item><title>By: DaveN</title><link>http://www.mattcutts.com/blog/watching-a-story-part-ii/#comment-91344</link> <dc:creator>DaveN</dc:creator> <pubDate>Mon, 11 Dec 2006 12:18:26 +0000</pubDate> <guid isPermaLink="false">http://www.mattcutts.com/blog/watching-a-story-part-ii/#comment-91344</guid> <description>a) the first write-ups were mostly WMR folks  ..nothing to do with the fact that it was wmr that found the story .. or the fact that wmr called on people they are close to, to look at the data.the terrorist side of the story is not what i wanted to get into .. The NSA are all over that with the FBI ,, and before we broke the story I believe.I&#039;m interested in the Clickdata from AIT .. and combining that with some other clients, in fact I&#039;m just getting the data for over 100 million dollars of ppc spend.. which I said to Adam i would share. But man the TW thing imo was a low blow,., the story was nothing to do with me being posted over there and deep down you know that.DaveN</description> <content:encoded><![CDATA[<p>a) the first write-ups were mostly WMR folks  ..</p><p>nothing to do with the fact that it was wmr that found the story ..<br /> or the fact that wmr called on people they are close to, to look at the data.</p><p>the terrorist side of the story is not what i wanted to get into .. The NSA are all over that with the FBI ,, and before we broke the story I believe.</p><p>I&#8217;m interested in the Clickdata from AIT .. and combining that with some other clients, in fact I&#8217;m just getting the data for over 100 million dollars of ppc spend.. which I said to Adam i would share. But man the TW thing imo was a low blow,., the story was nothing to do with me being posted over there and deep down you know that.</p><p>DaveN</p> ]]></content:encoded> </item> <item><title>By: CPCcurmudgeon</title><link>http://www.mattcutts.com/blog/watching-a-story-part-ii/#comment-91314</link> <dc:creator>CPCcurmudgeon</dc:creator> <pubDate>Mon, 11 Dec 2006 08:27:36 +0000</pubDate> <guid isPermaLink="false">http://www.mattcutts.com/blog/watching-a-story-part-ii/#comment-91314</guid> <description>Matt, to your credit, I have never seen any documentation claiming that Google&#039;s geolocation works 100% of the time.  My suggestion is that on pages such as the Local Business Ads help page, there might be some text that gives a caveat that geolocation is a best-effort service.  That way, it&#039;s much more likely that potential customers will see it.I remember the Nazi/Yahoo France case.  In fact, it is mentioned in the geolocation paper I provided a link to.  My understanding of Yahoo&#039;s statements is that they believed it was impossible to guarantee any level of accuracy of geotargeting results.  This doesn&#039;t mean that it would never work; certainly, there are instances where the mapping corresponds to the physical location of an (alleged) user.  But it would lead (and has led) to problems when the mappings fail, and advertisers are charged for usage they were (perhaps accidently) led to believe they would not be charged for.BTW, Jonathan, there are parallels to click fraud in the telecom industry, such as 1-900 phone scams.  However, this doesn&#039;t stop phone companies from providing detailed billing statements when that is warranted.  I think there is some merit to providing detailed click charges against IPs, and allowing advertisers to block on an IP range, provided that they understand that this might lead to the blocking of &quot;legit&quot; traffic if that range is transferred to another organization.  I would also understand if Google needed to charge more to provide this service.</description> <content:encoded><![CDATA[<p>Matt, to your credit, I have never seen any documentation claiming that Google&#8217;s geolocation works 100% of the time.  My suggestion is that on pages such as the Local Business Ads help page, there might be some text that gives a caveat that geolocation is a best-effort service.  That way, it&#8217;s much more likely that potential customers will see it.</p><p>I remember the Nazi/Yahoo France case.  In fact, it is mentioned in the geolocation paper I provided a link to.  My understanding of Yahoo&#8217;s statements is that they believed it was impossible to guarantee any level of accuracy of geotargeting results.  This doesn&#8217;t mean that it would never work; certainly, there are instances where the mapping corresponds to the physical location of an (alleged) user.  But it would lead (and has led) to problems when the mappings fail, and advertisers are charged for usage they were (perhaps accidently) led to believe they would not be charged for.</p><p>BTW, Jonathan, there are parallels to click fraud in the telecom industry, such as 1-900 phone scams.  However, this doesn&#8217;t stop phone companies from providing detailed billing statements when that is warranted.  I think there is some merit to providing detailed click charges against IPs, and allowing advertisers to block on an IP range, provided that they understand that this might lead to the blocking of &#8220;legit&#8221; traffic if that range is transferred to another organization.  I would also understand if Google needed to charge more to provide this service.</p> ]]></content:encoded> </item> <item><title>By: Matt Cutts</title><link>http://www.mattcutts.com/blog/watching-a-story-part-ii/#comment-91301</link> <dc:creator>Matt Cutts</dc:creator> <pubDate>Mon, 11 Dec 2006 06:47:46 +0000</pubDate> <guid isPermaLink="false">http://www.mattcutts.com/blog/watching-a-story-part-ii/#comment-91301</guid> <description>rob, nice comment. I think about this stuff all the time. When I talk to the AdWords folks with thoughts or suggestions, I usually come away thinking that they&#039;re smarter than me. Which is good--I&#039;m glad when they&#039;ve already thought of something that I suggest.I think your larger point is also more interesting: how does a company try to stay true to itself and our users as it grows? How do we make sure that we advocate for our users, and that the outside world knows that? When we have discussions internally, I&#039;ve been a fan of the idea of trying to bake the culture into our corporate DNA in different ways, so the culture doesn&#039;t rely on the personality of a few people.DaveN, the Baker/Boser/Shoemoney/TW stories all appeared the night of the 6th. That agrees with what I said in the post, then it got quiet for a while as the web mulled over the claims. The short mention in SEW was on the 7th, and the ClickZ article was on the 8th. I didn&#039;t say that it didn&#039;t get written up, just that a) the first write-ups were mostly WMR folks (not BH folks; I don&#039;t mean to imply that this was a BH thing), and b) not many other people wrote it up, given the considerable claims made for the story.CPCcurmudgeon, I agree that geotargeting is a best-effort service; if you see documentation that claims geotargeting to be 100% perfect, please point it out to me so that we can make sure the language is as accurate as possible. In November of 2000 I evaluated geolocation vendors for Google&#039;s initial implementation of geolocation, so I&#039;m well aware that no solution is perfect. On the other hand, do you remember the Nazi/Yahoo France case several years ago, where Yahoo claimed it was impossible to determine country-of-origin from an IP address? Measured by that incident, it&#039;s wonderful that geotargeting has gotten so much more accurate since then.</description> <content:encoded><![CDATA[<p>rob, nice comment. I think about this stuff all the time. When I talk to the AdWords folks with thoughts or suggestions, I usually come away thinking that they&#8217;re smarter than me. Which is good&#8211;I&#8217;m glad when they&#8217;ve already thought of something that I suggest.</p><p>I think your larger point is also more interesting: how does a company try to stay true to itself and our users as it grows? How do we make sure that we advocate for our users, and that the outside world knows that? When we have discussions internally, I&#8217;ve been a fan of the idea of trying to bake the culture into our corporate DNA in different ways, so the culture doesn&#8217;t rely on the personality of a few people.</p><p>DaveN, the Baker/Boser/Shoemoney/TW stories all appeared the night of the 6th. That agrees with what I said in the post, then it got quiet for a while as the web mulled over the claims. The short mention in SEW was on the 7th, and the ClickZ article was on the 8th. I didn&#8217;t say that it didn&#8217;t get written up, just that a) the first write-ups were mostly WMR folks (not BH folks; I don&#8217;t mean to imply that this was a BH thing), and b) not many other people wrote it up, given the considerable claims made for the story.</p><p>CPCcurmudgeon, I agree that geotargeting is a best-effort service; if you see documentation that claims geotargeting to be 100% perfect, please point it out to me so that we can make sure the language is as accurate as possible. In November of 2000 I evaluated geolocation vendors for Google&#8217;s initial implementation of geolocation, so I&#8217;m well aware that no solution is perfect. On the other hand, do you remember the Nazi/Yahoo France case several years ago, where Yahoo claimed it was impossible to determine country-of-origin from an IP address? Measured by that incident, it&#8217;s wonderful that geotargeting has gotten so much more accurate since then.</p> ]]></content:encoded> </item> <item><title>By: CPCcurmudgeon</title><link>http://www.mattcutts.com/blog/watching-a-story-part-ii/#comment-91291</link> <dc:creator>CPCcurmudgeon</dc:creator> <pubDate>Mon, 11 Dec 2006 05:26:20 +0000</pubDate> <guid isPermaLink="false">http://www.mattcutts.com/blog/watching-a-story-part-ii/#comment-91291</guid> <description>I appreciate Matt&#039;s comments on geotargeting.  As it turns out, the AdWords documentation confirms his statements that it may not work correctly all the time.  In fact, there are research papers that discuss the practical limitations of geotargeting, such as http://www.ccsl.carleton.ca/~jamuir/papers/TR-06-05.pdf .  Results can vary widely for many plausible reasons.  Click fraud can have an even worse effect on geotargeting.Perhaps the AdWords documentation can be reworded to describe geotargeting as a best effort service, making it clear to all concerned parties that while efforts are made to target, results cannot be guaranteed.Too bad you&#039;re not on the ads team, Matt.  BTW, I find the operator in the spam protection field difficult to read.  I realize this is intentional, but it might pose problems for people with poor eyesight.</description> <content:encoded><![CDATA[<p>I appreciate Matt&#8217;s comments on geotargeting.  As it turns out, the AdWords documentation confirms his statements that it may not work correctly all the time.  In fact, there are research papers that discuss the practical limitations of geotargeting, such as <a href="http://www.ccsl.carleton.ca/~jamuir/papers/TR-06-05.pdf" rel="nofollow">http://www.ccsl.carleton.ca/~jamuir/papers/TR-06-05.pdf</a> .  Results can vary widely for many plausible reasons.  Click fraud can have an even worse effect on geotargeting.</p><p>Perhaps the AdWords documentation can be reworded to describe geotargeting as a best effort service, making it clear to all concerned parties that while efforts are made to target, results cannot be guaranteed.</p><p>Too bad you&#8217;re not on the ads team, Matt.  BTW, I find the operator in the spam protection field difficult to read.  I realize this is intentional, but it might pose problems for people with poor eyesight.</p> ]]></content:encoded> </item> <item><title>By: DaveN</title><link>http://www.mattcutts.com/blog/watching-a-story-part-ii/#comment-91277</link> <dc:creator>DaveN</dc:creator> <pubDate>Mon, 11 Dec 2006 01:18:00 +0000</pubDate> <guid isPermaLink="false">http://www.mattcutts.com/blog/watching-a-story-part-ii/#comment-91277</guid> <description>added you said thatThe first phase of the story was fascinating because other than Loren Baker, pretty much the only write-ups the first night were from WebmasterRadio (WMR) hosts:http://blog.searchenginewatch.com/blog/061207-180311 http://www.clickz.com/showPage.html?page=3624150hmmm the date on that seems tell a different tale but then again it depends what your job is, Yours is fighting spam not reading the news I  guess..http://www.google.com/search?hl=en&amp;lr=&amp;safe=off&amp;client=firefox-a&amp;rls=org.mozilla%3Aen-US%3Aofficial&amp;hs=YQZ&amp;q=mattcutts.com&amp;btnG=Searchyou might want to clean up the proxy stuff and tiny url stuff and the edu stuff .. :) but then again bad serps is good for adwords ...DaveNI&#039;m glad these post where pointed out to me</description> <content:encoded><![CDATA[<p>added you said that</p><p>The first phase of the story was fascinating because other than Loren Baker, pretty much the only write-ups the first night were from WebmasterRadio (WMR) hosts:</p><p><a href="http://blog.searchenginewatch.com/blog/061207-180311" rel="nofollow">http://blog.searchenginewatch.com/blog/061207-180311</a><br /> <a href="http://www.clickz.com/showPage.html?page=3624150" rel="nofollow">http://www.clickz.com/showPage.html?page=3624150</a></p><p>hmmm the date on that seems tell a different tale but then again it depends what your job is, Yours is fighting spam not reading the news I  guess..</p><p><a href="http://www.google.com/search?hl=en&#038;lr=&#038;safe=off&#038;client=firefox-a&#038;rls=org.mozilla%3Aen-US%3Aofficial&#038;hs=YQZ&#038;q=mattcutts.com&#038;btnG=Search" rel="nofollow">http://www.google.com/search?hl=en&#038;lr=&#038;safe=off&#038;client=firefox-a&#038;rls=org.mozilla%3Aen-US%3Aofficial&#038;hs=YQZ&#038;q=mattcutts.com&#038;btnG=Search</a></p><p>you might want to clean up the proxy stuff and tiny url stuff and the edu stuff .. <img src='http://www.mattcutts.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> but then again bad serps is good for adwords &#8230;</p><p>DaveN</p><p>I&#8217;m glad these post where pointed out to me</p> ]]></content:encoded> </item> <item><title>By: DaveN</title><link>http://www.mattcutts.com/blog/watching-a-story-part-ii/#comment-91270</link> <dc:creator>DaveN</dc:creator> <pubDate>Mon, 11 Dec 2006 00:39:49 +0000</pubDate> <guid isPermaLink="false">http://www.mattcutts.com/blog/watching-a-story-part-ii/#comment-91270</guid> <description>Matt wtf  ...- Threadwatch started a discussion called “Is Google Funding Al Qaeda &amp; Hezbollah Terrorist Groups”. Threadwatch is co-owned by David Naylor, who co-hosts the Strikepoint show on WebmasterRadio.Debunk all you want but don&#039;t try make out this is some BH hat thing against google .... thats all I will say In Public .. on this at this time .. in fact if google needs infomation then they can go Via the correct channels.DaveN</description> <content:encoded><![CDATA[<p>Matt wtf  &#8230;</p><p>- Threadwatch started a discussion called “Is Google Funding Al Qaeda &amp; Hezbollah Terrorist Groups”. Threadwatch is co-owned by David Naylor, who co-hosts the Strikepoint show on WebmasterRadio.</p><p>Debunk all you want but don&#8217;t try make out this is some BH hat thing against google &#8230;. thats all I will say In Public .. on this at this time .. in fact if google needs infomation then they can go Via the correct channels.</p><p>DaveN</p> ]]></content:encoded> </item> <item><title>By: Joe Holcomb</title><link>http://www.mattcutts.com/blog/watching-a-story-part-ii/#comment-91248</link> <dc:creator>Joe Holcomb</dc:creator> <pubDate>Sun, 10 Dec 2006 22:44:12 +0000</pubDate> <guid isPermaLink="false">http://www.mattcutts.com/blog/watching-a-story-part-ii/#comment-91248</guid> <description>Don&#039;t dream too much longer Rob.  What you want is indeed coming.  Whether the current top guns like it or not.</description> <content:encoded><![CDATA[<p>Don&#8217;t dream too much longer Rob.  What you want is indeed coming.  Whether the current top guns like it or not.</p> ]]></content:encoded> </item> </channel> </rss>
<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk
Page Caching using disk (enhanced)
Database Caching 4/11 queries in 0.004 seconds using disk

Served from: www.mattcutts.com @ 2012-02-08 23:36:05 -->
