We are in the process of writing SEO code specifications for East, does anyone have suggestions or want to add anything to the spec before we send it to Rick? Currently it calls for WC3 compliant CSS/XHTML table-less coding that separates presentation (formatting) from behavior (scripting) and content. By using external CSS sheets for presentation, XHTML for framework and external scripting files we significantly increase the code to text ratio of a website, allowing the content to rise to the top so to speak. Additionally we stipulated that the CSS file to include formatting for all comment elements including H1, H2, H3, and that CSS be used to achieve roll over effects instead of javascript and for all scripting to be external rather than inline.I’ve had a great deal of success in the past coding websites in this manner and it’s made a significant difference in each site that I’ve coded. If anyone would like to see a copy before we submit it please let me know and I’ll email it and please let me know if you have any suggestions or additions.
SEO Coding Specifications
September 6th, 2007 Written by: Code Witch --> · 1 Comment
Tags: Code · Announcements
1 response so far ↓
1 Josh Simpson // Sep 20, 2007 at 1:15 am
I’m quite sure you are on the right track here. Where it might help our friends at 02I (east), I want to be able to hand over some more explicit directions and tools.
Of course we will first have to ask them which of the practices you mention they are already fluent & comfortable with. i suspect they will be up to speed on most of it.
I don’t know enough about the replacement of tables with CSS myself, and i’m not sure whether the rest of our team knows that much either.
I wonder how it changes the process or skills involved in everyday HTML editing, if at all?
Assuming that an SEO cares not about altering layout, and only wants to be able to format your text, what does he or she need to know other than how to call a CSS class (or write one if you need one)?
I’m assuming that to “go tableless” means using DIV layers with fixed placement & dimensions, plus a lot more text styles defined in CSS sheet to achieve effects like columns, indentations, etc.
This could confuse some of our otherwise dreamweaver fluent SEOs, including myself!!
I mean, i think it’s something that anyone who speaks basic CSS can get their heads around with a little effort, but it is a consideration in terms of overall cost-benefit.
Regardless, before anything else, i will present these suggestions to O2I and ask for their feedback.
As far as tools go … anyone know a good XHTML/CSS validator we could recommend to our web programmers?
At the risk of stating the obvious, it is a million times easier to code a site in an optimized way the first time than it is to strip out tables and font tags and other clutter and move it over to CSS across an entire site.
That said, for Ultra or Max accounts, you may want to consider dedicating the resources needed to overhaul a site’s code base (maybe anywhere from a 8 to a 20 hr job) … talk to me about if and how we can bring in outside help.
You must log in to post a comment.