Comments on: Is the code validation factor…valid? http://www.bitworm.com/search/2008/is-the-code-validation-factorvalid/ Thoughts from a search geek Thu, 11 Mar 2010 03:19:37 +0000 http://wordpress.org/?v=2.6.1 By: Leila http://www.bitworm.com/search/2008/is-the-code-validation-factorvalid/#comment-7883 Leila Mon, 27 Oct 2008 12:46:41 +0000 http://www.bitworm.com/search/?p=19#comment-7883 Good post. Good post.

]]> By: SEOBandy http://www.bitworm.com/search/2008/is-the-code-validation-factorvalid/#comment-7869 SEOBandy Sat, 06 Sep 2008 09:42:21 +0000 http://www.bitworm.com/search/?p=19#comment-7869 oops I meant on webmaster central.. very tired! ;) lol oops I meant on webmaster central.. very tired! ;) lol

]]> By: SEOBandy http://www.bitworm.com/search/2008/is-the-code-validation-factorvalid/#comment-7868 SEOBandy Sat, 06 Sep 2008 09:30:47 +0000 http://www.bitworm.com/search/?p=19#comment-7868 Thank you bitworm - when writing the article I realize I left out your reasoning which is very important as well. Thank for the clarification I probably should have come to as a conclusion, but overlooked. Yes, sites that are compliant will render properly in all browsers, thus increasing the user experience. I agree and wish to take it one step further. BUT wait.. interesting.. Google seemed to have updated their guidelines today (though I have not been there in a while, so maybe the date of Sept 5 is for some other changes - however!... "Step 1: Ensure browser compatibility by focusing on accessibility The same techniques that make your site more accessible to search engines, such as static HTML versus fancy features like AJAX, often help your site's compatibility on various browsers and numerous browser versions. Simpler HTML is often more easily cross-compatible than the latest techniques. Step 2: Consider validating your code If your code passes validation, you've eliminated one potential issue in browser compatibility. With validated code, you won't need to rely on each browsers' error handling technique. There's a greater chance that your code will function across different browsers, and it's easier to debug potential problems." Seems to support your idea... and the one step further.. If you take the 90-95% of sites on the net that do not worry about code compliance (a stat we have because we do accessibility) and you suddenly lower their rank because of this, how do they make it up? PPC! Lots and lots and lots of PPC. It would be a brilliant monetization plan. The guidelines have always said make your site compliant and accessible. It would not be new, so would not be much anyone could say should they start weighting for it.. Now to add something to the discussion.. go to the Google Accessible Index... these sites are not compliant sites, but cleanly coded sites.. your thoughts? It says for the disabled, but I can assure these sites are not. Seems they would go hand in hand.. a test index for testing compliant code.. But as I keep saying I could be wrong :) Thanks again though for your thoughtful post!! I appreciate the insight! And thank you for noticing I was just making observations from experience - that is where testing begins and that is all I was stating. Hope you have a good day! Smiles! Thank you bitworm - when writing the article I realize I left out your reasoning which is very important as well. Thank for the clarification I probably should have come to as a conclusion, but overlooked. Yes, sites that are compliant will render properly in all browsers, thus increasing the user experience. I agree and wish to take it one step further.

BUT wait.. interesting.. Google seemed to have updated their guidelines today (though I have not been there in a while, so maybe the date of Sept 5 is for some other changes - however!…

“Step 1: Ensure browser compatibility by focusing on accessibility
The same techniques that make your site more accessible to search engines, such as static HTML versus fancy features like AJAX, often help your site’s compatibility on various browsers and numerous browser versions. Simpler HTML is often more easily cross-compatible than the latest techniques.

Step 2: Consider validating your code
If your code passes validation, you’ve eliminated one potential issue in browser compatibility. With validated code, you won’t need to rely on each browsers’ error handling technique. There’s a greater chance that your code will function across different browsers, and it’s easier to debug potential problems.”

Seems to support your idea…
and the one step further..
If you take the 90-95% of sites on the net that do not worry about code compliance (a stat we have because we do accessibility) and you suddenly lower their rank because of this, how do they make it up? PPC! Lots and lots and lots of PPC. It would be a brilliant monetization plan. The guidelines have always said make your site compliant and accessible. It would not be new, so would not be much anyone could say should they start weighting for it..

Now to add something to the discussion.. go to the Google Accessible Index… these sites are not compliant sites, but cleanly coded sites.. your thoughts? It says for the disabled, but I can assure these sites are not.

Seems they would go hand in hand.. a test index for testing compliant code..

But as I keep saying I could be wrong :)
Thanks again though for your thoughtful post!! I appreciate the insight!
And thank you for noticing I was just making observations from experience - that is where testing begins and that is all I was stating.

Hope you have a good day!
Smiles!

]]>