Hoe bouw je een prompt-universum op voor AI-zichtbaarheid?

A “prompt universe” is a structured set of real buyer questions you run repeatedly in ChatGPT, Gemini, and Perplexity to see whether your brand shows up, gets cited, and gets described correctly. It’s less like brainstorming and more like building a measurement instrument you can trust month after month.

What a prompt universe is (and what it is not)

Teams often start by collecting 20–30 prompts in a doc, run them once, and call it “AI visibility tracking.” That creates noise, not signal, because the set is rarely tied to the buyer journey, and it’s rarely stable enough to compare over time.

A prompt universe is closer to a test suite. It maps prompts to funnel stage, intent type, and the pages you expect an assistant to retrieve or cite.

[prompt universe]
[prompt universe]

The practical outcomes you should expect

• Repeatable trend data: you can see whether mention rate and citation share are rising or falling.
• Clear diagnosis: you can tell if you have an indexing issue, an extractability issue, or a positioning issue.
• Actionable content work: prompts become a backlog of specific pages and sections to create or upgrade.

Three terms to align internally

Small wording mismatches can derail the whole system. Agree on definitions before you start logging.

• Visibility: your brand is mentioned, cited, or listed as an option.
• Nauwkeurigheid: the description matches what you actually do, for the right use case.
• Buyer journey coverage: you appear across discovery, evaluation, and implementation prompts.

Build the prompt universe around a real buyer journey

Start with your buyer journey, not your product. The buyer is trying to reduce uncertainty step by step: what this category is, which option fits, what it costs, how hard it is to implement, and what can go wrong.

To keep the set stable, design it as prompt “families.” Each family covers one stage and one type of decision the buyer must make.

Step 1: Define 5–7 journey stages you can actually measure

Pick stages that reflect how people ask questions in chat, not how your org chart is structured. A workable model for many B2B and SaaS categories looks like this:

• Category discovery (meaning and scope)
• Problem-first framing (symptoms and constraints)
• Approach selection (methods, frameworks, trade-offs)
• Vendor shortlisting (best tools for a use case)
• Vergelijking (Brand A vs Brand B)
• Uitvoering (steps, checklists, timelines)
• Proof and risk (trust, limitations, common mistakes)

Step 2: Create prompt families with controlled variation

Each family should have a base prompt and 2–3 controlled variations. That lets you measure stability without turning the universe into chaos.

• Base prompt: the most common way a buyer asks it
• Constraint variation: budget, team size, compliance, region, stack
• Persona variation: marketer, founder, e-commerce manager, agency

Step 3: Write prompts that predict the citations you want

If you want your website to be quoted, prompts must invite quoting. Prompts that ask for definitions, criteria, and steps tend to produce clearer citations than vague “tell me about” questions.

If you often see competitors cited, it can be a symptom of retrieval and source selection patterns, not “better marketing.” The diagnostic patterns in waarom AI naar concurrenten verwijst in plaats van naar jouw website help you spot whether the issue is access, structure, or trust packaging.

Design the prompt set so results are comparable

Prompt universes fail when teams can’t reproduce their own measurements. AI systems change, but your process should stay consistent.

A simple testing protocol (that most teams will maintain)

• Run the universe in the same language and target market each cycle.
• Use a clean session for the baseline run (new chat, minimal history).
• Run each prompt twice and record both outputs if they differ.
• Save the full answer text, plus citations and any “recommended options” list.

Build a scoring rubric before you look at results

If you score after reading answers, the rubric drifts. Lock the scale first. A compact rubric that works well:

• Vermelding: 0/1 (brand named or not)
• Bronvermelding: 0/1 (any citation) and 0/1 (your domain cited)
• Nauwkeurigheid: 1–5 (positioning, features, constraints, no invented claims)
• Competitor presence: count of competitors named in the shortlist

If you need to align stakeholders on the underlying concept of generative systems without turning it into a debate, Wikipedia’s overview of generatieve kunstmatige intelligentie is a neutral baseline.

Use a table to keep the universe structured and scalable

This table exists to prevent your prompt universe from becoming a loose list. It forces each prompt to have a purpose and a measurement outcome.

Where to get prompt candidates without guessing

Steal from reality, not from your imagination. Good sources include:

• Sales calls and onboarding questions (what people ask before they buy)
• Support tickets (what they struggle with after they buy)
• Search Console queries (especially “vs,” “best,” and “how to” patterns)
• Competitor comparison pages and “alternatives” pages (for language patterns)

Maintain the universe as a living asset, not a one-off project

The set should be stable enough for trend tracking, yet flexible enough to reflect market shifts. Treat changes like you would changes to a product analytics dashboard.

Version your prompt universe

• Core set: 30–60 prompts you keep stable for quarter-to-quarter tracking.
• Experimental set: 10–20 prompts you swap monthly to explore new themes.
• Retired set: prompts that no longer reflect your category or offering.

A monthly cadence that connects measurement to action

• Week 1: run the full universe and log results.
• Week 2: pick 5 prompts with the biggest business impact and worst scores.
• Week 3: ship content fixes (definition blocks, tables, clearer trade-offs, FAQs).
• Week 4: re-test only the affected prompt families.

When a drop is a technical problem, not a content problem

If your prompts stop producing citations to your domain across multiple tools, check index coverage and rendering stability before rewriting pages. For Bing-driven retrieval paths, the failure modes in Problemen met de weergave van JavaScript bij de indexering door Bing are common culprits.

Once your pages are accessible, your content structure and internal pathways still shape what gets retrieved. If you’re building clusters to support prompt families, the decision logic in strategie voor ankertekst bij interne links can help you keep page relationships clear at scale.

Turn the prompt universe into a repeatable AI visibility workflow

The main shift is mindset: prompts are not just for “testing chatbots.” They are a map of demand, a measurement framework, and a content architecture plan.

If you want a system that continuously publishes, interlinks, and updates content based on what your prompt universe reveals, Authora can help you turn those prompt families into a structured workflow that improves how often you’re retrieved, cited, and described correctly in AI answers.