I'm sorry to tell you, but this is flat wrong. I commented[1] about this a few months back with a random phrase as an example. I see it often in my day to day also.
Looking at all 22 results (without opening the "omitted results" section or image results), the phrase became harder to find off the first page, but I tended to find it in the source code, or the DOM, or the cached version of the page, or by disabling JS (sometimes requiring a combination of those techniques). I found it in 21 out of the 22. The one page I couldn't find it in (the dolls one) looks like a frequently updating page, and it was highlighted in the snippet, so it looks like it was there at the time of crawling but not now; the cache isn't there for that page.
Full disclosure I work at Google, but not on Search.
1) text appears in ALT text 2) text is not readily visible on a page (maybe in a menu bar or small text) 3) there's punctuation ("dog cat" will match "dog, cat" 4) page has changed after we've indexed it (so view the cached copy, if available)
In the [eggzackly this], you found matches of those words separated by punctuation -- which we interpret as a space, so the phrase is matched.
I wish we'd fix the situation with punctuation. I get that's confusing. But that's not a new change; quotes have operated that way for ages.
I just tested "eggzackly this" and every result on the first page contains the string "eggzackly this", albeit usually with different punctuation ("Eggzackly. This [...]", "Eggzackly, this.", "Eggzackly! This [...]")
We don't have control over this and it's very frustrating.
What you're talking about is probably a case where there's a quoted word or phrase as well as other words that aren't quoted. In such a case, we're going to absolutely look for content that matches the quoted parts. That's a must. The other words, we'll look for them, but we'll also look for related words and sometimes, we might find content that doesn't match one of them.
Because those other words aren't quoted, we'll tell you if we find a match that seems helpful but doesn't contain those non-quoted words. That's what the message is about. But it should never be telling you we omitted a quoted word or phrase because we won't -- with one exception.
If there's literally nothing on the web we know of that matches a quoted word or phrase, then we're not going to show anything at all and say we couldn't match any documents.
Interestingly I tried my pet peeve search, and it worked for the first time this year! It is for a specific recipe, and I search for 'ocau slow cooked balsamic beef'. I have had to manually find it in the archive of the overclockers.com.au forum for the past year, as Google seemingly forgot it existed no matter what search terms or operators I used.
The main difference is I am using Firefox on Manjaro and not my historically typical environment for searching. Normally I would either be using Chrome on Windows or Chrome on iOS if I am in the kitchen.
I will play around on some other devices and see what evidence I can find.
P.s. I'm being referred in for a role at Google currently, is the Search team only in a specific area like Silicon Valley or is it a global team? Most of the jobs in Australia seem to be commercial facing, not product facing.
https://www.google.com/search/howsearchworks/mission/users/ https://blog.google/products/search/overview-our-rater-guide... https://blog.google/products/search/raters-experiments-impro...
Though, why does enabling "Verbatim" (in tools) on a search reduce the number of search results if all my terms are already quoted? Enabling Verbatim often does it make it feels like my queries are interpreted more literally, but if quotes are already being respected I don't understand how Verbatim would reduce the number of search results.
On the counts -- basically, it's all really rough estimates. We make a rough quick count, you go deeper into the page, we make a fresh estimate. It can change, and it doesn't always make sense and personally, I'd hope we just get rid of counts because of this, perhaps more confusing than helpful.
Thank you, Google, for continuing to respect quotes!
Today I stumbled upon one. Here's a broken example query: linux next hop "[::]"
Here's the archive of the incorrect query result: https://archive.md/9WGe7
The first result (the man pages) does not contain [::] anywhere in the page text, the source, or the cached result. Could you take a look at this one?
I’m guessing this happens when there are less results matching my phrase
Now, if you quote something and put in other non-quoted words, then we'll look for stuff that matches the quoted part and the other things are optional. So when you see that strikeout message, it means basically "We found this page that has the exact words you quoted, and it probably has one or more of the other words or related words you didn't quote, but heads-up, it doesn't have one of those non-quoted words at all."
And we do this because sometimes there might be a useful page that doesn't contain all of your optional non-quoted words.
Totally agree it would help if we did a better job bolding the sections of a page where the quoted terms apply. Often we do, but sometimes the snippeting won't include them if there's better text to describe the page overall. But we're looking at maybe improving here.
"kitchen boss" "g320" "disassembly"
https://www.google.com/search?q=%22kitchen+boss%22+%22g320%2...
Nothing useful at all. Nothing mentioning disassembly. Not even a YouTube link.
It literally says `No results found for "kitchen boss" "g320" "disassembly".` right at the top, and then shows you the (properly explained) results for the non-quoted version of the query.
Anyway, with the terms I posted earlier, on desktop it says:
Results for kitchen boss g320 disassembly (without quotes):
It looks like there aren't many great matches for your search
What we can do is try searching for all of the words, so perhaps you'll find something useful that way. But even we can tell when doing this that the results might not be what you want, which is why that automatic warning about maybe these aren't great matches.
IE: we can't show you what we've got for a query where there are no exact matches. It's impossible. We can show you what we got if we don't require all the word be present. And we can tell you what we're doing. And you always have the choice to restart the query in another way if you don't like that.
Now here's something else. You probably used the quotes because I'm guessing you figured it was better to tell us exactly what to do than trust us to look at all the words and analyze the context and so on and see if we could make matches generally. If you had done that, just searched for [kitchen boss g320 disassembly], then the first web page result is the instruction manual for your sous vide machine. It has cleaning steps, which I'm guessing also might be what you're after? (It looks like it's just take off the outer casing).
Those results, doing it directly like that, are different than when we gave them to you after your quoted search failed. and that's probably because when you gave us quotes, and there were no matches, we might have tried some stricter matching to keep closer to the original requirements rather than use our general ranking.
To wrap up: maybe don't try the quotes at first. It's totally fine to type in a long natural language query like [how do I take apart a kitchen boss g320] and if you do that, the instruction manual is right there.
Showing results for non-quoted words isn't intended to be condescending nor an indication that we think someone made a mistake. Apologies that it comes across that way.
We think we're clearly saying there are no matches with the "No results found" message. If we stopped there, the page would have nothing else. And I get that for you -- and perhaps others -- that might be preferable, a further reinforcement that there's nothing out there.
For others, not so helpful. They potentially might give up with no real way of going forward, when just losing the quotes perhaps could get them useful information.
And I get the trade-off concerns. I've seen many comments here that things done to support less "pro" users are annoying. And yet, we do need to find a way to support everyone. I think that's why we've probably gone with the message about no matches with and showing the quotes.
Perhaps we should consider making that an option -- "Would you like to try this search again without quotes."
As for the message about not good matches, we always try to show the best stuff we have first. That's the point of our ranking. The warning is meant to indicate that even though we'll list the best we have, for that query, none of it is particularly helpful -- not that here are a bunch of results, and there's some good matches mixed in with poor ones. Ranking that way would make no sense.
But it might be also that we're so close to it -- that we always try to rank the most useful stuff first -- that we didn't consider the interpretation you had. So thank you again, it's really helpful to get that feedback.
Sorry the information doesn't appear to be out there. I hope if you disassemble it on your own, you'll post the info out to the open web. I'm pretty sure you'd end up ranking well for that and helping others who might have a similar need.
1. This is still horrific UX/UI 2. The culture internally at Google seems to have a "we know better than the users" attitude in all things. 3. Query rewriting is a horrific technique in general with almost zero value to life/society outside of fixing spelling errors. Whatever your A/B testing says about it's purported utility is polluted by Google's own dark patterns and political whims of the managers who run the internal search organizations.
It helps to actually know better than your users if you want to take the attitude in number 2. I don't believe that you or Google knows better than it's users, for many reasons previously enumerated in this thread and others.
One day Google search is going to be displaced and it's current utilization of query rewriting techniques will be one of the fundamental reasons for this.
You should take the absolutely massive amount of recent criticism and the fact that users repeatedly claim it's happening in the face of your claim it's not seriously rather than literally blaming the users writ large for a problem that is fundementally with the behavior of Google search.
Please fix it, like now. Displace your teams current sprint priorities, or the anti-google search backlash will turn into a situation where in 2025 Google is on the defensive for search market share from a Phoenix rising yahoo or something like that.
The fact that anyone at Google ever okayed this behavior at all in the first place is simply rage inducing and you should see that with the magnitude and persistence of the "actually it really doesn't work bro" kind of comments.