Public search

The help center's job is to answer questions before they become tickets — and search is the front door. Public search combines fast full-text matching with optional AI-generated answers.

Where search appears

• Home page — the hero search box, focused on load.

• Space and article pages — a persistent search entry in the header.

• Dedicated search page — full results for the reader's query, in their language.

How results work

• Search runs across all published articles in all locales (per the locale rules — the requested locale first, with fallback per your configuration).

• Results show title, excerpt, and context: the space name and the collection ancestor path ("Root / Billing / Refunds") render above each hit, so nested articles are self-explanatory.

• Match highlighting shows where terms hit within the article.

• Results deep-link to the article in the correct locale.

AI answers

When AI answers are enabled in help center settings, the search page can synthesize an answer from your published content — with citations to the underlying articles (each rendered as a link so readers can verify). AI answers only ever draw from published snapshots of external-capable spaces.

Search and the AI support agent

The same published content powers the support widget's help-center search (chat widget → built-in help center), so the site search, the widget, and AI answers all draw from one source of truth: your Docs.

Tuning search quality

• Put the key phrase in the title — titles carry the strongest signal.

• Fill in the excerpt; it renders in results.

• Use callouts and ToC blocks to structure answers — chunking follows headings, improving snippet quality.

• Watch Article feedback for high-traffic articles with poor helpful ratios; improve those first.