wrote:

>
> On 2-May-2005, John Bokma <john@castleamber.com> wrote:
>
>> > Can you think of a good reason to use a framed site that can't be
>> > achieved with a non framed site though? That's what I meant.
>
> If a menu is on every page then every page changes if an update
> changes the menu (from experience this seems to upset only
> Google) but then they are the most important.

Never had problems with this. This sounds like: a page edit upsets
Google.

> If there is a sizeable menu on each page (makes for a very
> friendly, easy to navigate site, particularly if links to already
> visited pages change colour)

Has nothing to do with frames, the colour change afaik.

> then the sizeable menu gets
> downloaded as part of every page, slows page loading and
> wastes bandwidth.

The overhead of a frameset can waste more bandwidth, and slow more down.
Depends on how many pages the visitor is going to watch.

> With an iframe the heads date/time/size data shouldn't
> change, only that for the iframe and any changed pages.
>
> Not sure if Google would notice the single page iframe
> change,

Of course, it's a stand alone page. Google doesn't "see" frames, only
links to pages and pages.

> and the one or two changed pages. I'm testing
> this theory at the moment. Giving only a few pages their
> iframe version, they look just the same. Speeds up
> page load, though for the first visit the iframe is uncached,
> so you get a blank white screen momentarily, then
> the iframe appears. Subsequent pages seem to use the
> browser cached iframe.

Of course, it's a stand alone page.

--
John Perl SEO tools: http://johnbokma.com/perl/
Experienced (web) developer: http://castleamber.com/
Get a SEO report of your site for just 100 USD:
http://johnbokma.com/websitedesign/seo-expert-help.html