# Search Results Differ by Sort Order

**URL:** <https://meta.discourse.org/t/search-results-differ-by-sort-order/417674>\
**Category:** UX\
**Tags:** search\
**Created:** [17 november 2026 om 18:41 UTC](https://meta.discourse.org/t/search-results-differ-by-sort-order/417674 "2026-11-17T18:41:18Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Carleas](https://avatars.discourse-cdn.com/v4/letter/c/57b2e6/32.png) [@Carleas](https://meta.discourse.org/u/Carleas)\
**Post date:** [17 november 2026 om 21:35 UTC](https://meta.discourse.org/t/search-results-differ-by-sort-order/417674/3 "2026-11-17T21:35:24Z")

</div>

Thank you, that is a useful workaround, and searching on that string I can find [the documentation](https://meta.discourse.org/t/searching-for-content-effectively/273328) (though it doesn’t mention the different behavior for ‘Most Liked’).

I don’t think it is clear to users that search is topic-based:

- The advanced search tab is labeled ‘Posts’
- The results are posts (rather than topics or even OPs)
- There is no mention in the UI that results are one-post-per-topic, or that the topics in the results may have other posts fitting the search parameters
- It isn’t clear why a particular post from a given topic is given priority over any others that match the search terms, nor how to modify the search to prioritize different posts
- The `in:all-posts` option isn’t presented to users, and seems only available by manually adding it
- Even the documentation linked above repeatedly uses “returns posts” to describe search behavior (though it does describe `in:all-posts` as returning “every post that matches the query, even when multiple posts match within the same topic”)

I can see the rationale behind a topic-based search. But nothing suggested that’s what was happening other than users complaining that they could not find posts they knew they’d made.

---

_[View the full topic](https://meta.discourse.org/t/search-results-differ-by-sort-order/417674)._
