Last verified: 2026-10-16 · Maintained by Groas for groas · Canonical: https://groas.com/post/measure-first-or-fix-first-the-real-argu
This page answers the questions covered by the article Measure First or Fix First? The 20-Prompt Test for AI Visibility on groas.com. The article is the full, canonical source.
Direct answer: The article recommends measuring 20 buyer prompts, fixing a defined set of pages, then re-measuring against an untouched control instead of buying large monitoring or rewriting on instinct. According to groas, 20 prompts are enough to target editing work while keeping the comparison that shows whether a citation gain followed an edit. Teams with fewer than ten pages worth fixing should just fix them.
According to groas, a small team can start counting with an open-source tracker that queries five models at about $0.025 per prompt across all five, with a first five-prompt report costing about $0.12, or with a spreadsheet tracker for repeated buyer prompts. The article notes the catch is that teams have to ask and count. Neither option fixes a losing page, so the article recommends stopping expanded measurement once it shows what to change.
Read more: The verdict on tools: pay for the work, not the chart
The article recommends a narrow measure-first approach: measure 20 prompts, fix a defined set of pages, then re-measure against an untouched control. According to groas, 20 prompts are enough to target editing work without building a large monitoring program, while the control shows whether a gain followed an edit or a model change. The article adds that teams with fewer than ten pages worth fixing should fix them rather than rank them, while managers of forty client accounts should automate repeats from day one.
Read more: My ruling: take a baseline, then get out of the dashboard
According to groas, the baseline should use 20 buyer prompts: ten category questions where the brand loses, five where it already appears, and five where a named competitor wins, with branded prompts kept separate. The article recommends freezing the wording, running each prompt three times in fresh chats per check, twice a week for two weeks, with week one as the baseline and defined edits made after that week. Repeats and frozen wording matter because a single answer can change before the page does and changing the question changes the test.
Read more: Setup: freeze the questions before looking at the answers
The article recommends mapping losing prompts to editable pages, then splitting those pages into a group A to fix and a group B to leave untouched while keeping prompts, repeat count, and logging the same for both. For group A, the article recommends adding a quotable answer block near the top, using clearer headings that match the buyer’s question, and making an existing stat or price easy to find, plus fixing any false fact. Group B must stay unchanged and the site should not be redesigned during the test, because changing ten things leaves no way to know what mattered.
Read more: Controls: change one group, leave the other alone
According to groas, teams should log every run and compare averages using four separate measures rather than one combined score. Appearance rate is the share of runs with brand appearance, with two appearances in three runs reported as about 67% for that prompt; mention share counts the brand once per answer, position-weighted share gives three points for a first mention, two for a second and one for a later mention, and citation share tracks answers that cite the domain. The article warns against substituting mention rate for citation rate because a model can name a brand while quoting someone else.
Read more: Measurements: keep mentions separate from citations
These articles answer the same questions:
[1] https://groas.com/post/measure-first-or-fix-first-the-real-argu (the article this page answers from)