Forum Moderators: Robert Charlton & goodroi
Google has released a new stable version of its Chrome browser, adding an "Instant Pages" service that attempts to accelerate your Google searches by rendering pages before you actually click on them.
[edited by: Robert_Charlton at 8:27 am (utc) on Aug 3, 2011]
Asked at press event earlier this summer how often Instant Pages chose the wrong link, Google Fellow Amit Singhal did not say. But there will surely be many cases where the service renders a page that you don't click on, and this could skew traffic numbers for sites across the web. In order to account for this fake traffic, webmasters must tap into a new Page Visibility API [code.google.com] that Google has submitted to the W3C as a standard.
It will be interesting to see how this ties in with google analytics..
Then why don't they serve the page from their own Ripped copy of the page?
In order to account for this fake traffic, webmasters must tap into a new Page Visibility API [code.google.com] that Google has submitted to the W3C as a standard.
RewriteCond %{HTTP_USER_AGENT} ^.*Chrome*$
RewriteRule ^/* http://www.example.com/sorry.html [L]
Fotiman wrote:
This really doesn't make any sense at all.
The Visibility API is code that runs client side, AFTER the page has already been served! By that time, it's too late to do anything about it. Yes, can do things like minimize the effect of pages that make AJAX requests to the server, but it really doesn't address the issue of skewed traffic numbers from pages that are pre-rendered.
Does the pre-fetch include execution of JavaScript?
[edited by: Leosghost at 6:52 pm (utc) on Aug 3, 2011]
johnmoose wrote:
@pfui: I checked my setting (enable instant on the basics page) and it was off. Must say that I upgraded from a previous version too. Can't tell what a fresh install would be on.
RewriteCond %{HTTP_USER_AGENT} ^.*Chrome*$
RewriteRule ^/* http://www.example.com/sorry.html [L]
that would prevent everyone who uses Chrome from viewing your pages, not just the pre-rendering
First, we’ve added some awesome to the omnibox by suggesting partial matches for URLs and page titles from your browsing history.
[edited by: Sgt_Kickaxe at 9:45 pm (utc) on Aug 3, 2011]
My charts are more accurate without this data so a way to set this data aside or give it it's own "prefetched" heading is a must.
Google - please respect the noarchive meta tag and do not prefetch pages that have it. thank you!
[edited by: Leosghost at 9:45 pm (utc) on Aug 3, 2011]
if that was the case I don't suppose they would stop now..it may just become more apparent.
And your point is...?
