<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Jarno S</title>
    <description>The latest articles on DEV Community by Jarno S (@jarnosaarimies).</description>
    <link>https://dev.to/jarnosaarimies</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4083706%2Ff35d75f1-cc6d-40b0-ab6d-0a05cb9bb4bb.jpg</url>
      <title>DEV Community: Jarno S</title>
      <link>https://dev.to/jarnosaarimies</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/jarnosaarimies"/>
    <language>en</language>
    <item>
      <title>How to Build a Repeatable AI Search Visibility Benchmark</title>
      <dc:creator>Jarno S</dc:creator>
      <pubDate>Tue, 18 Aug 2026 17:56:17 +0000</pubDate>
      <link>https://dev.to/jarnosaarimies/how-to-build-a-repeatable-ai-search-visibility-benchmark-1e4m</link>
      <guid>https://dev.to/jarnosaarimies/how-to-build-a-repeatable-ai-search-visibility-benchmark-1e4m</guid>
      <description>&lt;p&gt;Checking whether an AI assistant mentions your company once is interesting, but it is not a measurement system. Answers vary between models, sessions, dates, and prompt wording. A useful benchmark needs a stable set of questions, a consistent scoring method, and a record of what changed.&lt;/p&gt;

&lt;p&gt;This article describes a lightweight approach that a small team can run without an enterprise monitoring platform.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Start with decisions, not keywords
&lt;/h2&gt;

&lt;p&gt;Traditional rank tracking starts with search terms. AI-search monitoring should start with the decisions a potential customer asks an assistant to help make.&lt;/p&gt;

&lt;p&gt;Build prompts from four groups:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Category discovery: “What are the best ways to solve X?”&lt;/li&gt;
&lt;li&gt;Provider discovery: “Which companies help with X in Finland?”&lt;/li&gt;
&lt;li&gt;Comparison: “What is the difference between approach A and approach B?”&lt;/li&gt;
&lt;li&gt;Trust and validation: “How can I evaluate whether a provider is credible?”&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Keep the set small enough to run consistently. Twenty carefully selected prompts are more useful than two hundred prompts that change every month.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Freeze a golden prompt set
&lt;/h2&gt;

&lt;p&gt;A golden prompt set is a versioned list of prompts that stays stable between measurement rounds. Each row should include at least:&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;prompt_id, journey_stage, prompt_text, language, market, expected_entities
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;p&gt;Do not silently rewrite prompts after a run. If a prompt needs to change, create a new version. Otherwise, an apparent visibility improvement may only be the result of easier wording.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Capture more than mentions
&lt;/h2&gt;

&lt;p&gt;A binary “mentioned / not mentioned” score misses most of the useful information. For each response, record:&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;run_date
model
prompt_id
brand_mentioned
mention_position
recommendation_strength
linked_or_cited
cited_domains
answer_summary
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;p&gt;Recommendation strength can use a simple scale:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;0: not mentioned&lt;/li&gt;
&lt;li&gt;1: mentioned incidentally&lt;/li&gt;
&lt;li&gt;2: included as a relevant option&lt;/li&gt;
&lt;li&gt;3: clearly recommended or used as a primary example&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Keep the raw answer as evidence. Scores alone are difficult to audit later.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Separate visibility from citation
&lt;/h2&gt;

&lt;p&gt;These are related but different outcomes:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Visibility: the brand or entity appears in the answer.&lt;/li&gt;
&lt;li&gt;Citation: the assistant links to or names a source that supports the answer.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A company can be visible without its own website being cited. A website can also be cited while the brand is not recommended. Track both rates separately.&lt;/p&gt;

&lt;p&gt;For a prompt set with N prompts:&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;mention_rate = prompts_with_brand_mention / N
citation_rate = prompts_citing_owned_domain / N
recommendation_rate = prompts_with_strength_2_or_3 / N
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;p&gt;These simple metrics are easy to explain and hard to manipulate.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Control the test conditions
&lt;/h2&gt;

&lt;p&gt;Perfect repeatability is not possible, but avoid unnecessary variation:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Run the same prompts in the same order.&lt;/li&gt;
&lt;li&gt;Record the model and date.&lt;/li&gt;
&lt;li&gt;Use a fresh conversation for each prompt.&lt;/li&gt;
&lt;li&gt;Keep language and market context consistent.&lt;/li&gt;
&lt;li&gt;Avoid follow-up questions in the benchmark run.&lt;/li&gt;
&lt;li&gt;Run on a regular schedule, such as once a month.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The goal is not laboratory certainty. The goal is enough consistency to distinguish a durable trend from a lucky answer.&lt;/p&gt;

&lt;h2&gt;
  
  
  6. Review the evidence behind changes
&lt;/h2&gt;

&lt;p&gt;When a score moves, inspect the responses before drawing conclusions.&lt;/p&gt;

&lt;p&gt;Ask:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Did the assistant discover a new page or third-party source?&lt;/li&gt;
&lt;li&gt;Did a competitor disappear rather than our brand improve?&lt;/li&gt;
&lt;li&gt;Did the answer cite stronger evidence than last month?&lt;/li&gt;
&lt;li&gt;Did the model misunderstand the category?&lt;/li&gt;
&lt;li&gt;Is the change visible across several prompts or only one?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This review turns monitoring into an action list. For example, repeated category confusion suggests clearer entity and service descriptions. Missing evidence may suggest publishing a primary source, case study, methodology, or data page.&lt;/p&gt;

&lt;h2&gt;
  
  
  7. Report trends, not isolated wins
&lt;/h2&gt;

&lt;p&gt;A useful monthly report can fit on one page:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Mention rate&lt;/li&gt;
&lt;li&gt;Citation rate&lt;/li&gt;
&lt;li&gt;Strong recommendation rate&lt;/li&gt;
&lt;li&gt;Most frequently cited domains&lt;/li&gt;
&lt;li&gt;Prompts with the largest positive and negative changes&lt;/li&gt;
&lt;li&gt;Three evidence-backed actions for the next month&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Avoid presenting a single flattering answer as proof of authority. A stronger signal is repeated appearance across relevant prompts, models, and measurement rounds.&lt;/p&gt;

&lt;h2&gt;
  
  
  The practical takeaway
&lt;/h2&gt;

&lt;p&gt;AI-search visibility is noisy, but it is measurable. The key is to freeze the questions, preserve the raw evidence, score consistently, and investigate why the answers changed.&lt;/p&gt;

&lt;p&gt;I use this type of repeatable measurement thinking while developing &lt;a href="https://aeovara.fi/" rel="noopener noreferrer"&gt;AEOvara&lt;/a&gt;, a Finnish AI-search visibility and AEO project. The method itself is deliberately tool-independent: a spreadsheet and disciplined process are enough to begin.&lt;/p&gt;

</description>
      <category>seo</category>
      <category>ai</category>
      <category>llm</category>
      <category>analytics</category>
    </item>
  </channel>
</rss>
