Google can't cache

Google can't cache my site.

[markdidj]

I have an external JS that reads the location, and creates the page based on the location.

ie mysite.co.uk/folder/file.html
from which I get variables mysite,folder,file

This stops others from putting my site in their frames or site.

Which also stops Google cache-ing my site, as I just noticed they add ( cant see it now cos I think I've just been dropped from the index ), well, they add characters after the location, like "+google&hl=en&ie=UTF-8"

I think this is a bit of a problem?!?!?!?
Enough of a problem to get me dropped?

Something's up :(

[markdidj]

I could correct the JS function quite easily, does the cache result always come from "216.239.33.100"
I could use this to allow Google through my JS, but will this get me indexed again? Is this why I was dropped?

I also use a <noscript><iFrame src="menu.html"></noscript>
menu.html contains HTML links and a bit of text. Could it be this?

I have a dynamic site, which I've spent the entire of last month just trying to improve its SE indexing. I've got rid of my hidden layers, although they were made visible onmouseover, put in my headers and links, alt tabs, alternative navigation, the works. I was waiting in anticipation of seeing green, only to find the page where I should be indexed keeps swapping between 2 pages, the old, where I'm still indexed, and the new, where I am not. Now there's no green or white to be seen :( grey days ahead.

Oh well, and another month goes by........

[jdMorgan]

markdidj,

JavaScript and iFrames don't work well with Google.

You might want to post in the Scripting or Web Site Technology forum, and list out what you really want or need to achieve with all of this. A frame escape which does not affect Google is fairly easy to implement. You may have to wait until Monday/Tuesday for everyone to be there, though.

Jim

[markdidj]

I used to use a frame escaping script, but i've changed it. I don't mind the script not working for people trying to take it as their own.

What I am trying to work out is what has stopped me from getting indexed this time round, when I thought it was programmed better. my JS is external, so it shouldn't be that, it's just the functions not are working in the cached version.

I am wondering if that is why I'm not getting indexed, because the JS is causing an error in the cached version and Google is detecting the error?

If I correct the error will that get me indexed again?
(It would be quite easy if Google left something in the location which can be identified as Google's every visit)

[markdidj]

I've got it to stop the error, and realized only the html gets cached. It uses the current JS, whenever it was placed.
(it still doesn't work, but that's because the wrong HTML is cached)

I think the problem must be the noscript iFrame.
Well, I've got another month to work it out!

wouldn't mind some sort of permanant signature from Google in the location for the cached version. At the moment I open up the site for Google with a indexOf("+"),
Would prefer indexOf("GoogleCached") as well.....

[jdMorgan]

>> Well, I've got another month to work it out!

The deep crawl for next month's index will commence in a few days. Better get on it!

Jim

[markdidj]

>> The deep crawl for next month's index will commence in a few days. Better get on it!

Right, the index is done a month previous......

I used to use hidden layers as I had dynamic text which would appear on mouseover, which I've now changed to a scrolling division. I now focus the relevent division into view instead. Nothing's hidden.

I've done all my updates in the last month, so they wouldn't have been picked up yet?

If my site doesn't appear at all in the index, does that mean the site's banned?