Relevance overview

Relevancy from a high-level point of view - finding records, ranking, tie-breaking, typos, and other settings.

Relevance touches on every aspect of the Algolia search and discovery experience. It governs everything from structuring your data to how the engine queries your indices and orders the results to what your users see as they type. The aim is to find a general configuration that gets the best results in all situations.

Configuration is about telling Algolia how to search your data. You already began this process when structuring your data, where you told Algolia which attributes to search in and which to use to customize your ranking.

• Configure textual relevance (dashboard)
• Configure textual relevance (API clients)

Must dos

Defining searchable attributes and customizing your ranking are the two must do s before configuring anything else. These actions alone could get you production-ready.

• Searchable attributes
• Custom ranking

Get the best from Algolia

Before going live, you should become familiar with Algolia’s key features. Some are immediately useful, like:

• Creating synonyms
• Adding filters
• Alternative sorting strategies.

Others quickly become important, like:

• What to do if you get too few or no results
• Merchandising
• Grouping records
• Geolocation.

Later, as your solution evolves, you’ll take advantage of:

• Search analytics
• Personalization
• A/B testing.

Finally, learning how the engine works will be invaluable as you structure your data and fine-tune your results. You’ll want to learn the core features of Algolia’s engine, such as:

• Typo tolerance
• Prefix search
• Natural language processing (NLP)
• Detecting user intent.

What is relevance?

Relevance is finding results that match a query and ranking records so that the best-matched results appear at the top of the list.

• How does Algolia define relevance?
• What is search relevance?
• Search engine relevance

Finding results

Finding results consists of defining attributes and text-based comparisons that affect the engine’s choice of which objects to return. These include typos, prefixes, plurals, stop words, and other text-based criteria that Algolia uses to enhance relevancy. You may also need to consider some non-text-based criteria, such as filtering and geolocation.

Ranking records

Ranking is critical since users should see the results that most closely match their queries first: this is wholly dependent on the order in which records are presented. Algolia’s ranking uses a tie-breaking algorithm to determine how results are ordered.

Index settings and query parameters

You can configure Algolia in two ways (and at two times):

• During index configuration, that is, when you change index settings. These changes are permanent and global - they affect how the data is stored and affect every search.
• When setting query parameters. When you send a query to Algolia, you can add parameters that alter the index settings. These parameters only affect the current search.

You can change some settings only during index configuration, as they affect how the data is stored. For example, adding new synonyms or changing typo tolerance settings. The same applies to query parameters—some settings make sense only at query time, like filtering, geolocation, and defining which attributes to retrieve.

The specific API parameter documentation indicates whether a setting is available during index configuration, query time, or both.