Turn no-results searches into a weekly list of tickets

What does the analytics side give you?

The queries with no results, which is the most actionable list in any search product. People told you exactly what they wanted and got nothing.

A companion pulls it on a cadence, checks whether each term exists anywhere on the site, and turns the list into tickets. That read-plus-browser combination is what makes a search audit finish. Marketing usually owns the content half and product engineering the index half, which is part of why it stalls.

Why treat index settings as production?

Because Algolia applies them immediately with no version history to roll back to.

Searchable attributes, custom ranking, typo tolerance, synonyms: each one changes what every visitor sees on the next keystroke.

The Available tools list on the Algolia entry under `strawberry://settings/integrations` names every tool the connection exposes and marks the read-only ones. Use the Permissions block to keep settings and record-writing actions at Ask every time, and connect a search-only API key rather than an admin key where the tools you want work with one.

• No-results and popular query analytics: the highest-value reads here.
• Index settings: applied immediately, with no rollback, so keep them behind an approval.
• Record writes and index clears: destructive on a live index, and worth switching off.
• A search-only API key where the workflow allows it, rather than an admin key.

Get the replica test written up

A ranking change gets made on a replica index, tested, then applied.

A companion carries the reporting half: it reads the test results, pulls the search analytics for the period, and checks what changed on the site in the same window.

Then it writes the conclusion where somebody will read it, instead of leaving it in a dashboard for the one person who opens dashboards. That is research and analysis attached to a live experiment.

Frequently asked questions