HomeDev GuideAPI Reference
Dev GuideAPI ReferenceUser GuideGitHubNuGetDev CommunitySubmit a ticketLog In
GitHubNuGetDev CommunitySubmit a ticket

More like

Describes how to build functionality to search for related objects using the MoreLike method in Optimizely Search & Navigation.

Use the MoreLike method to find documents whose text content is "like" a given string. This functionality is typically used for, but not limited to, finding related documents/objects.


A simple example can look like this:

searchResult = client.Search<BlogPost>()

After invoking the MoreLike method, you can customize the search query with several methods. For instance, because you do not have a lot of documents with similar content, you probably want to lower the minimum document frequency requirement. That is the level at which words that do not occur in at least that many documents are ignored, which defaults to five.

searchResult = client.Search<BlogPost>()

A full list of extension methods for customizing the query follows below. But before you look at those, look at an example of finding documents "related" to a given document. Assuming you indexed two BlogPosts with similar content, you can search for similar documents as the first and expect the second using a query such as this:

var firstBlogPost = //Some indexed blog post about guitars
var secondBlogPost = //Another blog post about guitars

searchResult = client.Search<BlogPost>()
    .Filter(x => !x.Id.Match(firstBlogPost.Id))



When you issue these types of queries, use some caching because the result is not likely to change very often. Even if it does, a few minutes' delay might not matter.

Customize the query

As the nature of content can differ greatly between indexes and types, it is often a good idea to play around with available settings after having invoked the MoreLike method. The following methods can be called to customize the query. See also the Elastic Search guide.

  • MinimumDocumentFrequency – The frequency at which words are ignored, which do not occur in at least this many docs. Default is 5.
  • MaximumDocumentFrequency – The maximum frequency in which words may still appear. Words that appear in more than this many docs are ignored. Default is unbounded.
  • PercentTermsToMatch – The percentage of terms to match on. Default is 30 (percent).
  • MinimumTermFrequency – The frequency below which terms are ignored in the source doc. The default frequency is 2.
  • MinimumWordLength – The minimum word length below which words are ignored. Default is 0.
  • MaximumWordLength – The maximum word length above which words are ignored. Default is unbounded (0).
  • MaximumQueryTerms – The maximum number of query terms included in any generated query. Default is 25.
  • StopWords – A list of words considered "uninteresting" and ignored.