<?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: W3C Compliance Impact on&#160;SEO</title>
	<atom:link href="http://www.searchenginejournal.com/w3c-compliance-impact-on-seo/4846/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.searchenginejournal.com/w3c-compliance-impact-on-seo/4846/</link>
	<description></description>
	<lastBuildDate>Tue, 14 Feb 2012 14:29:13 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: Sean</title>
		<link>http://www.searchenginejournal.com/w3c-compliance-impact-on-seo/4846/comment-page-1/#comment-1083630</link>
		<dc:creator>Sean</dc:creator>
		<pubDate>Tue, 05 Aug 2008 08:18:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.searchenginejournal.com/w3c-compliance-impact-on-seo/4846/#comment-1083630</guid>
		<description>@Michael - Thanks for the posting the stonetemple.com link. Lasnik does say that compliance isn&#039;t taken into account by Google when ranking but also: &quot;...unless it is ... really bad HTML with lots of accidentally open tags...&quot;

Surely the easiest way of avoiding bad HTML is to check it for compliance?</description>
		<content:encoded><![CDATA[<p>@Michael &#8211; Thanks for the posting the stonetemple.com link. Lasnik does say that compliance isn&#8217;t taken into account by Google when ranking but also: &#8220;&#8230;unless it is &#8230; really bad HTML with lots of accidentally open tags&#8230;&#8221;</p>
<p>Surely the easiest way of avoiding bad HTML is to check it for compliance?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 北京翻译公司</title>
		<link>http://www.searchenginejournal.com/w3c-compliance-impact-on-seo/4846/comment-page-1/#comment-459232</link>
		<dc:creator>北京翻译公司</dc:creator>
		<pubDate>Sun, 06 May 2007 04:13:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.searchenginejournal.com/w3c-compliance-impact-on-seo/4846/#comment-459232</guid>
		<description>I do a lot of training for people that want to do SEO themselves, and the best way to describe how search engines read a web page is an analogy:  Search engines read your web page like a college professor reads a research paper.</description>
		<content:encoded><![CDATA[<p>I do a lot of training for people that want to do SEO themselves, and the best way to describe how search engines read a web page is an analogy:  Search engines read your web page like a college professor reads a research paper.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Josh</title>
		<link>http://www.searchenginejournal.com/w3c-compliance-impact-on-seo/4846/comment-page-1/#comment-459231</link>
		<dc:creator>Josh</dc:creator>
		<pubDate>Sun, 06 May 2007 04:12:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.searchenginejournal.com/w3c-compliance-impact-on-seo/4846/#comment-459231</guid>
		<description>Validating code may not affect your SEO, but I definitely agree with Graywolf&#039;s comment about mobile devices.  If starting a new site from scratch I would recommend XHTML Strict that validates and that takes into account the possiblity of being viewed on mobile devices.</description>
		<content:encoded><![CDATA[<p>Validating code may not affect your SEO, but I definitely agree with Graywolf&#8217;s comment about mobile devices.  If starting a new site from scratch I would recommend XHTML Strict that validates and that takes into account the possiblity of being viewed on mobile devices.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Johan</title>
		<link>http://www.searchenginejournal.com/w3c-compliance-impact-on-seo/4846/comment-page-1/#comment-458959</link>
		<dc:creator>Johan</dc:creator>
		<pubDate>Sat, 05 May 2007 15:57:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.searchenginejournal.com/w3c-compliance-impact-on-seo/4846/#comment-458959</guid>
		<description>Matt Cutts has also confirmed that Google does not look at compliance when it comes to ranking pages. 

I am not surprised, considering that google&#039;s pages do not validate, it would be surprising if they enforced it upon others.</description>
		<content:encoded><![CDATA[<p>Matt Cutts has also confirmed that Google does not look at compliance when it comes to ranking pages. </p>
<p>I am not surprised, considering that google&#8217;s pages do not validate, it would be surprising if they enforced it upon others.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Martinez</title>
		<link>http://www.searchenginejournal.com/w3c-compliance-impact-on-seo/4846/comment-page-1/#comment-458337</link>
		<dc:creator>Michael Martinez</dc:creator>
		<pubDate>Fri, 04 May 2007 16:17:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.searchenginejournal.com/w3c-compliance-impact-on-seo/4846/#comment-458337</guid>
		<description>As far as Google optimization is concerned, Adam Lasnik has just confirmed that they pay absolutely no attention to W3C compliance in their algorithm.

http://www.stonetemple.com/articles/interview-adam-lasnik.shtml</description>
		<content:encoded><![CDATA[<p>As far as Google optimization is concerned, Adam Lasnik has just confirmed that they pay absolutely no attention to W3C compliance in their algorithm.</p>
<p><a href="http://www.stonetemple.com/articles/interview-adam-lasnik.shtml" rel="nofollow">http://www.stonetemple.com/articles/interview-adam-lasnik.shtml</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

