Prompt
I’m building a prompt set to monitor brand mentions in ChatGPT and Gemini, how should I structure it?
Latest observation
A good prompt set for monitoring brand mentions in ChatGPT and Gemini should be modular, repeatable, and easy to compare across models. The goal is to reduce noise, make results attributable, and let you detect changes over time.
1) Start with a clear monitoring objective
Decide what you want to learn:
- Visibility: Does the model mention my brand at all?
- Positioning: How is the brand described?
- Competitors: Is the model recommending others instead?
- Accuracy: Are facts about the brand correct?
- Sentiment: Is the mention positive, neutral, or negative?
- Use cases: Which queries trigger the brand most often?
This determines your prompt design.
2) Use a structured prompt framework
Build prompts in a consistent format with these fields:
- Task
- What the model should do
- Context
- Industry, audience, locale, timeframe
- Query
- The actual user-style question
- Output constraints
- Short answer, bullets, citations, etc.
- Evaluation tags
- Brand mentioned? competitor mentioned? recommendation? factual accuracy?
Example template
Task: Answer as a consumer or buyer researching [category].
Context: The user is in [market/region] and wants a recommendation for [use case].
Query: What are the best [category] brands for [criteria]?
Output: Give a concise answer with 3–5 options and a one-sentence reason for each.
Evaluation: Note whether [Brand] appears, where it appears, and whether competitors are included.
3) Create prompt buckets
Use multiple prompt types instead of one generic query. This gives you a fuller picture.
A. Direct brand prompts
Checks baseline recognition.
- “What do you know about [Brand]?”
- “Is [Brand] a good option for [category]?”
- “Summarize [Brand] in one paragraph.”
B. Category recommendation prompts
Measures inclusion in recommendations.
- “What are the best [category] tools for small businesses?”
- “Recommend top [category] providers for enterprise teams.”
- “Which [category] brands are best for [use case]?”
C. Comparison prompts
See how the brand is positioned versus competitors.
- “[Brand] vs [Competitor]: which is better for [use case]?”
- “Compare the top 5 [category] brands.”
- “How does [Brand] stack up against alternatives?”
D. Problem/intent prompts
Captures real purchase intent.
- “I need a [category] solution that is [feature/constraint]. What should I use?”
- “What’s the best option if I need [budget/speed/integration]?”
- “Which [category] brands work best for [persona]?”
E. Negative/edge-case prompts
Checks resilience and misinformation.
- “Which [category] brands should I avoid and why?”
- “Is [Brand] still active?”
- “Has [Brand] had any recent issues or recalls?”
4) Vary prompt intent, not wording too much
To monitor reliably, keep:
- Core intent the same
- Wording controlled
- Variables changed one at a time
Example:
- Same query intent: “best CRM for startups”
- Change only one variable:
- startup vs enterprise
- US vs UK
- budget vs premium
- beginner vs advanced
This helps you identify what causes brand visibility to change.
5) Standardize the outputs you want
Ask the model to answer in a format that is easy to score.
Example:
Return:
1) Top 5 recommendations
2) One-line rationale for each
3) Mention any brands you are uncertain about
4) Do not browse or invent facts
If you want easier analysis, require structured output:
Format:
- Brand:
- Mentioned: yes/no
- Position: top/mid/other
- Tone: positive/neutral/negative
- Reason:
6) Build a scoring rubric
For each response, score:
- Mentioned? yes/no
- Rank position if included
- Sentiment positive/neutral/negative
- Accuracy correct/incorrect/unclear
- Recommendation strength strong/weak/not recommended
- Competitor presence which others were named
A simple scale works well:
- 0 = not mentioned
- 1 = mentioned briefly
- 2 = mentioned as an option
- 3 = recommended strongly
- 4 = top recommendation
7) Include control prompts
Use controls to know if the model is behaving normally.
Examples:
- A known category where your brand should not appear
- A prompt where your brand should almost always appear
- A prompt with an unrelated category to test false positives
This helps separate actual brand visibility from random mention noise.
8) Keep model-specific runs comparable
For ChatGPT and Gemini:
- Use the same prompts
- Use the same temperature/settings if possible
- Run multiple trials
- Record date/time/model version
- Note whether browsing/search is enabled
If browsing is on, results may reflect live web data rather than model memory.
9) Track metadata with every prompt
Store:
- Prompt ID
- Category
- Intent type
- Brand tested
- Competitors tested
- Model
- Date/time
- Region/language
- Output
- Score
This makes trend analysis possible.
10) Example prompt set structure
Here’s a practical starter set:
Tier 1: Baseline
- What is [Brand]?
- Is [Brand] trustworthy?
- What does [Brand] do?
Tier 2: Recommendation
- What are the best [category] brands?
- Which [category] brands are best for [persona]?
- What’s the best [category] for [budget/use case]?
Tier 3: Comparison
- [Brand] vs [Competitor]
- Compare [Brand], [Competitor A], and [Competitor B]
- What are the pros and cons of [Brand]?
Tier 4: Intent
- I need a [category] for [specific need]. What should I choose?
- Which [category] is easiest for beginners?
- What [category] brands integrate with [tool]?
Tier 5: Risk/accuracy
- Has [Brand] changed ownership?
- Are there any complaints about [Brand]?
- Is [Brand] still recommended in 2026?
11) Recommended prompt format for scale
If you’re running this as a monitoring program, use a template like:
[Intent Type]
[Category]
[Persona]
[Region]
[Constraints]
[Brand/Competitor Variables]
[Expected Output Format]
Example:
Intent: Purchase recommendation
Category: payroll software
Persona: small business owner
Region: United States
Constraints: under $100/month, easy setup
Brand Variables: Brand X, Brand Y, Brand Z
Output Format: ranked list with one-sentence justification
12) Best practices
- Keep prompts natural, like real user queries
- Use a mix of generic and branded prompts
- Avoid stuffing too many brands into one prompt
- Repeat prompts periodically to detect drift
- Compare outputs across time, not just one-off runs
If you want, I can also give you:
- a ready-to-use prompt library,
- a scoring spreadsheet schema, or
- a monitoring workflow for ChatGPT vs Gemini.