Guide · Launch
Launch search without a bad week.
A short list that teams use before switching production search: what to check in the data, how to set a quality baseline, what to lock down, and how to roll out gradually.
1. Data
Every product has a stable id
Re-imports update documents in place only when ids don't change between runs.
Fields have roles
Searchable text, filters, sort fields and display fields are set in the schema; the console suggests roles from your data.
Deletions propagate
Remove a test product at the source and check it disappears after the next sync.
2. Relevance baseline
Golden set from real queries
Take your top 50 queries and mark the products that should come first; this is your nDCG baseline.
Synonyms for the obvious gaps
Look at the zero-result report after a day of test traffic and add only the synonyms it asks for.
Rules for the business
Pin campaign products, exclude what must never show, schedule seasonal placements.
3. Security
No API keys in the page
The widget uses short-lived session tokens minted on your server.
Keys scoped and rotated
Use a separate key per integration with only the scopes it needs; set an expiry.
4. Rollout
Split traffic
Run the new profile as an experiment against the current one and compare conversion.