Turn on full-text search
Turn on the header search button#
- Open your docs site while signed in.
- Open Float Widget → Design → Header tab.
- Turn on Search button.
- Click Save.
The button appears in the top bar of every page.
Turn on sidebar search#
- Open your docs site while signed in.
- Open Float Widget → Design → Left Sidebar tab.
- Turn on Search in sidebar.
- Click Save.
The box appears above the navigation tree in the left panel.
Choose where the search box belongs#
Both placements can run at the same time. Enabling one is usually enough.
| Placement | Best for | Trade-off |
|---|---|---|
| Header | First-time visitors, who look at the top bar first | Competes for space with your header links |
| Sidebar | Readers who already navigate by the tree | Hidden on narrow screens where the sidebar collapses |
If your header already carries several links, use sidebar search instead of adding another control to the top bar.
What Docsbook search indexes#
Docsbook full-text search covers every markdown file the site publishes, and the index is rebuilt when your repository changes on GitHub. There is nothing to reindex by hand.
Search matches:
- Page titles
- Headings
- Body text
- Code blocks, ranked below prose
Keyword search runs against that index and never calls an AI model, so it does not draw on your project balance. Semantic search — matching by meaning rather than by keyword — does call a model, and is billed against the balance like any other AI usage.
Next steps#
- See what readers searched for — the queries that returned nothing tell you which page to write next.
- Content options — the other controls in the same Design panel.
Every new project starts with $1 of balance, and reader search does not spend it.