Duplicate ads in Google Cache

[Kanute78]

For some reason, in google cache our top banner ads are duplicated (just showing one when using site normally). We are using something called Madgex lazyad to lazy load the ads.

I understand that the indexed version and the cached version is not the same, but could a cached version like this be an indicator that we might unintentionally are serving duplicate ads above the fold?

[goodroi]

Have you tried fetching as Googlebot in Webmaster Central?

[OutdoorWebcams]

I'm having the same issue. On many pages of mine every ad (AdSense and Criteo) is shown twice.

Looking at the cache's source reveals that the second AdSense ads are shown as a second iframe with the source "about:blank" and are accompanied with the comment "<!--fakeads included as xttp://pagead2.googlesyndication.com/pagead/show_ads.js--> [more AdSense specific comments here]".
(xttp instead of http to maintain readability)

The Criteo code is simply repeated.

Fetching as Googlebot in Webmaster Central renders the page correctly but hands over crap to Google's cache.

The worrying thing is that those affected pages sometimes jump from SERP#1 to somewhere on page 2 to 4 (and back to #1, should Google get it right the next time).

So maybe this is actually something to have an eye on.

(This doesn't happen with AdSense's async code, only with the sync code, but the CTR on those async blocks is so bad that it's not an option (yet)).

[netmeg]

(The CTR on async is another issue that we could discuss in the AdSense forum - that's not been my experience at all)

One thing you could do is just stop Google caching your site. I'm a firm advocate of NOARCHIVE because... what purpose does it serve anyway? Most of my stuff is either client ecommerce or my own events, and neither is well-served by allowing cached content to be viewable.

[OutdoorWebcams]

Thanks for your reply, netmeg!

(The CTR on async is another issue that we could discuss in the AdSense forum - that's not been my experience at all)

It wasn't my intention to discuss CTR here, just pointing out why I use sync before somebody comes up with "use async and that's it".

I considered using NOARCHIVE too but I'm not sure if this will cure the root cause of the improper interpretation of my site (or part of it) by Google.

Something seems to make Google execute the ad code and place the result in it's cached version instead of caching the plain HTML source: The Criteo code consists of several 'document.write("ad"+"Stuff he"+"re...")' and in the cache's source the resulting "adStuff here..." is ALSO present.

I would really like to know what's triggering this behaviour (and what bugs me most: why just with SOME pages and not ALL or NONE?)

[OutdoorWebcams]

...and in the cache's source the resulting "adStuff here..." is ALSO present.

Sorry, forgot to mention: The resulting "adStuff here..." is also present TWICE.