Hello,
I’m using Kagi on macOS with the Safari extension. Searches entered in the Safari address/search bar are automatically forwarded to Kagi.
In most cases that works well. However, sometimes Kagi returns no results for a query. In that situation, the search flow becomes a dead end: there is no obvious way to continue the same query with another search engine.
This affects the user experience because the user has to manually copy the query, open another search engine, and search again.
Example query:
Ultimate365 Tapered Golf Pant - IT7860 (Farbe: Collegiate Navy)
For this query, I briefly saw Google results before Safari redirected to Kagi, where I got no results.
The feature would provide a fallback path for no-result searches, without changing Kagi as the default search engine.
The feature could be used directly from the Kagi no-results page.
When Kagi returns no results, the page could show a clearly visible option such as:
“Try this search on Google”
“Search with another engine”
“Open in fallback search engine”
Clicking that option would run the same query on the selected fallback engine without requiring the user to copy and paste the query manually.
A more advanced version could allow users to configure their preferred fallback engine in the Kagi settings, for example Google, Bing, DuckDuckGo, Brave Search, or another custom search URL.
Possible user flow:
- User enters a search query in the Safari address/search bar.
- The Kagi Safari extension redirects the search to Kagi.
- Kagi returns no results.
- The no-results page shows a fallback button.
- User clicks the button.
- The same query opens in the configured fallback search engine.
This would not replace Kagi as the default search engine. It would only provide an escape hatch for cases where Kagi has no useful results.
This would reduce friction and make Kagi feel more reliable, because a no-results page would not become a dead end.
