| 10:01 pm on Dec 18, 2005 (gmt 0)|
Anyone coming to your site inside the frame will not easily be able to bookmark your pages -- that's the first drawback that comes to mind. I would implement a framebuster script.
There is also some potential search engine confusion -- and that's something that a frame-busting will not fix. This kind of hijack is not "supposed" to happen these days, but sometimes it still does. Just keep an occasional eye out for that and, if you see it, then let the SE involved know. I've had such a problem in the past year or so, and got great cooperation to fix it.
| 11:32 pm on Dec 18, 2005 (gmt 0)|
Would you be so kind to tell a little bit more about "search engine confusion" problem that you've had in the past, please?
And, would adding "if (self!= top) top.location.href = self.location.href;" suffice?
| 4:13 am on Dec 19, 2005 (gmt 0)|
1. The framing site began to be listed for the content on my client's site and the site itslef no longer came up -- this was on Yahoo Search. I wrote to Yahoo and it was fixed after a couple months. They thanked me for the "data point".
| 8:27 pm on Dec 19, 2005 (gmt 0)|
Thanks a lot.
So, Yahoo considered it as a duplicated content?
| 3:31 am on Dec 20, 2005 (gmt 0)|
No, this wasn't duplicate content -- the content was never on the other domain the way it would be with a scraper site or content thief. This was a glitch in the algo (at that time) that allowed a framing site to hijack the framed pages in the search results, much the same as the Google 302 bug did.
From what I can see, this bug at Yahoo is now fixed, but it was supposed to be fixed long before my clients fell victim to it so I am watchful and wary. In this case the framing site was friendly and "trying to help".
| 8:58 pm on Dec 20, 2005 (gmt 0)|