The dashboard isn't the product. The fix is.
Every visibility gap becomes a suggested action with the evidence it came from and the steps to take. Mark it done and the prompt is measured before and after. Automations watch your metrics and open the next one before you ask.
Action queue · 24 openSORTED BY IMPACT
#87Unblock ClaudeBot on /help — robots.txt ruleIMPACT 8.4LOW EFFORT
#91Comparison page: Nike vs Adidas pricingIMPACT 7.9MED EFFORT
#88Refresh stale pricing page cached by GeminiIMPACT 6.2LOW EFFORT
WORKFLOW
When share of voice drops 2pt on any topic → open an action, attach evidence, notify #content in Slack.
● RUNNING01
Scored, not listed
Impact × effort scoring from your own answer data, so the queue starts with what moves the metric.
02
Evidence, not opinion
Each suggestion names the answers it came from, the pages they cited and the robots.txt line in the way — with the steps to take, ready to hand off.
03
Automations & reports
Threshold triggers, Slack routing, and scheduled exec reports that write themselves.
Suggested actionTECHNICALEFFORT S · REACH 1 OF 5
Let Perplexity read northwindrunning.com
Perplexity left Northwind Running out of “best trail running shoes”, and northwindrunning.com/robots.txt blocks PerplexityBot from the whole site.
1In robots.txt, allow PerplexityBot
2Blocking training crawlers doesn't keep you out of answers; blocking search agents can
3Check AI crawlers after the change — robots.txt is read again within 30 minutes
Add to queueIllustrative. Northwind Running is fictional.
Suggested actions
Hand your team the why, not just the what
Every gap opens into its evidence: the sampled answers, the pages they cited, and the robots.txt line that keeps an engine out. Each suggestion states what to do in two or three steps. Save it, mark it done, and the prompt is measured before and after — a change counts once ten answers are in on each side.
→Category, effort and the engines it reaches on every suggestion — no projected gain
→Scheduled exec reports assemble shipped work automatically
"Answr found the robots.txt rule in the first scan. Fifteen minutes of work bought back our whole docs presence."
Head of Web, North American payments provider · more stories
Close the loop on every answer.