<?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: Another adCenter bug</title>
	<atom:link href="http://www.web1marketing.com/blog/index.php/archives/another-adcenter-bug/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.web1marketing.com/blog/index.php/archives/another-adcenter-bug/</link>
	<description>News and Views on SEO, SEM, and Web Design</description>
	<lastBuildDate>Thu, 08 Sep 2011 20:16:09 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Josh</title>
		<link>http://www.web1marketing.com/blog/index.php/archives/another-adcenter-bug/comment-page-1/#comment-36957</link>
		<dc:creator>Josh</dc:creator>
		<pubDate>Tue, 09 Jun 2009 17:07:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.web1marketing.com/blog/?p=536#comment-36957</guid>
		<description>These are good points, C0rk, although this contradicts the meaning of exact and phrase match. While in most cases the conjunctions / stop words will not have an appreciable impact, it would be good to be able to test this. There are some cases where stop words could make a significant difference in meaning. As a somewhat silly example, if I am interested in searching for or selling the book &quot;The Cat in the Hat&quot;, I would not want my query to be normalized to &quot;cat hat,&quot; a search for feline clothing. I suspect that most instances where this is a problem would be branded searches.</description>
		<content:encoded><![CDATA[<p>These are good points, C0rk, although this contradicts the meaning of exact and phrase match. While in most cases the conjunctions / stop words will not have an appreciable impact, it would be good to be able to test this. There are some cases where stop words could make a significant difference in meaning. As a somewhat silly example, if I am interested in searching for or selling the book &#8220;The Cat in the Hat&#8221;, I would not want my query to be normalized to &#8220;cat hat,&#8221; a search for feline clothing. I suspect that most instances where this is a problem would be branded searches.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: C0rk</title>
		<link>http://www.web1marketing.com/blog/index.php/archives/another-adcenter-bug/comment-page-1/#comment-36956</link>
		<dc:creator>C0rk</dc:creator>
		<pubDate>Tue, 09 Jun 2009 16:57:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.web1marketing.com/blog/?p=536#comment-36956</guid>
		<description>This occurs due to an adCenter process known as &#039;normalization&#039; where extraneous/stop words like &#039;or&#039;, &#039;and&#039;, and &#039;to&#039; and special characters like &quot;?&quot;, &quot;!&quot;, and &quot;#&quot; are removed and/or ignored.

In adCenter&#039;s matching, the KW &quot;bike-repair&quot; will match the query &quot;bike repair&quot; and the query &quot;bike-repair&quot;, so there is no need to add all variants.

adCenter is essentially preventing your from adding KWs that would otherwise be treated as duplicates in terms of their matching. However, this does not account for the lack of &#039;reactive messaging&#039; which should be provided or the concern you raise about the value of being able to bid/link conjunctions differently. (Are you optimizing conjunctions differently?)

It&#039;s important to note that normalization does NOT account for plural forms, so be sure to add those.

You can find more details about normalization by going to the adCenter help section and searching for &quot;normalization&quot;.</description>
		<content:encoded><![CDATA[<p>This occurs due to an adCenter process known as &#8216;normalization&#8217; where extraneous/stop words like &#8216;or&#8217;, &#8216;and&#8217;, and &#8216;to&#8217; and special characters like &#8220;?&#8221;, &#8220;!&#8221;, and &#8220;#&#8221; are removed and/or ignored.</p>
<p>In adCenter&#8217;s matching, the KW &#8220;bike-repair&#8221; will match the query &#8220;bike repair&#8221; and the query &#8220;bike-repair&#8221;, so there is no need to add all variants.</p>
<p>adCenter is essentially preventing your from adding KWs that would otherwise be treated as duplicates in terms of their matching. However, this does not account for the lack of &#8216;reactive messaging&#8217; which should be provided or the concern you raise about the value of being able to bid/link conjunctions differently. (Are you optimizing conjunctions differently?)</p>
<p>It&#8217;s important to note that normalization does NOT account for plural forms, so be sure to add those.</p>
<p>You can find more details about normalization by going to the adCenter help section and searching for &#8220;normalization&#8221;.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

