Yes, it's another of my little polls.

This is a must need with many of those badly written 'made for adsense' sites - if 10000 people use them, google will drop their rankings. Simply making them W3C compliant will change their 'footprint' and make you different from the 9999 others.

Advantages of validating - tends to be more streamlined code = faster loading; tends to more accessible = meets with legal requirements; tends to more obvious to understand = better if you share the website with other coders; tend to look similar across multiple browsers and platforms (e.g. PC, WAP etc) = more visitors.

See http://validator.w3.org/.

a nice point you have made there regarding the made for adsense site... well i have just started making simple websites using html and css... but i dont validate it as of yet.. but once i am doing learn the language fully i will surely get the site validated ...

It has been a great use for me.. thanks.. I never thought of validating any of codings.. I mean.. what ever I know.. I learned it all myself... but I was ignorent about validating the codes.. But.. even thought I didn't validate any of my codings.. I fixed some of my problems because.. When I opened it in a FireFox browser.. they showed me some errors.. and where it is.. so I was able to fix that.. thanks anyway...

I've been validating my code at w3.org.

I hadn't realized about the subdomain, though. That's going to save me time.

Another thing to note is that it's good to validate often as you develop. Not to mention I've found these validators to be a tremendously helpful debugging tool as I've been learning CSS.

Like so many things that cascade, CSS can be hard to find bugs in. On a big project, twenty seconds with the validator can save you minutes of trying to find out which stylesheet has the extra period in it's font-size property and caused your text to dissapear, or some other CSS issue.

In the software development industry, there's a saying that goes "release early and release often". I'm just as comfortable telling a web developer to "validate early and validate often"

Thanks for the link. I never remember the URL, and have been browsing from the home page/index a lot!

I don't validate my website HTML code. I just look at the websites with different web browsers and if they come out all right, that's good enough for me.

I do validate my clients websites before actually releasing it. I also do testing on various browser and resolutions.

Creating a site without validating code is like proofreading a written article: yes it may not seem to be broken or anything, but there's stuff that may be better tweaked/improved upon.

I realy Never thought of it..........

I always validate (strct xhtml ftw!!) to make sure all my pages are correct. It also helps with the removal of extra tags if I so happen to accidentally add them. Lastly, it's also just cool to have the site show up with no errors upon it's validation.

Only probably in the past 6 months have I started to validate my css and since doing so it has mad the coding alot easier like said above with extra bits that shouldn't be there such as periods, semi-colons etc.

I'm suprised though, I thought pretty much everyone would be validating their pages. lol

I had never thought about validating my code. Now that I have read this thread it is like food for thought.

May need to start validating my pages. Thanks for the information. Very useful.