[WEB4LIB] Re: another tangent to Re: Inline forms in CSS problem

Vicki Falkland library at cryptic.rch.unimelb.edu.au
Tue Feb 26 17:32:27 EST 2002


>
>[Second things second: Who invented <NOINDEX>...</NOINDEX> 
>elements?  Proprietary/made-up stuff like that gets more and more likely to 
>screw things up as browsers start expecting you to abide by your doctype 
>declaration.]
>

I am in the process of implementing a search feature on our site using
Atomz (www.atomz.com)
While testing, I noticed that if I searched on a word which happened to be
used in various bits of navigation text, the search results listed every
page in the site and the descriptive text was simply a rehash of the
navigation text. 
Their help files suggest using <noindex></noindex> for any portions of text
I may wish to exclude from being indexed (like navigation!) to correct this
problem.

I shouldn't do this?? How else can I exclude navigation text from being
indexed and ending up in the search results?

V.



More information about the Web4lib mailing list