Understanding Issues
How to read Issues KPIs, priorities, and when to Optimize vs Ask Agent.
Understanding Issues
Issues is your prompt library action board: each active prompt becomes an Issue showing which AI search questions deserve priority.
Recommended order
Build prompts → run probes → Refresh estimates → filter Priority → Optimize / Ask Agent → retest
Do not skip prompts and probes—otherwise Health and Priority stay at defaults.
📸 Screenshot needed: issues-full-page
Path: Full Issues page
Save screenshot as public/help/screenshots/issues-full-page.png
| KPI | Meaning | If low |
|---|---|---|
| Diagnostic Score | Overall diagnostic | Run audit + content work |
| Prompt Health | Average prompt health | Improve library quality/coverage |
| Mentions Health | AI mention visibility | Confirm probes ran |
📸 Screenshot needed: issues-kpi-bar
Path: Issues top bar — three Health KPIs
Save screenshot as public/help/screenshots/issues-kpi-bar.png
| Button | Goes to | When to use |
|---|---|---|
| Optimize | Content Optimize / Create | You know the fix |
| Ask Agent | Agent (with prompt_id) | Need diagnosis first |
📸 Screenshot needed: issues-actions
Path: Issues row — Optimize vs Ask Agent
Save screenshot as public/help/screenshots/issues-actions.png
| Priority | Typical signal | Suggestion |
|---|---|---|
| High | Low Volume + Health < 50 | Consider replacing prompt, not forcing content |
| Medium | Medium Volume | Prioritize Optimize / new content |
| Low | High Volume | Long-term coverage; skip this week |
All Health 50—is that normal?
Yes, usually means Refresh estimates not run or insufficient probe data. Ensure ≥ 20 prompts and completed probes, then refresh.
audit vs Issues
- audit: whole-site GEO readiness (technical + content structure).
- Issues: per-prompt performance and priority.
They complement each other; neither replaces the other.