Add site search to your website and documentation

SiteOS Search helps visitors find pages in your website, documentation and resources. You choose the content, review what goes live and connect a search interface that belongs to your website.

One project, several search experiences

Each Project environment can contain several named indices. Documentation and Blog can share the same Project while keeping their content, crawlers, connection keys, relevance, suggestions and reports separate.

An index contains documents with stable IDs, titles, destination URLs and searchable text. A source identifies where a document came from, such as a crawler or import; it is not another index. Visitor-facing sections and snippets help people recognize the result.

Read Indices and environments before connecting more than one search experience.

What you can manage

Area	What it does
Overview	See search health, a Needs attention list and where content comes from.
Content	Inspect documents, import content, resolve source conflicts and see article activity.
Suggestions	Choose and order the articles visitors see before they type.
Crawlers	Fetch public HTML, review page outcomes and schedule updates.
Playground	Try queries against the published index without recording visitor activity.
Relevance	Compare field priorities, synonyms and typo settings before applying them.
Analytics	Explore searches, no-result queries and result clicks.
Activity	Follow updates: what started each one, what changed and why it failed.
Installation	Install and verify search on your website.
Settings	Website search, server and sync keys, visitor analytics and the crawler, each with its state.

Overview compares the last 30 days of visitor searches with the 30 before. Needs attention is ordered by how many visitors each item affects: a failed content update, queries that find nothing or rarely open a result, crawlers waiting for review, a website search that is not verified, keys that were never used and visitor analytics that is off. Items open the page where you can act on them; a query can also be tried in Playground or turned into a synonym draft (see Search relevance).

Search returns matching documents, snippets and links. It does not currently generate conversational answers from your content.

Keep content and installation in sync

Publishing a website page does not automatically update a prepared import. Run the configured crawler or import a fresh snapshot, review it and publish. Visitors keep the previous published index while an update builds; a failed publication does not replace it.

The search interface is a separate part of your website. Your agent can use Search skills to adapt it to your framework and design system. MCP can read results, configuration and reports; the CLI supports reviewed content and configuration changes.

Start with Set up Search. For an existing installation, see Content and indexing, Website connection or Search analytics. Moving from Algolia? Follow Migrate from Algolia, or compare the services first in SiteOS vs Algolia. The Search product page summarizes the features and compares other search tools.