On site SEO

BigBoris

Regular Member
Joined
Jan 5, 2011
Messages
207
Reaction score
50
Willing to pay someone to sort a few problems i have!

W3 validator org says i have 76 errors and 1 warning on my home page, home page is pretty simple so not sure how this has happened.

Also got a trial version of Website Auditor and ran my site through that and IBP trial version.

There seems to be errors all over the place! keyword density wrong etc etc

Any BHW SEO masters wana take a few hours and sort the on site SEO on my 5 page biz site?
 
Go and run the number one ranking site in your niche through the validator and see how many errors that has!

I wouldn't put too much store in html code errors.

Keyword density? Google can't even see KwD in it's rear-view mirror it's so far in the past!

If your site is not ranking well it is more likely to be due to backlinks, titles, headings, etc.

grab a copy of Market Samurai from this site, watch the tutorials and then run your site through it and see how it measures up.
 
Go and run the number one ranking site in your niche through the validator and see how many errors that has!

I wouldn't put too much store in html code errors.

Keyword density? Google can't even see KwD in it's rear-view mirror it's so far in the past!

If your site is not ranking well it is more likely to be due to backlinks, titles, headings, etc.

grab a copy of Market Samurai from this site, watch the tutorials and then run your site through it and see how it measures up.

Hi thanks for your advice, yeah i did that already
Top 2 competitors have 3 and 33, i have 76 and 1 warning.

I have Website auditor from the same makers of link assistant, rank checker and seo spyglass. The report it gives me is not good :(
 
I honestly stopped checking this stuff a long time ago. As long as your page loads reasonably fast and it renders in all of the browsers ok just leave it be. Most of the issues it finds aren't a big deal.

I would fix the warning though if you can.
 
I honestly stopped checking this stuff a long time ago. As long as your page loads reasonably fast and it renders in all of the browsers ok just leave it be. Most of the issues it finds aren't a big deal.

I would fix the warning though if you can.

Yeah maybe its not such a big deal.

The character encoding specified in the HTTP header (iso-8859-1) is different from the value in the <meta> element (utf-8). I will use the value from the HTTP header (iso-8859-1) for this validation.

Thats the warning i get!
 
Back
Top