Glossary
What is Persona-Based Querying?
Definition
Persona-based querying runs the same question as several different kinds of buyer, then compares the answers. Unlike a synthetic query, which varies the question, persona-based querying varies the asker: a price-led shopper, an enterprise evaluator, a technical buyer. The same brand often wins one persona and loses another.
At a glance
- CategoriesStrategy
- Related fieldsAnalytics, GEO
- DifficultyIntermediate
At a glance
- Persona-based querying holds the topic constant and changes the framing, constraints and vocabulary of the asker.
- The output is a grid: which brands get named for which kind of buyer.
- Differences come from wording and stated constraints, not from a model knowing who you are.
- It finds the segment you are invisible to, which an overall visibility number averages away.
Same question, different buyer, different answer
Take one question: what is the best project management tool. Now ask it four ways.
A freelancer asks for something cheap for one person. A marketing manager asks for something the team will actually adopt. An IT lead asks about SSO and data residency. A procurement analyst asks which vendors publish SOC 2 reports.
Same topic, four different retrievals. The constraints in each question pull back different passages, so the assistant assembles four different shortlists.
That is all that is happening. The model is not profiling the person, it is matching the words in front of it, and those words differ by buyer type. A page about team adoption scores well on the second question and never surfaces on the third, because nothing on it mentions SSO.
Your average result hides who you lose
A single visibility figure is an average, and averages hide the thing you need.
Say you appear in most of your tracked prompts. Healthy number, until you break it down and find every appearance came from small-business framings and none from the enterprise ones. Your pipeline problem and your LLM visibility problem are the same problem, and the headline number hid it.
The reverse happens too. A brand looks weak overall while quietly owning the answers for the one segment that converts. Cutting that program on the headline number would be the wrong call.
Segmented measurement also tells you what to write next. A gap against a technical persona is a missing spec page. A gap against a price-led persona is a pricing page behind a form.
Build a persona set worth running
Four personas is enough to be useful and few enough to keep running every month.
- Take your real segments, not invented ones. Use the buyer types in your CRM. If sales talks about SMB, mid-market and enterprise, those are your personas.
- Write each persona’s version of the same question. Topic fixed. Change the constraint, the budget, the job title and the vocabulary.
- Run every version on a fresh session. No memory, no history, no logged-in account, or you are measuring your own past behavior.
- Score into a grid. Personas down the side, prompts across the top, named or not in each cell. The empty row is your brief.
- Fix one row before touching the rest. Write what that persona needed, wait a month, re-run the grid.
Parsnipp runs persona sets as standard for this reason: a blended score tells a brand it is doing fine while a whole segment never hears its name.
Frequently asked questions
-
Is persona-based querying the same as writing synthetic queries?
They work together but change different variables. A synthetic query is a question you write to test whether you appear. Persona-based querying takes those questions and rewrites each one in the voice and constraints of a specific buyer, so you can see which buyers you show up for.
-
Do assistants really answer differently for different personas?
Differently, yes, but not for the reason people assume. The model is not identifying who you are. It responds to the constraints and vocabulary in the question, and a freelancer’s phrasing retrieves different passages from a procurement lead’s. Run-to-run variation can also look like a persona difference, so each version needs several runs.
-
How many personas should I track?
Three or four. Enough to cover the segments your sales team genuinely distinguishes, few enough that you will still run the set next month. A dozen personas produces a grid nobody maintains, and the marginal ones repeat what the main ones told you.
-
Can I do this without buying anything?
Yes, for a first pass. A spreadsheet, a browser and an afternoon gets you a real grid. The manual version breaks down when you want repeat runs across several assistants every month, because that is a lot of tabs and the results go stale fast.
-
Which persona should I fix first?
The one closest to revenue, not the one with the worst score. A big gap against a persona that rarely buys is a distraction. Take the segment sales most wants more of, read what the assistant cited instead of you, and write the page that answers that buyer’s constraint.