Improve Your Content Discoverability with a Linked List in Zendesk Guide

Improve content discoverability in Zendesk Guide by creating a custom page that shows records indexed by federated search. This enables businesses to offer a better experience for customers, making it easier for them to find the information they need.

Improve Your Content Discoverability with a Linked List in Zendesk Guide

As mentioned in last weeks' article on Federated Search, as businesses grow, their knowledge base expands too. From FAQs to product or marketing pages, there's an abundance of information available to help customers find what they're looking for. By default, the content indexed via Federated Search is only searchable, and not easily discoverable for your users.

In this article, we'll explore how to use Zendesk Federated Search and Custom Guide Pages to create a custom page that provides a curated list of links for end-users. What sets this solution apart is that the added links are browsable just like regular Guide articles in the same UI as Article sections. This approach allows businesses to make even more content available to their customers, not just traditional FAQ articles.

With our custom page, end-users will, for example, have access to App Store install pages, marketing pages, and more. Moreover, we'll also build an admin interface that allows team leads to manage the links indexed on the Help Center and giving them the ability to add or delete links as needed. This new feature provides a more personalised experience for customers, making it easier for them to find the information they need.

In summary, by using Zendesk Federated Search to create a custom landing page, businesses can make more content available to their customers in the same UI as Article sections. This personalised experience enables customers to browse and search through a curated list of links, not limited to traditional FAQ articles. So, let's dive in and explore how to build this custom page and admin interface.

Tutorial

As always you can find the full code on GitHub: