Meta refresh and frame-based site?

How to get rid of the meta refresh?

[chanda7]

I'm doing SEO work for a client, and they have a frame-based navigation system on ASP. When you initially hit the site, you get a meta refresh and you get taken to either an ASP or html page dependent on whether your browser supports frames (at least that is what I can deduce, FTP is down and I can't get the actual code).

Ideally, they would get rid of the frames. However, until they do, how can we get rid of this meta refresh index page?

Thanks,
Chanda

[mincklerstraat]

If you aren't a javascript wiz, try chopping out the various places javascript is called - including the javascript includes - bit by bit, trying to get the part that does the redirect out of there. It's probably a javascript thingie. You'll need to get at the source code, of course. Try turning off js to get source.

[chanda7]

There is only one line on the page, and it is a meta refresh tag. I guess I wasn't clear on how I was asking the question...What is the best way to deal with frame versus non-frame users? Are most people using simple click-throughs on their index page or is there another alternative? Do you just ignore the non-frame users or will the spiders hate you?

[TheDoctor]

Back in the 1990s, when I used frames, I merely coded up a non-frames menu page in the <noframes> section of my index.html. Since all my links to "home" came back to this page, this was all I needed to cope with users using "noframes" browsers (apart from having to deal with the content pages appearing outside of a frame - but that's another issue).

I don't know if there are any drawbacks with this. There didn't seem to be any.