whoogle-search: Self-Host a Privacy-Focused Search Interface

Overview

Whoogle is a self-hosted search interface designed to proxy Google results while removing ads, tracking links, AMP pages, and other unwanted elements. It was built for people who wanted a private-feeling, customizable alternative to using Google directly.

The project README now reports that Google has blocked the non-JavaScript search requests Whoogle depends on, and that its Custom Search fallback is no longer workable. As a result, it does not currently provide search results and is retained for reference or for independent forks rather than new deployments.

Key Features

• Historically presented Google results without ads or sponsored content.
• Filtered tracking tags, AMP links, and referrer headers from results.
• Supported self-hosting with Docker, Python package installation, and other deployment options.
• Offered themes, search suggestions, location filters, and DDG-style bangs.
• Included optional Tor and HTTP/SOCKS proxy routing.
• Could return sanitized search results as JSON through content negotiation.

Use Cases

• Review the code or deployment design of a Flask-based metasearch project, with the understanding that its upstream search path no longer works.
• Fork the project as a starting point for experimentation with a different search provider or upstream interface.
• Study an example of self-hosted web application configuration, including Docker, reverse proxies, and environment-based settings.
• Avoid choosing Whoogle for a new search deployment if you need a working service or ongoing maintainer support.

Getting Started

The README documents installation from source, but the project notice says deployments should not be expected to work today. For historical setup details and the code, see the official repository.

Considerations

• The README states that Whoogle no longer returns search results because Google blocked the requests it relied on.
• The documented Google Custom Search fallback is also described as no longer viable.
• The repository is archived, and the maintainers state that there will be no further releases, bug fixes, or contribution reviews.
• The MIT license permits forks, but adapting the code to another search provider would require independent development.