Plan requirement
| Subscription | Suite Growth or higher, Knowledge Professional or higher |
| Access | Agent |
Two labelling systems with different jobs. Labels are for search, so be thorough; content tags are visible to readers, so keep them few and meaningful.
The difference
| Labels | Content tags | |
|---|---|---|
| Visible to readers | No | Yes |
| Purpose | Being found by search | Grouping related articles |
| Free text | Yes, anything goes | Managed, from a controlled set |
| How many | As many as help | A few, deliberately |
Use labels for words
Synonyms, old names, misspellings, terms in the other language. Nobody sees them, so there is no cost to being thorough.
Use content tags for connections
A reader on one article seeing others about the same subject. Because they are visible and managed, they need to be few and meaningful: three that group usefully beat twenty that clutter.
Neither is on Suite Team
Labels are not available there at all, and content tags start at Suite Growth. So on Team there is nothing to choose between, and no scheme around either will work there.
One further limit: searching content tags across brands is Enterprise only. Within one brand they work from Growth upwards.
Do not use one for the other's job
Content tags as a synonym list clutters every article with words that mean nothing to a reader. Labels as a navigation scheme does nothing, because nobody can see them.
Comments
0 comments
Article is closed for comments.