It is told that valid HTML code is the 'right' way to build website. It is also said that valid HTML allows for greater accessibility, cross-browser compatability, and might effect search engine rankings. I have got a link wherein you can validate your site for right HTML. It is here.This is the W3C Markup Validation Service, a free service that checks Web documents in formats like HTML and XHTML for conformance to W3C Recommendations and other standards.

Reply

Hmm i might try this..
if it really does work my rankings would increase

it found 8 errors on my first page :S.

looks like i got some work to do

Reply

It is always good to validate your html, for the same reasons it was said above, but sometimes when you run scripts such as php, you can get content which might not be valid, fixing this kind of content will be a pain to use, so that is why I recommend to use tidy html on your computer even if you're offline. Some browsers do this, some only with addons.

But if you're working with some scripting/programming language which outputs html, you better use/find an editor which will look up the content for errors, css/rss/html - really comfortable, especially if you have a quite big software written in some language, it would be a pain to check everything when you finished, online through the w3c.

But note; that don't try to be always valid, because some things you're using never will be valid, because it is not the standard, but I always try to move to the best alternative. For example HellFire121's title page which I just checked has some errors he would rather fix and nothing will change.

Some people usually say that they don't validate their html, because they say: check google, they are not a valid site, so what ? it does not link to w3c and if you check their source, their main objective is to make it cross-platform friendly and to use as less bandwidth as possible, so they don't use some stuff. Furthermore, modern browsers try to fix the mistakes made by the webmaster to show the content as better as possible, but sometimes this thing is painful, due to you can't see your own errors, but some browsers, usually older has a select box how to show the source, strictly/compatible/etc.

 

 

 

Reply

The key is to write valid (X)HTML/CSS from the start, instead of developing your site then fixing it after it's been completed. This also helps when scripting too, making sure that what you output dynamically is also valid.

As for search ranking, it may improve your rank, because you're capable of accepting a much wider audience if your site is accessible for everyone, which may bring you more traffic because you cater for everyone's needs.

Most companies don't even care about having a site that conforms to standards, but if you can tell them how valid (X)HTML/CSS can increase their revenue, lower their expenses and draw in more customers and in the long run, make it easily maintainable, then you'll be doing a lot better than most the web designers I've come across.

Just remember, comply to the standards, and try to keep it valid, there might be some things that don't validate that you use, I'm positive there would be an alternative to it, because I've rarely come across many problems in my time, but I do await CSS3 which will make creating sites how you want, easier.


Cheers,


MC

Reply

I myself am all for complying with Web standards. I've always thought that the Internet was the perfect medium for global interaction, and standards are a wonderful way to realize this goal.

That said, I don't believe that sticking to these standards will, at least at this point in time, make a difference in SE Ranking. I mean, sny Website that's not standard-compliant but renderable by a browser is invariably guaranteed to be indexed and treated the same by SEs as another one that is fully compliant. And that's a good thing, from the perspectives of Web surfers and SEs.

I mean, SEs are not into the business of enforcing standards. They're into the business of providing Web surfers with Websites that has the information they're searching for. They don't really care if those Websites comply to the standards or not.

Yes, I agree that a compliant Website might have a slight edge to one which isn't. But that edge is really, really slight, that it isn't enough incentive.

Of course, that doesn't mean standards are worthless. Quite the contrary. I think standards can actually make it easier for Webmasters to make their Websites more SE-friendly.

Anyway, to sum up, although I don't believe standards-compliance makes much of a difference to SE Ranking, I still firmly believe that it's a great thing to keep in mind nonetheless.

Reply

Thanks everybody for your interests, suggestions and comments.
Let me directly come on to the topic. While testing some sites for W3C compliance, I found that almost none is cent percent valid. And it has also been reported by the members of different other forums that they had the same experience. So I think, one may not bother too much if there are few errors in their webpages. But I don't want to mean that you can ignore such errors.
Now here is a good suggestion for those using scripting/programming languages.

If someone in this forum is using such an editor for PHP scripts, will you mind telling the name/link of that editor.It'll be of great help for me.
Now comes few views regarding search engine ranking.
So far as search engine ranking goes, as it has already been pointed out, they really care least for valid HTML till date. But you never know what will happen in the near future even.
Finally, I have a question, and frankly speaking, it may appear to be meaningless to you all, but it has bothered me a lot.
I would like to spell out it in little more details.
While validating my site for correct HTML, I really could not find a suitable <!DOCTYPE> declaration. My site uses lots of PHP Scripts. So I used the following declaration :
<!DOCTYPE php PUBLIC "-//W3C//DTD php 4.01 Transitional//EN">
And I observed two things.
1. My CSS got distorted, that means, each <DIV> layer seems to be shifted by few pixels.
2. The brightness of the image appears to improve.
So far as the first observation goes, I corrected it by changing the positions of the <DIV> layers, but regarding the second observation, I am really confused.
Now on changing the <!DOCTYPE> declaration back to :
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd"> - both the position of <DIV> layers and the brightness of images were restored.
Also I tried to validate few other websites having PHP Scripts ( few popular forums) and found that these are not W3C.
Now my question is that, whether there is any other <!DOCTYPE> declaration for pages containg PHP Scripts?
And is there any site that will validate my PHP pages?
Once again, I must say that my question as well as observations may appear funnny but I am helpless. <!DOCTYPE> declaration for PHP pages has really bothered me a lot.

Before leaving, just one more link for those who actually intend to validate their sites for W3C. W3.org provides the necessary guideline for selection of proper document type for your HTML pages.
Regards,
Sid

Reply

It is recommended that your page validates, because you search engine
rankings might be affected if you have a lot of errors on your page or
only fancy features.

Google recommends for example site maps:

"Offer a site map to your users with links that point to the important
parts of your site. If the site map is larger than 100 or so links,
you may want to break the site map into separate pages."
http://www.google.com/webmasters/guidelines.html

Google also recommends that you don't use fancy features everywhere on
your site:

"If fancy features such as Javascript, cookies, session ID's, frames,
DHTML, or Flash keep you from seeing all of your site in a text
browser, then search engine spiders may have trouble crawling your
site."
http://www.google.com/webmasters/guidelines.html

In addition to fancy features you should also have a page with static
links so the Google bots can follow the links:

"Make a site with a clear hierarchy and text links. Every page should
be reachable from at least one static text link."
http://www.google.com/webmasters/guidelines.html

There are other validation services besides W3C. Here are some
validation results for your page http://www.reinhartlaw.com/ :

"I was not able to extract a character encoding labeling from any of
the valid sources for such information. Without encoding information
it is impossible to validate the document."
http://validator.w3.org/

[can't validate]
http://searchengineworld.com/validator/

"CSE HTML Validator Lite v3.50 generated 1 error message, 6 warning
messages, and 2 other messages when checking this web page. These
problems could damage this web page's search engine rankings as well
as cause viewing problems for visitors."
http://www.htmlvalidator.com/lite/onlineval.php

wojta

Reply

There is no DOCTYPE for PHP, because PHP is a scripting language, it's not a web language for documents. You are most likely using PHP to output (X)HTML so you should use a DOCTYPE that works for that language and make sure your scripts output correctly.

I use PHP extensively, I also know what type of documents I'm using it to output which is mostly XHTML 1.1, Everything I do web wise should be standard compliance, everything I want to do web wise will be standard compliance. I don't like IPB because of how many errors it produces, while it tries to conform to XHTML 1.0 Transitional (an easy DOCTYPE to pass in my opinion, yet it fails). IPB still uses deprecated elements for bold, italics and underline, and because it doesn't allow people to modify it, it will remain that way till their developers think seriously about it.

If you're looking for a forum software that does it's best keeping to XHTML 1.0 Strict, then I would have to recommend PunBB which is quite clean, not so many features, and fast to load, which I'm currently looking at cleaning up it's code and implementing more features into it.

As for a PHP editor, tsWebEditor is quite good and another called PHP Developer (I think). It doesn't matter what editor I use, but these ones may help you out.


Cheers,


MC

Reply

Thanks for your reply. And I think, I have got my answer in your post. It is clear that there is no DOCTYPE declaration for PHP. Depending upon the output, I have to choose an appropriate DOCTYPE.
Anyway, I have a specific question regarding Google Adsense and HTML validation. Please look at the code for Adsense for Searches:

"</input>" tags that it contains do not seem to comply with HTML standards. The "<br/>" tags are not XHTML compliant. What to do with those tags?

Regards,
Sid

Reply

Add a space between the 'r' and the backslash.

Reply