21 ms·
I'd love to see + do what + was supposed to do and not do the guessing. Has been frustrating to me, too -- though I suspect (this is part of what I'll be learni
by sullivandanny 9y ago
I'd love to see + do what + was supposed to do and not do the guessing. Has been frustrating to me, too -- though I suspect (this is part of what I'll be learning) that for the vast majority of people, it might help. In the meantime, when you search, after doing a search, look for Tools under the search box then select "Verbatim" which is supposed to do exactly what you ask.
- nathancahill 9y agoHuh, TIL about Verbatim. Wish there was a setting to make it the default, like you can set SafeSearch.
- pasbesoin 9y agoThank you. That has been mentioned, previously, and I believe there is also a corresponding query string value that can be appended to a search URL to enable it. At least that would amend itself to e.g. being incorporated into a bookmarklet for one-click access.
- pasbesoin 9y agojavascript:void((function(){var%20loc%20=%20location.href;%20loc.indexOf("?")%20==%20-1%20?%20(location.href%20=%20loc+"?li=1")%20:%20(location.href%20=%20loc+"&li=1");})()); or, taking a bit more care: javascript:void((function(){var%20loc%20=%20location.href;%20if%20(loc.indexOf('li=1')%20>=%200)%20return;%20loc.indexOf("?")%20<%200%20?%20(location.href%20=%20loc+"?li=1")%20:%20(location.href%20=%20loc+"&li=1");})()); or I guess it could be modified further to change the parm if it's already present with a different value. Modified from (because I'm lazy): https://stackoverflow.com/questions/20677974/bookmarklet-to-add-a-parameter-at-end-of-each-url#answer-20678352 https://stackoverflow.com/questions/20677974/bookmarklet-to-...
- sytelus 9y agoThis is almost becoming an epidemic. I find my confidence is search quality has lowered significantly since new algorithms just keeps ignoring the terms I specify. Most of the times behavior is so stupid that I can't really believe if this is not impacting heavily internal search metrics. At least the requery related metrics should have exposed the problem. I would not be surprised if it was decided to change the metrics just so these new algorithms could be deployed.