Irrelevant pinned site in search results - Invalid search result at top for "firefox git repo"

erik

Steps to reproduce:

open Kagi
have learn.microsoft.com pinned
search for: firefox git repo

Expected behavior:

Kagi produces a list of relevant results.
as long as they contain relevant results, pinned sites are shown on top
pinned sites are prioritized as long as they are somehow relevant
pinned sites does not show up if they are very irrelevant

I was very conflicted about this bug report as I understand it might be a hard case and there might be ranking signals I don't see like incoming links or synonyms for Firefox or what do I know. I also understand that I should probably use "Raise" instead of "Pin", But as the highlighted (in my screenshot) explanation says: "If you pin it, we will rank it on top of the results for you (if relevant)."

Debug info:

Browser: Firefox
OS: Windows 10
Connected to: EUROPE-WEST2 Network latency: 97ms

Image/Video:

Vlad

erik What exactly is the issue?

erik

Sorry for the late answer [1]. I tried to explain it above, but the crux of it is this:

Should a site show up if it

is pinned
but isn't relevant (no mention of Firefox)

My guess based on first using Google happily for some years and the suffering from it second guessing me the next decade and seeking explanations is that something behind the scenes expanded <Firefox> to <browser> or maybe something even wider and then it matched.

Maybe this is correct for many and I should write Firefox in doubleqoutes to demand an exact match, but personally I write browser when I mean any browser and Firefox when I mean Firefox specifically.

Hope this helps.

[1]: which is a good sign because I haven't had any other issues with Kagi since February[2]

[2]: hich is a long time in my world, I had issues with Google on a weekly basis and DDG probably every day

Vlad

erik A pinned site may suface low in our results (say poistion 50 and still be on our 'first page') but because it is pinned it will surface on top. Perhaps using "Raise" instead of Pin would work better for your use case.