Google Chrome Bug With Rel=Next Can Lead To An AdSense Ban

Feb 28, 2013 • 8:54 am | comments (5) by twitter Google+ | Filed Under Google Search Engine Optimization
 

ChromeA WebmasterWorld thread has one webmaster claiming that Chrome 25.x and 26.x (beta) has a bug with their prefetching and prerendering techniques that can ultimately lead to your Google AdSense account being banned.

How so?

It seems that if your site uses the rel=next webmaster parameter, the Chrome prefetch technique will go to the next page and prefetch it. It will do so as long as it seems the rel=next and go on and on forever.

The webmaster explained:

And if you have next/prerender link in header to another page, even if the visitor doesn't visit the page or visits other pages even from other websites, Chrome keeps prerendering the next page and the next page from your site.

As long as the user keeps the window open, Chrome keeps prerendering.

It starts to happen if the user doesn't visit the prerendered page and goes to another url. Once it starts, it prerenders the next page every 30 seconds. (I think it happens when Chrome tries to evict the preprendered page)

Google Analytics or other stats that have implemented Page Visibility API doesn't record it. But others, like Adsense, record the impressions.

Sound scary to me. I am not sure if this is legit, but he seems to act like he knows what he is talking about.

Forum discussion at WebmasterWorld.

Previous story: Google Calendar Events In Google Search Results
 
blog comments powered by Disqus