| I suspect it's a reflection of the way the majority of their audience interacts with search. For a large number of people, Google's ability to answer the underlying question, rather than explicitly identify pages where all search terms appear, means it works better. If you think of Google as a way to get answers, this is good. If you think of Google as a search engine, and particularly if you have historical experience with (and expectations of) search engines, this is very frustrating. And the workarounds of clicking the "must contain" link (or surrounding all of your search terms with quotation marks) are a seemingly unnecessary inconvenience. As a personal anecdote, I was an early adopter of smartphones (particularly relative to a non-technical audience). So I was excited when I could speak to my phone, then disappointed when I discovered that I had to structure my queries and instructions very carefully. A few years ago I was on a road trip with a very non-technical friend. We decided to stop for Chipotle. Had it been up to me, I would probably have pulled out my phone, opened Google Assistant (or perhaps Maps directly), and told my phone (speaking as clearly as possible) "navigate to the closest Chipotle" or something similar. But I was driving, so she just pulled out her iPhone and half-shouted "I want a burrito!" at it. And that worked just fine. Point being, I had expectations for how things should work based on interactions with earlier iterations of an interface. She didn't. |
Google really needs to develop a "pro mode" search engine that works for this use case. I get the need for an "answers engine" for less savvy users and more casual use cases, but it's a massive company. It can afford to execute two products in its core competency (rather than umpteen messaging apps that it will kill, along with a lot of other useless and/or doomed stuff).