QuQi
AI-SUCHE (GEO)

Report citation share to stakeholders

Use when you have to report assistant visibility without dressing it up as rank tracking.

citation-share-reporting.md
.md herunterladen
You are building a reporting frame for visibility in assistant answers. You are not forecasting traffic or revenue.

The frozen prompt set and how often each prompt is run: {{TRACKED_PROMPTS}}
Logged results, one row per run: assistant, prompt, named or not, cited or not, URL cited: {{RESULTS_LOG}}
Who reads the report and what they decide with it: {{STAKEHOLDER}}
Period being reported: {{REPORTING_PERIOD}}

Produce:
1. Definitions for mention rate, citation rate, cited URL concentration, competitor share and position within the answer. For each, the exact calculation over {{RESULTS_LOG}} and one line on what it cannot tell you.
2. A table for {{REPORTING_PERIOD}}: | Metric | This period | Previous period | Change | Runs behind it | Larger than run to run variation? |
3. Three sentences written for {{STAKEHOLDER}} saying what moved and what it does not prove.
4. A "do not report" list: numbers that look impressive and mean nothing.

Constraints:
- Calculate only from {{RESULTS_LOG}}. Where a metric needs runs that are missing, say what to start logging rather than estimating it.
- Put the run count beside every rate. Never present one run as a trend.
- Do not credit a change to our work unless {{TRACKED_PROMPTS}} was identical across both periods.

Vor dem Start ausfüllen

Ersetzen Sie jeden Platzhalter durch Ihre eigenen Angaben. Je genauer Sie sind, desto weniger erfindet das Modell.

  • {{TRACKED_PROMPTS}}
  • {{RESULTS_LOG}}
  • {{STAKEHOLDER}}
  • {{REPORTING_PERIOD}}

So wird das Ergebnis besser

  1. Freeze the prompt set and the schedule before the first report, or every comparison after it is noise.
  2. Log the cited URL, not just the mention, since only the URL tells you what to edit.
  3. Run each prompt several times per period; the same prompt returns different answers on different days.