It sounds as if you are having frame targetting issues due to nested frames. The basic problem is that you are running a framed website under a forwarded domain which itself uses a frame. So you have one 100% frame containing your "real" hosting space, and within that 100% frameset you have another framset containing your site pages. So if you use link targets such as "_top", it will try to replace the 100% frame, not your expected parent frame.

It is difficult to get round such problems. You could try replacing _top with _parent, but the problem may be deeper than that. Your best bet unfortunately would be to stop using a framed forwarded domain and get some real hosting - something that doesn't come free (even if it is reasonably cheap).

Point all links that would ordinarily point to index.html, which contains your frameset, instead to your redirected domain name. This will cause a little slower performance because you are calling on a dns lookup and redirection service back to where you were to begin with, but your search results will be more for your domain name instead of your webhost's name/your account.

You then want to put some descriptive text of your site plus links to your content pages inside the noframes tag. This will let your framed site be seen in the Google results as more than "Your browser does not support frames," or nothing at all.

This will also let people visit your site without the hinderance of frames if they can't use them. It is therefore to also include some navigation links on your content pages and not just on your menu frame.

I used to use frames and they really created some interesting issues, but back then I knew nothing about use of robots.txt, more to be learned by searching for "robots txt" on Google [google.com], with the quotes.

I could have thusly disallowed my menu page from the search results and kept the focus more on the content pages.

Larry