> ## Documentation Index
> Fetch the complete documentation index at: https://algolia.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Search is more than textual matching

> Understand that a good search experience is more than textual matching.

Search isn't just a letter-by-letter comparison.
Compare searches on these sentences ([records](/doc/guides/sending-and-managing-data/prepare-your-data#algolia-records)):

{/* vale Google.Exclamation = NO  */}

{/* vale Algolia.We = NO  */}

1. To be or not to be that is the question
2. This was the best of times the worst of times
3. Ask not what your country asks of you but what you can do for your country
4. For a long time I used to go to bed early
5. Shakespeare and Dickens are both famous British authors
6. By George, I should've known that! I'll be a dickens!
7. An accomplished woman almost always knows more than we men, though her knowledge is of a different sort

{/* vale Google.We = YES  */}

{/* vale Google.FirstPerson = YES  */}

* A search for "ask" returns one result: sentence 3.
* A search for "time" returns two result: sentences 2 and 4.
* A search for "be" returns four results: sentence 1 and 6 "be", sentence 2 "**be**st", and sentence 4 "**be**d".

## Where textual matching doesn't work

Consider these searches on the preceding sentences:

* "qestion" ("question" mistyped). No sentences are returned.
* "be". What sentence should come first? The ones that match exactly (the word "be")? Or some other criteria?
* "literary quotes"? Textual matching doesn't know anything about these sentences - are these political or literary quotes? The quotes need to be classified, tagged as coming from novels, politicians, authors, countries.

All these queries require something more.

## Going beyond textual matching

Simple textual matching won't solve every search problem: it's only the starting point.

## Add structure

By adding more information to the preceding sentences (records), their relevance can be improved:

{/* vale Google.Exclamation = NO  */}

{/* vale Vale.Spelling = NO  */}

1. "To be or not to be, that is the question", shakespeare, british, hamlet, theater
2. "It was the best of times, it was the worst of times", dickens, british, tale of two cities, novel
3. "Ask not what your country asks of you but what you can do for your country", kennedy, american, speech, politics
4. "For a long time I used to go to bed early", proust, french, recherche, novel
5. "Shakespeare and Dickens are both famous British authors", georgette, british, history of british literature, essay
6. "By George, I should've known that! I'll be a dickens!", landly, british, my fair lady, theater
7. "An accomplished woman almost always knows more than we men, though her knowledge is of a different sort.", george elliot, british, middlemarch, novel

{/* vale Vale.Spelling = YES  */}

{/* vale Google.Exclamation = YES  */}

## Going further

A good search experience also needs to consider [filtering](/doc/guides/managing-results/refine-results/filtering), [attribute priorities](/doc/guides/managing-results/must-do/searchable-attributes), [custom ranking](/doc/guides/managing-results/must-do/custom-ranking), [handling typos](/doc/guides/managing-results/optimize-search-results/typo-tolerance), [synonyms](/doc/guides/managing-results/optimize-search-results/adding-synonyms), and more.
Insights from [user actions](/doc/guides/sending-events), [analytics](/doc/guides/search-analytics/overview), [personalization](/doc/guides/personalization/classic-personalization/what-is-personalization), and [A/B testing](/doc/guides/ab-testing/what-is-ab-testing) can also help you fine-tune your search experience to better meet the needs of your users.