<laugh> Well, I cetainly don't want to use techniques like this myself, but
there are clever ways to spam that the engines can't detect. I know because
I see it all the time in the SERPS. I am certainly not an expert on CSS/SEO
spamming though :)

Chris

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Ted Drake
Sent: Thursday, February 03, 2005 11:42 AM
To: [email protected]
Subject: [WSG] cover me -- I'm gonna be naughty!

The recent discussion of css and seo had me wondering.

I have convinced the big wigs that although search engine rankings are very
important, and they are with our very competitive keyword, we need to
maintain accessibility. I have kept our alt tags pure, our h1 tags are using
an image replacement technique, but still are not filled with spam.  We use
no <noscript> spam or doorway pages.

However, I have been thinking, hmmmm could we spam an h4 tag and put a
class="spam", clever huh?  Then move the text off screen in the main style
sheet, display none in the print style sheet... normal, although unethical
stuff so far.  But what about the screen reader. It certainly would be
unfair for them to hear their screen reader emphasize spam words and because
of that I am against the idea.

However, we have that media="aural" descriptor.  Could I set up a new aural
css with .spam {display:none;}?

For those covering your ears and eyes screaming NOOOOOOOO! I know it is a
bad thing to spam your keywords. But if we need to do it to be competitive,
would this at least protect those that are innocent, the people who need to
use screenreaders?

Ted
******************************************************
The discussion list for  http://webstandardsgroup.org/

 See http://webstandardsgroup.org/mail/guidelines.cfm
 for some hints on posting to the list & getting help
******************************************************



******************************************************
The discussion list for  http://webstandardsgroup.org/

 See http://webstandardsgroup.org/mail/guidelines.cfm
 for some hints on posting to the list & getting help
******************************************************

Reply via email to