<?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://harlanh.tech/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://harlanh.tech/tags/algolia/index.xml" rel="self" type="application/rss+xml"/><item><title>11 Algolia A/B Testing Gotchas, Tips, and Lessons!!</title><link>https://harlanh.tech/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://harlanh.tech/2026/02/algolia-ab-testing-gotchas-tips-lessons/</guid><description>
&lt;p&gt;I've supported A/B testing of Algolia search systems at three companies now, and have
&lt;a href="https://harlanh.tech/tags/a/b-testing/"&gt;dived deep&lt;/a&gt; into A/B testing generally as well as specifically for search.
The &lt;a href="https://www.algolia.com/doc/guides/ab-testing/what-is-ab-testing"&gt;Algolia documentation&lt;/a&gt; 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 &lt;strong&gt;11 Algolia A/B Testing Gotchas, Tips, and Lessons!!&lt;/strong&gt;
All of the horrible illustrations are generated by AI, the rest are from earlier posts.&lt;/p&gt;</description></item><item><title>Post Query Refinement Suggestions in Search UX, and an Algolia Demo App</title><link>https://harlanh.tech/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://harlanh.tech/2026/01/post-query-refinement-suggestions-in-search-ux/</guid><description>
&lt;h2 id="what-are-post-query-refinement-suggestions"&gt;What are Post-Query Refinement Suggestions?&lt;/h2&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;figure style="display:inline-block;"&gt;
&lt;img src="etsy_filter_suggestions.png"
width="600"
/&gt;
&lt;figcaption&gt;
&lt;h4&gt;Filter Suggestions on Etsy&lt;/h4&gt;
&lt;/figcaption&gt;
&lt;/figure&gt;
&lt;p&gt;PQRS is a mouthful of an abbreviation, but most of what I'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;). So PQRSs it is, sorry.&lt;/p&gt;</description></item><item><title>Vibe-Coding the Missing Algolia Comparison Dashboard</title><link>https://harlanh.tech/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://harlanh.tech/2026/01/vibe-coding-missing-algolia-comparison-dashboard/</guid><description>
&lt;p&gt;&lt;a href="https://www.algolia.com/"&gt;Algolia&lt;/a&gt; is a tremendously powerful search platform, especially for e-commerce. But like most SaaS tools, the management dashboard doesn't do everything you need it to do. In particular, it's hard to compare search result rankings across variations in indexes -- a super common pattern when you're testing and iterating on index configurations before A/B testing, implementing algorithm and UI proof-of-concepts, or refining search relevance.&lt;/p&gt;
&lt;p&gt;At several places I've worked, I've built (or spec'ed out) comparison apps that allow you to run the same query in parallel and easily see and compare the results, for internal testing. Most recently, I vibe-coded an app that has worked very well. I can't share the code itself, so I've written a spec for a generic, equivalent app that is free for anybody to use and customize.&lt;/p&gt;</description></item></channel></rss>