[GH-ISSUE #1265] [BUG] Mullvad Leta results are Brave instead of Google results #745

Closed
opened 2026-02-25 20:36:28 +03:00 by kerem · 3 comments
Owner

Originally created by @searchjaunt on GitHub (Oct 10, 2025).
Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/1265

Describe the bug
It seems that the current Mullvad Leta implentation returns Brave instead of Google results
I don't see any switch to force Google results. Pls provide a switch to have the choice.

To Reproduce
Steps to reproduce the behavior:

  1. Go to Mullvad Leta
  2. Do a search
  3. Do the same search with Whoogle
  4. The results of the latter is identical to the Mullvad Leta results with the Brave option and not the Google resuts

Deployment Method

  • Heroku (one-click deploy)
  • [X ] Docker
  • run executable
  • pip/pipx
  • Other: [describe setup]

Version of Whoogle Search

  • [X ] Latest build from [source] (i.e. GitHub, Docker Hub, pip, etc)
  • Version [version number]
  • Not sure
Originally created by @searchjaunt on GitHub (Oct 10, 2025). Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/1265 **Describe the bug** It seems that the current Mullvad Leta implentation returns Brave instead of Google results I don't see any switch to force Google results. Pls provide a switch to have the choice. **To Reproduce** Steps to reproduce the behavior: 1. Go to Mullvad Leta 2. Do a search 3. Do the same search with Whoogle 4. The results of the latter is identical to the Mullvad Leta results with the Brave option and not the Google resuts **Deployment Method** - [ ] Heroku (one-click deploy) - [X ] Docker - [ ] `run` executable - [ ] pip/pipx - [ ] Other: [describe setup] **Version of Whoogle Search** - [X ] Latest build from [source] (i.e. GitHub, Docker Hub, pip, etc) - [ ] Version [version number] - [ ] Not sure
kerem 2026-02-25 20:36:28 +03:00
Author
Owner

@Don-Swanson commented on GitHub (Oct 14, 2025):

@searchjaunt
I'm running tests and comparing results, and my Whoogle results 100% match the Leta Google Results, but start to differ from the Leta Brave Results towards the end of the 1st page, and definitely on the second.

Whoogle is hardcoded to use the Leta Google Results, so if you are finding otherwise, Please provide your evidence.

def gen_query_leta(query, args, config) -> str:
    """Builds a query string for Mullvad Leta backend
    ...
    """
    # Ensure search query is parsable
    query = urlparse.quote(query)
    
    # Build query starting with 'q='
    query_str = 'q=' + query
    
    # Always use Google as the engine (Leta supports 'google' or 'brave')
    query_str += '&engine=google'
<!-- gh-comment-id:3399706526 --> @Don-Swanson commented on GitHub (Oct 14, 2025): @searchjaunt I'm running tests and comparing results, and my Whoogle results 100% match the Leta Google Results, but start to differ from the Leta Brave Results towards the end of the 1st page, and definitely on the second. Whoogle is hardcoded to use the Leta Google Results, so if you are finding otherwise, Please provide your evidence. ``` def gen_query_leta(query, args, config) -> str: """Builds a query string for Mullvad Leta backend ... """ # Ensure search query is parsable query = urlparse.quote(query) # Build query starting with 'q=' query_str = 'q=' + query # Always use Google as the engine (Leta supports 'google' or 'brave') query_str += '&engine=google' ```
Author
Owner

@searchjaunt commented on GitHub (Oct 14, 2025):

Indeed, you're right. I guess I've confused it with the results from Google itself, which differ significantly from the Leta Google Results

<!-- gh-comment-id:3400343963 --> @searchjaunt commented on GitHub (Oct 14, 2025): Indeed, you're right. I guess I've confused it with the results from Google itself, which differ significantly from the Leta Google Results
Author
Owner

@Don-Swanson commented on GitHub (Oct 14, 2025):

You’ll need to keep in mind that the Leta Google search results are not only cached, but also only for a specific region, so if you can match those 2, they will match exactly

<!-- gh-comment-id:3401361054 --> @Don-Swanson commented on GitHub (Oct 14, 2025): You’ll need to keep in mind that the Leta Google search results are not only cached, but also only for a specific region, so if you can match those 2, they will match exactly
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/whoogle-search#745
No description provided.