Search operator for site filtering via existing bang shortcuts

tuesday

What: Add a search operator (I suggest @) which can be used with established ! shortcuts to instead initiate a site: search on the relevant domain.

Example:

User searches for testing @w
Kagi sees that !w redirects to a page at wikipedia.org
Kagi displays results for testing site:wikipedia.org

Why: Kagi is better than most websites’ own search engines, so I often want to use Kagi to search a site rather than using a bang operator. Typing out the full site: operator takes a long time, and this would be much quicker!

Implementation:

This could be handled in the same way as bangs and custom search shortcuts are (i.e. it redirects to a Kagi URL containing “site:example.com”, and that’s what the user sees in the search field of the results page). This means that the user can edit the domain if necessary (e.g. specifying a subdomain or subdirectory), and might make it somewhat simpler to implement, as well.
I can see arguments for either including subdomains or only the second-level domain and TLD — for example, !w actually points to a page at en.wikipedia.org; should @w point there or to wikipedia.org? I would suggest the latter, but I would be happy with either implementation, and it might be more useful to include subdomains. Opinions welcome below.
[edited to add:] Like bangs, custom search shortcuts should take precedence, and @ should use the domain specified by the user if a custom shortcut exists for the string.

CatX

If this proposal ends up in Kagi, some means of escaping the @-character would be useful.

Examples:

\@w should literally search for @w.
Searches like user@domain should not trigger this system.

Searches should behave like normal and not trigger this system unless the query matches something similar to the following regular expression (note the requirement of a space):
^.+ @[a-zA-Z0-9]+$

Edits: Trying to get the text formatting right.

tuesday

CatX Certainly agree with the space requirement! That’s how ! works and I would certainly expect them to behave the same.

However as Kagi currently stands, I don’t think searching for @w or even "@w" searches for the symbol — the first result is the wikipedia page for the letter W, which doesn’t contain any instances of @ at all. (and ditto for !)