Sadly, no. I haven't used Google in many years, I use DuckDuckGo instead. Every now and then they ask for community input and I ask and beg them to reinstate a string search feature but it never happens. There's no logical reason why they can't run both.
String search is considerably more expensive than word search at scale, and I'd expect it to be very troublesome with large-scale caching, which has to be in use with the big search engines.
I'm not sure if you care much, so a lightweight explanation:
There aren't many words in an given language, and most of them aren't used often. This allows for a kind of fast search based on indexing each word. The tech is fairly simple and was available in products quite long ago - it's older than SQL.
You can e.g. use the
index to figure out adjacent words in the same document, which in turn allows for pulling by phrase and sentence
It's great for document searching, and some high-end version is certainly in use in Google.
Note that they've been playing with the tech for a long time. Whatever they're doing will be optimized for their purposes.
The doc selection based on payments to the search engine has to be an overlay, but it wouldn't interfere with the "inverted index" tech.
The first issue with string search is that it isn't natural to implement it with the same indexing system, because it would kick up the number of "word analogs" by a lot.
It could be done as an overlay OFC, but they'd have gone for selling searches first.
The possible interaction with caching is that the increase in the number of indexed terms ("words") would affect index and search caching too. Caching is great if you reuse what's in the cache instances often, less good if you don't get a lot of repeat hits, and slows you down if you get "cache-sync-thrashing" (made up the name for this post, but the issue is 100% real).
(Thrashing as in the (maybe old) term for memory overuse <-> swap-file data rates topping out.
FWIW I think it would be possible to users to select string search for individual searches but would never allow it to be "always on" for normies. With selective use and user acceptance of slower search speeds it wouldn't be particularly hard technically.
But it would mess with the income-generating sale of search strings. Management wouldn't like it.