Clean markup and building with web standards not only helps you do this, but will save you both time and money in the long run. -A“Clean” Markup,: it means free of clutter, standards-compliant, and using the tags and structures of each language for their intended purpose.Do you really think that the major search engines will adhere to special, sloppy coding methods? They’re finicky, and if you are not standards compliant you’re kicking your search ranking in the face-Do’s and Don’ts: DO use tags as they are intended. For example: h1 is the first top-level element on the page, then h2, h3 and so on. There should only be one h1 tag per page. DO name your CSS classes and IDs using meaningful terms, and ask yourself if someone else will know what a class/ID does from its name alone. Which naming convention makes more sense: #box12 or #comment-footer? DO make good use of CSS inheritance. For example: if you set a font on a container, you don’t need to specify it again on every child element unless that child element needs to use a different font. This will keep your style sheets lean and quick to load. DO validate your HTML, CSS and XML and correct as many errors as possible. Pay attention to the warnings generated as well. DO double check WYSIWYG generated code and clean up as necessary. They’re notorious for spitting out bulky, bloated markup with loads of unnecessary, invalid junk. DON’T inject inline styles or extraneous tags and attributes just because you’re in a rush. DON’T settle for “it works.” Just because a page renders it doesn’t mean that the markup under the hood is standards-compliant, problem-free or search engine friendly.