Welcome to WebmasterWorld Guest from 54.161.228.30

Forum Moderators: phranque

Message Too Old, No Replies

My site is framed by another site - the drawbacks?

Should i implement an unframing script immediately?

   
9:33 pm on Dec 18, 2005 (gmt 0)

10+ Year Member



I discovered today that my site is framed by another site (without permission of course). The page with frameset has my site's url in its title.
What are the drawbacks of this? Should i implement an unframing script immediately?
Thanks in advance.
10:01 pm on Dec 18, 2005 (gmt 0)

WebmasterWorld Senior Member tedster is a WebmasterWorld Top Contributor of All Time 10+ Year Member



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)

10+ Year Member



Thanks, tedster.

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)

WebmasterWorld Senior Member tedster is a WebmasterWorld Top Contributor of All Time 10+ Year Member



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".

2. Yes, that's one possible framebuster javascript -- it should work OK.

8:27 pm on Dec 19, 2005 (gmt 0)

10+ Year Member



Thanks a lot.
So, Yahoo considered it as a duplicated content?
3:31 am on Dec 20, 2005 (gmt 0)

WebmasterWorld Senior Member tedster is a WebmasterWorld Top Contributor of All Time 10+ Year Member



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)

10+ Year Member



Thanks again.