Weekly Algolia synonym and rule suggestions in Slack

Every Friday afternoon, get a Slack review list of proposed synonyms and query rules to rescue Algolia searches that returned zero results this week.

Agentic Task
AlgoliaSlackMarketingOperationsAI ReportsDaily DigestsNotifications & Alerts
PromptCreate

Every Friday at 3pm in my timezone, run this workflow against my main Algolia index. The goal is a weekly, human-reviewable list of synonym and query rule fixes for the merchandising team. Do not apply any changes automatically.

Step 1. Pull the last 7 days of search analytics from Algolia. Use the Analytics: Top Searches with No Results operation to get the failing searches, and the Analytics: Top Searches operation to get overall volume context. Prioritize the zero-result queries with the highest search volume, since those are the ones costing us the most missed hits.

Step 2. For each high-volume zero-result query, reason about why it failed and propose one or more candidate fixes: a synonym (for example 'trainers' should also match 'sneakers'), a one-way synonym (for example 'parka' returns 'winter jacket' records but not vice versa), or a query rule (for example when the query contains 'gift for dad', pin the Father's Day category).

Step 3. Before including any candidate synonym in the review list, verify it is real. For each alternative phrasing you propose, call the Search Single Index operation against my main index using that alternative wording. If the alternative returns relevant records where the original returned zero, keep the suggestion. If the alternative also returns nothing useful, drop it. Do not guess.

Step 4. Compose a Slack message with a numbered list of up to 10 suggestions, ranked by the search volume of the failing query. For each item include: the failing search term and its 7-day search volume; whether this is a synonym suggestion or a query rule suggestion; the proposed change stated in plain language the merchandising team can act on; and one example matching record (title or objectID) you actually found under the alternative phrasing, so the reviewer can sanity-check the mapping before applying.

Step 5. Send the message with Slack's Send a Message operation to the merchandising review channel. End with a short reminder that these are suggestions for a human to apply, and that nothing has been changed in Algolia.

Hard constraint: do not call any Algolia write operation. Do not call Save Synonym, do not call Save Rule, do not call any indexing or settings write endpoint. The point of this workflow is a weekly reviewable suggestions list, not silent index changes. Human-in-the-loop is a feature, not a bug, because bad synonyms silently degrade relevance.

Additional information

What does this prompt do?
  • Pulls the last 7 days of your top searches and top zero-result searches from Algolia every Friday afternoon
  • Uses AI to propose synonyms and query rules that would rescue the searches that returned nothing
  • Confirms each candidate by actually running the alternative phrasing against your main index and keeping only suggestions where matching records really exist
  • Posts a numbered Slack review list to the merchandising team so a human can approve and apply the fixes by hand
What do I need to use this?
  • An Algolia account with search analytics enabled
  • The name of the main index you want to tune
  • A Slack workspace and the channel your merchandising team reviews
How can I customize it?
  • Change when it runs, from Friday afternoon to any schedule that matches your review rhythm
  • Point it at a different index, a different Slack channel, or a different time window than the last 7 days
  • Adjust how many failing searches to look at each week and how strict the 'matching records must actually exist' check should be

Frequently asked questions

Will this change my Algolia synonyms or rules for me?
No. The workflow is intentionally read-only in Algolia. It reads analytics and runs test searches, then hands you a suggestions list in Slack. A human approves and applies each fix by hand, which is the whole point: bad synonyms silently degrade relevance, so a review step is safer.
How does it decide a suggestion is worth including?
For every candidate phrase, the workflow runs a real search against your index under the alternative wording. If the alternative returns relevant records where the original returned zero, that is a real gap worth fixing and it gets included in the list. Candidates that also return nothing useful are dropped.
Can I run it more or less often than weekly?
Yes. Weekly on Friday afternoon is the default because that fits a natural merchandising review rhythm, but any schedule works: daily, twice a month, or aligned to a specific team meeting.
Which Algolia API key does it need?
A Search-Only key is enough, because the workflow only reads analytics and runs test searches. It never writes to Algolia.
Can it post to a specific Slack channel or thread?
Yes. You pick the channel your merchandising team reviews when you connect Slack, and you can change it later if the team moves.

Turn Algolia's zero-result searches into a weekly review list.

Get concrete synonym and query rule suggestions in Slack every Friday, ready to approve and apply.