Validation
Web pages are written in the HTML or XHTML language. Like any language there are certain ground rules or standards. The process of testing a page against these standards is called validation . The HTML standards are defined by the World Wide Web consortium (www.w3c.org).
They help web authors to write pages that can be used by a variety of different browsers, Internet Explorer, Firefox, Safari or even Lynx. Despite these standards the world of HTML seems somewhat anarchic. This sentiment stems from the browser wars of the mid 90s when Netscape and Micrsoft added new features to HTML with scant regard for standards. There is a feeling among some SEOers that standards are not important for search engine ranking and there is some truth in this. Point enough inbound-links at an junk page with good anchor text and Google will probably end up returning that page in its results. This feeling is reinforced by statement from Google: "Any parser which is designed to run on the entire Web must handle a huge array of possible errors. These range from typos in HTML tags to kilobytes of zeros in the middle of a tag, non-ASCII characters, HTML tags nested hundreds deep, and a great variety of other errors that challenge anyone's imagination to come up with equally creative ones.
In other words, forget standards, our search engine will sort out your HTML spaghetti whatever. hile this may have been true when Google relied heavily on its PageRank algorithm it certainly won't prove true as search engines move into better understanding of the semantics of page. It is easy for some web authors to forget that HTML is not a formatting language but a mark-up language. It describes the structure of the document in terms of Title elements, Heading levels, Lists, Quotations etc. While these are on-page elements and therefore prone to manipulation they still give the search element clues to the meaning of the page. Even worse, syntax errors with HTML tags may cause the search engine to confuse content and mark-up or to give the wrong significance to parts of the page. In order to use a validation tool to trap errors the first thing to decide is which standard you are going to follow. The most popular, partially because it is the most flexible is 4.01 Transitional . Add a Doctype element at the start of each page to tell your clients, web browsers, validation and tools and potentially robots (although they almost certainly don't use this information) that you are following this standard: !DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" Some web authoring tools do this for you. Once your page is online you can go the the W3C's validator at and enter the address of your page. A common error is missing ALT text from images although some web authoring tools produce very poor code.Apart from indicating to search engine algorithms the structure of your page, validated HTML is easier for third parties such as web design companies and search engine optimization consultants to work on. It will also make the code more portable between different web authoring packages.
Although many sites rank well without adhering to standards, validation should help protect your site from changes to the way browsers and search engines work. Certainly if you are optimizing code professionally it should adhere to one of the standards.On a related topic some web developers and optimizers like to get an idea of how their snazzy page will render on simple browsers. If validated HTML is used along with style sheets for formatting, graphically interesting pages shouldn't present any problems. The Lynx web browser is often used for this purpose as it is a text only web browser. If you don't want to install Lynx the following website aims to emulate the output and is useful for giving an idea of how readable the content is.





