Viewing search data
Search data includes only end-user searches directly in Help Center, not searches in the Web Widget.
To open the search analytics dashboard
- In Support, click the Reporting icon () in the sidebar, then click the Search tab.
- Click any of the four options for viewing search
- Total, all performed searches.
- With no result, searches that returned 0 results.
- With no clicks, searches where no result was selected.
- Tickets created, searches that led to a ticket being created.
- Click one of the four data sets to see a more detailed
graph with a node for each day (the graph for Total
shows by default). Hover your mouse over a node to
see the total number for that day.
- Below the detailed graph you can see search data in a
table. The Total data set includes data for the top
500 searches overall. Each of the other data sets
filters the top 500 search terms accordingly to show
data for searches that had no results, no clicks, or
resulted in tickets.
- To filter the data based on the channel the search was
initiated from, click All channels to open
the drop-down menu, and select All channels,
Help Center, Mobile SDK, or Web
Widget to display the data from a
|Search string||Exact term the end-user entered in the search|
|Total searches||Total number of end-user searches for a term over the last 30 days|
|Avg number of results||Average number of search results displayed for a search term|
|Click-through rate||Percentage of end-users who clicked one of the search results displayed for a search term.|
|Tickets created||Total number of tickets created by end-users clicking Submit a request in Help Center immediately after a search|
|Top clicked result||Knowledge base content that was the most selected from search results|
Following up on search data
Search analytics gives you insight into what your customers are looking for and where they are failing to find answers.
To make end-users more successful you can analyze search data (review searches with no clicks or no results, look at click-through, notice whether the best content appears in results, and so on), then take actions to improve search results and your knowledge base content.
After you make changes, it will take about three minutes before the content is indexed and can be searched.
Improve search results
- Add labels to content. (Guide Professional) You can add tags to content so that the appropriate content appears in search results. For example, if you see that end-users are searching for "e-mail" but you use "email" without a dash in your content, add a label with the similar term to the content.
- Update content titles. You can rewrite titles to more closely match end-user searches. For example, if your article is titled "Deleting an email account" and end-users are searching for "removing a user from email," consider updating the title.
- Break content into smaller articles. You can divide large articles into smaller articles to help customers find what they are looking for. For example, instead of "Managing email" consider smaller articles about "Setting up email," "Adding email accounts," and "Deleting email accounts."
- Update content body text. You can add common end-user search terms to the body of appropriate articles so that the article appears higher in search results.
- Remove old content. You can remove old content so that it does not clutter search results and confuse your customers.
Improve your knowledge base content
- Update existing content. You can update existing content to be more complete. For example, if end-users are searching for how to schedule a backup, and you have an article on running manual backups but not how to schedule backups, consider adding that information to the article. If scheduling backups is not an option, you might want to add that info to the article so that end-users don't continue looking for an answer.
- Add new content. You can add content for common searches that aren't yielding any search results. For example, if end-users are searching for "accessing email remotely" and no content exists on that article, consider adding that article to your knowledge base.