Google Bug Prevents Clicking On Second Search Results

Jun 22, 2010 • 8:03 am | comments (7) by twitter Google+ | Filed Under Google Search Engine
 

There seems to be a weird bug with Google's search results, which highly discourages people from clicking on the second search result.

Typically, a searcher will search for search for something, go to the first result and if unhappy with that result, they will click the back button. After they click the back button, they may try to click on the second search result. In this case, Google is making it a bit hard for the user to click on that second search result.

What happens is that Google will push down the second search result when you click on it and load up a "Get more results from the past 24 hours" link, in its place.

Try it yourself, search for [search engine roundtable], then click on the first result. Then click your browser's back button. When the search results load again, click on the second result and you should see the "Get more results from the past 24 hours" link come up in its place.

Here is a video demo of this happening to me on Google Chrome on my Mac:

Many are complaining about this in the forums.

Forum discussion at Google Web Search Help.

Previous story: Daily Search Forum Recap: June 21, 2010
 

Comments:

Martin Greenwood

06/22/2010 12:19 pm

Sneaky, however this only seemed to happen in Google Chrome, I just tried this in Firefox and safari and it doesn't seem to do it.

Mark

06/22/2010 01:10 pm

Chrome only on my end also... FF and IE seem to handle it fine.

Nate Schubert

06/22/2010 02:13 pm

Sort of interesting that the only web browser that seems to replicate this bug is Google's own browser, isn't it?

Christi

06/22/2010 02:28 pm

It is not limited to Chrome, IE8 displays this behavior.

Jonathan Richman

06/22/2010 03:06 pm

Hmmm...no issue for me in Chrome. This bug isn't occurring. On the plus-side, I clicked through to your site about 20 times to test this, so, you're welcome.

Francois Paren

06/22/2010 04:19 pm

It happen in FF and in google.fr on my end.

jim

06/23/2010 02:00 pm

It happened an all the browsers firefox, internet explorer and chorme. Very shady

blog comments powered by Disqus