# Search feature improvements
**URL:** https://discourse.nodered.org/t/search-feature-improvements/101792
**Category:** Feature Requests
**Created:** [16 September 2026 07:32 UTC](https://discourse.nodered.org/t/search-feature-improvements/101792 "2026-09-16T07:32:32Z")
**Posts on this page:** 10
**Page:** 1
### Author:  [@svefro](https://discourse.nodered.org/u/svefro)
#### Post date: [16 September 2026 07:32 UTC](https://discourse.nodered.org/t/search-feature-improvements/101792/1 "2026-09-16T07:32:32Z")
i can only search for one string at a time
if i want to find a "change" node that sets the topit to motion and the value to outside i can not do that. i have to either search for motion or outside
when i implement search i split by space and do multiple searches so both words match.
or you can use "+" for this
---
### Author:  [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)
#### Post date: [16 September 2026 10:17 UTC](https://discourse.nodered.org/t/search-feature-improvements/101792/2 "2026-09-16T10:17:00Z")
Adding `type:change` will help somewhat.
Additional filters can be added too:
---
### Author:  [@svefro](https://discourse.nodered.org/u/svefro)
#### Post date: [16 September 2026 10:29 UTC](https://discourse.nodered.org/t/search-feature-improvements/101792/3 "2026-09-16T10:29:20Z")
But change is only going to show changed nodes right?
That does not help, since i mostly search to do a change. not after.
And limiting to one flow does not help me.
---
### Author:  [@knolleary](https://discourse.nodered.org/u/knolleary)
#### Post date: [16 September 2026 10:35 UTC](https://discourse.nodered.org/t/search-feature-improvements/101792/4 "2026-09-16T10:35:01Z")
> [@svefro](#):
>
> But change is only going to show changed nodes right?
No, a search of `type:change` will filter the results to `change` nodes. Just as `type:inject` would filter the results to `inject` nodes.
---
### Author:  [@svefro](https://discourse.nodered.org/u/svefro)
#### Post date: [16 September 2026 10:58 UTC](https://discourse.nodered.org/t/search-feature-improvements/101792/5 "2026-09-16T10:58:55Z")
ah. i did not get that. thanks for the tips.
Unfortiunatly it would not give me all the results i would like containing outside AND motion.
---
### Author:  [@knolleary](https://discourse.nodered.org/u/knolleary)
#### Post date: [16 September 2026 12:47 UTC](https://discourse.nodered.org/t/search-feature-improvements/101792/6 "2026-09-16T12:47:07Z")
Essentially, it means splitting the whole search term by space, searching for each individually and then sorting results based on number of matches across those individual searches - as well as looking for precise matches of the terms as provided.
Entirely doable, and a well scoped feature request for someone to pick up. If you wanted to raise an issue on gh covering this feature request, that would be welcome.
---
### Author:  [@svefro](https://discourse.nodered.org/u/svefro)
#### Post date: [16 September 2026 13:24 UTC](https://discourse.nodered.org/t/search-feature-improvements/101792/7 "2026-09-16T13:24:22Z")
> [@knolleary](#):
>
> based on number of matches across those individual searches - as well as looking for precise matches of the terms as provided.
>
> Entirely doable, and a well scoped featu
I can do that.
But there is one issue when using space as a separator. When you want to find something that contains an exact string.
i have used the + sign as a " "(space) replacement before to do this.
But since we are searching for source code here i think it can cause issues.
I suggest using "AND" in upper case as a separator. And add it to the search option list.
Then we can still search for terms like "value + offset" without it beeing split.
I considered using && but that could also interfer with source code
Another option is to use "and:also" as a separator. that looks more similar to the other modifiers
What do you think?
---
### Author:  [@knolleary](https://discourse.nodered.org/u/knolleary)
#### Post date: [16 September 2026 13:29 UTC](https://discourse.nodered.org/t/search-feature-improvements/101792/8 "2026-09-16T13:29:14Z")
The precise implementation details can be thrashed out in the issue.
Without having put much thought into it, I can see a way that searches more smartly without the user needing to know all the syntax tricks.
If they searched for `red blue green`, we could search the index `red blue green`, `red`, `blue`, `green`, then sort the results based on how much of a match they are.
If a user wanted more precise multi-word search, then `"red blue" green` would search for `red blue` and `green` separately.
I think that would lead to a more intuitive search result without needing to adopt new syntaxes.
---
### Author:  [@svefro](https://discourse.nodered.org/u/svefro)
#### Post date: [16 September 2026 13:40 UTC](https://discourse.nodered.org/t/search-feature-improvements/101792/9 "2026-09-16T13:40:58Z")
Ok. i'll make a git issue on it. Thanks 🙂
---
### Author:  [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [16 September 2026 13:44 UTC](https://discourse.nodered.org/t/search-feature-improvements/101792/10 "2026-09-16T13:44:28Z")
Is it worth considering the use of a 3rd-party search library?