Introducing Ceisium Search

A few months back, a friend/colleague of mine shared an example of incorrect search results by Algolia on our company website. That message led me to a series of tinkering, experiments, optimization and the results of which become “Ceisium Search” - The simplest out of box search experience for your website and docs.

While working on it, I realized three things wrong with how current tools approach setting up the “Search box” for a website.

1. The setup needs you to define certain configuration to work properly. Things like setting up the searchable attribute, correct order, synonyms, and more.
2. Even after spending time and effort figuring out the right setup, it can go stale quickly as your website or docs evolve.
3. And finally, the search quality can be pretty spiky depending on the type of queries your user ask.

As people get used to working with LLMs, the tend to ask for longer, detailed queries which are not well handled by the out of box experience of current website search providers (likes of algolia, typesense, miliesearch). The one thing the current website search providers were good at was the speed of showing the results (which was wrong at times).

Ceisium Search solves all three problems while making a concious tradeoff of ~2 second P95 end to end latency. (Update: now we have made the P95 latency ~1 sec without compromising the quality gains or the out of the box setup experience).

The Youtube Analogy

YouTube search can take vague words, a half-remembered phrase, or a feeling and still put the right video first. Website search should do the same for the right page.

Ceisium Search brings this goal to any public website. It also handles the maintenance loop that keeps results useful as the site changes.

Your docs update. A new pricing page ships. A changelog entry goes live. And the search results visitors see still point to content from three months ago, or return nothing at all. Keeping search current means refreshing content, checking coverage, debugging missing pages, and starting over the next time something changes.

Ceisium Search handles that loop.

Give Ceisium Search a URL. It keeps your public pages searchable, refreshes as the site changes, and gives you the tools to see what visitors can find. Website search that keeps up with your website.

Start from a URL

Create a search project, add a source with the paths you want visitors to find, and Ceisium Search takes it from there.

Click to pause Open full video

Create a Search project by adding the site URL, include paths, crawl frequency, and page limit.

For a docs-heavy site, that might mean starting with /docs/, /pricing/, /changelog/, and /blog/, excluding noisy paths, setting a crawl frequency, and capping pages. Ceisium Search keeps those pages searchable and keeps crawl history available when you need to inspect coverage.

Search through the API or UI

Use the Search API with your existing search box, or start with one of our UI examples. The API returns ranked pages with titles, URLs, and short text previews.

Choose a search layout for your website:

• A command palette for keyboard shortcuts
• Inline search with results below the input
• A search bar that opens a modal
• A search modal with an input and results

Try each layout with your project’s indexed pages. Copy the example code, or give the supplied setup instructions to your coding assistant.

Connect from your website with a Browser/public search key restricted to your allowed sites. You can also connect through your server with a private Server key.

Get Started with Ceisium Search

Ceisium Search works best for teams with docs, pricing, changelog, guides, blog, and product pages that need to stay searchable as the site changes.

Get started with Ceisium Search .