Forum Moderators: martinibuster

Message Too Old, No Replies

Funny Stop Word experience

Stop! In the name of love...

         

wizarddave

10:29 pm on Oct 26, 2005 (gmt 0)



One of my sites is news aggregation. I have built into the system the ability to flag a story so that the listing on my site can have this text appended: [WARNING: This site sometimes contains Adult Language]

I haven't flagged a story like that possibly since I started with AS. I did one today, and, understandably now that I think about it, the page started getting alternate ads. (Removing the text made AS ads come back.)

Of course, the text "this site" in my warning means the site in the link, not my site. But I can see why a bot would misunderstand it.

Can anyone suggest a wording for this warning which won't set off the word police?

Thanks.

jurii

10:33 pm on Oct 26, 2005 (gmt 0)

10+ Year Member



Use a graphic ;-)

incrediBILL

10:48 pm on Oct 26, 2005 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Here's something I learned the other day that certain stop words appear to have more impact towards the top of the page than they do at the bottom of the page. I know I have a stop word on 2 pages and it's at the top of one, no ads, bottom of the other, full ads.

That was an eye opener in itself!

jomaxx

1:36 am on Oct 27, 2005 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



BTW, I doubt the ambiguous meaning of "this site" was the problem. Bots do not literally parse your sentence and try to comprehend it. Probably the words "warning" and "adult language" tripped the stopwords filter.

I would start by removing the all-caps WARNING and simply say "site may contain adult language". See what happens. If your first reaction was to provide a warning, then you should probably include one of some kind.

wizarddave

1:58 am on Oct 27, 2005 (gmt 0)



I was half-kidding about the interpretation of "this site" and assumed it was the condition of the words "adult" and "language" being together that caused the problem.

I solved the problem by changing the warning to a graphic. I hope that's not against TOS somewhere...