<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>algolia on Harlan D. Harris</title>
    <link>https://www.harlan.harris.name/tags/algolia/</link>
    <description>Recent content in algolia on Harlan D. Harris</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <managingEditor>harlan@harris.name (Harlan Harris)</managingEditor>
    <webMaster>harlan@harris.name (Harlan Harris)</webMaster>
    <lastBuildDate>Mon, 09 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.harlan.harris.name/tags/algolia/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>11 Algolia A/B Testing Gotchas, Tips, and Lessons!!</title>
      <link>https://www.harlan.harris.name/2026/02/algolia-ab-testing-gotchas-tips-lessons/</link>
      <pubDate>Mon, 09 Feb 2026 00:00:00 +0000</pubDate>
      <author>harlan@harris.name (Harlan Harris)</author>
      <guid>https://www.harlan.harris.name/2026/02/algolia-ab-testing-gotchas-tips-lessons/</guid>
      <description>
        
          
            I&#39;ve supported A/B testing of Algolia search systems at three companies now, and have dived deep into A/B testing generally as well as specifically for search. The Algolia documentation on search A/B testing is technically adequate for getting started, and the dashboard has improved, but there are still many ways that you can go wrong when A/B testing Algolia search results. In the style of a 2014-era Buzzfeed listicle, here are 11 Algolia A/B Testing Gotchas, Tips, and Lessons!
          
          
        
      </description>
    </item>
    
    <item>
      <title>Post Query Refinement Suggestions in Search UX, and an Algolia Demo App</title>
      <link>https://www.harlan.harris.name/2026/01/post-query-refinement-suggestions-in-search-ux/</link>
      <pubDate>Fri, 23 Jan 2026 00:00:00 +0000</pubDate>
      <author>harlan@harris.name (Harlan Harris)</author>
      <guid>https://www.harlan.harris.name/2026/01/post-query-refinement-suggestions-in-search-ux/</guid>
      <description>
        
          
            What are Post-Query Refinement Suggestions? One of my favorite search UX patterns is post-query refinement suggestions — buttons that appear between the search box and results, adjusting the query in various ways. See, for instance, these suggestions on Etsy, which recommend that I filter by shipping speed, seller type, cost range, style, etc.
Filter Suggestions on Etsy PQRS is a mouthful of an abbreviation, but most of what I&#39;ve seen as alternatives either describes the UI element (&amp;quot;refinement pills&amp;quot;) rather than the function, or is excessively vague (&amp;quot;guided search&amp;quot;).
          
          
        
      </description>
    </item>
    
    <item>
      <title>Vibe-Coding the Missing Algolia Comparison Dashboard</title>
      <link>https://www.harlan.harris.name/2026/01/vibe-coding-missing-algolia-comparison-dashboard/</link>
      <pubDate>Tue, 13 Jan 2026 00:00:00 +0000</pubDate>
      <author>harlan@harris.name (Harlan Harris)</author>
      <guid>https://www.harlan.harris.name/2026/01/vibe-coding-missing-algolia-comparison-dashboard/</guid>
      <description>
        
          
            Algolia is a tremendously powerful search platform, especially for e-commerce. But like most SaaS tools, the management dashboard doesn&#39;t do everything you need it to do. In particular, it&#39;s hard to compare search result rankings across variations in indexes -- a super common pattern when you&#39;re testing and iterating on index configurations before A/B testing, implementing algorithm and UI proof-of-concepts, or refining search relevance.
At several places I&#39;ve worked, I&#39;ve built (or spec&#39;ed out) comparison apps that allow you to run the same query in parallel and easily see and compare the results, for internal testing.
          
          
        
      </description>
    </item>
    
  </channel>
</rss>
