starred/whoogle-search

Fork 0

mirror of https://github.com/benbusby/whoogle-search.git synced 2026-04-25 20:25:51 +03:00

[GH-ISSUE #417] [BUG] First result not shown sometimes #277

New issue

Closed

opened 2026-02-25 20:35:19 +03:00 by kerem · 5 comments

kerem commented

2026-02-25 20:35:19 +03:00

Owner

Originally created by @Mazawrath on GitHub (Sep 5, 2021).
Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/417

Describe the bug
When making a search Whoogle sometimes omits the first result.

To Reproduce
Search something like "Google" and you will see the second result on top. This only happens on some searches but not others. It will happen every time on certain search terms
I was not able to reproduce this using the public instances. I would rather keep my search engine URL omitted but if needed I can PM you it for testing.

Deployment Method
DigitalOcean App via Docker

Version of Whoogle Search
Latest build

Desktop (please complete the following information):

OS: Wndows
Browser: Brave
Version: V1.29.76

Additional context
https://imgur.com/a/kOEZA24
https://imgur.com/a/RwpnodJ

Originally created by @Mazawrath on GitHub (Sep 5, 2021). Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/417 **Describe the bug** When making a search Whoogle sometimes omits the first result. **To Reproduce** Search something like "Google" and you will see the second result on top. This only happens on some searches but not others. It will happen every time on certain search terms I was not able to reproduce this using the public instances. I would rather keep my search engine URL omitted but if needed I can PM you it for testing. **Deployment Method** DigitalOcean App via Docker **Version of Whoogle Search** Latest build **Desktop (please complete the following information):** - OS: Wndows - Browser: Brave - Version: V1.29.76 **Additional context** https://imgur.com/a/kOEZA24 https://imgur.com/a/RwpnodJ

kerem

2026-02-25 20:35:19 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-25 20:35:19 +03:00

Author

Owner

@benbusby commented on GitHub (Sep 15, 2021):

If you clear your language search settings (from the screenshot it looks like it's currently set to English), does that fix it for you? The language config seems to really mess with Google search results, so I'm guessing that's the culprit here.

@benbusby commented on GitHub (Sep 15, 2021): If you clear your language search settings (from the screenshot it looks like it's currently set to English), does that fix it for you? The language config seems to really mess with Google search results, so I'm guessing that's the culprit here.

kerem commented

2026-02-25 20:35:19 +03:00

Author

Owner

@Mazawrath commented on GitHub (Sep 19, 2021):

I removed the WHOOGLE_CONFIG_SEARCH_LANGUAGE variable and I'm still missing the first result.

@Mazawrath commented on GitHub (Sep 19, 2021): I removed the `WHOOGLE_CONFIG_SEARCH_LANGUAGE` variable and I'm still missing the first result.

kerem commented

2026-02-25 20:35:19 +03:00

Author

Owner

@Mazawrath commented on GitHub (Oct 27, 2021):

I hate to ping again but I would really like a solution to this. I love using Whoogle but this is a issue I'd really like fixed.

@Mazawrath commented on GitHub (Oct 27, 2021): I hate to ping again but I would really like a solution to this. I love using Whoogle but this is a issue I'd really like fixed.

kerem commented

2026-02-25 20:35:19 +03:00

Author

Owner

@benbusby commented on GitHub (Oct 27, 2021):

Ah, my bad. I meant to come back to this and look into it further, but forgot, so I apologize.

The issue I was having previously with investigating this on my end is that I ultimately just can't reproduce it, so I may need you to send me details about your config (environment variables set, config items set, where it's being hosted, other search terms that reproduce the error, etc). My email is on my profile if you want to send all of that over privately. My guess is that there's either an issue where the geographic location of where your instance is being hosted is skewing results, or there's some misconfigured config value that maybe is causing problems.

For reference, here's a search for "google" on a US hosted instance with all default config settings:

And then here's a search for "google" in an instance hosted in Ireland, also with all default config settings. As you'll see, the first result is now google.ie solely due to hosting location and nothing else:

Then if you manually set the "filter by country" to the US for that instance, it still doesn't really cause the results to match an instance hosted in the US:

From everything I've tried with various query parameters, you can't really replicate "organic" US hosted results with Whoogle. All I can really do is periodically trial-and-error various settings to see if it's possible to modify Whoogle results to be the same regardless of hosting location.

Then again, maybe your issue is just caused by a simple config setting that we can fix. Hopefully this at least helps illuminate the difficulty of narrowing down your problem, even if it isn't an actual solution.

@benbusby commented on GitHub (Oct 27, 2021): Ah, my bad. I meant to come back to this and look into it further, but forgot, so I apologize. The issue I was having previously with investigating this on my end is that I ultimately just can't reproduce it, so I may need you to send me details about your config (environment variables set, config items set, where it's being hosted, other search terms that reproduce the error, etc). My email is on my profile if you want to send all of that over privately. My guess is that there's either an issue where the geographic location of where your instance is being hosted is skewing results, or there's some misconfigured config value that maybe is causing problems. For reference, here's a search for "google" on a US hosted instance with all default config settings: <img width="763" alt="Screen Shot 2021-10-26 at 8 39 29 PM" src="https://user-images.githubusercontent.com/33362396/138990566-2590e0fa-77e6-4ddc-87f1-a28e8eb8e76d.png"> And then here's a search for "google" in an instance hosted in Ireland, also with all default config settings. As you'll see, the first result is now `google.ie` solely due to hosting location and nothing else: <img width="745" alt="Screen Shot 2021-10-26 at 8 48 23 PM" src="https://user-images.githubusercontent.com/33362396/138991717-7988b7fb-2f32-4d91-b6c6-50c8e74a473e.png"> Then if you manually set the "filter by country" to the US for that instance, it still doesn't really cause the results to match an instance hosted in the US: <img width="756" alt="Screen Shot 2021-10-26 at 8 50 56 PM" src="https://user-images.githubusercontent.com/33362396/138991764-5b5844d4-bc13-478c-9c3b-5fdfa60d3121.png"> From everything I've tried with various query parameters, you can't really replicate "organic" US hosted results with Whoogle. All I can really do is periodically trial-and-error various settings to see if it's possible to modify Whoogle results to be the same regardless of hosting location. Then again, maybe your issue is just caused by a simple config setting that we can fix. Hopefully this at least helps illuminate the difficulty of narrowing down your problem, even if it isn't an actual solution.

kerem commented

2026-02-25 20:35:19 +03:00

Author

Owner

@Mazawrath commented on GitHub (Oct 27, 2021):

Ah, it seems that it was one of the other config settings I was using!
I set the location because sometimes Google would just think I'm in Afghanistan or something and would give me totally foreign results.
Quite an odd issue. I'm running this in New York so I honestly don't even know how my server even goes overseas to ping Google.

@Mazawrath commented on GitHub (Oct 27, 2021): Ah, it seems that it was one of the other config settings I was using! I set the location because sometimes Google would just think I'm in Afghanistan or something and would give me totally foreign results. Quite an odd issue. I'm running this in New York so I honestly don't even know how my server even goes overseas to ping Google.