Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(categories): better web results rankings #621

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

aleksasiriski
Copy link
Member

@matijakljajic @k4lizen Do you agree with this?

Copy link

netlify bot commented Nov 18, 2024

Deploy Preview for hearchco ready!

Name Link
🔨 Latest commit c5eee26
🔍 Latest deploy log https://app.netlify.com/sites/hearchco/deploys/673b67fa70cd80000812ef2c
😎 Deploy Preview https://deploy-preview-621--hearchco.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@aleksasiriski
Copy link
Member Author

Btw you can use the Netlify preview deployment above to test the changes, since the agent now works as the frontend tells it to :)

@matijakljajic
Copy link
Member

matijakljajic commented Nov 18, 2024

Can you give some specific example queries you've tried out where this config works better?

@aleksasiriski
Copy link
Member Author

aleksasiriski commented Nov 19, 2024

Not so much in query but in a scenario:

I noticed once that only Google, Mojeek and Bing returned results and there were many unique ones which ended up having the top 5 results be all from different engines and since all engines had the same multiplier it resulted in a random order (Mojeek result was first). This made me come up with this slight change in ranking, preferring results from Google and Bing and all of their leeches (since we already set those two to be required by origin, whereas Mojeek is only preferred) :)

@aleksasiriski
Copy link
Member Author

@matijakljajic What's the conclusion here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants