Skip to main content

When creating a solution article there is a field to enter Tags as well as a filed to enter Keywords.  I am trying to understand what the difference is between the two.  What do I use Tags for and what do I use keywords for?

Hi @todd5903 , keyworks will help your users reach the articles better by showing the article if the user input has those keywords. For example if Article 1 has keyword VPN, then article would pop up in the portal when user searches for VPN or search has keyword VPN.

Tags is for internal purpose and you can add tags to know how many articles you are maintaining related to a particular type. For example articles related to security could have tag security. You would eventually be able to check on how many solution articles and tickets are there in the system related to a particular tag.


This newer answer seems to go against this:

 

And then there’s this:

 

We opened a ticket about if they are deprecating Keywords and Tags fields:

​Freshservice still uses keywords to search, and here's a detailed article on how the keyword search works on each module. 

https://support.freshservice.com/en/support/solutions/articles/231703-how-search-works-in-freshservice

Also, for solution articles along with the keywords we allow searching based on the title.  

 

Then I found this: https://support.freshservice.com/en/support/solutions/articles/50000005608-best-practices-to-create-solution-articles 

“The title should contain the primary keyword(s) that the article is about.”

“Avoid relying on tags and keywords”


Hello! I am looking to make it easy for our customers to search for support articles in our portal and would love clarification on the thread & responses above. 

  • Are adding tags within our solution articles for internal purposes only?
  • Is the key to searching for articles primarily in the title? 
  • Do you have a definitive tagging best practice article to 1) help users search and 2) for our ticketing system to suggest articles within tickets? 

Thanks! 


Reply