AI search for technical documentation

Give readers one place to search your docs

Find guides and reference pages across your documentation sites. When page results are not enough, readers can send the same question to Ask AI.

14-day free trialNo credit card required
connect sources
Data sources(3 results)
Connect your documentation site
Add a sitemap or website URL in the project source settings.
Connect a GitHub repository
Choose the repository and file patterns Biel should index.
Connect a Confluence space
Add the space URL and credentials for an account that can read it.
Project setup(1 result)
Review connected sources
Check the indexing run before testing questions against your documentation.
Navigate↑↓Select↵CloseEsc
Powered by biel.ai

Used by documentation and developer-experience teams

ScyllaDB
Katalon
Tezos
Talon.one
GrepTime
CrazyGames
SecuroSys
ScyllaDB
Katalon
Tezos
Talon.one
GrepTime
CrazyGames
SecuroSys
Search and Ask AI

Find a page or ask for an explanation

Use search to find a known page or setting. Use Ask AI when the question needs an explanation drawn from the documentation.

Page search

Find the right page

  • →Returns matching pages immediately for fast navigational queries.
  • →Works well when an experienced reader knows the page, API, or setting they need.
  • →Keeps the familiar search-bar and keyboard-navigation workflow.
  • →Can search one index spanning multiple documentation sites and platforms.
  • →Offers Ask AI on the same query when a result list is not enough.
Ask AI

Get an explanation

  • iSynthesizes an answer from the documentation, with sources for verification.
  • iiHandles questions whose answer spans several pages or uses different terminology.
  • iiiCarries the search query into the chatbot without making the reader type it again.
  • ivSupports follow-up questions when the first answer needs more context.
  • vLogs questions and weak answers so documentation teams can identify content gaps.
Multi-source

Search across your documentation sites

Connect your published guide sites and API references to one search experience. The page-search widget indexes website content; uploaded files are available to chat, not page search.

Docusaurus
Sphinx
MkDocs
Starlight
Astro
WordPress
One unified search
→ The answer your user needs

Keep your existing publishing tools

Your guides and API reference can stay on different platforms. Biel searches the website sources you connect and sends readers to the relevant page.

Choose a refresh schedule or trigger indexing from your publishing workflow. New results become available after the refresh completes.

Ranking

Guide readers to the most useful pages

Adjust page ranking with metadata, let readers filter results, and exclude content that should not appear. The search configuration guide explains each option.

i.

Prioritize useful pages

Add a boost score to a page’s metadata to increase or decrease its search ranking. Use it to favor maintained guides or reference pages.

<meta name="biel:boost_score"
      content="0.5">
ii.

Let readers filter results

Configure category filters so readers can narrow the result list to guides, API references, or other content groups.

Example categories:
Guides · API reference · Tutorials
iii.

Exclude what shouldn't rank

Review the URLs you index and exclude paths that should not appear in this project. Search exclusions are not a substitute for reader authentication.

Review source URLs and excluded paths
before publishing the search widget.

Use cases

Three places teams replace their old search

Keep your current search alongside Biel or replace it after testing the results on your own documentation.
Replacing Algolia DocSearch

Familiar search. Ask AI when needed.

Keep the familiar keyboard shortcut, modal, and page-result workflow. An Ask AI option passes the same query to the chatbot when the reader needs an explanation instead.

Cross-platform unification

One bar across your stack

For teams whose docs span multiple platforms. One search index, one search bar, one ranking system, regardless of where each piece of documentation actually lives.

Documentation redesign

Improve discovery without moving docs

Add search and chat to an existing documentation site. Test representative queries before changing your readers’ search experience.

“Reads all our sites without trouble, and helps us learn what questions our users ask.”

Tim McMakin · Technical Writer at TriliTech

Questions about AI search

What content can search cover?

The page-search widget returns pages from the website sources in your project. It can span several sites. Uploaded files are available to chat, but not page search.

How is this different from a chatbot?

Search returns matching pages. The chatbot generates an answer with source links. Ask AI sends the current search question to the chatbot.

Can we keep our existing search?

Yes. Use Biel as your page-search widget, or keep your existing search and install only the chatbot. When both Biel widgets are installed, Ask AI passes the current query to chat.

How are search results kept up to date?

Refresh from the dashboard or use scheduled indexing. On plans with API access, your publishing workflow can trigger a refresh after each update.

Can Ask AI handle multilingual questions?

Yes. Ask AI can answer in the reader's language and link to the supporting documentation.

Can I see what readers search for?

Yes. The dashboard records search queries. Chat analytics separately show answers, sources, ratings, and unanswered questions.

Does it work with private docs behind a login?

Private-site indexing requires custom configuration on Business or Enterprise. Reader access must also be configured separately. Book a demo to review your setup.

Help users find the page. Or ask for the answer.

14-day free trial · No credit card required
Try me ↓