http://www.searchenginejournal.com/google-responds-to-adwords-quality-score-variable-leak/6814/ Latest Search Engine News from the Search Engine Journal Fri, 19 Mar 2010 20:37:12 -0500 http://wordpress.org/?v=abc hourly 1 http://www.searchenginejournal.com/google-responds-to-adwords-quality-score-variable-leak/6814/comment-page-1/#comment-1075997 Jaan Kanellis Fri, 02 May 2008 22:59:52 +0000 http://www.searchenginejournal.com/google-responds-to-adwords-quality-score-variable-leak/6814/#comment-1075997 The statement sounds a lot like goobledegook The statement sounds a lot like goobledegook

]]> http://www.searchenginejournal.com/google-responds-to-adwords-quality-score-variable-leak/6814/comment-page-1/#comment-1075861 George Davis Thu, 01 May 2008 14:36:29 +0000 http://www.searchenginejournal.com/google-responds-to-adwords-quality-score-variable-leak/6814/#comment-1075861 I wouldn't put much stake in the statement. I think it was made to calm the ignorant and confuse the educated. I wouldn’t put much stake in the statement. I think it was made to calm the ignorant and confuse the educated.

]]> http://www.searchenginejournal.com/google-responds-to-adwords-quality-score-variable-leak/6814/comment-page-1/#comment-1075852 RandomJohn Thu, 01 May 2008 11:38:45 +0000 http://www.searchenginejournal.com/google-responds-to-adwords-quality-score-variable-leak/6814/#comment-1075852 Google a lot of news: a new quality parameter, pagerank up:) Google a lot of news: a new quality parameter, pagerank up:)

]]> http://www.searchenginejournal.com/google-responds-to-adwords-quality-score-variable-leak/6814/comment-page-1/#comment-1075847 Adam Thu, 01 May 2008 08:11:30 +0000 http://www.searchenginejournal.com/google-responds-to-adwords-quality-score-variable-leak/6814/#comment-1075847 They said it wasn't systematic - it could be that one datacenter had a debug copy of the code put on it by mistake. The load balancing across datacenters would then make it appear randomly. Remove the bad copy and problem solved. They said it wasn’t systematic – it could be that one datacenter had a debug copy of the code put on it by mistake. The load balancing across datacenters would then make it appear randomly. Remove the bad copy and problem solved.

]]> http://www.searchenginejournal.com/google-responds-to-adwords-quality-score-variable-leak/6814/comment-page-1/#comment-1075839 Michael VanDeMar Thu, 01 May 2008 00:40:14 +0000 http://www.searchenginejournal.com/google-responds-to-adwords-quality-score-variable-leak/6814/#comment-1075839 If it can't be reproduced, then how are they going to do enough debugging to know that they've fixed it...? If it can’t be reproduced, then how are they going to do enough debugging to know that they’ve fixed it…?

]]>