Web Standards & W3C Guidelines
The author's views are entirely their own (excluding the unlikely event of hypnosis) and may not always reflect the views of Moz.
Web standards and code validation can often be a boring subject in the SEO and web development world. It's not fun to hack through the W3C's validation complaints about missing alt tags, improperly entered text symbols and incomplete div tags, but it is neccessary.
In a thread at SEOChat, several posters who are more informed than myself on the subject of validation note that Google does give a very slight preference to validated pages (and every little bit helps, right?). They also note that forgetting to inclulde a doctype in the header of a web page tells browsers to use pre-1997 html standards which, while still mostly compatible, can cause some errors.
It is NOT critical for SEOs to insure complete W3C validation on every page of every site they work on. The benefits to SEO and ranking are very minimal. What is critical is taking care to provide a usable and standardized experience for every user. This means testing your site's functionality and visual layout with Mozilla's Firefox, Opera, Internet Explorer & Netscape. It can be a pain, but the value is certainly there.
On the subject of validation, here are some excellent resources pointed out in the thread and other I have dug up myself:
- Web Standards Project - A noble effort to attempt to "fight for standards that reduce the cost and complexity of development".
- Finding the Right Document Type - From A List Apart
- LIFT for Dreamweaver - As a novice coder, I am ashamed to rely on Macromedia's WYSIWYG editor. For those like me, this plug-in software can help to simplify the process of making Dreamweaver code W3C compatible.
- Why & How to Build an Accessible Site - By James Byrne of the Making Connections Unit of Glasgow
Comments
Please keep your comments TAGFEE by following the community etiquette
Comments are closed. Got a burning question? Head to our Q&A section to start a new conversation.