Clean your spaces before you judge Rovo, because Rovo and Confluence search answer from the same pages. In public accounts, keyword search draws the most complaints, 14 accounts, one more than AI placed on every page, while people who use Rovo's answers praise them. Page structure, freshness, and permissions decide what either returns.
When you need this
- People skip search and ask colleagues because search returns the wrong pages.
- Several departments keep their own copy of the same project pages.
- AI-written pages are piling up without review.
Evaluation criteria
One home per topic
Does each project or policy have one owned page, or one per department?
Look forMerge duplicates and leave redirects. A PeerSpot reviewer gets fifteen pages about one project from a single search and blames separate departmental page structures.
Current, reviewed pages
Who reviews AI-written content before it becomes a source for Rovo?
Look forRequire a person to review each AI draft and cut it to readable length, and link pages to their Jira work items. One user finds about 80% of Rovo ticket summaries correct, and the rest miss details the tickets never recorded.
Permissions that match intent
Will Rovo show a page to someone who should not see it?
Look forAudit space and page permissions before rollout. Rovo shows everything a user can open, including personal spaces left fully shared.
Search habits to test
Do your most common questions get the right page from Rovo Search?
Look forRun 30 or more real questions through Rovo Search and Chat before and after cleanup. One commenter finds the right page on the first results page two times in three. Another found Rovo listed 3 of their 60 articles.
AI placement users accept
Will the AI summary help or slow down the people who search most?
Look forTest search with heavy users before rollout. A daily wiki user of 12 years says the AI summary holds back regular results until it renders, and individual users have no switch to turn it off.
Questions to ask vendors
- Which ten spaces answer the most questions, and who owns each?
- How many pages in those spaces have not been updated in a year?
- Which personal spaces are fully shared, and do their owners know Rovo reads them?
- What share of our test questions returns the right page before and after cleanup?
Red flags
- Rolling out Rovo to fix search without cleaning the spaces it reads.
- Department copies of the same project pages left in place.
- AI-drafted pages published without review.
- Measuring success by Rovo usage and never by questions answered correctly.
Products in this piece
Sources
- Official documentation
- 4
- Public source
- 6
- Atlassian Support: Rovo Search
- Atlassian Support: What is Rovo?
- Atlassian Trust Center: Rovo AI security and trust
- Atlassian Support: Rovo data, privacy, and usage guidelines
- PeerSpot review by Patrik Rosendahl: duplicate pages and search (Mar 19, 2026)
- Reddit r/atlassian: how accurate Rovo is when tickets are incomplete (Sep 2, 2026)
- Ask HN: Is every company's internal wiki just broken by default? (Jul 9, 2025)
- Hacker News comment on Confluence search finding pages two times in three (Jul 9, 2025)
- Hacker News comment on Rovo finding 3 of 60 Confluence articles (Mar 12, 2026)
- Hacker News comment on the AI summary holding back Confluence search results (Nov 21, 2025)