<?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>Think Search &#187; penalty</title>
	<atom:link href="http://www.thinksearch.co.uk/tag/penalty/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.thinksearch.co.uk</link>
	<description>Online Marketing Made Simple</description>
	<lastBuildDate>Tue, 14 Jun 2011 15:02:52 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>GoCompare ranking penalty (again!)</title>
		<link>http://www.thinksearch.co.uk/2009/04/23/gocompare-ranking-penalty-again/</link>
		<comments>http://www.thinksearch.co.uk/2009/04/23/gocompare-ranking-penalty-again/#comments</comments>
		<pubDate>Thu, 23 Apr 2009 21:47:42 +0000</pubDate>
		<dc:creator>Administrator</dc:creator>
				<category><![CDATA[SEO]]></category>
		<category><![CDATA[google]]></category>
		<category><![CDATA[penalty]]></category>

		<guid isPermaLink="false">http://www.thinksearch.co.uk/?p=92</guid>
		<description><![CDATA[Isn&#8217;t it great when the authorities in your field pick up on something that used to be such a hot topic within a much smaller community. I remember the last time round (must have only been a year and a half ago) when GoCompare incurred their last ranking penalty that it was only really picked [...]]]></description>
			<content:encoded><![CDATA[<p>Isn&#8217;t it great when the authorities in your field pick up on something that used to be such a hot topic within a much smaller community. I remember the last time round (must have only been a year and a half ago) when GoCompare incurred their last ranking penalty that it was only really picked up by the SEO community. This time round it was <a href="http://econsultancy.com/blog/3717-has-gocompare-been-given-another-google-penalty" target="_blank">Econsultancy that broke the news</a> which inspired <a href="http://weblogs.hitwise.com/robin-goad/2008/02/google_blacklists_gocompare.html" target="_blank">Hitwise to release free data</a> (wow) backing the story up!</p>
<p>The great thing about stories like this in the SEO community is that it defines boundaries. We all know how crappy Google has been at imposing it&#8217;s own ethical policies and that SEO is all about testing and pushing limits (not on client sites of course!) but it&#8217;s always a good thing to see just how far you can go before you get noticed.</p>
<p>What&#8217;s so funny about the story this time round is that GoCompare are going to suffer much worse than their 6 month drop first time round. This time their media spend is going to have to be enormous to counter their lack in visibility on brand terms. Hell I might even have a bid myself! Thanks again to Google&#8217;s relaxation in trademark bidding policies every man and his dog can bid on GoCompare&#8217;s brand terms and get away with it, making competition all the more expensive.</p>
<p>You&#8217;ve got to love them &#8211; Google and GoCompare too! Here&#8217;s a lovely graph for the wall courtesy of Hitwise.</p>
<div class="wp-caption alignnone" style="width: 538px"><img title="GoCompare loose traffic from Google ban" src="http://www.thinksearch.co.uk/wp-content/uploads/2009/04/gocompare.png" alt="gocompare GoCompare ranking penalty (again!)" width="528" height="410" /><p class="wp-caption-text">GoCompare loose traffic from Google ban</p></div>
<div class="shr-publisher-92"></div>]]></content:encoded>
			<wfw:commentRss>http://www.thinksearch.co.uk/2009/04/23/gocompare-ranking-penalty-again/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

