# Feedback on our instant search experiment

**URL:** https://meta.discourse.org/t/feedback-on-our-instant-search-experiment/308705
**Category:** Feature
**Tags:** search, feedback
**Created:** [May 20, 2024, 2:42pm UTC](https://meta.discourse.org/t/feedback-on-our-instant-search-experiment/308705 "2024-05-20T14:42:54Z")
**Posts on this page:** 15
**Page:** 2

<div class="post-metadata">

### Author: ![Saif](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/saif/32/318253_2.png) [@Saif](https://meta.discourse.org/u/Saif)
#### Post date: [May 24, 2024, 9:55pm UTC](https://meta.discourse.org/t/feedback-on-our-instant-search-experiment/308705/21 "2024-05-24T21:55:27Z")

</div>

> [@JammyDodger](#):
>
> Another small hiatus 🌴 Be back soon. 🙂

I was wondering what happened. Thought I used the search too much 😅

---

<div class="post-metadata">

### Author: ![jordan-violet](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jordan-violet/32/281428_2.png) [@jordan-violet](https://meta.discourse.org/u/jordan-violet)
#### Post date: [May 25, 2024, 10:40am UTC](https://meta.discourse.org/t/feedback-on-our-instant-search-experiment/308705/22 "2024-05-25T10:40:39Z")

</div>

Maybe not feedback just for instant search, but in the topic of revamping search:

A coup de grace for search would be the ability for admins to somehow define some kind of categorical/hierarchical search result for users. For example, if my user searches for “workflows” then might get a response where the results are grouped like:

> Announcements & Blogs (made up of 4 categories):
> 
> - result 1
> - result 2
> - result 3
> 
> Community Marketplace (made up of five categories):
> 
> - result 1
> - result 2
> 
> Product A discussions:
> 
> - result 1
> - result 2

This would be incredible to achieve rather than just a wall of responses.

---

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [May 29, 2024, 4:49pm UTC](https://meta.discourse.org/t/feedback-on-our-instant-search-experiment/308705/23 "2024-05-29T16:49:57Z")

</div>

> [@jordan-violet](#):
>
> the ability for admins to somehow define some kind of categorical/hierarchical search result for users.

If we decide to ship Instant Search, we already plan on defaulting the search to be a multi-type by default, searching posts, topics, users, and chats all at the same time and displaying results organized by type.

This would also unlock what you describe here, which is a side effect of moving search away from generating load on the main database that in turn makes us less hesitant about running speculative searches.

* * *

As for everyone else, please make your voice heard around the future of search in Discourse, either you like it or not. We will soon need to make a decision on going forward or not and we appreciate the opinion of people who search on Discourse and what about it that we can make better for **all instances**.

---

<div class="post-metadata">

### Author: ![jordan-violet](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jordan-violet/32/281428_2.png) [@jordan-violet](https://meta.discourse.org/u/jordan-violet)
#### Post date: [May 29, 2024, 5:09pm UTC](https://meta.discourse.org/t/feedback-on-our-instant-search-experiment/308705/24 "2024-05-29T17:09:27Z")

</div>

I just had this thought while reading your response…

It would be amazing if you could forcibly define a search priority for a user group the same way you can forcibly subscribe groups to notifications of categories.

Imagine you have a group of product A customers, so their search results might return (in priority order):

- Product A announcements
- Product B announcements (because it’s an upsell to A)
- Product A marketplace
- Product A support

But for a group of partners, it might be:

- Marketplace
- Announcements
- Support

I think you get the idea. Being able to define a search priority for user groups would be incredible!

---

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [May 29, 2024, 5:11pm UTC](https://meta.discourse.org/t/feedback-on-our-instant-search-experiment/308705/25 "2024-05-29T17:11:33Z")

</div>

> [@jordan-violet](#):
>
> It would be amazing if you could forcibly define a search priority for a user group the same way you can forcibly subscribe groups to notifications of categories.

Interesting concept. We are already using a search prioritization in this experiment, where categories with `Search Priority` set get their topics/posts bumped a few positions, so extending this to groups would be completely doable.

---

<div class="post-metadata">

### Author: ![jordan-violet](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jordan-violet/32/281428_2.png) [@jordan-violet](https://meta.discourse.org/u/jordan-violet)
#### Post date: [May 29, 2024, 5:24pm UTC](https://meta.discourse.org/t/feedback-on-our-instant-search-experiment/308705/26 "2024-05-29T17:24:07Z")

</div>

This is a common concept we use in our search for our parent site above our Discourse community. We do different search rankings based on certain criteria.

I see so much value in translating that concept to our community, too.

---

<div class="post-metadata">

### Author: ![j127](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/j127/32/79093_2.png) [@j127](https://meta.discourse.org/u/j127)
#### Post date: [May 29, 2024, 8:10pm UTC](https://meta.discourse.org/t/feedback-on-our-instant-search-experiment/308705/27 "2024-05-29T20:10:14Z")

</div>

Looks great so far.

---

<div class="post-metadata">

### Author: ![JammyDodger](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jammydodger/32/254611_2.png) [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [May 29, 2024, 8:51pm UTC](https://meta.discourse.org/t/feedback-on-our-instant-search-experiment/308705/28 "2024-05-29T20:51:35Z")

</div>

Another small hiatus for some tweaking. BRB…

---

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [May 29, 2024, 10:17pm UTC](https://meta.discourse.org/t/feedback-on-our-instant-search-experiment/308705/29 "2024-05-29T22:17:25Z")

</div>

It should be back now.

---

<div class="post-metadata">

### Author: ![denvergeeks](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/denvergeeks/32/327671_2.png) [@denvergeeks](https://meta.discourse.org/u/denvergeeks)
#### Post date: [June 5, 2024, 11:54pm UTC](https://meta.discourse.org/t/feedback-on-our-instant-search-experiment/308705/30 "2024-06-05T23:54:49Z")

</div>

Hey where can I find the Instant Search here on Meta?

Please give it a test at `https://meta.discourse.org/instant-search` (doesn’t exist 🧐 )

---

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [June 5, 2024, 11:56pm UTC](https://meta.discourse.org/t/feedback-on-our-instant-search-experiment/308705/31 "2024-06-05T23:56:59Z")

</div>

It’s disabled for maintenance, should be back tomorrow.

---

<div class="post-metadata">

### Author: ![Moin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/moin/32/554653_2.png) [@Moin](https://meta.discourse.org/u/Moin)
#### Post date: [June 6, 2024, 1:47pm UTC](https://meta.discourse.org/t/feedback-on-our-instant-search-experiment/308705/33 "2024-06-06T13:47:43Z")

</div>

When you search for users, the links in the result often don’t work because the `<mark>` is added to it. So when you click “Lilly”

 ![Screenshot_20240606_153943_Chrome](https://global.discourse-cdn.com/meta/original/4X/c/4/6/c46ff6687b430ae0a9a3101d6557176bccffdc38.jpeg)

the link is `https://meta.discourse.org/u/%3Cmark%3ELilly%3C/mark%3E` which doesn’t work.

---

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [June 6, 2024, 2:37pm UTC](https://meta.discourse.org/t/feedback-on-our-instant-search-experiment/308705/34 "2024-06-06T14:37:17Z")

</div>

> [@Moin](#):
>
> When you search for users, the links in the result often don’t work because the `<mark>` is added to it. So when you click “Lilly”

Thanks for the report.

Considering this is a time-constrained experiment, some issues like this and others are to be expected, and shouldn’t impact testing the search capabilities and search UX possibilities that the new tech is bringing and giving us feedback if this is something worth pursuing for all Discourse instances. Our time budget for further polishing this experiment is out, so we can’t afford to spend more engineering time here as we have other plates to keep spinning.

---

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [August 7, 2024, 2:47pm UTC](https://meta.discourse.org/t/feedback-on-our-instant-search-experiment/308705/35 "2024-08-07T14:47:53Z")

</div>

Thanks everyone who shared their feedback on this experiment. It’s now disabled here on Meta.

---

<div class="post-metadata">

### Author: ![JammyDodger](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jammydodger/32/254611_2.png) [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [August 9, 2024, 2:48pm UTC](https://meta.discourse.org/t/feedback-on-our-instant-search-experiment/308705/36 "2024-08-09T14:48:30Z")

</div>

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.

[Previous page](https://meta.discourse.org/t/feedback-on-our-instant-search-experiment/308705.md?page=1)
