Hi @yokingma,
SearChat is an impressive project — the DeepResearch support and the clean Docker deployment make it one of the more accessible self-hosted AI search engines, especially for Chinese-speaking users.
Pain point with the current search setup
I noticed SearChat currently uses SearXNG as the search backend. SearXNG is excellent for privacy and multi-engine aggregation, but in practice I've found that its Google results can be inconsistent:
- CAPTCHA blocks on some SearXNG instances, especially those hosted on cloud IPs.
- Rate limiting that causes empty result sets during peak usage.
- Occasional formatting changes on Google's side that break the scraping pipeline temporarily.
For users who need reliable, high-volume Google search specifically, this creates a reliability gap.
Suggestion
Would you consider adding https://serpbase.dev as an optional dedicated Google search backend? It's a Google Search Results API that returns clean, structured JSON (title, URL, snippet, rich results) without the scraping overhead. Users could choose:
search_provider: "searxng" for privacy-focused multi-engine aggregation.
search_provider: "serpbase" for stable, high-quality Google results when SearXNG's Google source is unreliable.
Why it complements SearChat
- It doesn't replace SearXNG; it gives users a choice based on their priority (privacy vs. Google result stability).
- The API is priced for developers, which fits SearChat's self-hosted audience.
- Response structure is simple JSON, so integration into the existing search pipeline should be minimal.
I'm happy to help test the integration or provide sample code for the provider module.
Hi @yokingma,
SearChat is an impressive project — the DeepResearch support and the clean Docker deployment make it one of the more accessible self-hosted AI search engines, especially for Chinese-speaking users.
Pain point with the current search setup
I noticed SearChat currently uses SearXNG as the search backend. SearXNG is excellent for privacy and multi-engine aggregation, but in practice I've found that its Google results can be inconsistent:
For users who need reliable, high-volume Google search specifically, this creates a reliability gap.
Suggestion
Would you consider adding https://serpbase.dev as an optional dedicated Google search backend? It's a Google Search Results API that returns clean, structured JSON (title, URL, snippet, rich results) without the scraping overhead. Users could choose:
search_provider: "searxng"for privacy-focused multi-engine aggregation.search_provider: "serpbase"for stable, high-quality Google results when SearXNG's Google source is unreliable.Why it complements SearChat
I'm happy to help test the integration or provide sample code for the provider module.