Forum Moderators: open
Another benefit of doing that was the fact the meta tags and title including keywords, description and even the small content area was indexed in the search engines as a nice extra benefit. That search engine indexing could be verified by looking at the SE cache or looking at the source code.
Masked/Cloaked frame forwarding (excuse me if that is not the correct term to use) is where the visitor is forwarded to a different website but the URL in the address bar does not change, i.e. example2.com forwards to example.com however the visitor sees example2.com in his browser window.
Recently we discovered that our url masking no longer works in that example.com now appears in the browser (IE) address window instead of example2.com, which always worked before. To clarify, the forwarding still works fine but the problem is the URL masking has stopped. In addition, the SE is no longer indexing example2.com as it did in the past and instead is indexing the example.com site. That can be seen by viewing source code or new SE cache.
Can someone please shed some light on how that masking somehow stopped working? Was it possibly a recent change made by the browser or the search engines?
Is there a work-around by modifying my code below? If there is a solution can someone please say what code modifications are needed? Thanks for feedback and help.
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<title>Widgets website</title>
<meta name="keywords" content="red widgets">
<meta name="description" content="Widgets website">
<base href="http://example2.com/">
<script language="JAVASCRIPT" type="text/javascript">
if (top != self) top.location.href = location.href;
</script>
</head>
<frameset rows='*' frameborder='NO' border='0' framespacing='0' cols='*'>
<frame name='content' src='http://example.com/'></frameset>
<noframes>
<a href='http://example2.com'><font size='+2'>
Our new red Widgets are top quality widgets for all your widget needs. More information about red widgets is next...
</font></a></noframes>
</html>
It isn't clear from your post if the problem is only in MSIE or if you have only checked in MSIE. Guessing the latter I think the most likely reason is a frame busting script in example2.
Thanks for the suggestion tedster. I removed the base href but it made no difference.
Could there be something else involved?
