What is the best way to manipulate/influence the search results apart from tags?

[Thomas Pötzsch]

Some pages in our Confluence instance are re-created for every meeting, monthly, sometimes weekly.
After one has created a few of these pages, let's say "meeting 04/05", "meeting 05/05" and "meeting 06/05", naturally, the first search for "meeting" result will be "meeting 04/05". For some amount of reasons, people tend to click the first result, then navigate through the page tree to find the most recent meeting site.

Is there a possibility influence the search results? Or to mark some pages as the most "recent/relevant" ones out of a folder?

The expected behaviour is, that the most recent meeting site, the one that people _do_ spend time on, the one that people_actually edit_ is the first search result for "meeting".

Before someone answers "use tags": In our experience, tags do not influence search results enough. Anyway, tag "recent meeting" and remove it from the prior site every week/new page :D ?

I tagged Jira as well, we experienced this problem with Jira as well.

[JP _AC Bielefeld Leader_ · Accepted solution]

HI,

you're totally correct on the usage of tags. Don't use them to influence search, but tag them to have an additional filter option on search as you can search on a set of pages having a common tag.

I use another approach:

* All current / upcoming meetings get a tag "current"

* Use a page properties macro and an embedded table to describe the meeting (Topic, room, date, time, members, status,...)

* Create a page property report on a page with title "Current meetings" & list all current meetings there. Once a meeting is not current anymore remove the tag & create a new page.

If you play around with this feature you'll get the idea. Train your users to search for "current meetings".

Best

JP

[Thomas Pötzsch]

Thank you for your answer!

Imho, Confluence should try to tackle this problem. I am sure that most companies have reoccuring content that is hard to find using the Confluence-search.
I'll think about writing a feature request.