# Documentation: Tips & tricks how to use search?

**URL:** https://meta.discourse.org/t/documentation-tips-tricks-how-to-use-search/234507
**Category:** General
**Created:** [July 30, 2022, 10:42am UTC](https://meta.discourse.org/t/documentation-tips-tricks-how-to-use-search/234507 "2022-07-30T10:42:57Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![Jagster](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jagster/32/192154_2.png) [@Jagster](https://meta.discourse.org/u/Jagster)
#### Post date: [July 30, 2022, 10:42am UTC](https://meta.discourse.org/t/documentation-tips-tricks-how-to-use-search/234507/1 "2022-07-30T10:42:57Z")

</div>

**First some general meta 😉**

On my forum I used decent amount of categories. Mostly because of I had same structure on another sites and everybody is doing same. But as everyone knows, or should know, a lot of categories and plenty of sub-categories plus all sub-sub-categories are almost impossible to handle. And the most important part: categories don’t help an user to find relevant content.

Nothing new actually. That is one reason why Discourse supports only two level categories and using tags are guided so often.

Quite many are against tag, though. I reckon it leads to wide misuse of tags on another platforms, mixing them with keywords (partly tags and keywords are same) and hashtag abuse by Instagram etc. Plus… common point on view is because of that history ordinary users don’t know how to use tags.

They can. For them, what they see on the screen, tags are same thing than categories — but gives better results (IF used right by admins).

But tags work best with searches. And that is an issue too. As tags are widely misused so it is searches — because it just doesn’t work. Users had learned not to use search, because it gives too many hits. It is neverending fight between skills of users, should all hits shown to an user or can we use someking guessing like Google is doing.

That is an issue devs must solve out. But it is different story.

Anyway. Mine audience are just ordinary people, not tech-savvy what so ever. They have difficulties to start use composer of Discourse and they couldn’t change theme. Sure, they can now, mostly, but it needed a quite lot guidance.

But they adapt lack of categories and started use tags right away. For them it was really intuitive act. Or as a couple users said: clicking tags is like searching, but better. All I needed to do on guidance level was just to tell then click tags and find out what happends and tell where `Tags` on hamburger leads.

**Back to business**

Discourse has one of the best search engines on free web-world. It is not perfect, of course, but is far superior than native search of wordPress or another CMSes (if you don’t know WordPress search plugin Relevantti, you should check it out; it is quite good).

I’m teaching now my users how to improve search results. Actually even that was much easier task than I expected — and those users almost never use search anywhere (I don’t blame them, because searches sucks so often).

But now I’m lacking some references. I know Discourse can use plenty of tricks right in the search terms — but those fragments and bits of knowledge are spreaded in… many posts and topics.

I know — writing document and tips&tricks need more work than coding itself. I’ve done documentation quite lot. It is not just to write one, but there must be at least three different documents depending of need and skills of users. Plus someone should keep those updated too.

That’s why I totally understand I couldn’t find overwhelming guide of mastering searches on Discourse 😉 (or I just… can’t search)

What I’m asking from community is

- simple listing for (or _of_; sometimes I hate english so much) search parameters or just examples/links
- teach your users to use search, most of them just can’t
- dump categories and start using tags instead (well, it needs some planning to do right, though)

---

<div class="post-metadata">

### Author: ![Heliosurge](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/heliosurge/32/571810_2.png) [@Heliosurge](https://meta.discourse.org/u/Heliosurge)
#### Post date: [July 30, 2022, 8:13pm UTC](https://meta.discourse.org/t/documentation-tips-tricks-how-to-use-search/234507/2 "2022-07-30T20:13:40Z")

</div>

Very much agreed. There are 2 excellent plugins that can also enhance user xp with searches.

- Saved Searches
- Docs

However yes setting up forum guides is a definite must to help users better use a forum and improve there xp. That is where the Docs plugin can definitely be an asset. There is also a theme component that can be used with docs plugin.

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [June 27, 2024, 2:17am UTC](https://meta.discourse.org/t/documentation-tips-tricks-how-to-use-search/234507/3 "2024-06-27T02:17:10Z")

</div>

> [@Jagster](#):
>
> simple listing for (or _of_; sometimes I hate english so much) search parameters or just examples/links

> **[Comprehensive Guide to Discourse Search Options Unleashed](https://meta.discourse.org/discourse-ai/ai-bot/shared-ai-conversations/C1gZYz_2yHdvX5GMgc0_uQ)**
>
> sam: read lib/search.rb, spec/lib/search\_spec.rb in discourse/discourse and then provide with a beautifully formatted markdown user guide for all the various search options. 
> The guide should be exhaustive and cover every single search option.

@hugh / @JammyDodger do we need something like this in the documentation topic?

---

<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 27, 2024, 3:14am UTC](https://meta.discourse.org/t/documentation-tips-tricks-how-to-use-search/234507/4 "2024-06-27T03:14:53Z")

</div>

> [@sam](#):
>
> do we need something like this in the documentation topic

There is [Searching for content effectively](https://meta.discourse.org/t/search-tips-and-tricks/273328)

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [June 27, 2024, 3:49am UTC](https://meta.discourse.org/t/documentation-tips-tricks-how-to-use-search/234507/5 "2024-06-27T03:49:03Z")

</div>

Cool I integrated everything (using the claude-3.5-sonnet) happy with the edit, but feel free to review.

---

<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 27, 2024, 9:59am UTC](https://meta.discourse.org/t/documentation-tips-tricks-how-to-use-search/234507/6 "2024-06-27T09:59:44Z")

</div>

I removed most of them because:

> [@Searching for content effectively](https://meta.discourse.org/t/searching-for-content-effectively/273328/1):
>
> This topic aims to list other filters that aren’t available in the advanced search form

I like that the topic highlights the filters that I can’t discover by using the advanced search. If you want to change the scope, just revert the edit.

I left the order options because those are not shown in the search input field, so it’s more difficult to use them without the drop-down.

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [June 27, 2024, 10:06am UTC](https://meta.discourse.org/t/documentation-tips-tricks-how-to-use-search/234507/7 "2024-06-27T10:06:39Z")

</div>

I think its better to change the scope… this rule feels very arbitrary. Maybe we just edit “This topic aims to list other filters that aren’t available in the advanced search form” out of it?

@JammyDodger what do you think?

I get that you can discover a lot by clicking around but the documentation saves you from that. Plus this edit makes search less good.

Eg:

`tracking search` will no longer find this document which is a shame.
