Published: Aug 16, 2008 - 08:03 am
Story Found By: crashingflwrgrl 1739 Days ago
Category: PPC
28 Comments
28 Comments
Search Engine Land produces SMX, the Search Marketing Expo conference series. SMX events deliver the most comprehensive educational and networking experiences - whether you're just starting in search marketing or you're a seasoned expert.
Join us at an upcoming SMX event:


Learn more about search marketing with our free online webcasts and webinars from our sister site, Digital Marketing Depot. Upcoming online events include:
Comments
Its not actually adsense ad. its just an image of one. the adsense ads in twitters google cache is not clickable, I wonder how they still manage to make it contexual?
It actually is an adsense ad and not an image of one - from the source: google_ad_client = "pub-3167622637866239"; google_alternate_color = "9AE4E8"; google_ad_width = 234; google_ad_height = 60; google_ad_format = "234x60_as"; google_ad_type = "text"; google_color_border = "FFFFFF"; google_color_bg = "FFFFFF"; google_color_link = "0000ff"; google_color_text = "000000"; google_color_url = "000000"; I am guessing you cant click on it because the div with the picture and name is laying on top of it, but that is just a guess, cause I suck at css ;-)
I just checked the examples in the article and from my end I cant see ads. Am i missing something or did they already fix things?
Im still seeing ads on the caches.
Yep I noticed this some time back and wondered what they were playing at. Looking around I saw they had run Adsense as an experiment and stopped. I was just seeing old messages with the ads on, not the news ones, so assumed Google had not updated their cache on these. http://labnol.blogspot.com/2007/04/twitter-removes-adsense-ads.htmlYoure right though Rae, now there are cached Adsense on very recent comments made this week. So sometime in the last few months they have turned this on again. Maybe during one of their system meltdowns someone reloaded an old version of the code and have now turned it off again? Or they ran another test and no one noticed?
No youre right, blatently cloaking for Google. Look at this Tweet of mine:http://twitter.com/nickwilsdon/statuses/887709381Now run through Google translate to get a Google IP:http://google.com/translate?u=http%3A%2F%2Ftwitter.com%2Fnickwilsdon%2Fstatuses%2F887709381&hl=en&ie=UTF8&sl=fr&tl=enNo idea why they would be doing this though, cache has limited views and its not even clickable. I need my morning coffee :)
Weirdness. Its a good example of why a company should at least occasionally be working with an SEO consultant so the web devs dont do anything this cryptic.
>>>No idea why they would be doing this thoughYeah, the why was curious to me too, but hopefully, theyll be forcedto provide Google with some type of explanation if this gets in front of enough people.
re: CSS - its behind < h2 class="thumb" > so you cant click it. pretty goofy placement, sure looks like a mistake.
Even if it isnt clickable to the point of costing advertisers money, it adds to their impressions and drops their click through rates - which affects their bid prices.
And actually, some are clickable - finally found one thanks to a tweet that made the suggestion to look for shorter usernames from bunltd (and my realization I needed to find a shorter username that was coupled with a longer ad title) - see addendum at the bottom of my post: http://www.sugarrae.com/is-twitter-cloaking-their-site-to-show-adsense-ads-in-their-cache/
Ok, i can see the ads now. Before i couldnt because I had the Ads Blocking Plugin on in FF. Honestly this looks like a mistake. I dont think that this is anything more then some one using old code from back when they tested the adsence. More examples of twitters inability to keep the "gremlins" out of their system.
>>>mistakeI might agree if the adsense wasnt seemingly being cloaked to only appear in the cache and wasnt on status messages from yesterday.Id just like to know the "why" behind it.
adsense code is on the page: http://twitter.com/sugarrae/statuses/888566067just not viewable
awesome find Sugarrae. I would be super mad if I was that Lipo company...
xDFuNK what exactly are you seeing? Cause I have viewed the source of a bunch of the non cached ones, including the one you linked to, and dont see any adsense code?
That said, i havent viewed the regular page giving off googlebot as my user agent...
xDFuNK is right... code is there no matter what if youre not logged into twitter - however, it only is VISIBLE to the end user if the end user is Googlebot (and thus why it shows in the cache): http://www.sugarrae.com/is-twitter-cloaking-their-site-to-show-adsense-ads-in-their-cache/
>code is there no matter what if youre not logged into twitterId swear it wasnt there this morning. I looked for that myself through the source code and just found an empty space. Edit: Ah sorry was being slow. I see what you mean. If youre logged into Twitter you dont get the Ads.
This is probably part of the same type of ad system that sites like wordpress.com and others use to only show ads to visitors that access the site via search. For example there is a Wordpress plugin that is designed for Wordpress MU only that shows adsence ads to visiters that 1. have never been to the site before and 2. get there through a search engine like Google. Given the fact that they are cloaking except to a Google bot tells me that they are trying to implement the same type of system, its just that we arent aware of it because we dont fall into either category.
I just tested the above theory by clearing my browser history and cache, and then searching for a twitter page through google. And unfornately I didnt see any ads, which means that my theory might be wrong. However, i am going to keep testing...
Ok think Ive got this now. This isnt about cloaking, as xDFuNK discovered, its about showing different content to logged in users (no ads). It just happens that Google/Yahoo and other spiders see the same logged out state (ads shown) because they are also unable to login. Why do the ads show in Googles cache? Its a display issue caused by the extra META content tag that Google inserts into the top of the page there. You could even say this is a display error, as Google’s code makes the page non-compliant. The first thing on the page should be the DOCTYPE declaration but Google injects their meta tag and header divs above that. [meta http-equiv="Content-Type" content="text/html; charset=US-ASCII"] Twitter arent doing anything in particular for Google. I dont even think it counts as cloaking by their own definition. Its just a combination of trying to stop ads being shown to users and Google inserted cache code (which makes the page non-compliant). As Halfdeck says though, this is a good case why companies should be hiring SEOs. Any consultant worth his money would have raised questions once they knew about Twitters plan to selectively show the advertising. So the only question left is why have the advert code in there but not show it visibly on the page? My guess is that they tried the adverts in there, had the public backlash and told the devs to stop them being shown. Instead of removing the code, the devs just changed the CSS to hide them, probably thinking this idea would be reactivated sometime later.
@NickWilsdon I think you are very close to the answer, but as a developer it just doesnt make sence to me for them to hide it by changing the CSS. I mean, that still leaves massive potential for different issues to arrise later. And, in theory it makes each page load slower for loading unused code. It just seems that they would take it out completely. But at the same time, I feel like I have tested this under all possible senarios and I havent seen any ad outside the Google cache.
Invalid XHTML on the page too.... http://validator.w3.org/check?uri=http%3A%2F%2Ftwitter.com%2Fsugarrae%2Fstatuses%2F888566067&charset=%28detect+automatically%29&doctype=Inline&group=0&sphinnnull=
@joehall Heres a test page with the Googles extra meta tag inserted (in same way as their cache template). http://nickwilsdon.com/test-twitter.html I agree though, it does seem odd to hide the ads rather than remove them. Like I said though, maybe they knew this was a test soon to be repeated. Twitter must be keen to monetize their content to have run the test in the first place. Maybe someone thought they would save some time or didnt realise the implications? Still I cant see Google coming down on them for this. They can claim they were trying to improve the experience for their users by removing the ads. This doesnt seem malicious.
You know, the funny thing here is that if Twitter *do* get a penalty for displaying the ads, it will be due to invalid markup. Admittedly its probably Googles poor markup at fault but would be a great case for making sites W3C compliant. :-D
I can hear it now, TWITTER: "Hey Google, we were only trying to remove your ad content to improve our users expierirnce,.....no, no..its not that!...they love your ads! hell, everyone loves your ads,....its just that well....umm....please dont hurt our results!"
"I think you are very close to the answer, but as a developer it just doesnt make sence to me for them to hide it by changing the CSS. I mean, that still leaves massive potential for different issues to arrise later."But, assuming that youve had to make adjustments to a major website while it is live, some things dont turn out the way youd like at the end of your work session.. and I could just see a developer trying to create or manage a process, hitting a snag, and instead of erasing all of his work [s]hed just quickly cover it up until they could figure out the snag. Depending on the circumstances, it could take days or even weeks. Not saying its right and certainly not saying anything about the developers themselves, but I could definitely see it.