A lot of content can make it hard for your users to find what they're looking for. That's why we developed the Userlane Search! Your users can now search through the content you create for them nice and easy.

How does it work?

The Userlane Search will search through the following:

Interactive Guides:

  1. Chapter title
  2. Chapter subtitle
  3. The title of the guide (viewable in the Userlane Dashboard)
  4. The subtitle of the guide (viewable in the Userlane Dashboard)

Inside a guide:

  1. Intro/Outro Title
  2. Step title
  3. Text and content of a step
  4. Infobox content
  5. Link title
  6. Link description
  7. Content of specific value-inputs

Announcements:

  1. The public title of the Announcement
  2. The message
  3. The text of the button of the primary link
  4. The text of the button of the secondary link

How are search results filtered and ranked?

Now that we know, which content users are able to find through the Userlane Search, let's talk about, how Search structures search results.

Ranking

Userlane Search ranks according to Term Frequency / Inverse Document Frequency

Term Frequency

e.g. searching “user” ranks a tutorial that contains the word “user” five times higher than a tutorial that contains “user” only once.

Inverse Document Frequency

e.g. searching “user” ranks a short announcement that contains only 10 words, one of which is “user”, higher than a long tutorial that contains twenty steps, one of which contains the word “user” once.

Filtering

The Userlane Search will, however, make sure that only the accessible content is shown in the search results. What do we mean by accessible content? Keep reading:

Tutorials

  • Only show active tutorials in active chapters
  • Only show tutorials that match user segmentation
  • Only show tutorials that match page segmentation
  • Only show tutorials in the language of the user or with a fallback language

Announcements

  • Only show announcements active at the time of searching
  • Only show announcements that match user segmentation
  • Only show announcements that match page segmentation
  • Only show announcements in the language of the user or with a fallback language

Related Articles

Did this answer your question?