« Rich Sage Brand BuildingUpdate June 2008 »

June 27th, 2008 | by RichSage

Validating HTML

Category: ONLINE SUCCESS, TRAFFIC BUILDING

Validating Your Web Site HTML

After switching to WordPress 2.5.1 and taking on many changes to Rich Sage dot com, I also looked into the very ‘nuts and bolts’ of the code that makes up the site.  I wanted to do what I could to minimize all kinds of problems that lead to less traffic.

Site navigation is very important because of humans navigating the site.  I cannot do much about that as the direction of traffic is dictated by WordPress and the theme.  However, that is only half the traffic picture.  The site is navigated by various bots, including Google, Yahoo and MSN crawlers that catalog everything.

The problem with poor HTML on the site means that these crawlers have a hard time cateloging the content, which of course leads to fewer visitors from the search engines. After a year of online work, search engines are my best generator of traffic, with Google leading the way.

HTML Validating Service at W3C.ORG:  Just enter your URL and the script will let you know how many errors you have.

Validating HTML


Steps I take to Validate HTML, While Writing in WordPress:

First of all I use the visual editor in WordPress Admin.  When I upgraded to the latest WordPress, I used the html editor, but that resulted in dozens of HTML errors.  Now using the WordPress VISUAL editor, my errors are down to a few -occasionally, none.

More about my HTML Validating Process…

Since you want to validate the HTML before publishing your posts, WordPress enables you to preview the post that you’ve written.  What I do is press the “PREVIEW THIS POST” button and take the resulting URL and post it in the W3C HTML validate page.

WordPress ADMIN Area

IF after you validate your temporary page and there are too many errors, you can select the HTML tab in the WordPress admin and work on correcting the mistakes.  You may have countless mistakes especially if you ‘cut and pasted’ text from another publishing program.

Now that you’ve looked into the errors and corrected as many as you could, you can proceed to publishing your post.  This pre-posting care will go a long way to helping you get the best results from all the “digital visitors” you receive.

Carpe Diem,
Rich Sage

  • Popularity: 60% [?]
You might be interested in those posts as well:

RSS feed | Trackback URI

2 Comments »

collapseicon Comment by g1smd
2008-06-27 11:08:10

I use the HTML Validator extension for Firefox instead.

Just look for the Green Tick in the bottom right to know the code is 100% correct.

If there is a yellow exclamation mark or a red cross, then click it to bring up a list of errors.

 
collapseicon Comment by RichSage
2008-06-27 11:36:19

Well, I can almost agree with you. The problem with what you suggest is the it’s a yes or no type of issue. Either you have a perfect score or there is a problem. The advantage of the validation at W3C is that you can pick the worst problems and address them quickly.

I don’t look for perfection in the HTML –just good behavior. I’ve looked at several other sites, like shoemoney, which has hundreds of errors in the last post!

So, I don’t spend a lot of time trying to ‘get each post’ perfect.

RS.

 

Your Comment (smaller size | larger size)

You may use these HTML tags:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> .