![]() ![]() |
Hall of Famer![]() ![]() Group: Hall Of Fame
Joined: 3-November 05
Posts: 3,461
From: CHeeseland
|
Dec 22 2006, 01:16 PM |
|
|
An interesting comment by Adam Lasnik in the Google Groups thread Is W3C validation really essential for Google to list my site ?
QUOTE Our Googlebot is amazingly persistent and resourceful and is given antacids each day before he crawls. Seriously... I don't want to discourage anyone from validating their site; however, unless it's REALLY broken, we're likely going to be able to spider it pretty decently. It's more important -- from a Google-friendly site perspective -- that your site adheres to our guidelines and is broadly accessible (serverwise, browserwise, platformwise, etc.) Being more specific: I'm betting that in the vast majority of cases in which folks have indexing or ranking concerns, the core issue is NOT that their site doesn't perfectly validate. So "really broken" is bad, "accessible" is good, and those who don't know where to look and start to get a page to validate in order to get it indexed are looking in the wrong place :-). But how much is "really broken" and how accessible does it have to be? Are we starting the discussion all over again? John |
||
| Offline | ![]() |
Moderator Alumni![]() Group: Hall Of Fame
Joined: 31-August 02
Posts: 15,634
|
Dec 22 2006, 02:25 PM |
|
|
I look at validation in a couple of ways.
The first is to help me catch any stupid errors that I may have made. It's like having a free proofreader. The second is to help mitigate risk, in case something is really wrong, and it might cause problems with something getting indexed. And you know, spidering a site "pretty decently" is fine and good, but I don't think that there's anything wrong with wanting to try to do the best you can on a site. There's nothing wrong with aiming towards accessible pages, or pages that look good in different browsers. I spent a couple of months in 2005 training someone in SEO who had an incredible amount of education and experience in standards based html coding and had been the lead accessibility person on some major federal US government web sites. What made that a lot of fun was explaining where semantically meaningful uses of standards could make it easier for search engines to understand the contents of pages, and their connections to other pages on the same site. I recently researched and wrote about how search engines are looking at segmenting pages for handhelds, and it was pretty obvious that having better control over your code and the way it is presented would mean that it would be better presented on a smaller screen through some proxy service though a Google or Nokia, or other potential point of access. That breaking down of pages, and segmenting them may have implications for SEO in a number of ways, because they may provide opportunities for the search engines to understand pages better. For example, it might be preferable to pull snippets from the main content of a page instead of a footer or sidebar, if there is no meta description or it doesn't contain the keywords used in the query that the page showed up in search results for. The value of links could be calculated differently if they were in headings, or footers, or sidebars, or main content areas. Duplicate content filtering might be more meaningful if it could focus upon the main content section of a page. And keyword or phrase indexing might also be more meaningful if those words were from an content area, then say, a footer. Sure, even text files will get indexed. But, there's a chance that the text in an <h2> in a sidebar isn't as important to a page as the text in an <h2> in the main content of a page. Is this something a search engine is presently looking at? I don't know. Here's a blog post I wrote a while back about how Google might handle navigation when trying to take large pages and put them on small screens: Google Indentifies Navigation Bars for Small Screens, Snippets, and Indexing Here's a snippet: QUOTE The primary focus of this patent is on identifying navigation bars on a page that can safely be re-written or changed in some manner for display on a smaller screen. An integral part of the process involves actually identifying navigation bars. It’s probably important that the patent mentions (briefly) that this identification can be helpful in indexing a page and deciding upon which text to use to provide snippets to searchers, which goes beyond the reauthoring process. Considering the ways in which search engines may want to manipulate the content of a site, and possibly even rewrite parts of it, I want as much control over the code as possible. So yes, search engine spiders are forgiving of bad code. But, how much control do you want to turn over to them in their ranking and presentation of your site to others? |
||
| Offline | ![]() |
Moderator Alumni![]() Group: Hall Of Fame
Joined: 31-August 02
Posts: 15,634
|
Dec 22 2006, 02:54 PM |
|
|
I've heard good things about these books:
Gradiva Couzin and Jennifer Grappone's Search Engine Optimization: An Hour a Day Bill Hunt and Mike Moran's Search Engine Marketing, Inc.: Driving Search Traffic to Your Company's Web Site Aaron's SEO Book and Dan's Search Engine Marketing Kit also introduce the concepts of SEO at an early level of knowledge, and include advanced topics as well. |
||
| Offline | ![]() |
Technical Administrator![]() ![]() Group: Technical Administrators
Joined: 8-March 06
Posts: 2,650
From: Minneapolis/Saint Paul, MN
|
Jan 23 2007, 11:49 AM |
|
|
I wrote an article recently on the subject of validation - Beyond Validation. I was shooting from the perspective of accessibility, but SEO has some very similar issues. Basically, what I said is that validation is nothing but a minor tool - it doesn't tell you anything about whether you've used semantic code, whether you've made barriers to use via javascript, whether you've chose impossible to read color combinations, or whether you've nested 300 tables with all inline styles inside each other to create your design.
Validation is extremely important from a standards commitment perspective - but it's very important to remember that validation really only means that you've written HTML or XHTML which matches the syntax rules laid down by the W3C - and that's really not saying that much. The W3C rules aren't all that strict. |
||
| Offline | ![]() |
![]()
|
|
| Lo-Fi Version | Time is now: 9th February 2010 - 02:53 PM |
| Meet our Moderators: | cre8pc : projectphp : sanity : Black Phoenix : bwelford : EGOL : Ruud : rustybrick : AbleReach : swainzy : joedolson: eKstreme: dazzlindonna : SEOigloo: iamlost : RisaBB |