What are the benefits of labels compared to rovo search?

[Carlotta Meyer _ Acker e_V_]

With the introduction of rovo search options have expanded a lot. I don´t really see a big advantage in using labels on confluence pages anymore. I can easily find related content using rovo. Am I missing something? 

[Thorsten Letschert _Decadis AG_ · Accepted solution]

Hey @Carlotta Meyer _ Acker e_V_ ,

Interesting take. However, to me, it's not an "either or". While Rovo perfectly fits in content discovery use cases as you've described, I'd still go for labels when it comes to deterministic filtering or automation, since labels are explicit(!) metadata and still used for:

• Page Properties + Page Properties Report

• Macros that filter pages by label

• Structured overview pages (“All runbooks”, “All ADRs”)

• Automation rules (via API or apps)

• External integrations

So it's probably rather “Labels help me define content” than “Labels help me find content”.

Regards from Germany,
Thorsten

[Yulia Lenina _AppFox_ · Accepted solution]

Hi Carlotta, thanks for your question. I can see at least 2 reasons for still using labels. First, a label provides an information about a page without needing to do a Rovo search - it gives the structure and a quick insight. Second, labels are used in automations and other apps, like Workflows for Confluence, for example. Using this app, you can automatically apply a particular workflow to a page with a label. So, labels give another dimension to the content of a page. I bet there are more use cases for labels, these 2 are just quick ones.

[Barbara Szczesniak]

When using Scroll Sites/Viewport, I have to use a specific label to exclude a page from being picked up by the app and other labels for other features.