Cache: command. Ambiguous results

[SlyOldDog]

Any Google gurus out there?

I have a site which shows no cache when I use the cache: command in Google.

However when I seach for site: I see it indexed, and cached. If I click the cache link I see a cache.

The main difference in the google URL is some sort of document ID. Here is what I see in google's own cache...

[209.85.135.104...]

The variable cache:zhool8dxBV4J only appears when you are not using the cache command. So what is the significance of being cached one way but not the other? I am stumped.

[SlyOldDog]

<bump>

C'mon guys. Doesn't anyone know?

[tedster]

Are those results conflicting results always on the same ip address, or does it happen for any data center?

[SlyOldDog]

Yes tedster.

If i look up the cache by clicking the "cached" page in google it goes to this data centre.

[209.85.135.104...]

If i perform the cache: command in this datacentre (i.e. without the document reference) my index page is unfound.

[ashear]

How long as this been going on?

[SlyOldDog]

I've seen it on 2 of my domains. It's been like it for months.

[ashear]

Strange, sounds like a filter that may be causing issues.

[SlyOldDog]

yes, I'm curious to see what PR I have in the next update on those sites.

They still rank for on page text...

[Whitey]

This has been reported on several posts [ including a few by myself ) but i don't recall any definitive explanations.

There is potentially some correlation to the site: command, which also acts without regularity[ IMO ]