Thirty Frozen Questions Beat Three Hundred Loose Ones

Thirty buyer questions, frozen for a quarter and run ten times each, will tell you more about your position in AI answers than three hundred questions run once. That is the whole case for a prompt library, and it is falsifiable: if you cannot re-run the identical set next month, the movement you see is your editing, not the engines. AI engines are highly inconsistent when recommending brands, and AI recommendation lists rarely repeat exactly, so a moving question set gives you two moving parts and no baseline.

Our working answer is a recommendation, not a measured optimum: 25 to 50 questions, about 30 for most teams, split across category questions, head-to-head comparisons, job-to-be-done phrasings, and objection questions, written in buyer language, frozen before the first run, and re-run at least ten times per question per cycle. The reason to bother at all is that AI chatbots are now the single largest influence on B2B shortlists and 51% of software buyers now begin research inside an AI chatbot. The library is also a proxy, and the rest of this piece is about building one that admits it.

What can a prompt panel honestly claim to measure?

A panel measures how engines answer your questions, not how buyers ask theirs, and the size of that gap is now measured rather than guessed. Across 8,133 multi-turn human-LLM conversations, the final user message carried only 35.6% of the session's unique user-side content vocabulary, and a complete final state appeared in the last message in only 26.1% of 456 commercial conversations and 26.2% of 4,534 PRISM conversations.

Worse for panel design, 43.5% of sessions carried at least one constraint dimension present only in the history. The budget, the team size, the integration requirement, the compliance rule: stated once, early, and absent from the message that actually triggers the answer. A panel that tracks only the bare final question is asking something roughly four in ten buyers would not have asked that way.

That is the finding behind the case that single-turn prompt panels measure the wrong question. The response is to state what the panel covers: your library is a lossy proxy for buyer sessions, and you compensate by carrying constraints into some of the phrasings.

So write the claim you are entitled to before collecting anything. This set of questions, run this many times, on these engines, in this window, produced these appearance and citation rates. Not: our AI visibility is 34.

How many questions can your team actually sustain?

Twenty-five to fifty, with about thirty as the starting point we use with most teams. Treat that as an operating heuristic and nothing more. The binding constraint is run volume, not imagination: one answer proves nothing, so every question needs repetition, and thirty questions across four engines at ten runs each is 1,200 answers per cycle before anyone reads one of them.

We start small because a smaller set swings hard on a single unusual answer, and we cap the set because past a few dozen entries teams begin writing variants of questions they already have. Neither cut point is a measurement. What is measured is the underlying noise: a 2026 variance-components study found run-to-run variation large enough to swamp real differences in small samples, and Ronald Sielinski's "Quantifying Uncertainty in AI Visibility" reaches the same conclusion with confidence intervals. Those two establish the noise. Neither says where to draw the line on library size.

Resist matching the scale of published indexes. Semrush's AI Visibility Index is a market map, not an instrument for your account.

What mix of questions belongs in the library?

Four types, and the weighting is an editorial default with no study behind it: category questions take the largest share, head-to-head comparisons and job-to-be-done phrasings sit roughly equal below them, and objection or risk questions take the smallest share but never zero. Each type fails differently, and a library weighted toward one type measures one slice of the buying process while reporting it as the whole.

Category questions test whether you appear in the consensus list an engine assembles. That stage is worth its own entries because one-third of buyers purchased from a vendor they had never heard of before. Head-to-heads test whether you survive the narrowing. 6sense found 3.8 of the roughly 5 vendors buyers evaluate are known before contact, which is why the narrowing stage is worth tracking separately from discovery. Job-to-be-done phrasings describe the problem without naming a category, which is where a buyer starts before knowing a product class exists.

The fourth type is the one most libraries skip. Objection and risk questions ask what goes wrong: is this hard to implement, what are the downsides, does it hold up for regulated teams. Those answers lean on material you did not write, and Profound's analysis of citation origins puts 57% of AI citations outside domains the brand controls. The IAB's Presence, Prominence, Portrayal, and Persuasion frame is a useful cross-check here: a library of category questions alone measures presence and stops.

How do you write questions in buyer language instead of keyword language?

Strip your brand name, strip your internal feature names, then put real buyer constraints back in. A question containing your brand measures recall, and a question built on a feature name only you use inflates a reading against queries no buyer runs.

The multi-turn work above codes buyer constraints into nine frozen cue families, and those are the dimensions most likely to be missing from a bare final question. Write roughly a third of your entries with one or two constraints carried in the phrasing. Ask for a workflow tool for a two-person marketing team on a small monthly budget, not for the best workflow tools.

Cut questions too broad to constrain the answer space, and cut questions that assume their own conclusion. And do not treat the library as a testbed for phrasing tricks on your own pages: C-SEO Bench (NeurIPS 2025) tested ten conversational-SEO rewrite methods across two tasks and six domains and found only 3 of 54 unilateral conditions produced statistically significant citation-rank gains. Most rewrite tactics do nothing. The library exists to show you where you stand.

Why does the set have to be frozen before the first run?

Because a baseline is a comparison against an identical instrument, and every edit after the first run quietly redefines what you are comparing. Change three questions in week four and week five is not comparable to week one, though the chart will happily draw a line between them.

Freezing means version-controlled text: exact wording, engine list, run count and date, stored where nobody edits casually. The urge to fix a poorly worded question peaks in week two, exactly when the baseline is worth least and the damage is worst.

There is a second reason. Retrieval is live. ChatGPT turns a user question into one or more targeted queries against a moving index, and an analysis of 500 SearchGPT citations found 87% of them matched Bing's top results, so the pool your panel draws from is a live web index and moves when it does. If the questions shift too, no change can be attributed to anything.

How often should you re-run, and when is a result a reading?

Re-run the full set every two weeks, and treat one run of one question as an anecdote. Ten runs per question per cycle is the floor, spread across days, because indexes update between runs and time of day becomes a variable you never meant to test.

Report distributions. Platform medians and interval estimates survive scrutiny; a lone percentage does not. The honest unit is a count: we appeared in 6 of 10 runs of this question on this engine this cycle, against 3 of 10 last cycle. "Visibility rose 30%" is a chart, not a finding.

Keep the rungs apart while you are at it. Mention, citation, recommendation and shortlist position are different outcomes with different causes, and blending them into one number hides which rung you are losing. Record each one per question, per engine, per run.

How do you add questions without destroying the comparison?

Version the library additively and never renumber. The original thirty become cohort v1 and stay untouched; new questions enter as v2 with their own start date and their own baseline. Trend lines are drawn inside a cohort, never across a version boundary, and every chart carries the version it came from.

Retire a question and add a replacement. If the wording was wrong, the question is dead: retire it with a date and a reason, then enter the corrected wording as a new question. An edited question that keeps its old identity is the most common way a panel produces a confident and wrong trend.

When a new question exposes a hole, treat it as a gap first. Citation gap analysis asks what evidence is missing and where the answer is being sourced before it asks what to publish. An AirOps analysis of 548,534 pages mapped which page traits correlate with being pulled into answers, and the GEO study (Aggarwal et al., KDD 2024) found that adding statistics, quotations and citations lifted citation visibility in its own benchmark, though C-SEO Bench did not reproduce that on commercial tasks. Evidence gaps of that kind are the briefs worth writing; a new tracked question is not one by itself.

How does Trovance keep a tracked question set worth comparing?

Trovance treats the library as the instrument itself. You define the tracked questions your buyers actually ask, constraint-carrying phrasings included, and Trovance runs them repeatedly across AI engines on a fixed analysis cycle. Every answer run is preserved as an answer snapshot with its full context: who was mentioned, who was cited, who was recommended, and which sources carried the answer.

Because the whole run is preserved, the comparison holds. Answer coverage is reported per question and per engine, so you can see that you hold six of ten runs on a category question while losing the head-to-head outright. Adding questions opens a new cohort with its own start date and leaves the existing history intact, which puts the versioning discipline above under the system's control.

The record then feeds decisions. Your Brand Core holds the claims you are entitled to make and the proof behind each one, and each recommended action names the specific asset the evidence points at: the benchmark that answers a competitor's quoted study, the objection page a review thread is currently answering on your behalf. Drafts are produced from approved claims, and a person reviews everything before it publishes.

What Trovance will not promise is a single visibility score, a guaranteed citation or recommendation, or control over what a model says. It also will not claim your panel reproduces how buyers really prompt, because the multi-turn evidence says it does not. The claim is narrower and checkable: the same questions, run the same way, compared over time, with every source preserved so you can verify the reading yourself.

What should you do this week?

Write thirty questions in one sitting using the four-type split, then audit them: no brand names, no internal feature names, nothing broad enough to capture an entire market, nothing that assumes its own answer. Add carried constraints to about a third. Then stop editing, timestamp the file, and call it v1.

Run it before you improve it. Ten runs per question across at least two engines, spread over a week, recording mention, citation and recommendation separately. Expect the first cycle to feel uninformative, because a baseline is not a verdict. Gartner projected in 2024 that search engine volume would fall 25% by 2026; whether or not that number landed, the baseline you need still takes a full cycle to build, so the boring part is worth starting now.

If you would rather not run twelve hundred queries by hand every cycle, start a free Trovance analysis and let the tracked questions run on a schedule while you spend your time reading the sources behind the answers.

Design the measurement

• The prompt panel is measuring the wrong question - why a bare final question misses the constraints buyers already stated.

• There is no such thing as an AI visibility score - why the results stay unblended.

• How to measure AI search visibility without one score - the reporting shape a frozen library supports.

• AI recommendation confidence is not a trust signal - how to read a confident answer correctly.

Act on what the panel shows

• AI citation gap analysis - what to do once a tracked question exposes a hole.

• How to track AI citations - the recording layer underneath the question set.

• AI share of voice - the competitive read a frozen library makes possible.

• A visibility gap is not a content brief - why a gap does not automatically justify a page.

FAQs