Official guidance on how to structure Atlassian content to improve Rovo search

[oliver_garnett]

My company plans to review, restructure, and rewrite some of our confluence pages soon. Is there guidance on how to do this to improve Rovo search quality?

I understand general best practices for creating content that enables efficient AI search of content such as (suggested by Rovo):

• Use consistent terminology and avoid jargon/acronyms unless defined.

• Structure content with headings, bullet points, and tables for clarity.

• Link related pages and tickets for context.

• Use metadata (labels, tags, components) liberally.

• Keep content up to date and archive obsolete pages/tickets.

But are there any additional tips specific to Atlassian / Confluence / Rovo itself?

[Anthony Morais · Accepted solution]

Hi @oliver_garnett 

Take a look at these recommendations based on your purpose; I believe they will help.

- Best practices for Rovo prompts
- Unraveling Rovo search relevance
- Tips and tricks for using AI - AI best practices for Atlassian Intelligence in Confluence
- Building better content libraries with Confluence databases

I hope this helps!

[oliver_garnett]

Thanks @Anthony Morais - I had not seen some of these resources!

They are helpful but not exactly what I was looking for since they mostly focus on how to use Rovo search or generally structure content libraries. 

I was looking for explicit content-authoring rules for Confluence to improve findability for Rovo, but Im guessing no such article exists yet. 

[Anthony Morais]

Hi @oliver_garnett 

That's right! That article doesn't exist yet; I've compiled the best practices I've found so far to try and help. If you discover anything new on the topic, I'd love to continue this exchange!

If you can, mark this answer as accepted, and if you have a new topic to discuss, open a new question.

Best Regards,
Anthony