<?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: How Google Treats&#160;Punctuation</title>
	<atom:link href="http://www.searchenginejournal.com/how-google-treats-punctuation/10073/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.searchenginejournal.com/how-google-treats-punctuation/10073/</link>
	<description></description>
	<lastBuildDate>Tue, 14 Feb 2012 12:56:44 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: malcolm coles</title>
		<link>http://www.searchenginejournal.com/how-google-treats-punctuation/10073/comment-page-1/#comment-1147054</link>
		<dc:creator>malcolm coles</dc:creator>
		<pubDate>Tue, 17 Nov 2009 13:44:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.searchenginejournal.com/?p=10073#comment-1147054</guid>
		<description>Does anyone have any experience of google&#039;s treatment of apostophes? As far as I can tell, if you do an intitle search for the word I&#039;m (ie intitle:I&#039;m), then Google won&#039;t return results where the word I&#039;m is rendered as I &amp; #039; m in the HTML (Extra spaces added to avoid code getting changed to apostrophe).

As wordpress etc change the &#039; to its ASCII code like this, this stops pages ranking well for searches that include the words I&#039;m.

Does anyone have any experience of this?!? (Here&#039;s an example: this search: http://bit.ly/OeGgT doesn&#039;t return this: http://bit.ly/4jZxlo/)</description>
		<content:encoded><![CDATA[<p>Does anyone have any experience of google&#8217;s treatment of apostophes? As far as I can tell, if you do an intitle search for the word I&#8217;m (ie intitle:I&#8217;m), then Google won&#8217;t return results where the word I&#8217;m is rendered as I &amp; #039; m in the HTML (Extra spaces added to avoid code getting changed to apostrophe).</p>
<p>As wordpress etc change the &#8216; to its ASCII code like this, this stops pages ranking well for searches that include the words I&#8217;m.</p>
<p>Does anyone have any experience of this?!? (Here&#8217;s an example: this search: <a href="http://bit.ly/OeGgT" rel="nofollow">http://bit.ly/OeGgT</a> doesn&#8217;t return this: <a href="http://bit.ly/4jZxlo/" rel="nofollow">http://bit.ly/4jZxlo/</a>)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott @ scottydonald.com</title>
		<link>http://www.searchenginejournal.com/how-google-treats-punctuation/10073/comment-page-1/#comment-1099863</link>
		<dc:creator>Scott @ scottydonald.com</dc:creator>
		<pubDate>Fri, 08 May 2009 07:45:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.searchenginejournal.com/?p=10073#comment-1099863</guid>
		<description>thanks for the post</description>
		<content:encoded><![CDATA[<p>thanks for the post</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: CAP Digisoft Solutions Inc.</title>
		<link>http://www.searchenginejournal.com/how-google-treats-punctuation/10073/comment-page-1/#comment-1099786</link>
		<dc:creator>CAP Digisoft Solutions Inc.</dc:creator>
		<pubDate>Thu, 07 May 2009 11:35:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.searchenginejournal.com/?p=10073#comment-1099786</guid>
		<description>It&#039;s long time since they have changed the algo on using these Punctuation&#039;s. Also there has been some discussion going on this some times back. But while seeing @ the others it&#039;s very sad :(((((((</description>
		<content:encoded><![CDATA[<p>It&#8217;s long time since they have changed the algo on using these Punctuation&#8217;s. Also there has been some discussion going on this some times back. But while seeing @ the others it&#8217;s very sad :(((((((</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ann Smarty</title>
		<link>http://www.searchenginejournal.com/how-google-treats-punctuation/10073/comment-page-1/#comment-1099482</link>
		<dc:creator>Ann Smarty</dc:creator>
		<pubDate>Sun, 03 May 2009 13:27:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.searchenginejournal.com/?p=10073#comment-1099482</guid>
		<description>@Ryan, good question! Unfortunately I have no answer yet, but I&#039;ll do my homework :) 

I used to see this question pop up from time to time, e.g.:
http://www.brainhandles.com/techno-thoughts/ampersands-google-wierdness

Does anyone have any idea?

@niceguyted, thanks for the catch!</description>
		<content:encoded><![CDATA[<p>@Ryan, good question! Unfortunately I have no answer yet, but I&#8217;ll do my homework :) </p>
<p>I used to see this question pop up from time to time, e.g.:<br />
<a href="http://www.brainhandles.com/techno-thoughts/ampersands-google-wierdness" rel="nofollow">http://www.brainhandles.com/techno-thoughts/ampersands-google-wierdness</a></p>
<p>Does anyone have any idea?</p>
<p>@niceguyted, thanks for the catch!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jenny</title>
		<link>http://www.searchenginejournal.com/how-google-treats-punctuation/10073/comment-page-1/#comment-1099356</link>
		<dc:creator>Jenny</dc:creator>
		<pubDate>Fri, 01 May 2009 08:12:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.searchenginejournal.com/?p=10073#comment-1099356</guid>
		<description>Great post. It&#039;s information like this that helps to understand what not to do. I like how it&#039;s understandable in a very clear and concise table, great way of displaying information. All the other comments are informative too. Excellent.</description>
		<content:encoded><![CDATA[<p>Great post. It&#8217;s information like this that helps to understand what not to do. I like how it&#8217;s understandable in a very clear and concise table, great way of displaying information. All the other comments are informative too. Excellent.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: niceguyted</title>
		<link>http://www.searchenginejournal.com/how-google-treats-punctuation/10073/comment-page-1/#comment-1099194</link>
		<dc:creator>niceguyted</dc:creator>
		<pubDate>Tue, 28 Apr 2009 20:43:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.searchenginejournal.com/?p=10073#comment-1099194</guid>
		<description>:  &lt;---  Colon

;  &lt;---  Semicolon

Colons are generally used to signify that a list follows; semicolons are used to connect two individually complete sentences into a single thought.</description>
		<content:encoded><![CDATA[<p>:  &lt;&#8212;  Colon</p>
<p>;  &lt;&#8212;  Semicolon</p>
<p>Colons are generally used to signify that a list follows; semicolons are used to connect two individually complete sentences into a single thought.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mevans05</title>
		<link>http://www.searchenginejournal.com/how-google-treats-punctuation/10073/comment-page-1/#comment-1099178</link>
		<dc:creator>mevans05</dc:creator>
		<pubDate>Tue, 28 Apr 2009 16:38:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.searchenginejournal.com/?p=10073#comment-1099178</guid>
		<description>On a related topic, one thing I haven&#039;t been able to find elsewhere is how the engines treat special characters in URLs. For instance: tildes, umlauts, etc. Has anyone seen any information on this?</description>
		<content:encoded><![CDATA[<p>On a related topic, one thing I haven&#8217;t been able to find elsewhere is how the engines treat special characters in URLs. For instance: tildes, umlauts, etc. Has anyone seen any information on this?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan Smith</title>
		<link>http://www.searchenginejournal.com/how-google-treats-punctuation/10073/comment-page-1/#comment-1099176</link>
		<dc:creator>Ryan Smith</dc:creator>
		<pubDate>Tue, 28 Apr 2009 16:25:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.searchenginejournal.com/?p=10073#comment-1099176</guid>
		<description>Any insight into how Google treats the ampersand?  It seems to read them both as the same but returns different results for (q and a) vs. (q &amp; a).</description>
		<content:encoded><![CDATA[<p>Any insight into how Google treats the ampersand?  It seems to read them both as the same but returns different results for (q and a) vs. (q &amp; a).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: art jewelry</title>
		<link>http://www.searchenginejournal.com/how-google-treats-punctuation/10073/comment-page-1/#comment-1099145</link>
		<dc:creator>art jewelry</dc:creator>
		<pubDate>Tue, 28 Apr 2009 08:59:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.searchenginejournal.com/?p=10073#comment-1099145</guid>
		<description>Great information - would like to see a similar explanation for plural versus singular searches.  There is a difference but it&#039;s not a clear difference.</description>
		<content:encoded><![CDATA[<p>Great information &#8211; would like to see a similar explanation for plural versus singular searches.  There is a difference but it&#8217;s not a clear difference.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://www.searchenginejournal.com/how-google-treats-punctuation/10073/comment-page-1/#comment-1099125</link>
		<dc:creator>John</dc:creator>
		<pubDate>Tue, 28 Apr 2009 01:48:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.searchenginejournal.com/?p=10073#comment-1099125</guid>
		<description>As always, very interesting information. 
Thank you Ann.</description>
		<content:encoded><![CDATA[<p>As always, very interesting information.<br />
Thank you Ann.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

