> For the complete documentation index, see [llms.txt](https://vitrina-blogerov.gitbook.io/bloggers-showcase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vitrina-blogerov.gitbook.io/bloggers-showcase/product-docs/product-docs-en/admin-panel/tag-editor.md).
# Tag editor
The tag editor manages categories, tags, icons, and internal blogger attributes. This data is used in storefront filters, profile cards, the admin editor, and AI search.
### What tags are for
Tags help the user quickly narrow down the catalog: choose a topic, platform, format, or another blogger attribute.
They also help AI search and the Telegram consultant better match a client’s request with cards in the database.
{% hint style="success" %}
An important feature of the editor is hidden tags. They are not shown to the user on the storefront, but remain in the database and can work as internal instructions for AI.
{% endhint %}
### What can be configured
* create categories;
* rename categories;
* delete categories;
* add tags inside a category;
* assign an icon to a tag;
* hide or show a tag on the storefront;
* delete tags.
```mermaid
flowchart TD
A["Category"] --> B["Tag 1"]
A --> C["Tag 2"]
A --> D["Tag 3"]
B --> E["Icon"]
B --> F["Storefront visibility"]
B --> G["AI attribute"]
```
### Categories
Categories group tags. For example, blog topics, social networks, formats, or other attributes can be stored separately.
{% hint style="info" %}
Categories make filters clearer for the user. If there are many tags, it is better to group them logically rather than put them all into one shared list.
{% endhint %}
### Icons
For tags, you can choose icons from the built-in gallery or upload new files.
Icons are used on the storefront and help users read filters and cards faster.
{% hint style="success" %}
Create a tag category called "Social networks." Icons have already been uploaded for this category. The tag icons in this category are displayed directly in the card.
{% endhint %}
### Tag visibility
A tag can remain in the database but be hidden from the storefront. This is useful if the tag is needed not by the user, but by the internal matching logic.
{% tabs %}
{% tab title="Visible tag" %}
Shown to users in filters, can be selected on the storefront, and participates in search.
{% endtab %}
{% tab title="Hidden tag" %}
Stays in the database and in the admin panel, but is not shown in the public filter list. Such a tag can be used as a semantic label for AI: for example, “suitable for premium brands,” “soft integration,” “young audience,” “do not use for gambling.”
{% endtab %}
{% endtabs %}
### Hidden tags as instructions for AI
The public storefront gets only visible tags. At the same time, the card in the database may have more attributes than the user sees.
This allows you to add internal AI labels:
* blogger’s commercial level;
* niche restrictions;
* preferred integration format;
* audience type;
* risky topics;
* priority for certain brands;
* internal team segments.
{% hint style="info" %}
A hidden tag should not replace the card description. It is better to use it as a short, precise label that helps AI choose or exclude a blogger.
{% endhint %}
Examples of hidden tags
`premium-fit` - the blogger is suitable for premium brands.
`family-safe` - the blogger is safe for family products.
`avoid-finance` - do not suggest for financial integrations.
`soft-native-ads` - works better with native integrations.
### How not to overload tags
Tags should remain manageable. If you create too many similar attributes, it will become harder for the administrator to maintain the database, and AI may receive conflicting signals.
A good approach is to make visible tags understandable for the user, and use hidden tags only where they really help with matching.
### Be careful with deletion
Deleting a tag may affect the cards that were linked to it. Before deleting, make sure the tag is no longer needed in the catalog, filters, or AI matching.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://vitrina-blogerov.gitbook.io/bloggers-showcase/product-docs/product-docs-en/admin-panel/tag-editor.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
