Google Images & Frame buster code

Does Frame buster prevent new image indexing?

[bumpski]

Recently I've been trying to introduce some new pictures to Google "Images" search. I know it's a long process but in reviewing the images from my site(s) that I now see in the Google Images index, it appears no new images from my site(s) with Frame Buster code have been added to the Google Images index.

Older images that have been indexed for several years remain, but really no sign of more recent images. I've had the Frame Buster code installed for at least a year and a half.

I've been using the "site:" operater to locate all my images. (Also found some copies out there).
Google's Image bot (Googlebot-Image) has crawled these new pictures.

I wish I would have kept closer tabs but I believe quite a few of my images have been dropped by Google Images.

Anybody have a similar experience?

For now I'm pulling the Frame Buster code just to see what happens. I'll probably have to wait two months before I can draw any conclusions though.

[tedster]

Most of the time "frame buster" refers to javascript in the head section of an html document that aims at protecting an entire page from being framed. Since you are speaking of protection for image files, this cannot be what you are using, right? If so, what kind of technology are you using?

[bumpski]

I am speaking of the typical "frame buster" code at the top of the html file to prevent the framing of a sites webpages. (The code I use does support the "back" button properly.)

When you click on an image result of Google Image search Google shows your website's page in a frame. Of course with frame buster code the Google Image's frame is immediately "busted" by this code, and only my webpage is shown. Google may not like this, I don't know. Perhaps they will not index new images from sites that use code to bust Google Image's frame.

It appears I haven't had new images included in the Google Images index in quite a while. I know my robots.txt text is OK. In fact I used Google's test of my robots.txt file (see Google Sitemaps) it said Googlebot-Image would index my site's images.

[tedster]

Thanks for the clarification. I don't have up to date information on this one, but as a general rule, Google does not actually run javascript that it finds (big security risk there). So I find it unlikely that frame busting javascript would keep images out of Google's Image Search.

It does sound like you have noticed a timing pattern though. More reports would be quite welcome.

Yahoo's Image Search runs code that breaks the
frame-buster script and re-frames the page anyway -
clever little buggers. At least Google isn't doing that!

[bumpski]

I guess I was thinking more that Google was just looking for the code versus executing it. There's really only a couple ways to break out of a frame.

Your comment about Yahoo is interesting I'll have to look at their code!

Thanks for your input and if I observe something significant I'll post again. I would like more images indexed.

The images that show at the top of search results can have tremendous value.