<?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: SEO Techniques that Don&#8217;t work</title>
	<atom:link href="http://blog.curvine.com/2010/02/17/seo-techniques-that-dont-work/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.curvine.com/2010/02/17/seo-techniques-that-dont-work/</link>
	<description></description>
	<lastBuildDate>Mon, 24 Oct 2011 18:38:16 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: jason</title>
		<link>http://blog.curvine.com/2010/02/17/seo-techniques-that-dont-work/comment-page-1/#comment-1052</link>
		<dc:creator>jason</dc:creator>
		<pubDate>Thu, 18 Feb 2010 22:25:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.curvine.com/wordpress/?p=212#comment-1052</guid>
		<description>Vanessa,
Thank you for writing: Maybe I should add this to my list of myths! There was a time where search engines couldn&#039;t handle Web sites that had unusual characters in the URLs. For example:

http://www.example.com/example.html would be indexed without difficulty
http://www.example.com/example.php?id=123&amp;page=445 would not be indexed or would be less likely to be indexed.

The 2nd example was a URL that a Web site that is run by a database would generate. Today, that is not the case for two reasons. First, search engines have matured and can now index pages with these characters. Second, database Web sites can now rewrite the URL so that even a database Web site can have a URL that is more like:
http://www.example.com/example.html</description>
		<content:encoded><![CDATA[<p>Vanessa,<br />
Thank you for writing: Maybe I should add this to my list of myths! There was a time where search engines couldn&#8217;t handle Web sites that had unusual characters in the URLs. For example:</p>
<p><a href="http://www.example.com/example.html" rel="nofollow">http://www.example.com/example.html</a> would be indexed without difficulty<br />
<a href="http://www.example.com/example.php?id=123&#038;page=445" rel="nofollow">http://www.example.com/example.php?id=123&#038;page=445</a> would not be indexed or would be less likely to be indexed.</p>
<p>The 2nd example was a URL that a Web site that is run by a database would generate. Today, that is not the case for two reasons. First, search engines have matured and can now index pages with these characters. Second, database Web sites can now rewrite the URL so that even a database Web site can have a URL that is more like:<br />
<a href="http://www.example.com/example.html" rel="nofollow">http://www.example.com/example.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vanessa Schaefer</title>
		<link>http://blog.curvine.com/2010/02/17/seo-techniques-that-dont-work/comment-page-1/#comment-1051</link>
		<dc:creator>Vanessa Schaefer</dc:creator>
		<pubDate>Thu, 18 Feb 2010 22:15:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.curvine.com/wordpress/?p=212#comment-1051</guid>
		<description>Great topic! Here&#039;s a myth I&#039;d like debunking: Is content in a database (such as JOOMLA) &quot;harder&quot; for search engines to &quot;find&quot;? Why or why not?</description>
		<content:encoded><![CDATA[<p>Great topic! Here&#8217;s a myth I&#8217;d like debunking: Is content in a database (such as JOOMLA) &#8220;harder&#8221; for search engines to &#8220;find&#8221;? Why or why not?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

