Information Systems Information Retrieval Semantic Search and Vector Embeddings

When Search Learned to Measure Meaning Instead of Words

Semantic search added a new sense computers never had — and quietly got worse at the exact matches keyword engines always nailed.

S.J. Nam 7 min read
When Search Learned to Measure Meaning Instead of Words

In October 2019, Google told the world that a single change to its search engine would touch roughly one in ten queries — and that the change hinged, of all things, on tiny words like "for" and "to." A search for how a Brazilian traveler reaches the United States means something different depending on which direction those prepositions point. For twenty years, the world's most powerful search engine had mostly been throwing those little words away. The update, called BERT, was Google's admission that it had been reading like a machine that counts words instead of one that understands them.

That distinction — counting versus understanding — is the whole story of semantic search. It is also where most explanations of it go wrong. The popular version says AI made search "smarter," as if the old way were merely a dumber cousin of the new. The truth is stranger and more useful: semantic search didn't make computers better at what keyword search already did. It made them good at something keyword search could never do at all, while quietly becoming worse at a few things keyword search had always nailed. Understanding why is the difference between using these tools and being fooled by them.

The Tyranny of the Exact Word

Classic search rests on an elegant, almost mechanical idea called the inverted index. Picture the index at the back of a textbook: every important term, followed by the list of pages where it appears. A keyword engine builds that same structure across billions of documents, mapping each unique word to every place it occurs. Type a query, and the system looks up your words, finds the documents that contain them, and ranks the overlap. It is fast, transparent, and honest about what it's doing.

It is also literal to a fault. The machine has no idea that "car repairs," "automotive maintenance," and "vehicle servicing" describe the same afternoon in a garage. To an inverted index, those are three unrelated strings of letters. Ask it about "AI regulation in Europe" and it may sail right past an article titled "EU passes new AI safety act," because the exact words don't line up — even though that article is precisely, maddeningly, what you wanted. Word overlap between your question and the perfect answer can be zero. Language is generous with synonyms and stingy with exact repeats, and keyword search feels every bit of that gap.

For decades we adapted to the machine rather than the other way around. We learned to strip our questions down to nouns, guess the phrasing a document might use, and try again when nothing came back. We called it "search skills." It was really just accommodation.

When Meaning Became Coordinates

The breakthrough that eventually fixed this arrived in 2013, from a small team led by Tomáš Mikolov at Google. Their system, Word2Vec, did something that still sounds faintly magical: it turned words into coordinates. Each word became a long list of numbers — a vector — positioned in a space with hundreds of dimensions. Words used in similar contexts landed near each other, because the model learned them by predicting the company each word keeps.

The payoff was almost poetic. Because meaning had become geometry, you could do arithmetic on it. Take the vector for "king," subtract "man," add "woman," and you land remarkably close to "queen." The direction that separates man from woman turned out to be roughly the same direction that separates king from queen — the model had captured a relationship no one had programmed into it. Meaning had quietly become math.

Modern systems extend this from single words to whole sentences and documents, using embeddings that typically run from 512 to a few thousand dimensions. The engine converts your query into one of these vectors and converts every document into its own, then measures the angle between them using cosine similarity — a score that runs from -1 for opposite meanings to 1 for identical ones. "Car repairs" and "automotive maintenance" now sit close together in this space not because they share letters but because they share meaning. The search stops matching words and starts measuring conceptual distance. That is the entire trick, and it is enough to find the document with zero words in common that keyword search would have buried on page nine.

The Word That Broke the Old Search

Word2Vec had a stubborn limitation: every word got exactly one vector. "Bank" by a river and "bank" holding your money were the same point in space, forever. Meaning depends on context, and a single frozen coordinate per word can't capture that.

BERT, the model behind that 2019 Google update, dissolved this problem by reading each word in light of the words around it — in both directions at once. The same word now gets a different vector depending on its neighbors. This is why Google framed the update around prepositions and conversational phrasing: the small connective words that determine whether you're traveling to a country or from it, whether you can pick up a prescription for someone else or need one for yourself. Google called it the most important leap in five years and estimated it affected around ten percent of all searches. Search engineers watched queries that had returned generic filler suddenly surface the specific, correct answer, because the machine had finally started weighing the words most of us use without thinking.

What the Machine Still Can't Find

Here is the part the breathless coverage leaves out. Semantic search is not a strict upgrade. It is a different instrument, and for a whole class of problems it is the wrong one.

Ask a semantic engine to find the product with serial number "SKU-2847-B" and its talent for meaning becomes a liability. It will happily surface visually and conceptually similar codes — SKU-2846, SKU-2847-C — because in the geometry of embeddings those things are near neighbors. But you didn't want something close. You wanted that exact string, and nothing else. The same failure haunts legal citations, error codes, part numbers, rare proper nouns, and any query where precision matters more than resemblance. Meaning-based search smears the edges of exactness that keyword search keeps razor-sharp.

Which is why the engineers who actually build these systems reached a conclusion that undercuts the marketing entirely: they refused to choose. Serious production search runs both engines side by side — the inverted index for exact terms and rare identifiers, the vector index for meaning and paraphrase — and blends the results. The industry calls it hybrid search, and it is now the default architecture precisely because neither approach is good enough alone. The story wasn't replacement. It was a truce.

That truce is the honest answer to why AI finds results keyword search misses. It isn't that the new machine is smarter across the board. It's that it converts language into a space where nearness means similarity of meaning — a genuinely new sense the old machine lacked, and a genuinely worse tool for the handful of jobs the old machine performed flawlessly. The most capable search systems ever built are also the most humble about it. They keep the literal-minded index around, because sometimes you don't want the computer to understand what you meant. You want it to find exactly what you said.

References

Related Essays

The Guessing Instinct That Retrieval Never Touches
Information Systems Technology Adoption and Management

The Guessing Instinct That Retrieval Never Touches

A language model asked the same factual question three times gave three confident, wrong answers. The real culprit isn't broken software — it's benchmarks that reward bluffing over honesty, a flaw retrieval-augmented generation can narrow but never actually cure.

S.J. Nam, Ph.D Jul 7, 2026 7 min read
The Bottleneck Was Never the Vector
Information Systems Software Development

The Bottleneck Was Never the Vector

Vector-search benchmarks measure the one part every engine already optimized and ignore the thing that actually breaks production retrieval: filtering against live business data. That reframes the entire pgvector vs Qdrant vs Pinecone debate.

S.J. Nam, Ph.D Jul 4, 2026 7 min read
Search Engines Quietly Abandoned Recall, Not Just Improved It
Information Systems Information Retrieval

Search Engines Quietly Abandoned Recall, Not Just Improved It

Precision is easy to report; recall requires counting every relevant document that exists, which nobody has done since the web outgrew ten blue links. The AI search industry hasn't solved that problem — it has stopped mentioning it.

S.J. Nam, Ph.D Jul 2, 2026 7 min read
The Filing Clerk Beats the Genius: Why Hybrid Search Works
Information Systems Information Retrieval

The Filing Clerk Beats the Genius: Why Hybrid Search Works

Vector search misses exact strings; keyword search misses meaning. The reason hybrid retrieval works isn't that it's smarter — it's that it refuses to trust either retriever's confidence, and hands the decision to a score-blind referee.

S.J. Nam, Ph.D Jul 1, 2026 7 min read