Feature3 min read

Tracked Prompts

Manage the question list every scan measures: prompt types, locales, status — and the habits that keep the list honest.

Tracked Prompts is your measurement contract: every question here is asked across your engines on every run. The quality of the list decides the quality of every score downstream.

Prompt properties

Type — the intent behind the question, e.g. COMMERCIAL ("best CRM for startups") vs INFORMATIONAL ("what is a CRM"). Commercial prompts drive pipeline; informational prompts build presence.
Locale — the language/market the prompt is asked in, for multi-market tracking.
Status — active prompts run every scan; inactive prompts keep their history but stop consuming runs.

Screenshot: Tracked Prompts list with type and status columns

Screenshot: Prompt detail page with per-engine results

Best practices

Track 10–30 prompts. Fewer is too noisy to trend; many more dilutes attention and burns run quota.
Mix intents — mostly commercial and comparison prompts, seasoned with informational ones that build category presence.
Deactivate, don't delete. Deactivated prompts keep their history, so you can resume tracking later without losing the trend.