css & keywords

Do you have a question? Post it now! No Registration Necessary.  Now with pictures!

Threaded View
Does it help at all to write your css classes as keywords.

If your keyword is 'umbrellas', does it help to make a class '.umbrellas',
rather than let's say '.footer-text'?

Re: css & keywords

g dulli wrote:

Quoted text here. Click to load it

Except that it would make your site harder to maintain, it won't make a
difference. And I don't have proof for that. (Just common sense.)

Re: css & keywords

Quoted text here. Click to load it

Oh, please don't guess and draw such a quick conclusion. Google's
algorithm is a subject for discussion these days and I wouldn't be surprised
at all if they check *ALL* the text in the HTML document to see if the user has
deliberately tried to optimize the page. And in that case you might get minus
points for keyword stuffing.

Nobody knows, but my recommendation is to avoid that kind of things and
concentrate on the real content instead.

Re: css & keywords

Quoted text here. Click to load it

It would be silly for Google to penalise keywords in classes, and I have
seen no evidence at all of this: in fact I have sites that do (not
particularly for SEO reasons) which are doing very well.  

There are perfectly good reasons to use keywords in css classes.

You have one site, 4 sections, widgets, grommits, doodads and

What could be more natural than to give them, say, different highlight
colours using:

body id="widgets"
body id="grommits"
body id="doodads"
body id="thingummies"

to make it clearer which section the user is in?  

Then in theory you could set other properties using

 #doodads a
 #thingummies h1
 # widgets ul a:hover

but I don't think it would be unnatural to set a class of say

.doodad-bottomlinks instead if you were finding some browsers having
problems with inheritance.

This doesn't make the site harder to maintain either: it make it easier.

Clare Associates Ltd
http://www.clareassoc.co.uk /
01822 835802

Site Timeline