About this block

Help Search Results renders the results page for a help center query. A search field carries the active query empty export file, and a left facet rail groups matches by Type (Articles 7, Videos 2, Community 2, API reference 1), a set of Category links, and an Updated time filter. The results list blends articles, a video walkthrough, a community answer, and an API reference, each row showing a breadcrumb, title, an excerpt with the matched term highlighted, and meta badges for type, freshness, and helpfulness. A footer strip offers Ask the community and Contact support when nothing fits.

Facets and results are separate typed arrays. The matched term is wrapped in a small Hl span, and each row swaps its icon by content type, so the whole page renders on the server with no client state.

When to use

Reach for this block as the search results route of an in-app help center, wired to your search index. Replace the static facet counts and result rows with live hits ranked by your relevance model.

A natural flow around it on an Application Pro page:

Before

• Filters and search
• Help center home

After

• Article reader
• Submit request form

What you can display

One strong use is the federated help search page. Other configurations:

• Single source. Hide the facet rail and list only article hits from one content set.
• Blended results. Keep the type facet to mix docs, videos, and community answers in one list.
• Empty query state. Lead with the support strip when the search returns nothing.

Tip: attaching the query and its top results to a new ticket saves the agent the first round of back and forth.