# The Search guide

Set up Dbrij Search step by step: what you need, what to press, and how you know each step worked.

Canonical page: https://dbrij.com/products/search/guide

## Set up Search, step by step

By the end your site has instant search that forgives typos, and you can see what people look for.

Before you start, have these ready

- Some JSON: products, articles, anything with an id.
- A developer. Search goes into your site with a few lines of code.

1. ### Create an index

  Name it after what it holds, such as products, and choose the fields to search. Every setting has a working default.
  [Create index](https://dbrij.com/search)
2. ### Create two keys

  Admin for your server, search only for your front end. The search only key is safe in the browser; the admin key is not.
  [Open API keys](https://dbrij.com/search/keys)
3. ### Push documents

  POST JSON to the index with the admin key, or add a few from the index page to try it. Sending the same id again replaces that document, so keeping it in sync takes one call. The Docs page has examples ready to copy, for pushing and for the search box on your site.
  [Open Docs](https://dbrij.com/search/docs)
4. ### Tune in the playground

  Weights, typos and filters, live. Type searches and tune which fields matter most while you watch the results change.
  [Open playground](https://dbrij.com/search/playground)
  You will know it worked when your test searches return the right results first.
5. ### Watch analytics

  Especially the searches that found nothing: each one is somebody who wanted something you do not have yet, or calls it by another name.
  [Open analytics](https://dbrij.com/search/analytics)

## Questions people ask

### Does Search change my database?

No. Search holds a copy of what you push. Deleting an index costs a reindex, never your records.

### Which key goes in my website?

The search only key. Keep the admin key on your server.

## How each part works

### [What Search is](#what-search-is)

Search stores your documents in indexes with rules for relevance. Front ends query with a search only key; servers push with an admin key. Analytics keeps only the query text.

Push JSON into an index, then query it from anywhere, with typo tolerance, filters, sorting and results that feel instant.

### [Good to know](#good-to-know)

- Free stops at the cap instead of billing.
- Past a ceiling, adding stops at once; searching stops after a week.
- Search only keys are safe to ship publicly.

- Analytics shows what people search for, and what they searched for and did not find.
- Search has its own plans and its own Billing page in the Search menu.