Re: frames compatibility

> Would that still hold true with a framed site that had (comprehensive)
<.NO
> FRAMES> content?

It depends on what the definition of "is" is to repeat an often used (gag!)
phrase.  Infoseek will work with <.no-frames> tags, but the only sure way
for the other SE's is to have a frame area and a non-frame area for them.
If you have ever seen websites with a frame/no-frame choice at the home
page, you will know how to build it. Liberal use of the "no-index" and
"no-follow"  meta tags in the framed section would keep the SE's out of that
part of the website so that the website is not penalized for frames.  I use
this to keep them out of my shopping cart pages because we found CGI chokes
some spiders too.

We decided two areas was almost as much work as two separate websites and
not worth the effort just for the convenience of having the framed menus.
We are interested in the utility, but not at the loss in business caused by
it.

We looked at early versions of layering to see if we could get the same
effect, downside was poor compatibility.  We are thinking in database driven
XML server side delivery but are not sure about SE's reaction to that.  As a
matter of fact I have seen almost nothing written on the subject of XML and
SE's.

Paul Wilson
webgooru(at)gte.net

HTML: hwg-basics mailing list archives, maintained by Webmasters @ IWA