[GH-ISSUE #1922] Search doesn't seem very relevant #1189

Closed
opened 2026-03-02 11:55:39 +03:00 by kerem · 10 comments
Owner

Originally created by @Sacmanxman2 on GitHub (Sep 9, 2025).
Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/1922

Describe the feature you'd like

I vaguely remember this being much better a few versions ago but I'm not sure, if that's the case this might be more of a bug report than a feature request.

I can search for the exact title of a bookmark, but the results might not have that bookmark until a few rows down. The first items don't even contain all the words I'm searching for. I have it sorted by "Most relevant first", and I tried re-indexing all the bookmarks (I've got about 900 at this point). Meilisearch version is v1.13.3, karakeep app version is 0.27.0.

For example, I searched for an article called "Give yourself a ripcord to pull" using that exact title text. When I use quotes it comes up first, but without quotes it doesn't show up until about the 5th row of results. The first result doesn't even contain all the words I'm searching for.

When I search for just "ripcord" that article comes up (and ONLY that article - I don't think anything else I've saved uses that word). I'd expect adding more words would bring more results, but shouldn't the first result be the one that contains all the words?

Appreciate everything you guys are doing on this app, I use it all the time and it's one of my favorite things I've self-hosted!

Describe the benefits this would bring to existing Karakeep users

Would make it easier to find desired pages.

Can the goal of this request already be achieved via other means?

I can search for the title with quotes, but that backfires if I miss a word or don't have it exactly right.

Have you searched for an existing open/closed issue?

  • I have searched for existing issues and none cover my fundamental request

Additional context

No response

Originally created by @Sacmanxman2 on GitHub (Sep 9, 2025). Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/1922 ### Describe the feature you'd like I vaguely remember this being much better a few versions ago but I'm not sure, if that's the case this might be more of a bug report than a feature request. I can search for the exact title of a bookmark, but the results might not have that bookmark until a few rows down. The first items don't even contain all the words I'm searching for. I have it sorted by "Most relevant first", and I tried re-indexing all the bookmarks (I've got about 900 at this point). Meilisearch version is v1.13.3, karakeep app version is 0.27.0. For example, I searched for an article called "Give yourself a ripcord to pull" using that exact title text. When I use quotes it comes up first, but without quotes it doesn't show up until about the 5th row of results. The first result doesn't even contain all the words I'm searching for. When I search for just "ripcord" that article comes up (and ONLY that article - I don't think anything else I've saved uses that word). I'd expect adding more words would bring more results, but shouldn't the first result be the one that contains all the words? Appreciate everything you guys are doing on this app, I use it all the time and it's one of my favorite things I've self-hosted! ### Describe the benefits this would bring to existing Karakeep users Would make it easier to find desired pages. ### Can the goal of this request already be achieved via other means? I can search for the title with quotes, but that backfires if I miss a word or don't have it exactly right. ### Have you searched for an existing open/closed issue? - [x] I have searched for existing issues and none cover my fundamental request ### Additional context _No response_
kerem 2026-03-02 11:55:39 +03:00
Author
Owner

@psjay commented on GitHub (Sep 9, 2025):

Same issue, I believe it was introduced by the last few versions.

<!-- gh-comment-id:3268917892 --> @psjay commented on GitHub (Sep 9, 2025): Same issue, I believe it was introduced by the last few versions.
Author
Owner

@thiswillbeyourgithub commented on GitHub (Sep 9, 2025):

I agree. I have a feeling that the title is weighed about as much as the content when doing search, which is terrible because if I remember two words from the title, I have to wade through 50 results that contain those two words in the content to then finally find the bookmark containing those words in the title.

Hence I'm suspicious that there is a configuration mishap in the meilisearch parameters.

Also, I think that supporting title: search (as requested here) should be of higher priority than low and should maybe be a good first issue as there are already selectors implemented..

<!-- gh-comment-id:3270847703 --> @thiswillbeyourgithub commented on GitHub (Sep 9, 2025): I agree. I have a feeling that the title is weighed about as much as the content when doing search, which is terrible because if I remember two words from the title, I have to wade through 50 results that contain those two words in the content to then finally find the bookmark containing those words in the title. Hence I'm suspicious that there is a configuration mishap in the meilisearch parameters. Also, I think that supporting `title:` search (as requested [here](https://github.com/karakeep-app/karakeep/issues/1675)) should be of higher priority than `low` and should maybe be a `good first issue` as there are already selectors implemented..
Author
Owner

@MohamedBassem commented on GitHub (Sep 13, 2025):

Turns out that this is actually a bug. In a big refactoring that I recently did (github.com/karakeep-app/karakeep@b94896a0f8), I broke by mistake the ranking score that I was sorting the results with :) Will send a fix now.

<!-- gh-comment-id:3288725227 --> @MohamedBassem commented on GitHub (Sep 13, 2025): Turns out that this is actually a bug. In a big refactoring that I recently did (https://github.com/karakeep-app/karakeep/commit/b94896a0f8fa43b957a9bdd6ab57ada0ab8101af), I broke by mistake the ranking score that I was sorting the results with :) Will send a fix now.
Author
Owner

@thiswillbeyourgithub commented on GitHub (Sep 13, 2025):

Turns out that this is actually a bug. In a big refactoring that I recently did (b94896a), I broke by mistake the ranking score that I was sorting the results with :) Will send a fix now.

So happy to read this. Thank you so much!

<!-- gh-comment-id:3288727796 --> @thiswillbeyourgithub commented on GitHub (Sep 13, 2025): > Turns out that this is actually a bug. In a big refactoring that I recently did ([b94896a](https://github.com/karakeep-app/karakeep/commit/b94896a0f8fa43b957a9bdd6ab57ada0ab8101af)), I broke by mistake the ranking score that I was sorting the results with :) Will send a fix now. So happy to read this. Thank you so much!
Author
Owner

@MohamedBassem commented on GitHub (Sep 13, 2025):

Fix is in github.com/karakeep-app/karakeep@3bae3aad9a which will be available in the nightly build in 20 mins. I'd appreciate if you can give it a try and let me know if the sorting of the results is better :)

<!-- gh-comment-id:3288728075 --> @MohamedBassem commented on GitHub (Sep 13, 2025): Fix is in https://github.com/karakeep-app/karakeep/commit/3bae3aad9a62dbf2cc9a0038c90ea992166cc336 which will be available in the nightly build in 20 mins. I'd appreciate if you can give it a try and let me know if the sorting of the results is better :)
Author
Owner

@MohamedBassem commented on GitHub (Sep 13, 2025):

If it indeed improves the results, I'll probably create a hotfix release.

<!-- gh-comment-id:3288728398 --> @MohamedBassem commented on GitHub (Sep 13, 2025): If it indeed improves the results, I'll probably create a hotfix release.
Author
Owner

@thiswillbeyourgithub commented on GitHub (Sep 13, 2025):

I'm on it!

Edit: I'm building the app so it's taking some time as my server was already doing intensive IO work.

<!-- gh-comment-id:3288729595 --> @thiswillbeyourgithub commented on GitHub (Sep 13, 2025): I'm on it! Edit: I'm building the app so it's taking some time as my server was already doing intensive IO work.
Author
Owner

@thiswillbeyourgithub commented on GitHub (Sep 13, 2025):

Okay there is no errors from running the fix. The results seem relevant to me. Thanks a lot @MohamedBassem looks good to me.

<!-- gh-comment-id:3288743307 --> @thiswillbeyourgithub commented on GitHub (Sep 13, 2025): Okay there is no errors from running the fix. The results seem relevant to me. Thanks a lot @MohamedBassem looks good to me.
Author
Owner

@MohamedBassem commented on GitHub (Sep 13, 2025):

Thanks for confirming @thiswillbeyourgithub! I've published 0.27.1 as a hotfix.

<!-- gh-comment-id:3288783432 --> @MohamedBassem commented on GitHub (Sep 13, 2025): Thanks for confirming @thiswillbeyourgithub! I've published 0.27.1 as a hotfix.
Author
Owner

@MohamedBassem commented on GitHub (Sep 13, 2025):

@thiswillbeyourgithub and gpt-5 implemented the title: search qualifier for you: https://github.com/karakeep-app/karakeep/pull/1940 :)

<!-- gh-comment-id:3288832369 --> @MohamedBassem commented on GitHub (Sep 13, 2025): @thiswillbeyourgithub and gpt-5 implemented the `title:` search qualifier for you: https://github.com/karakeep-app/karakeep/pull/1940 :)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/karakeep#1189
No description provided.