1

I tend to search and type fast. On Google and most other search engines, it will ask "did you mean to search for xxx instead?". Since it seems we have to be more conservative with are searches with Kagi, it would be great for Kagi to correct our spelling before we submit so that we aren't having to request the search engine crawl the same thing twice. Helps premium members not send as many searches but also especially helps those who end up having a good chunk of their 50 searches go towards grammar mistakes.

  • Vlad replied to this.

    I think this is already what is done?

    https://kagi.com/search?q=nike+river

    If you click above it will just return the exact same answers. If you really mean you query, you can click on the "nike river" bold part and be redirected to it.

    Looking at the interface, the visual interface is not so intuitive and the underlined/bold string could be different to make it a little simpler.

    • Vlad replied to this.
      8 days later

      Browsing6853

      Looking at the interface, the visual interface is not so intuitive and the underlined/bold string could be different to make it a little simpler.

      How?

          NoGoogle This is a hard problem. Correction may depend on actual results being available as a signal, so not always possible to do it beforehand. PLus what about non-english searches.

              4 days later

              Vlad Didn't know that. In that case perhaps only providing basic spelling checks for the most common and obvious errors instead of anything extensive is better than nothing and only making it a suggestion for the user to click on instead of correcting it automatically. It could offer a user to only correct obvious spelling errors like "corectting" instead of "correcting" and "obviosuly" instead of "obviously" instead of "their/there/they" that would rely on context. As for non-english searches, I forgot to consider them so unsure what approach if any should be done but if you go for just basic correction instead of anything extensive then perhaps that would easier to do as well.

              Overall though I didn't consider corrections deepened on actual results being available as a signal so just scratch this if it requires more effort then worth the while.

                  Vlad "Search instead for X", maybe making X bolder or adding underline to it would help to recognize that's not just a string and you can actually click it.

                  • Vlad replied to this.
                      a month later

                      Hello Vlad , I don't know about NoGoogle meaning for "basic corrections", but a simple but effective middle ground could be: two adjacent letter swap.
                      Two possible approaches could be:

                      • either having a list in a dedicated table (step 1: english language) of "wrong spelling - right spelling"
                      • or, for searches with very few results, try to identify more common variants
                        (but I think that only the first option could be feasible for us)

                      What do you think?

                      • Vlad replied to this.

                            I'm trying to produce some example for you.
                            The fact that, until now, Kagi is catching every two letter swap is an evidence of your hard work.
                            I'll keep you posted, thanks anyway.

                              No one is typing