# Introduce per-device tags **URL:** \ **Category:** Feedback\ **Created:** [June 21, 2026, 2:45am UTC](https://forum.gl-inet.com/t/introduce-per-device-tags/69469 "2026-06-21T02:45:17Z")\ **Posts on this page:** 1\ **Showing post:** 7
**Author:** ![will.qiu](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/w/b38774/32.png) [@will.qiu](https://forum.gl-inet.com/u/will.qiu)\ **Post date:** [July 10, 2026, 8:58am UTC](https://forum.gl-inet.com/t/introduce-per-device-tags/69469/7 "2026-07-10T08:58:31Z")
Hi, We understand the improvement you're suggesting. By adding tags such as `Flint 3 | BE9300`, users could search using either name and find the relevant information. However, as we mentioned previously, this still doesn't fully address the underlying issue: 1. Existing threads do not have these tags, so users would still need to search for both **BE9300** and **Flint 3** separately to find all relevant results. 2. Even for new threads, some users may not add the appropriate tags when creating a post, resulting in relevant content being missed. 3. In some cases, users share findings or workarounds within broader discussion threads, such as **[Firmware v4.9 Preview: What to Expect](https://forum.gl-inet.com/t/firmware-v4-9-preview-what-to-expect/68088)**. These posts cannot be fully covered by tags either, so users would still need to search for both **BE9300** and **Flint 3** separately to discover them. For these reasons, we believe adding tags would provide only limited benefit in this case. It could also create the impression that searching by tags will find _all_ relevant content, causing users to overlook other useful information. At the moment, searching for **BE9300** and **Flint 3** separately is still the most effective approach. We are also internally testing a feature similar to **Google AI Overview** to see whether it can help address this issue in the future. --- _[View the full topic](https://forum.gl-inet.com/t/introduce-per-device-tags/69469)._