View Full Version : W3C compliance
gaydemon_jr
03-19-2008, 05:25 AM
Who here makes sure all their sites validate? I see so many sites that don't validate. Does validating your website mean more people can see your site therefore more sales?
TropixxxMichael
03-19-2008, 06:36 AM
Who here makes sure all their sites validate? I see so many sites that don't validate. Does validating your website mean more people can see your site therefore more sales?
I don't even have the slightest clue what you are talking about...
Nicedreams
03-19-2008, 08:12 AM
I validate our pages both html and css. I'm not sure if more people can see it, but I like doing it to check the coding.
Jimmy
Gaystoryman
03-19-2008, 09:48 AM
They say, cleaner the code, the better for all those hungry SE bots.. so it makes sense but isn't that easy for novices or rookies, given that both IE & Firefox render things differently. So it is a good idea, but oiy, what a pain in the ass it is... and not the good kind..
gaydemon_jr
03-19-2008, 09:53 AM
Yeah, definitely a pain, but a necessary evil maybe?
I find my site looks the same in both IE and firefox when it fully validates. Clean, efficient code is good for search engines.
http://validator.w3.org/
The W3 validator tells you exactly where and on what line it finds an error so you can fix it. Definitely worth the time spent I think.
Gaystoryman
03-19-2008, 10:34 AM
Yeah, definitely a pain, but a necessary evil maybe?
I find my site looks the same in both IE and firefox when it fully validates. Clean, efficient code is good for search engines.
http://validator.w3.org/
The W3 validator tells you exactly where and on what line it finds an error so you can fix it. Definitely worth the time spent I think.
True but all those red marks and warnings I get, it is like having a hot boyfriend, who you think you satisfied, only to read in the morning paper how limp your dick was... it is deflating and so depressing when all you see is 'warning' after 'warning' after 'warning' after... :bang:
TropixxxMichael
03-19-2008, 11:18 AM
Yeah, definitely a pain, but a necessary evil maybe?
I find my site looks the same in both IE and firefox when it fully validates. Clean, efficient code is good for search engines.
http://validator.w3.org/
The W3 validator tells you exactly where and on what line it finds an error so you can fix it. Definitely worth the time spent I think.
Ok, so I just go there and type in my URL, then click check?
When I did that, all it said was "Congratulations this page is XHTML 1.0 Transitional."
So that is a good thing right? If there was a problem I am guessing it would have said something else?