I guess I am a little amused by people trying to SEO their sites, with out thinking about the Optimization part of the equation. They want their page to come up as first in Google, but they don't really think about the rest of it. All that is fine by me, to me it means that people are finally driven to care about the mess of HTML code that they are leaving behind.
Editors like this one, and Front-Page(the granddaddy of all hateful editors) have been leaving junk codes behind them in volumns (petrabytes per day I am sure), with people happily adding their words, and as long as it "looks right on my screen" that is good enough. Along comes Google, and they disregaurded the meta tags. And SEO was born.
I like SEO because the goal is to produce a page that can be read by a none-human agent! If Google can make contextual sense out of a page, then maybe a Reader like JAWS (used by the blind) will stand half an chance to wade through the mess in the backend.
To futher this goal of making clean pages, I put my styles out-side of my markup (in CSS files where they belong), I post a doc-type (which is more then simply rendering instructions) and I use a FULL SET OF HTML TAGS. Yes and I will say it again, A FULL SET. This includes the LABEL element, the EM, STRONG, FIELDSET, THEAD, CAPTION, LEGEND, TH, TBODY, TFOOT, BLOCKQUOTE, DL, DT, DD, CODE, Q, BIG, BUTTON, SUP, SUB, PRE, ADDRESS and SMALL. These very nice tags are simply ignored by my industry and I don't know why.
Let me state my case. Using a full set of tags increases the level of understanding that a rendering agent (like the GoogleBot) will have for your document. If the goal of GoogleBot is to make sense of your document, via contextual linking, then a full set of tags is a way for you to Tutor GoogleBot about what portion of your document is important (your keywords). And before any of the SEO guys tell me that only TITLE and H1 and B are important and read, I will remind you that the Google guys are UberGeeks and they care strongly about these things also.
Regards,
Comments(12)