4 ms·

Works for me. Link to a query?

andrewprock 8y ago
Here is a great example: https://www.google.com/search?q=%22Documentation+around+this+isn%27t+as+good+as+it+could+be%2C+and+it%27s+rough+that+the+search+codeset+changed+when+G%2B+came+around+so+that+%2Bword+no+longer+meant%22&oq=%22Documentation+around+this+isn%27t+as+good+as+it+could+be%2C+and+it%27s+rough+that+the+search+codeset+changed+when+G%2B+came+around+so+that+%2Bword+no+longer+meant%22&aqs=chrome..69i57.1792j0j7&sourceid=chrome&ie=UTF-8 https://www.google.com/search?q=%22Documentation+around+this... Links to this page, but says "no results found, showing related results"
- fixermark 8y ago
  Interesting. If the bolding of the match is to be believed, it looks like the algorithm is dropping joining words and words too common to provide useful search signal, but as a result doesn't have enough data in the backing corpus to be confident it has an exact match, as you requested. DDG on the same query gives exactly that page but nothing else. I wouldn't be surprised if Google finds that to be an inferior experience (because the common use case is people kind of remember a quote, but don't remember it exactly, so a few words out of place would false-negative the search where the answer the requester is looking for is edit-adjacent to the input).
  - jvolkman 8y ago
    It looks like this particular example is actually due to the "+word" in the quote. Here's everything up to but excluding "+word": https://www.google.com/search?q="Documentation+around+this+isn%27t+as+good+as+it+could+be%2C+and+it%27s+rough+that+the+search+codeset+changed+when+G%2B+came+around+so+that" https://www.google.com/search?q="Documentation+around+this+i... And including "+word":https://www.google.com/search?q="Documentation+around+this+isn%27t+as+good+as+it+could+be%2C+and+it%27s+rough+that+the+search+codeset+changed+when+G%2B+came+around+so+that+%2Bword" https://www.google.com/search?q="Documentation+around+this+i...

Here is a great example: https://www.google.com/search?q=%22Documentation+around+this+isn%27t+as+good+as+it+could+be%2C+and+it%27s+rough+that+the+search+codeset+changed+when+G%2B+came+around+so+that+%2Bword+no+longer+meant%22&oq=%22Documentation+around+this+isn%27t+as+good+as+it+could+be%2C+and+it%27s+rough+that+the+search+codeset+changed+when+G%2B+came+around+so+that+%2Bword+no+longer+meant%22&aqs=chrome..69i57.1792j0j7&sourceid=chrome&ie=UTF-8 https://www.google.com/search?q=%22Documentation+around+this... Links to this page, but says "no results found, showing related results"

fixermark 8y ago
Interesting. If the bolding of the match is to be believed, it looks like the algorithm is dropping joining words and words too common to provide useful search signal, but as a result doesn't have enough data in the backing corpus to be confident it has an exact match, as you requested. DDG on the same query gives exactly that page but nothing else. I wouldn't be surprised if Google finds that to be an inferior experience (because the common use case is people kind of remember a quote, but don't remember it exactly, so a few words out of place would false-negative the search where the answer the requester is looking for is edit-adjacent to the input).
- jvolkman 8y ago
  It looks like this particular example is actually due to the "+word" in the quote. Here's everything up to but excluding "+word": https://www.google.com/search?q="Documentation+around+this+isn%27t+as+good+as+it+could+be%2C+and+it%27s+rough+that+the+search+codeset+changed+when+G%2B+came+around+so+that" https://www.google.com/search?q="Documentation+around+this+i... And including "+word":https://www.google.com/search?q="Documentation+around+this+isn%27t+as+good+as+it+could+be%2C+and+it%27s+rough+that+the+search+codeset+changed+when+G%2B+came+around+so+that+%2Bword" https://www.google.com/search?q="Documentation+around+this+i...