# Understanding relevance and ranking ### Search score When performing a search, Search.io assigns a search score to each document in the index. The score ranges from 0 (no match) to 1 (perfect match) and search results are ordered starting with the highest score. The relevance score consists of three score components: the *keyword score,* the *neural score*, and the *boost score*. ![The components of the search score.](/files/z05pPwh6WNCeChs0s9NE) ### Relevance The **keyword score** represents the \[[Textual relevance](/documentation/fundamentals/search-settings/textual-relevance.md)]\(/pages/F654qUlittxw1Y3cYpxT) of the result. In other words, how well does the search text match the content. This considers spelling, synonyms, stemming, and other language specific features. The **neural score** represents the neural hash similarity of the result and the search text. The larger of these two scores is used when calculating the overall **search score**, and their contribution generally comprises the majority of the total score, since most users are looking for results which match their query. ### Ranking The **boost score** represents the business-specific ranking of the **search score**. Generally comprising a smaller portion of the total score, it can be used to make [Ranking adjustments](/documentation/fundamentals/search-settings/ranking-adjustments.md) to better tailor results to business requirements or to personalize search results. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.search.io/documentation/fundamentals/search-settings/understanding-relevance-and-ranking.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.