<?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: Is W3C Compliance Important For SEO?</title>
	<atom:link href="http://www.vanseodesign.com/seo/is-w3c-compliance-important-for-seo/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.vanseodesign.com/seo/is-w3c-compliance-important-for-seo/</link>
	<description>Helping you build search engine friendly websites</description>
	<lastBuildDate>Tue, 27 Jul 2010 18:07:45 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Steven Bradley</title>
		<link>http://www.vanseodesign.com/seo/is-w3c-compliance-important-for-seo/comment-page-1/#comment-706</link>
		<dc:creator>Steven Bradley</dc:creator>
		<pubDate>Sat, 12 May 2007 00:44:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.vanseodesign.com/blog/uncategorized/is-w3c-compliance-important-for-seo/#comment-706</guid>
		<description>That&#039;s true about the inbound links. There are geeks among us who might want to look at your code before linking to you. If you&#039;re code isn&#039;t validating no link.

I think at some point the accessible search will make its way into the general algorithm too. I&#039;m not sure I agree the spammers are poor coders though. The more obvious ones are, but some of the most profitable spammers are also some of the best coders. It&#039;s what makes them so profitable.

I think the accessible search will eventually find its way in once the U.S. decides it should be taken more seriously. I think we&#039;ll eventually see a certain amount of legal requirements to make a site accessible.

I also think valid code is an indicator of quality. I can understand that search engines care about content first, but I think sites that take the little bit of extra time to meet accessibility compliance are also the sites that have put a little more into the quality of their content as well. Sooner or later search engines will make that connection too.</description>
		<content:encoded><![CDATA[<p>That&#8217;s true about the inbound links. There are geeks among us who might want to look at your code before linking to you. If you&#8217;re code isn&#8217;t validating no link.</p>
<p>I think at some point the accessible search will make its way into the general algorithm too. I&#8217;m not sure I agree the spammers are poor coders though. The more obvious ones are, but some of the most profitable spammers are also some of the best coders. It&#8217;s what makes them so profitable.</p>
<p>I think the accessible search will eventually find its way in once the U.S. decides it should be taken more seriously. I think we&#8217;ll eventually see a certain amount of legal requirements to make a site accessible.</p>
<p>I also think valid code is an indicator of quality. I can understand that search engines care about content first, but I think sites that take the little bit of extra time to meet accessibility compliance are also the sites that have put a little more into the quality of their content as well. Sooner or later search engines will make that connection too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SEFL</title>
		<link>http://www.vanseodesign.com/seo/is-w3c-compliance-important-for-seo/comment-page-1/#comment-705</link>
		<dc:creator>SEFL</dc:creator>
		<pubDate>Fri, 11 May 2007 14:17:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.vanseodesign.com/blog/uncategorized/is-w3c-compliance-important-for-seo/#comment-705</guid>
		<description>This is one of those cases where there are actually benefits, but they&#039;re a little harder to see.

For example, the dam situation created by poor code.   Valid code = no dams = better for SEO than poor code = benefits.

What also needs to be considered in the equation (and never is) is the possibility of organic traffic and inbound links that occur as the result of a combination of a well-coded site and unique content.   Both of these elements will need to be in place (along with design, of course) in order to maximize these types of links.

You also touched on the Accessible Search.  My personal belief is that it&#039;s only a matter of time before accessibility becomes part of the regular algorithm simply because most spammers are poor coders and it would provide an indirect means of algorithmically reducing spam.  It may not be here yet, but it&#039;s coming (at least from Big G&#039;s standpoint.)</description>
		<content:encoded><![CDATA[<p>This is one of those cases where there are actually benefits, but they&#8217;re a little harder to see.</p>
<p>For example, the dam situation created by poor code.   Valid code = no dams = better for SEO than poor code = benefits.</p>
<p>What also needs to be considered in the equation (and never is) is the possibility of organic traffic and inbound links that occur as the result of a combination of a well-coded site and unique content.   Both of these elements will need to be in place (along with design, of course) in order to maximize these types of links.</p>
<p>You also touched on the Accessible Search.  My personal belief is that it&#8217;s only a matter of time before accessibility becomes part of the regular algorithm simply because most spammers are poor coders and it would provide an indirect means of algorithmically reducing spam.  It may not be here yet, but it&#8217;s coming (at least from Big G&#8217;s standpoint.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steven Bradley</title>
		<link>http://www.vanseodesign.com/seo/is-w3c-compliance-important-for-seo/comment-page-1/#comment-704</link>
		<dc:creator>Steven Bradley</dc:creator>
		<pubDate>Tue, 08 May 2007 15:08:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.vanseodesign.com/blog/uncategorized/is-w3c-compliance-important-for-seo/#comment-704</guid>
		<description>Absolutely. And once you go through all the typos and other obvious things I find so many of the validation errors are gone as well. One error in the code can often lead to dozens of validation errors in the report, especially if the error is a closing tag.</description>
		<content:encoded><![CDATA[<p>Absolutely. And once you go through all the typos and other obvious things I find so many of the validation errors are gone as well. One error in the code can often lead to dozens of validation errors in the report, especially if the error is a closing tag.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Forrest</title>
		<link>http://www.vanseodesign.com/seo/is-w3c-compliance-important-for-seo/comment-page-1/#comment-703</link>
		<dc:creator>Forrest</dc:creator>
		<pubDate>Tue, 08 May 2007 15:06:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.vanseodesign.com/blog/uncategorized/is-w3c-compliance-important-for-seo/#comment-703</guid>
		<description>I&#039;ve noticed the same thing about validation errors generally predicting which pages are going to work on some browsers and not others.  You need to go a little bit further if you&#039;re using png files, but for simple mistakes ( like [script src=&quot;x&quot; /] or [?a] instead of [/a] ) it&#039;s much, much easier to learn as soon as possible that you made a typo that needs to be fixed.  The missing alt attribute report is as handy as it is important, too.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve noticed the same thing about validation errors generally predicting which pages are going to work on some browsers and not others.  You need to go a little bit further if you&#8217;re using png files, but for simple mistakes ( like [script src="x" /] or [?a] instead of [/a] ) it&#8217;s much, much easier to learn as soon as possible that you made a typo that needs to be fixed.  The missing alt attribute report is as handy as it is important, too.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
