<?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: Expanded Broad Match Corrupted Around Aug 20 &#8212; Stop Using It!</title>
	<atom:link href="http://www.semclubhouse.com/expanded-broad-match-googles-eps-earning-per-share-equalizer/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.semclubhouse.com/expanded-broad-match-googles-eps-earning-per-share-equalizer/</link>
	<description></description>
	<lastBuildDate>Wed, 28 Jul 2010 00:45:36 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Chris</title>
		<link>http://www.semclubhouse.com/expanded-broad-match-googles-eps-earning-per-share-equalizer/comment-page-1/#comment-1238</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Tue, 15 Jun 2010 14:23:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.semclubhouse.com/expanded-broad-match-googles-eps-earning-per-share-equalizer.html#comment-1238</guid>
		<description>How come this isnt illegal, since we never signed up for (in the original ToS) a service that primarily hurts both my PPC campaign and my wallet?  

For Pete&#039;s sake  - we paid $5.49 for &#039;Electronic Data Interchange&#039; to have it show up for &quot;albanian english dictionary&quot;.  I can&#039;t even do a 6 degrees of separation here...</description>
		<content:encoded><![CDATA[<p>How come this isnt illegal, since we never signed up for (in the original ToS) a service that primarily hurts both my PPC campaign and my wallet?  </p>
<p>For Pete&#8217;s sake  &#8211; we paid $5.49 for &#8216;Electronic Data Interchange&#8217; to have it show up for &#8220;albanian english dictionary&#8221;.  I can&#8217;t even do a 6 degrees of separation here&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AdWords&#8217; Expanded Broad Match and the &#8220;1-2 Punch&#8221; Are Eating Your Click Money &#124; Clix Marketing PPC Blog</title>
		<link>http://www.semclubhouse.com/expanded-broad-match-googles-eps-earning-per-share-equalizer/comment-page-1/#comment-406</link>
		<dc:creator>AdWords&#8217; Expanded Broad Match and the &#8220;1-2 Punch&#8221; Are Eating Your Click Money &#124; Clix Marketing PPC Blog</dc:creator>
		<pubDate>Mon, 09 Mar 2009 12:37:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.semclubhouse.com/expanded-broad-match-googles-eps-earning-per-share-equalizer.html#comment-406</guid>
		<description>[...] and Mike Churchill wrote two excellent posts on the topic here and here. The second post describes the &#8220;1-2 Punch&#8221; phenomenon that we too have [...]</description>
		<content:encoded><![CDATA[<p>[...] and Mike Churchill wrote two excellent posts on the topic here and here. The second post describes the &#8220;1-2 Punch&#8221; phenomenon that we too have [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alan Rimm-Kaufman</title>
		<link>http://www.semclubhouse.com/expanded-broad-match-googles-eps-earning-per-share-equalizer/comment-page-1/#comment-365</link>
		<dc:creator>Alan Rimm-Kaufman</dc:creator>
		<pubDate>Fri, 23 Jan 2009 12:27:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.semclubhouse.com/expanded-broad-match-googles-eps-earning-per-share-equalizer.html#comment-365</guid>
		<description>More info on broad match error:

http://www.rimmkaufman.com/rkgblog/2009/01/21/google-broad-match/</description>
		<content:encoded><![CDATA[<p>More info on broad match error:</p>
<p><a href="http://www.rimmkaufman.com/rkgblog/2009/01/21/google-broad-match/" rel="nofollow">http://www.rimmkaufman.com/rkgblog/2009/01/21/google-broad-match/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Expanded Broad Match - Google Adwords &#124; Blog de posicionamiento web en buscadores (SEO) y marketing online</title>
		<link>http://www.semclubhouse.com/expanded-broad-match-googles-eps-earning-per-share-equalizer/comment-page-1/#comment-25</link>
		<dc:creator>Expanded Broad Match - Google Adwords &#124; Blog de posicionamiento web en buscadores (SEO) y marketing online</dc:creator>
		<pubDate>Wed, 05 Mar 2008 08:46:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.semclubhouse.com/expanded-broad-match-googles-eps-earning-per-share-equalizer.html#comment-25</guid>
		<description>[...] Para m&#225;s informaci&#243;n&#160;ver aqu&#237; [...]</description>
		<content:encoded><![CDATA[<p>[...] Para m&aacute;s informaci&oacute;n&nbsp;ver aqu&iacute; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: WordPress SEO</title>
		<link>http://www.semclubhouse.com/expanded-broad-match-googles-eps-earning-per-share-equalizer/comment-page-1/#comment-24</link>
		<dc:creator>WordPress SEO</dc:creator>
		<pubDate>Mon, 05 Nov 2007 11:37:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.semclubhouse.com/expanded-broad-match-googles-eps-earning-per-share-equalizer.html#comment-24</guid>
		<description>Thanks for the writeup Jim.

After we got burned in August, we followed your exact advice: &lt;a title=&quot;&quot; href=&quot;http://foliovision.com/2007/11/05/adwords-expanded-broad-match/&quot; rel=&quot;nofollow&quot;&gt;don&#039;t use AdWords broad match&lt;/a&gt; at all to avoid expanded broad match altogether. Check out the awful sales numbers I got out of &lt;strong&gt;expanded broad match&lt;/strong&gt; and how much better things look &lt;strong&gt;without broad match at all&lt;/strong&gt;.</description>
		<content:encoded><![CDATA[<p>Thanks for the writeup Jim.</p>
<p>After we got burned in August, we followed your exact advice: <a title="" href="http://foliovision.com/2007/11/05/adwords-expanded-broad-match/" rel="nofollow">don&#8217;t use AdWords broad match</a> at all to avoid expanded broad match altogether. Check out the awful sales numbers I got out of <strong>expanded broad match</strong> and how much better things look <strong>without broad match at all</strong>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: How to Make Money with AdWords: No Broad Match, No Expanded Match</title>
		<link>http://www.semclubhouse.com/expanded-broad-match-googles-eps-earning-per-share-equalizer/comment-page-1/#comment-23</link>
		<dc:creator>How to Make Money with AdWords: No Broad Match, No Expanded Match</dc:creator>
		<pubDate>Mon, 05 Nov 2007 10:53:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.semclubhouse.com/expanded-broad-match-googles-eps-earning-per-share-equalizer.html#comment-23</guid>
		<description>[...] Their recommendation is also to just stop using broad match. The put the blame on the new feature on Google trying to meet Wall Street quarterly targets: [...]</description>
		<content:encoded><![CDATA[<p>[...] Their recommendation is also to just stop using broad match. The put the blame on the new feature on Google trying to meet Wall Street quarterly targets: [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carl Parry</title>
		<link>http://www.semclubhouse.com/expanded-broad-match-googles-eps-earning-per-share-equalizer/comment-page-1/#comment-22</link>
		<dc:creator>Carl Parry</dc:creator>
		<pubDate>Mon, 15 Oct 2007 23:05:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.semclubhouse.com/expanded-broad-match-googles-eps-earning-per-share-equalizer.html#comment-22</guid>
		<description>Yeah we picked this up too;
http://forums.digital-m.co.za/showthread.php?t=2278

But we think we have evidence that &quot;broad match&quot; was expanded to include a user&#039;s search history, and not just semantic variations of a search phrase. It makes sense to try this if you think about it - at least for users anyway. If someone does a search for &quot;apple&quot; then Google have a lot better chance of matching an ad if historically you&#039;ve made a lot of searches for computer terms, music, or fruit; but for us it&#039;s not worked out well. I agree, Google can&#039;t lose here.</description>
		<content:encoded><![CDATA[<p>Yeah we picked this up too;<br />
<a href="http://forums.digital-m.co.za/showthread.php?t=2278" rel="nofollow">http://forums.digital-m.co.za/showthread.php?t=2278</a></p>
<p>But we think we have evidence that &#8220;broad match&#8221; was expanded to include a user&#8217;s search history, and not just semantic variations of a search phrase. It makes sense to try this if you think about it &#8211; at least for users anyway. If someone does a search for &#8220;apple&#8221; then Google have a lot better chance of matching an ad if historically you&#8217;ve made a lot of searches for computer terms, music, or fruit; but for us it&#8217;s not worked out well. I agree, Google can&#8217;t lose here.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: LynnS</title>
		<link>http://www.semclubhouse.com/expanded-broad-match-googles-eps-earning-per-share-equalizer/comment-page-1/#comment-21</link>
		<dc:creator>LynnS</dc:creator>
		<pubDate>Mon, 15 Oct 2007 18:18:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.semclubhouse.com/expanded-broad-match-googles-eps-earning-per-share-equalizer.html#comment-21</guid>
		<description>Wow - Thanks. I have been fighting that for over 6 weeks. At least now, I know where to look to make the correction.</description>
		<content:encoded><![CDATA[<p>Wow &#8211; Thanks. I have been fighting that for over 6 weeks. At least now, I know where to look to make the correction.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Terry Howard</title>
		<link>http://www.semclubhouse.com/expanded-broad-match-googles-eps-earning-per-share-equalizer/comment-page-1/#comment-20</link>
		<dc:creator>Terry Howard</dc:creator>
		<pubDate>Sat, 13 Oct 2007 04:35:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.semclubhouse.com/expanded-broad-match-googles-eps-earning-per-share-equalizer.html#comment-20</guid>
		<description>Nice article. The more pressure that can be put on them about this, the better. Expanded broad match is a crock. Previous to implementing an extensive and ever expanding negative keyword strategy, maybe 10% of the terms in the search query report for broad match were relevant. Another 50% were totally irrelevant horrible matches (everything from &quot;used jeans&quot; to &quot;wholesale automatic weapons&quot;) and the rest, well, let&#039;s say they ranged from cartoon sex clips to things that get people put into sex offender databases. Let me tell you, it&#039;s great to learn a client&#039;s brand was associated with that.</description>
		<content:encoded><![CDATA[<p>Nice article. The more pressure that can be put on them about this, the better. Expanded broad match is a crock. Previous to implementing an extensive and ever expanding negative keyword strategy, maybe 10% of the terms in the search query report for broad match were relevant. Another 50% were totally irrelevant horrible matches (everything from &#8220;used jeans&#8221; to &#8220;wholesale automatic weapons&#8221;) and the rest, well, let&#8217;s say they ranged from cartoon sex clips to things that get people put into sex offender databases. Let me tell you, it&#8217;s great to learn a client&#8217;s brand was associated with that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam Audette</title>
		<link>http://www.semclubhouse.com/expanded-broad-match-googles-eps-earning-per-share-equalizer/comment-page-1/#comment-19</link>
		<dc:creator>Adam Audette</dc:creator>
		<pubDate>Fri, 12 Oct 2007 19:12:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.semclubhouse.com/expanded-broad-match-googles-eps-earning-per-share-equalizer.html#comment-19</guid>
		<description>We&#039;ve been dealing w/ the exact same issue, started about late Aug and really peaked into the &quot;sphere of awful&quot; about 10 days ago. Cost:conversion was through the roof. We notched back the main offenders using phrase and exact, left a few proven phrases in broad, and are watching closely.

This has such a dramatic effect on ROI it&#039;s just silly for Google to do. Need to throttle that down. Then again why not keep it aggressively broad if you&#039;re Google? The big fish with huge spends probably don&#039;t even notice or care, while the smaller players who are careful about conversion costs get hammered.</description>
		<content:encoded><![CDATA[<p>We&#8217;ve been dealing w/ the exact same issue, started about late Aug and really peaked into the &#8220;sphere of awful&#8221; about 10 days ago. Cost:conversion was through the roof. We notched back the main offenders using phrase and exact, left a few proven phrases in broad, and are watching closely.</p>
<p>This has such a dramatic effect on ROI it&#8217;s just silly for Google to do. Need to throttle that down. Then again why not keep it aggressively broad if you&#8217;re Google? The big fish with huge spends probably don&#8217;t even notice or care, while the smaller players who are careful about conversion costs get hammered.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
