I think this little change is going to fundamentally change the internet landscape. a) no more long tail keywords. those people will see an answer before they get to the part of the phrase that makes it longtail(so if you ranked for that 5 term keyword...too bad). i.e. if you rank for "best auto insurance companies", you've now lost all your business to those who rank for "best auto insurance" b) much faster searchin…
Google Instant Search Released
191–200 of 227 posts
Re: Google Instant Search Released
#192I think this little change is going to fundamentally change the internet landscape. a) no more long tail keywords. those people will see an answer before they get to the part of the phrase that makes it longtail(so if you ranked for that 5 term keyword...too bad). i.e. if you rank for "best auto insurance companies", you've now lost all your business to those who rank for "best auto insurance" b) much faster searchin…
For me (and I'll admit it perhaps doesn't apply to others), it has almost no effect. I use the firefox search box mostly.
Re: Google Instant Search Released
#193Earlier quoted context omitted.
True. But you'll have to agree that such argument have a diminishing marginal return pattern. 500ms vs. 250ms may be great, but what about 100ms vs. 50ms? Once you reach the point my brain is the bottleneck, what's the point? On the other hand it could be distracting to get something happening in the screen while you are thinking the best way to form your query. Usually when I am about to ask someone a question and t…
Experiments have shown that 100 Ms is the threshold.
Re: Google Instant Search Released
#194edit: Apparently Opera is not among the browsers listed here: http://www.google.com/instant/
Re: Google Instant Search Released
#195Annoyingly busy. I sort of feel like this is a prime example why you don't put engineers in charge of UI. Just because we can is not a good enough reason to do it. Also, having both a dropdown and a whole page refresh, what?
Re: Google Instant Search Released
#196Earlier quoted context omitted.
Why would inflating the number of impressions matter at all when Google makes money from clicks?
Probability of some old man clicking one of the four different links kindly proposed on the top of the page by Google while he's typing his search query is higher than the probability of him clicking the only ad shown to him with the old search technique. I guess.
Re: Google Instant Search Released
#197I often use Google to search for very specific phrases -- error messages, for example, in quotes -- and that doesn't help. It actually hurts. What hurts even more is that Google returns documents that don't contain all the search terms, but where the missing search terms can be found in incoming links (or so it says). If you try to use the allintext: parameter you're almost always considered a bot (why??!?) and your…
Re: Google Instant Search Released
#198Re: Google Instant Search Released
#199This is a logical extension of the trend to do ever more computation on every key press. Think spelling correction and auto-complete. But here instead of just a local process every key press invokes hundreds of remote machines, required to assemble a single search results page. It's impressive and decadant to think your cat walking accross the keyboard can light up whole racks of remote machines.
> every key press invokes hundreds of remote machines, Not really. Apparently Google has an improved cache system for the most common keywords. The pre-computed results come from just one machine.