When cloaking slips up....

A strange search snippet showed a cloaking error

[georged]

I was searching for a niche phrase not related to the optimization industry, just to see who was up to what.

The #1 result, which was IMO a fair result, had the following snippet in the Google serps, which I have paraphrased as to the particulars of the url (except the scooter bit):

<snip>

Now I don't do cloaking, mostly because I would probably routinely produce that kind of error, so purely for information I'd like to know what could cause this kind of SNAFU?

Was it the doubled-up forward-slash around the Scooter bit? Is it just that the page wasn't found for whatever reason? Something else?

Does anyone have any general comments regarding cloaking and potential foul-ups that they would add in light of the above example?

[edited by: Brett_Tabke at 2:34 am (utc) on Mar. 31, 2004]
[edit reason] no specifics or keywords - please see tos [/edit]

[JasonD]

I "think" I have found the page you are speaking about in the SERPs and after looking at the page it doesn't seem to be a cloaking issue but rather an SSI error from an advertising site that is using Server Side Includes to call a CGI that outputs PPC adverts.

I could be wrong of course